armando-migliaccio 0759ed18a9 Allow L3 base to handle extensions on router creation
By changing the boolean flag, API extensions made to
the router model can be handled correctly: this means
that on router creation, the response body will
contain all the extension attributes being part of
the resource. Prior to this fix, it was only on GETs
or PUTs, leaving the user at loss as to whether
the flag was actually being processed.

Closes-bug: #1325608
Supports-blueprint: neutron-ovs-dvr

Change-Id: I6f913c8417676a789177e00f30eb5875e7aaa3ae
2014-06-04 01:27:15 -07:00
2013-11-28 23:18:03 +08:00
2014-05-16 13:40:04 -04:00
2014-05-19 12:16:56 +02: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
2014-05-19 12:16:56 +02: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%