5477faab67
In commit bc45c56f10, the live migration
RPC APIs were changed such that they intentionally wouldn't communicate
with older versions that don't provide the extra parameters that were
added. This breaks people using live migration to move workloads between
icehouse and juno compute nodes during an upgrade. It also generally
runs counter to our policies regarding RPC API compatibility.
The original bug only affected shared block storage users, which means
a large portion of users aren't even affected. Thus, this patch restores
compatibility with the older versions in all cases, but logs weighty
warning messages for the operators when a migration is performed that
looks to be affected by the bug. If we have enough information to
determine that the migration is not affected, we avoid the warning, but
otherwise err on the side of caution. If an operator is not actually
affected by the bug, they will see the warnings while the RPC API
version cap is in place (i.e. during the upgrade window) and then
the warnings will stop once it is removed.
UpgradeImpact: This will resolve upgrade issues from Icehouse->Juno
when using live migration.
DocImpact: Documenting the potential for data loss when migrating from
Icehouse to Juno when using live migration is something operators should
be aware of.
Change-Id: I5651fb7ba95f38e2e2f8a48a98ff04072c6bb885
Closes-Bug: #1402813
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