11e22a435a
Split rpc.callbacks interface into consumer and producer parts. Better terms are chosen for two RPC APIs we have: - pull when a component actively requests a new object state; - push when a component updates anyone interested about an object change. Also, for callback registration, the following terms are used: - subscribe when a component is registered in consumer registry; - provide when a component is registered in provider registry. Covered the registries with some unit tests. Lots of existing tests utilize the registries now, and need to be isolated from other tests that mess with the managers (that are singletons), so introduced a common qos base test class to mock the manager with per-test instance of it). Co-Authored-By: Ihar Hrachyshka <ihrachys@redhat.com> Partially-Implements: blueprint quantum-qos-api Change-Id: I130cfbc8b78da6df4405b90ea1ab47899491ba41
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
-
http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html
- 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.