openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
27,149 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
74e0ba7e65
Go to file
Jeegn Chen 74e0ba7e65 Fix live-migration failure in FC multipath case 
Currently, /dev/dm-<NUM> instead of /dev/mapper/<multipath_id> is
used to access multipath FC volumes by Compute Node and
multipath_id in connection_info is not maintained properly and
may be lost during connection refreshing.

This implementation will make source Compute Node and destination
Compute Node fail to disconnect/connect to volumes properly and
result in live-migration failure.

To fix it, /dev/mapper<multipath_id> will be used instead of
/dev/dm-<NUM> to access multipath devices, just like iSCSI multipath
implementation, and logic to preserve the unique (across Compute
Nodes) multipath_id is also added.

Closes-Bug: #1327497
(cherry picked from commit 3ea14e8a70)

Conflicts:
	nova/storage/linuxscsi.py
	nova/tests/virt/libvirt/test_libvirt_volume.py
	nova/virt/block_device.py
	nova/virt/libvirt/volume.py

This backport commit adjust oslo.i18n usage to oslo-incubator common code,
due to we didn't have oslo.i18n in icehouse.
And remove unused  variable value dev_str in test_libvirt_volume.py,
it should be deleted but not worth a specific commit in stable/icehouse.

Change-Id: I17f15852c098af88afd270084c62eb87693c60d4
2014-09-24 15:39:50 +08:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
doc Revert "Remove broken quota-classes API" 2014-06-10 13:13:25 -07:00
etc/nova Fix rootwrap for non openstack.org iqn's 2014-09-09 15:16:50 -06:00
nova Fix live-migration failure in FC multipath case 2014-09-24 15:39:50 +08:00
plugins/xenserver Merge "Rename Openstack to OpenStack" 2014-03-18 01:17:47 +00:00
tools Re-work how debugger CLI opts are registered 2014-03-25 06:44:50 -04:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore Add nova.conf.sample to gitignore 2014-03-27 11:57:42 -07:00
.gitreview Opening stable/icehouse 2014-04-17 14:41:19 +02:00
.mailmap Update the mailmap 2014-02-15 09:59:26 +08:00
.testr.conf Fix tests to work with mysql+postgres concurrently 2013-10-27 09:46:45 +11:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
CONTRIBUTING.rst Fix the section name in CONTRIBUTING.rst 2014-03-28 12:12:11 +01:00
HACKING.rst Replace assertEqual(None, *) with assertIsNone in tests 2014-02-16 17:31:28 +08: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
openstack-common.conf notifier middleware broken by oslo.messaging 2014-03-04 16:58:50 -05:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
README.rst Update references with new Mailing List location 2013-07-28 11:28:46 -07:00
requirements.txt Block sqlalchemy migrate 0.9.2 as it breaks all of nova 2014-09-13 18:52:21 +00:00
run_tests.sh Fix run_tests.sh lockutils when run with -d 2014-02-10 14:16:13 +01:00
setup.cfg Bump stable/icehouse next version to 2014.1.3 2014-08-08 10:13:56 -04:00
setup.py Updated from global requirements 2013-09-05 11:12:57 -04:00
test-requirements.txt Updated from global requirements 2014-07-24 16:50:27 +00:00
tox.ini Fix live-migration failure in FC multipath case 2014-09-24 15:39:50 +08: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:

http://github.com/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

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://nova.openstack.org/

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

-- End of broadcast