openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
39,367 Commits 9 Branches 84 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Sylvain Bauza c71c4e01b2 Stop providing force_hosts to the scheduler for move ops 
Since now we provide the original RequestSpec for move operations (unshelve,
live-migrate and evacuate), it can also provide the original force_hosts/nodes
to the scheduler.
In that case, it means that if an admin was asking to boot an instance forcing
to an host, a later move operation could then give again the forced value and
then wouldn't permit to get a different destination which is an issue.

TBH, that is not a problem for live-migrate and evacuate that do provide an
optional host value (which bypasses then the scheduler) but since unshelve
is not having this optional value, it would mean that we could only unshelve
an forced instance to the same host.

Change-Id: I03c22ff757d0ee1da9d69fa48cc4bdd036e6b13f
Closes-Bug: #1561357
(cherry picked from commit 446d15568e)
 		2016-03-25 20:35:28 +00:00
api-guide/source fixed typo in word "OpenStack" 2016-03-13 00:31:32 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Enable rebuild tests in cellsv1 job 2016-03-04 19:58:57 +00:00
doc Typo fix in documentation 2016-03-14 15:08:31 -07:00
etc/nova Abort an ongoing live migration 2016-02-26 15:11:41 +00:00
nova Stop providing force_hosts to the scheduler for move ops 2016-03-25 20:35:28 +00:00
plugins/xenserver Merge "plugins/xenserver: Resolve PEP8 issues" 2016-03-10 14:27:09 +00:00
releasenotes stop setting mtu when plugging vhost-user ports 2016-03-22 11:54:12 -04:00
tools Merge "Add a tool for reserving migration placeholders during release time" 2016-02-10 19:48:44 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Merge "Add reno for release notes management" 2015-11-13 16:24:51 +00:00
.gitreview Update .gitreview for stable/mitaka 2016-03-16 19:16:46 +01: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 Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Hacking: check for deprecated os.popen() 2016-02-19 21:55:20 -02:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10: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
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
openstack-common.conf Use imageutils from oslo.utils 2016-02-16 18:34:43 +08:00
requirements.txt Updated from global requirements 2016-03-05 20:48:35 +00:00
run_tests.sh Add description on how to run ./run_test.sh -8 2016-01-11 13:17:04 +00:00
setup.cfg register the config generator default hook with the right name 2016-03-11 16:02:05 -05:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2016-02-08 02:42:24 +00:00
tests-py3.txt XenAPI: introduce unit test for XenAPI plugins 2016-03-02 06:54:06 +00:00
tox.ini Do not use constraints for venv 2016-02-28 19:06:50 +01: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