Hi,
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.
Thanks
Gary
From: Monotosh Das <monotosh@ericsson.com<mailto:monotosh@ericsson.com>>
Reply-To: OpenStack List
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 23, 2016 at 1:52 PM
To: OpenStack List
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Networking-vSphere] - changes in nova compute driver
Hi,
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,
Thanks,
Monotosh
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
