Jump to: navigation, search

Difference between revisions of "Manila/usecases"

(Created page with "=== Use Cases (DRAFT) === === 1) Share existing to Nova instances === Coordinate and provide shared access to previously (externally) established share / export === 2) Create...")
 
(Adapt use cases to ML discussion)
 
Line 1: Line 1:
=== Use Cases (DRAFT) ===
+
= Use Cases =
  
=== 1) Share existing to Nova instances ===
+
== 1.) Create a share and use it in a tenant ==
Coordinate and provide shared access to previously (externally) established share / export
+
Initial creation of a shared storage volume and assign it to several VM’s
=== 2) Create and share to Nova instances ===
+
== 2.) External consumption of a share ==
Create a new commonly accessible (across a defined set of instances) share / export
+
Accommodate and provide mechanisms for last-mile consumption of shares by
=== 3) Bare-metal / non-virtualized consumption ===
+
consumers of the service that aren't mediated by Nova.
Accommodate and provide mechanisms for last-mile consumption of shares by consumers of the service that aren't mediated by Nova.
+
== 3.) Detach a share and don’t destroy data (deactivate) ==
=== 4) Cross-tenant sharing ===
+
Share is flagged as inactive and data are not destroyed for later
Coordinate shares across tenants
+
usage or in case of legal requirements.
=== 5) Import pre-existing shares ===
+
== 4.) Unassign and delete data of a share ==
Wrap Manila around pre-existing shares / exports so that they can be provisioned.
+
Destroy entire share with all data and free space for further usage.
 +
 
 +
 
 +
= Wish list =
 +
 
 +
== 1.) Assign a preexisting share to a VM with Manila ==
 +
Import an existing share with data and assign it to a tenant. E.g. migrating an existing production storage to OpenStack.
 +
== 2.) Resize Share ==
 +
Resize existing and assigned share on the fly.

Latest revision as of 08:17, 5 December 2014

Use Cases

1.) Create a share and use it in a tenant

Initial creation of a shared storage volume and assign it to several VM’s

2.) External consumption of a share

Accommodate and provide mechanisms for last-mile consumption of shares by consumers of the service that aren't mediated by Nova.

3.) Detach a share and don’t destroy data (deactivate)

Share is flagged as inactive and data are not destroyed for later usage or in case of legal requirements.

4.) Unassign and delete data of a share

Destroy entire share with all data and free space for further usage.


Wish list

1.) Assign a preexisting share to a VM with Manila

Import an existing share with data and assign it to a tenant. E.g. migrating an existing production storage to OpenStack.

2.) Resize Share

Resize existing and assigned share on the fly.