Brian Haley
955fa1c075
This patch introduces an API to allocate an externally connected private tenant network on demand. The API is idempotent in that, once the topology is provisioned, further API calls keep returning the same topology to the caller. The API, as introduced by the patch, is not currently on, and its design carefully ensures minimal impact on the existing codebase. In fact the feature depends on and enhances the external-net extension, but it does so via callbacks. A subsequent patch in this series will make it available by default, and API tests will be added to validate the functionality. Partially-implements: blueprint get-me-a-network Co-Authored-By: Armando Migliaccio <armamig@gmail.com> Co-Authored-By: Henry Gessau <HenryG@gessau.net> Change-Id: I4abd45252026431452f0d2cb2805043489c2f6ad
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 git.openstack.org at <http://git.openstack.org/cgit/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
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.