[Openstack] Using VMWare ESXi with openstack

Atul Gosain atul.gosain at gmail.com
Thu Apr 26 02:22:38 UTC 2012


Hi

 Thanks a lot for the responses. I still have some clarifications.
Openstack documentation states (
http://docs.openstack.org/trunk/openstack-compute/admin/content/hypervisor-configuration-basics.html
)
*Hypervisor Configuration Basics*

*The node where the nova-compute service is installed and running is the
machine that runs all the virtual machines, referred to as the compute node
in this guide.*

This gave me an impression that nova-compute service has to be installed on
hypervisor(and not VM).

Though from the links below, it seems that nothing needs to be installed on
ESX server for openstack to manage it, from the documentation (
http://wiki.openstack.org/XenServer/GettingStarted), it seems like this
package needs to be built on Ubuntu and then install on XenServer for it to
be managed by Openstack.

Sorry for my confusion, but couldnt figure out from the documentation.

-------------

Secondly, what i mainly wanted to know was that how does openstack assign
IP addresses to the new VMs it creates. If i see in the API's of individual
hypervisors Xen, HyperV etc doesnt provide any direct method of setting IP
address on the host, though they provide to set the MAC address. Cloudstack
uses an internal DHCP server to set the IP addresses in VM's for the
assigned MAC.

I looked into the openstack code, it seems like the network configuration
is injected into the VM images. Is it true ? As i understand, these images
are stored on Glance server. How are these images installed on hypervisors
by openstack. It does need to have some software running on hypervisors to
which controller can push the image of the VM.

Where does the network information get injected inside the image ? Is it on
the glance server or hypervisor ?


Thanks

Atul

On Wed, Apr 25, 2012 at 8:23 PM, John Garbutt <John.Garbutt at citrix.com>wrote:

> The VMWare and XenServer OpenStack support have very similar
> architectures. Every hypervisor has a VM that runs the nova-compute code.
> You don’t as such install it into the hypervisor. In the case of XenServer,
> there are certainly some plugins that are installed, but nova, at the
> moment, still runs in a VM on top of the hypervisor.****
>
> ** **
>
> I don’t think OpenStack requires vCenter at all.****
>
> ** **
>
> The email linked below looks like what is in the manual (and was
> previously on the wiki). I guess the format of the nova conf should be
> updated, but it looks mostly accurate from what I remember.****
>
> ** **
>
> I hope that helps a little.****
>
> ** **
>
> Thanks,****
>
> John****
>
> ** **
>
> *From:* openstack-bounces+john.garbutt=eu.citrix.com at lists.launchpad.net[mailto:
> openstack-bounces+john.garbutt=eu.citrix.com at lists.launchpad.net] *On
> Behalf Of *Jorge de la Cruz
> *Sent:* 25 April 2012 14:33
> *To:* Atul Gosain
> *Cc:* openstack at lists.launchpad.net
> *Subject:* Re: [Openstack] Using VMWare ESXi with openstack****
>
> ** **
>
> Hi,
> I worked with Cloudstack too, Cloudstack use the vCenter for launch the
> VM's, destroy, etc. That is a good idea but you depend, always, for the
> good funcionality of vCenter.
>
> The Information for Openstack is so short:
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/VMWare_configuration_options.html
>
> But i readed a good message before, this:
> https://lists.launchpad.net/openstack/msg09607.html
>
>
> Cheers****
>
> --
>
> ****
>
> Jorge de la Cruz
> *Cloud Architect*
> *www.stackops.com** | * jorge.delacruz at stackops.com<http://login.jsp?at=a467f3be-21c0-4b31-9a1c-beee62395a4e&mailto=jorge.delacruz@stackops.com>| +34
> 91 309 48 77 | skype:jorge.delacruz.stackops*
> * <http://www.stackops.com/>****
>
> *[image: Image removed by sender.]***
>
> ******************** ADVERTENCIA LEGAL ********************
> Le informamos, como destinatario de este mensaje, que el correo
> electrónico y las comunicaciones por medio de Internet no permiten asegurar
> ni garantizar la confidencialidad de los mensajes transmitidos, así como
> tampoco su integridad o su correcta recepción, por lo que STACKOPS
> TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
> Si no consintiese en la utilización del correo electrónico o de las
> comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
> conocimiento de manera inmediata. Este mensaje va dirigido, de manera
> exclusiva, a su destinatario y contiene información confidencial y sujeta
> al secreto profesional, cuya divulgación no está permitida por la ley. En
> caso de haber recibido este mensaje por error, le rogamos que, de forma
> inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
> atención y proceda a su eliminación, así como a la de cualquier documento
> adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
> utilización de este mensaje, o de cualquier documento adjunto al mismo,
> cualquiera que fuera su finalidad, están prohibidas por la ley.
>
> ***************** PRIVILEGED AND CONFIDENTIAL ****************
> We hereby inform you, as addressee of this message, that e-mail and
> Internet do not guarantee the confidentiality, nor the completeness or
> proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
> does not assume any liability for those circumstances. Should you not agree
> to the use of e-mail or to communications via Internet, you are kindly
> requested to notify us immediately. This message is intended exclusively
> for the person to whom it is addressed and contains privileged and
> confidential information protected from disclosure by law. If you are not
> the addressee indicated in this message, you should immediately delete it
> and any attachments and notify the sender by reply e-mail. In such case,
> you are hereby notified that any dissemination, distribution, copying or
> use of this message or any attachments, for any purpose, is strictly
> prohibited by law.****
>
> ** **
> ------------------------------
>
> *De: *"Atul Gosain" <atul.gosain at gmail.com>
> *Para: *openstack at lists.launchpad.net
> *Enviados: *Miércoles, 25 de Abril 2012 15:18:35
> *Asunto: *[Openstack] Using VMWare ESXi with openstack
>
> Hi ****
>
> ** **
>
>  I tried to see how we can control any existing infrastructure of
> VMWare/XenServer etc from openstack. ****
>
> What i understood is that nova compute needs to be installed on the
> hypervisors(compute hosts) which can be Ubuntu Servers for KVM etc. ****
>
> Also for XenServer, we can build a package on Ubuntu and then will have to
> install on XenServer so that it can be controlled by cloud controller. ***
> *
>
> ** **
>
> Basically openstack compute should be installed on hypervisor and accepts
> the instructions from controller to create VM's, assign IP addresses,
> destroy, attaching volumes etc. ****
>
> Please confirm this understanding. ****
>
> ** **
>
> Based on this, i did not find anything on VMWare ESXi. How does the
> compute gets installed on ESXi server ?****
>
> ** **
>
> Also, i have seen cloudstack working which seems to be little different
> than how openstack works. Cloudstack can control existing
> VMWare/XenServer/KVM etc using their respective API's. ****
>
> It doesnt require any installation on the hypervisor itself. If my
> understanding is correct, then this seems to be a better model.****
>
> What is the reason that openstack cannot operate the hypervisors without
> installing compute on them ? ****
>
> ** **
>
> Thanks****
>
> Atul****
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120426/493ef0db/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/x-citrix-jpeg
Size: 823 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120426/493ef0db/attachment.bin>


More information about the Openstack mailing list