e5f635ee4f
Cloud deployed at scale most likely will use these scheduler drivers because they allow a fairer resource allocation compared to chance schedulers (which randomly place resources on the hosts). Because of their importance, it's only wise to test them in the gate on a continuous basis, so that we do not get surprised by accidental regressions. Rather than pushing this down through devstack-gate/project-config patches, this chance alters the default of the scheduler drivers, so that users can also pick these up out of the box. This means that after an upgrade they would observe a change in the scheduling behavior, if they relied on the default config. DocImpact UpgradeImpact Closes-bug: #1494667 Change-Id: I5927914cb88eff66bc7a045340ff68cb8da95ad6
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.