[openstack-dev] [Networking-vSphere] - changes in nova compute driver
gkotton at vmware.com
Wed Feb 24 15:12:41 UTC 2016
I suggest that the guys who maintain this driver provide you the reasons why they maintain the Nova driver like this It is problematic and at times the driver can break as it is not in tree.
From: Monotosh Das <monotosh.das at ericsson.com<mailto:monotosh.das at ericsson.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, February 23, 2016 at 1:52 PM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Networking-vSphere] - changes in nova compute driver
In Networking-vSphere (ovsvapp), 'vsphere' is used as nova compute driver. I want to know if there is any modification in the default vsphere driver that is specific to ovsvapp. If yes, can you give an idea about the changes ?
If not, then how does vsphere driver get to know port group creation is complete, as mentioned in the wiki (https://wiki.openstack.org/wiki/Neutron/Networking-vSphere) ? In the code (nova/virt/vmwareapi/vmops.py : spawn() ), it appears that VM is created first, then neutron is updated about the nic, and then VM is powered on. It doesn't wait for any event before powering on the VM.
Some clarification about this will be very helpful,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev