24ff74fec9
Currently, Nova premises a situation which iSCSI target is not changed before and after live migration. Therefore, if destination node has different iSCSI target, the live migration fails in current Nova's specification. However, if each compute node uses same iSCSI target, each compute node recognizes all volumes in the iSCSI target and this is undesirable situation from the view point of security. Therefore, this spec proposes to support live migration of instances with Cinder volumes among compute nodes that need to log into different iSCSI targets to access the volumes. For your reference, if iSCSI storages have features to manage visibility of LUNs for each initiator within one iSCSI target, using same iSCSI target for each compute node is not a problem. But general iSCSI storages don't have such kind features, therefore they need this feature to support live migration. Change-Id: I9f0212cb74804e0122200ff543c46f1a91a39921 Blueprint iscsi-live-migration-different-target
README
OpenStack Nova Specifications
This git repository is used to hold approved design specifications for additions to the Nova project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The layout of this repository is:
specs/<release>/Where there are two sub-directories:
specs/<release>/approved: specifications approved but not yet implemented specs/<release>/implemented: implemented specifications
This directory structure allows you to see what we thought about
doing, decided to do, and actually got done. Users interested in
functionality in a given release should only refer to the
implemented directory.
You can find an example spec in specs/template.rst.
Specifications are proposed for a given release by adding them to the
specs/<release> directory and posting it for review.
The implementation status of a blueprint for a given release can be
found by looking at the blueprint in launchpad. Not all approved
blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see https://wiki.openstack.org/wiki/Blueprints
For more information about working with gerrit, see https://wiki.openstack.org/wiki/Gerrit_Workflow
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
$ toxAfter running tox, the documentation will be available
for viewing in HTML format in the doc/build/ directory.