76df5b1dc1
bug #1042028 Allows user to invoke L3-agent in a way that limits the agent to implementing only routers associated with a particular external network. Thus, it is possible to have a deployment with multiple external networks, since you can run one agent per external network. Also makes l3-agent pay attention to router admin_state_up field. Change-Id: Ia79d29301530718bc381c8e5a9d197de9452bce2
# -- Welcome! You have come across a cloud computing network fabric controller. It has identified itself as "Quantum." It aims to tame your (cloud) networking! # -- External Resources: The homepage for Quantum is: http://launchpad.net/quantum . Use this site for downloading the latest code, asking for help, and filing bugs. The latest and most in-depth documentation on how to use Quantum is available at: http://docs.openstack.org . This includes: Quantum Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/ Quantum API Reference: http://wiki.openstack.org/Quantum/APIv2-specification/ The start of some developer documentation is available at: http://wiki.openstack.org/QuantumDevelopment For help using or hacking on Quantum, you can send mail to openstack-dev@lists.openstack.org .