<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://archives.opennebula.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://archives.opennebula.org/feed.php">
        <title>OpenNebula - Flexible Enterprise Cloud Made Simple documentation:archives:rel1.2</title>
        <description></description>
        <link>http://archives.opennebula.org/</link>
        <image rdf:resource="http://archives.opennebula.org/lib/tpl/mmKanso/images/favicon.ico" />
       <dc:date>2026-09-13T13:38:58+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:api?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:api_examples?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:architecture?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:cg?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:cli?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:ec2g?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:howto_net?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:howto_vnet?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:ignc?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:img?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:kvmg?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:nm?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:qg?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:sm?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:ug?rev=1389095273&amp;do=diff"/>
                <rdf:li rdf:resource="http://archives.opennebula.org/documentation:archives:rel1.2:xeng?rev=1389095273&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://archives.opennebula.org/lib/tpl/mmKanso/images/favicon.ico">
        <title>OpenNebula - Flexible Enterprise Cloud Made Simple</title>
        <link>http://archives.opennebula.org/</link>
        <url>http://archives.opennebula.org/lib/tpl/mmKanso/images/favicon.ico</url>
    </image>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:api?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:api</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:api?rev=1389095273&amp;do=diff</link>
        <description>This documentation provides a description of the xmlrpc methods exposed by OpenNebula. The methods consist of the name of the method that will be invoked, input values needed to the execution and results of execution as outputs.

* * this parameter functionality is not fully implemented so dummy values must be used.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:api_examples?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:api_examples</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:api_examples?rev=1389095273&amp;do=diff</link>
        <description>Here are some examples of several implementations of xml-rpc clients to invoke OpenNebula to execute a Submit action (one.vmallocate), which submits the template with the description of a VM.

C++ Example

This sample submits a string containing a definition of a virtual machine (template) and gets the resulting vid, for more information on XML-RPC go to</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:architecture?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:architecture</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:architecture?rev=1389095273&amp;do=diff</link>
        <description>The OpenNebula internal architecture can be divided into three layers:

	*  Tools, management tools developed using the interface provided by the OpenNebula Core.
	*  Core, the main virtual machine, virtual network and host management components.
	*</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:cg?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:cg</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:cg?rev=1389095273&amp;do=diff</link>
        <description>Cluster Configuration

This section describes the basic configuration of the main subsystems of a typical cluster architecture: users, storage and networking. Also in this section you can find some hints and pointers to make the supported virtualizers work with OpenNebula.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:cli?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:cli</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:cli?rev=1389095273&amp;do=diff</link>
        <description>Command Line Interface

OpenNebula provides three commands to interact with the system:

	*  onevm: to submit, control and monitor virtual machines
	*  onehost: to add, delete and monitor hosts
	*  onevnet: to add, delete and monitor virtual networks</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:ec2g?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:ec2g</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:ec2g?rev=1389095273&amp;do=diff</link>
        <description>You should take into account the following technical considerations when using the EC2 cloud with OpenNebula:

	*  There is no direct access to the dom0, so it cannot be monitored (we don&#039;t know where the VM is running on the EC2 cloud).

	*  Since EC2 is beta, you can launch simultaneously at much 20 instances. Although you can request a higher number to Amazon.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:howto_net?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:howto_net</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:howto_net?rev=1389095273&amp;do=diff</link>
        <description>This tutorial shows how to contextualize networking parameters in a virtual machine using standard networking tools. This approach can be followed if all your virtual machines can be placed in the same broadcasting domain.

Requirements

System

	*</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:howto_vnet?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:howto_vnet</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:howto_vnet?rev=1389095273&amp;do=diff</link>
        <description>Since release 1.2 OpenNebula has the ability to automatically assign MAC and IP addresses to new deployed Virtual Machines. What is needed now is to make running VM&#039;s aware of its network configuration. One way to do this is to use DHCP (described in</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:ignc?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:ignc</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:ignc?rev=1389095273&amp;do=diff</link>
        <description>OpenNebula assumes a typical cluster configuration, with a cluster front-end that will act as the OpenNebula server and cluster nodes, where Virtual Machines will be executed. There is at least one physical network joining all the cluster nodes with the front-end. Additionally, folders can be shared through</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:img?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:img</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:img?rev=1389095273&amp;do=diff</link>
        <description>The Information Manager (IM) is in charge of monitoring the cluster nodes. It comes with various sensors, each one responsible of a different aspects of the computer to be monitored (CPU, memory, hostname...). Also, there are sensors prepared to gather information from different hypervisors (currently KVM and XEN).</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:kvmg?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:kvmg</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:kvmg?rev=1389095273&amp;do=diff</link>
        <description>KVM (Kernel-based Virtual Machine) is a complete virtualization technique for Linux. It offers full virtualization, where each Virtual Machine interacts with its own virtualized hardware. This guide describes the use of the KVM virtualizer with OpenNebula, please refer to KVM specific documentation for further information on the setup of the KVM hypervisor itself.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:nm?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:nm</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:nm?rev=1389095273&amp;do=diff</link>
        <description>The physical hosts that will conform the fabric of our virtual infrastructures will need to have some constraints in order to be able to deliver virtual networks effectively to our virtual machines. Therefore, we can define our physical cluster under the point of view of networking as a set of hosts with one or more network interfaces, each of them connected to a different physical network.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:qg?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:qg</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:qg?rev=1389095273&amp;do=diff</link>
        <description>This QuickStart guide aims to show how to prepare a simple cluster consisting of one cluster front-end and two cluster nodes to install OpenNebula, and how to configure OpenNebula to manage VMs in the aforementioned cluster. As seen in the following picture, the front-end machine is where OpenNebula is installed. OpenNebula supports XEN and KVM hypervisors (and it can interface with Amazon&#039;s EC2) on the hosts to manage the VM lifecycle across them. This QuickStart guide focuses on the XEN hyperv…</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:sm?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:sm</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:sm?rev=1389095273&amp;do=diff</link>
        <description>One key aspect of virtualization management is the process of dealing with Virtual Machines images. Allegedly, there are a number of possibly different configurations depending on the user needs. For example, the user may want all her images placed on a separate repository with only http access. Or images can be shared through NFS between all the hosts. OpenNebula aims to be flexible enough to support as many different image storage configurations as possible.</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:ug?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:ug</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:ug?rev=1389095273&amp;do=diff</link>
        <description>OpenNebula is a VM manager that is executed and configured by a cluster administrator. This cluster administrator would be also the ONE administrator, and therefore he should be the holder of the &lt;oneadmin&gt; account. This guide assumes that the cluster administrator is the only user for</description>
    </item>
    <item rdf:about="http://archives.opennebula.org/documentation:archives:rel1.2:xeng?rev=1389095273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-07T11:47:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:archives:rel1.2:xeng</title>
        <link>http://archives.opennebula.org/documentation:archives:rel1.2:xeng?rev=1389095273&amp;do=diff</link>
        <description>The  XEN hypervisor offers a powerful, efficient and secure feature set for virtualization of x86, IA64, PowerPC and other CPU architectures. It delivers both paravirtualization and full virtualization. This guide describes the use of Xen with OpenNebula, please refer to the Xen specific documentation for further information on the setup of the Xen hypervisor itself.</description>
    </item>
</rdf:RDF>
