XenServerMigrations
Summary
Release Note
We need the ability to move XenServer instances from one host in a zone to another host within the same zone. This provides a substantial amount of useful functionality, such as the ability to replace a dying or obsolete host with newer hardware by evacuating instances from it. Migrations are also the base dependency for functional resizes.
Rationale
As above, the ability to evacuate a host for any physical reason is highly desirable.
User stories
As operations, I want to be able to evacuate a host with failing hardware so that I can replace the box with minimal impact to customers As a user, I want to be able to migrate my instance so that I can move to faster and/or newer hardware
Assumptions
The ability to snapshot a running XenServer instance already exists
Design
You can have subsections that better describe specific parts of the issue.
Implementation
Code Changes
The Openstack API will modify the "action" endpoint to expose "resize" functionality, which is simply a migration with a larger RAM and disk quota.
Migration
Functionality already exists within the Openstack API, but returns HTTP 501 at this time. Afterwards, existing API clients should be able to successfully migrate through the "resize" functionality present in the API. Additionally, functionality will be exposed through the Admin API for migration without resizing the instance.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
