Public bug reported:

The vmware-nsx repo has a number of different plugins. The DVS plugin enables 
one to be able to use Neutron with a number of limitation (no security groups 
and no layer 3 support). If one wants to achieve this with the DVS plugin then 
there are many different examples that they can use - for example 
https://github.com/openstack/networking-vsphere/blob/master/networking_vsphere/drivers/dvs_driver.py
 (that requires the ML2 plugin).
In the vmware-nsx dvs case there are no agents running. A instance is unable to 
get a DHCP address as we are unable to plugin the DHCP agent to the OVS. This 
cannot be done as the DeviceManager is hard coded and we need to make use of 
the network information to get the VLAN tag.
Enabling the plu and unplug opertaions for the DHCP agent to be overriden will 
enable the plugin to expose this and for people a chance to get neutron up and 
running in an existing vsphere env.

** Affects: neutron
     Importance: Undecided
     Assignee: Gary Kotton (garyk)
         Status: In Progress


** Tags: rfe

** Changed in: neutron
    Milestone: None => newton-rc1

** Tags added: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1621043

Title:
  VMware-NSX: unable to get a DHCP address when using the simple-dvs
  plugin

Status in neutron:
  In Progress

Bug description:
  The vmware-nsx repo has a number of different plugins. The DVS plugin enables 
one to be able to use Neutron with a number of limitation (no security groups 
and no layer 3 support). If one wants to achieve this with the DVS plugin then 
there are many different examples that they can use - for example 
https://github.com/openstack/networking-vsphere/blob/master/networking_vsphere/drivers/dvs_driver.py
 (that requires the ML2 plugin).
  In the vmware-nsx dvs case there are no agents running. A instance is unable 
to get a DHCP address as we are unable to plugin the DHCP agent to the OVS. 
This cannot be done as the DeviceManager is hard coded and we need to make use 
of the network information to get the VLAN tag.
  Enabling the plu and unplug opertaions for the DHCP agent to be overriden 
will enable the plugin to expose this and for people a chance to get neutron up 
and running in an existing vsphere env.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1621043/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to