[one-users] Some basic questions after a firts OpenNebula 2.0 install

[Carlos Martín Sánchez]

On 3 December 2010 17:54, <jean-paul.pigache at bull.net> wrote:

>
> Hi OpenNebula.
>
>
Hi Jean-Paul,


> This is my first mail on this list. So it contains some basic questions we
> have after making a first install of OpenNebula 2.0.
>
> First of all: the context:
> We have installed OpenNebula 2.0, compiled from downloaded source files.
>
> All the mandatory librairies are there but we have got some errors because
> OpenNebula requires a precise librairy version (ex:  libcrypto.so.6 when
> we have libcrypto.so.10 in Fedora14).
>
> Anyway, we have succeeded to install a front end and a clusternode, both on
> Fedora12.
>
> We had to do everything using command lines. The configuration of the Vms
> and the network must be done manually in text files. Is this the normal way
> ?
>
Yes, OpenNebula uses simple, human-readable templates to make it both user
and script friendly as possible.

>  To get a graphical interface, do you suggest us to try *Management
> Console* from Sara ?
>
You may want to ask about it in the ecosystem mailing list [1], but as far
as I know the Management Console [2] is only compatible with OpenNebula 1.4.
The EC2 Query API tools [3] are a user-oriented alternative, you can give it
a try and check if it suits you needs.

 The creation of images (of OS) must be done through an external tool (like
> virt-manager). Is this correct ?
>
The actual virtualization will be performed by the hypervisor of your
choice, so you can use any available tool for it.
But it is not mandatory, you can create them using only OpenNebula (creating
blank images, where you will install the OS form a cd-rom iso).

>  OpenNebula manages the Vms but not the OS images. Is this correct ?
>
This was true for 1.4, but in OpenNebula 2.0 the Image repository [4] was
introduced; and now you can let OpenNebula manage your image files.

> To manage IP addresses in the VMs, we need to use the contextualization
> mecanism. Is this correct ?
>
That's the preferred way, yes. As a reminder, the contextualization guide is
documented in [5].
There was an interesting thread some weeks ago about using DHCP instead, you
can check it in the list archives [6].

If we want to interface with a Vmware cloud, we need to use the Wmware
> drivers from C12G labs.
>
That's right. Links: usage guide [7] and addon download [8].

> If we want to interface with another OpenNebula Cloud, we need to use the
> Libcloud Driver or the Deltacloud Driver from cisa-research.org.
>
We plan to release in the mid-term a federation toolkit specifically
designed for OpenNebula, that will offer better integration than the
components you mention.
You may be also interested in the EC2 driver [9] to outsource VMs to Amazon.

>  Thank you for any answer or confirmation for these basic questions.
>
> Jean-Paul Pigache
> Bull SAS.
>
> Regards,
Carlos

[1] http://opennebula.org/community:mailinglists
[2] http://opennebula.org/software:ecosystem:management_console
[3] http://opennebula.org/documentation:rel2.0:ec2qec
[4] http://opennebula.org/documentation:rel2.0:img_guide
[5]
http://opennebula.org/documentation:rel2.0:cong#using_virtual_network_leases_within_a_virtual_machine
[6]
http://lists.opennebula.org/pipermail/users-opennebula.org/2010-November/003349.html
[7] http://opennebula.org/documentation:rel2.0:evmwareg
[8] http://opennebula.org/software:addons:vmware
[9] http://opennebula.org/documentation:rel2.0:ec2g

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org <http://www.opennebula.org/>

>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20101210/f68b2365/attachment-0002.htm>