b30f876885
Moving validation logic from Cisco service driver, into a validation subclass, so that it'll be applied during the persistence phase (so validation failures can block the persistence, instead of setting to error state). This is part of the effort to separate out L3 validation and builds upon the reference implementation changes being reviewed in 102351. Note: One unit test is commented out, due to a bug in oslo.messaging 1.3.0. It will be uncommented later, once 1.4.0.0.a3 or newer is available for use. Change-Id: I6040e6d8ab32b707bcf67a0882507b7ee2d4bebe Partial-Implementation: blueprint l3-svcs-vendor-validation
# -- 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>.