1. Feature Overview: Heat schema organization to facilitate Live migration a) Name of feature: INTEL OSP 10 FEAT HEAT SCHEMA for LIVE MIGRATION b) Feature Description: organize schema migrations scripts into "expand" and "contract" phases that are also linked to major release versions in a backwards compatible way. 2. Feature Details: a) Architectures: 64-bit Intel E Power System/390 b) Bugzilla Dependencies: c) Drivers or hardware dependencies: d) Upstream acceptance information: Current status and Any links to specification; upstream acceptance, and/or blueprint e) External links: f) Severity (H,M,L): H High (required for Hardware Enablement) Medium Low g) Feature Needed by: 3. Business Justification: Enterprise Readiness Feature a) Why is this feature needed? b) What hardware does this enable? c) Is this hardware on-board in a system (eg, LOM) or an add-on card? d) Business impact? e) Other business drivers: 4. Primary contact at Red Hat, email, phone (chat) Only if you have one Phone Number 5. Primary contact at Partner, email, phone (chat) Grzegorz.Grasza
Forgot to add link: https://bugs.launchpad.net/heat/+bug/1505974
A unit test to verify this policy is adhered to merged upstream in Mitaka, so it should be guaranteed in OSP9 (although this has been the policy upstream for some time).
The unit test is there for several months now and seems to be testing well the implementation of the migration "ban". Its verified enough to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1597.html