OpenStack Compute (Nova)
Go to file
Sylvain Bauza 459ca56de2 Check server group policy on migrate/evacuate
This patch changes server group checking in the instance group setup.
Previously, it checked for the presence of the 'group' scheduler hint
as an indication that the instance was a member of a group.  However,
that hint is only present on initial boot.  It is not present when the
scheduler is being used to pick a destination for a migration or
evactuate.

The updated logic checks the database to see if the instance is a
member of a group.  For performance reasons, it only does this is
server group functionality is enabled in the scheduler (group filters
are enabled).

This change makes it so server group policy enforcement will still
occur for migrations and evactuations, instead of only on first boot.

It also adds the call to setup_instance_group in evacuate, resize,
cold migrate and live migrate methods because now it is possible to
access the group setup.

Implements blueprint anti-affinity-on-migration

Closes-bug: #1379451

Change-Id: I6e9ea6ba69e8658fa5126a3488ee12cf2437460c
2014-11-26 11:14:19 +01:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
doc Merge "Add 'instance-usage-audit-log' plugin for V2.1" 2014-11-17 03:40:14 +00:00
etc/nova Add 'instance-usage-audit-log' plugin for V2.1 2014-11-13 14:38:25 +09:00
nova Check server group policy on migrate/evacuate 2014-11-26 11:14:19 +01:00
plugins/xenserver xenapi plugins must target only Python 2.4 features 2014-11-10 07:29:03 -08:00
tools remove use of explicit lockutils invocation in tests 2014-10-29 14:22:45 -04:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore Remove duplicate entry from .gitignore file 2014-09-29 19:21:02 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add tox -e functional 2014-11-12 15:31:06 -05:00
CONTRIBUTING.rst Fix the section name in CONTRIBUTING.rst 2014-03-28 12:12:11 +01:00
HACKING.rst Remove use of unicode on exceptions 2014-10-22 18:05:48 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Switch Nova to use oslo.concurrency 2014-10-30 00:19:14 +00:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
requirements.txt Use oslo.middleware 2014-10-30 18:27:20 -04:00
run_tests.sh move all tests to nova/tests/unit 2014-11-12 15:31:08 -05:00
setup.cfg Add 'instance-usage-audit-log' plugin for V2.1 2014-11-13 14:38:25 +09:00
setup.py Updated from global requirements 2014-04-30 02:43:45 +00:00
test-requirements.txt Updated from global requirements 2014-11-13 22:32:42 +00:00
tox.ini move all tests to nova/tests/unit 2014-11-12 15:31:08 -05:00

README.rst

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:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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:

http://bugs.launchpad.net/nova

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:

https://git.openstack.org/cgit/openstack/nova

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:

http://docs.openstack.org/developer/nova/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast