Difference between revisions of "Zone migration"
(→Problem description) |
(→Use Cases) |
||
| Line 4: | Line 4: | ||
== Use Cases == | == 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. | ||
Revision as of 05:47, 25 January 2017
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 each workload, 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.
