> I pinged Anne Gentle about the docs missing this (apparently
> core) API server action and she will be working to get this added to the
> current docs -- especially since novaclient already has support for it...
Good good.
> The more I think about it, I believe a single migration API would be simplest,
> with the ability to specify options for the migration.
> Something like:
>
> POST /servers/<SERVER_ID>/action
>
> {
> 'action': 'migrate',
> 'migrate_options':
> {
> 'live': true,
> 'no_live_fallback': true,
> 'migrate_disks':
> {
> <DISK_UUID1>, ...
> }
> }
> }
>
> With the options being fairly self-explanatory other than the
> 'no_live_fallback': true being used to indicate the caller wishes to fallback
> on a stop/move/start migration if shared disk (or a hypervisor restriction or
> non-matching CPU restriction) prohibits the "live" migration.
+1
This is exactly what I was attempting to propose in the blueprint Renuka was
planning to write and work on.
Cheers,
John
--
Mailing list: https://launchpad.net/~openstack-qa-team
Post to : openstack-qa-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help : https://help.launchpad.net/ListHelp
