Difference between revisions of "Zone migration"
(→Proposed change) |
|||
| Line 15: | Line 15: | ||
== Proposed change == | == Proposed change == | ||
| − | OpenStack Watcher plugin "Zone migration" is being developed | + | CLI application includes OpenStack Watcher plugin "Zone migration" is being developed. |
<big>TODO</big>: write in detail | <big>TODO</big>: write in detail | ||
| − | |||
== Dependencies == | == Dependencies == | ||
Revision as of 09:36, 26 January 2017
This page explains "Zone migration" which is automatically migrate VMs and volumes for scheduled maintenance.
Problem description
There are thousands of physical servers and storage running various kinds of workloads in the Cloud system. Administrator have to migrate instances and block storage for tenants for hardware maintenance once a quarter or so. It requires operators manually to watch workloads, choose instances to migrate and migrate for each instances and block storage for efficiently, with minimum downtime. It is a hard task.
Use Cases
As administrator, I want watcher to propose which instances or block storages should be migrated, and migrate destination(physical server, storage system) based on fresh data model.
As administrator, I want watcher to migrate proposed instances or block storages automatically.
As administrator, I want to know percentage of migrated resources I have to do.
Proposed change
CLI application includes OpenStack Watcher plugin "Zone migration" is being developed.
TODO: write in detail
Dependencies
OpenStack Watcher
References
None
