597c46fde1
Server groups can be used to control the affinity and anti-affinity scheduling policy for a group of servers (instances). Whilst this is a useful mechanism for users such scheduling decisions need to be balanced by a deployers requirements to make effective use of the available capacity. This change adds quota values to constrain the number and size of server groups a user can create. Two new quota values are be introduced to limit the number of server groups and the number of servers in a server group. These will follow the existing pattern for quotas in that: * They are defined by config values, which also include the default value * They can be defined per project or per user within a project * A value of -1 for either quota will be treated as unlimited * Defaults can be set via the quota groups API * Values may be changed at any time but will only take effect at the next server group or server create. Reducing the quota will not affect any existing groups, but new servers will not be allowed into group that have become over quota. This is part one of a linked sequences of changes that implement the new quotas - split to make the reviews easier. This part adds the definition of the new quota values, but leaves the V2 API unchanged. The V2.1 API is updated as it shows all quota values. The second part adds the new V2 API extension to make the new quota values visible and changeable. At this point a Tempest change is required to get a clean run as it checks for a specific set of values. The third part implements the quota checks themselves. Thanks to Cyril Roelandt for supplying some of the unit tests. Co-authored-by: Cyril Roelandt <cyril.roelandt@enovance.com> Implements: blueprint server-group-quotas DocImpact Change-Id: Ib281e43eabfbd176454bde7f0622d46fb04fcb79
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast