armando-migliaccio c62d5ed0ba NSX: ensure that no LSN is created on external networks
Logical Service Nodes (LSN) are those that provide dhcp
and metadata services to networks when the NSX plugin is
used without the openstack dhcp and metadata proxy
agents. External networks do not work with Neutron's
dhcp and metadata services, therefore there is no need
to provision a LSN in this case.

Added UT to avoid regression.

Closes-bug: #1316795

Change-Id: I3dab0c9cbecdd9296466c991d02d590d6bd5bd49
2014-05-07 08:10:30 -07:00
2013-11-28 23:18:03 +08:00
2014-02-10 15:48:48 +09:00
2013-07-06 15:02:43 -04:00
2013-11-11 10:32:34 -08:00
2013-07-06 15:02:43 -04:00
2013-07-06 15:02:43 -04:00
2014-04-30 02:41:29 +00:00
2014-02-26 11:03:46 -05:00

# -- Welcome!

You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!

# -- External Resources:

The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.

The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:

Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/

Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/

The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment

For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.

Description
A set of Neutron drivers for the VMware NSX.
Readme 97 MiB
Languages
Python 98.5%
Shell 1.5%