Add a migration type global hypervisor parameter
Since migration live/non-live is more stable (e.g.) for Xen-PVM versus Xen-HVM, we introduce a new parameter for what mode we should use by default (if not overridden by the user, in the opcode). The meaning of the opcode 'live' field changes from boolean to either None (use the hypervisor default), or one of the allowed migration string constants. The live parameter of the TLMigrateInstance is still a boolean, computed from the opcode field (which is no longer passed to the TL). Signed-off-by:Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
Showing
- lib/cli.py 7 additions, 0 deletionslib/cli.py
- lib/cmdlib.py 17 additions, 6 deletionslib/cmdlib.py
- lib/constants.py 11 additions, 0 deletionslib/constants.py
- lib/hypervisor/hv_base.py 5 additions, 0 deletionslib/hypervisor/hv_base.py
- lib/hypervisor/hv_kvm.py 1 addition, 0 deletionslib/hypervisor/hv_kvm.py
- lib/hypervisor/hv_xen.py 2 additions, 0 deletionslib/hypervisor/hv_xen.py
- man/gnt-instance.sgml 16 additions, 9 deletionsman/gnt-instance.sgml
- man/gnt-node.sgml 4 additions, 2 deletionsman/gnt-node.sgml
- scripts/gnt-instance 12 additions, 2 deletionsscripts/gnt-instance
- scripts/gnt-node 11 additions, 2 deletionsscripts/gnt-node
Loading
Please register or sign in to comment