Jump to: navigation, search

Difference between revisions of "Zone migration"

m (Proposed change)
(Why Zone migration?)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page explains "Zone migration" which is automatically migrate VMs and volumes for scheduled maintenance.
+
==Mission==
  
== Problem description==
+
Zone migration is the tool to migrate VMs and volumes for scheduled maintenance efficiently, automatically, and with minimum downtime.
  
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.
+
=== Why Zone migration?===
  
=== Use Cases ===
+
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 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.
  
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.
+
== Use Cases ==
  
As administrator, I want watcher to migrate proposed instances or block storages automatically.
+
As administrator, I want zone migration to propose the best instances or block storage should be migrated, and migrate destination(physical server, storage) based on fresh data model.
 +
 
 +
As administrator, I want zone migration to migrate proposed instances or block storage automatically.
  
 
As administrator, I want to know percentage of migrated resources I have to do.
 
As administrator, I want to know percentage of migrated resources I have to do.
  
== Proposed change ==
+
==Architecture==
 +
 
 +
Zone migration is composed of UI and  [http://docs.openstack.org/developer/watcher/dev/plugin/base-setup.html OpenStack Watcher plugin] we created. OpenStack Watcher plugin is main part. UI is for monitoring and reporting.
 +
 
 +
==Plan==
  
CLI application includes OpenStack Watcher plugin "Zone migration" is being developed.
+
Zone migration is under development, will be released in April 2017 as PoC.
  
<big>TODO</big>: write in detail
+
We want zone migration to contribute to OpenStack foundation in the future.
<big>TODO</big>: Define the storage-related requirements the Watcher data model should provide
 
  
== Dependencies ==
+
==Documentation==
  
OpenStack Watcher
+
Internal as of now
  
== References ==
+
==Source code==
  
None
+
Internal as of now

Latest revision as of 02:41, 23 February 2017

Mission

Zone migration is the tool to migrate VMs and volumes for scheduled maintenance efficiently, automatically, and with minimum downtime.

Why Zone migration?

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 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 zone migration to propose the best instances or block storage should be migrated, and migrate destination(physical server, storage) based on fresh data model.

As administrator, I want zone migration to migrate proposed instances or block storage automatically.

As administrator, I want to know percentage of migrated resources I have to do.

Architecture

Zone migration is composed of UI and OpenStack Watcher plugin we created. OpenStack Watcher plugin is main part. UI is for monitoring and reporting.

Plan

Zone migration is under development, will be released in April 2017 as PoC.

We want zone migration to contribute to OpenStack foundation in the future.

Documentation

Internal as of now

Source code

Internal as of now