Difference between revisions of "Manila/SAP enterprise team"
< Manila
Bernd.herth (talk | contribs) (→Open Topics:) |
Bernd.herth (talk | contribs) (→Open Topics:) |
||
| Line 11: | Line 11: | ||
|1|| Snapshot: make it possible for users to specify "full copy clones" or "copy-on-write clones" || In order to speed up the rollout the concept requires to 'clone a template' , where a template is a snapshot of a master volume and clone resolves into a snapshot (manila create --snapshot) || A || ? || || | |1|| Snapshot: make it possible for users to specify "full copy clones" or "copy-on-write clones" || In order to speed up the rollout the concept requires to 'clone a template' , where a template is a snapshot of a master volume and clone resolves into a snapshot (manila create --snapshot) || A || ? || || | ||
|- | |- | ||
| − | |2|| Snapshot: make it possible for users decouple the "copy-on-write clones" from it's source snapshot || | + | |2|| Snapshot: make it possible for users decouple the "copy-on-write clones" from it's source snapshot || Shares based on Snapshots are bound to the source pool. Over the lifetime of a project the need may arise to migrate the shares to other backends. The first step towards this is to break the dependency from the source i.e. break the "copy-on-write-clones" || A || ? || || |
|- | |- | ||
| − | |3|| Manila-share active-active HA || Manila service manila-share should be active-active HA. This means a backend should be managed by at least 2 services. || | + | |3|| Manila-share active-active HA || Manila service manila-share should be active-active HA. This means a backend should be managed by at least 2 services. || A || ? || https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/ha-aa-tooz-locks.html || |
| + | |- | ||
| + | |4|| Migrate a share to a different pool || With growing projects capacity (or performance) requires to move a share within the same share server / share network. Migration should support this preferably as function within the backend specific driver to keep overhead to a minimum || A || ? || || | ||
|- | |- | ||
|10|| MTU Size must be definable || actual there is no way to define the MTU Size for the broadcast domain setup (NetApp driver) || A || SAP & NetApp|| https://bugs.launchpad.net/manila/+bug/1606190 || | |10|| MTU Size must be definable || actual there is no way to define the MTU Size for the broadcast domain setup (NetApp driver) || A || SAP & NetApp|| https://bugs.launchpad.net/manila/+bug/1606190 || | ||
Revision as of 09:39, 8 August 2016
Misson
The SAP Manila enterprise team tries to address topics to make Manila enterprise ready. The listed topics can be bugs, features or even long running tasks.
Open Topics:
| No | Issue | Description | Priority | Assignee | Reference | Release |
|---|---|---|---|---|---|---|
| 1 | Snapshot: make it possible for users to specify "full copy clones" or "copy-on-write clones" | In order to speed up the rollout the concept requires to 'clone a template' , where a template is a snapshot of a master volume and clone resolves into a snapshot (manila create --snapshot) | A | ? | ||
| 2 | Snapshot: make it possible for users decouple the "copy-on-write clones" from it's source snapshot | Shares based on Snapshots are bound to the source pool. Over the lifetime of a project the need may arise to migrate the shares to other backends. The first step towards this is to break the dependency from the source i.e. break the "copy-on-write-clones" | A | ? | ||
| 3 | Manila-share active-active HA | Manila service manila-share should be active-active HA. This means a backend should be managed by at least 2 services. | A | ? | https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/ha-aa-tooz-locks.html | |
| 4 | Migrate a share to a different pool | With growing projects capacity (or performance) requires to move a share within the same share server / share network. Migration should support this preferably as function within the backend specific driver to keep overhead to a minimum | A | ? | ||
| 10 | MTU Size must be definable | actual there is no way to define the MTU Size for the broadcast domain setup (NetApp driver) | A | SAP & NetApp | https://bugs.launchpad.net/manila/+bug/1606190 | |
| 11 | Manila hierarchical port binding support | Port binding with multi-segement support | A | SAP | https://blueprints.launchpad.net/manila/+spec/manila-hpb-support | Newton |
| 12 | allow more than one aggr with parameter "netapp_root_volume_aggregate" | Current issue: In case of a node fail all SVM´s are affected and takeover/giveback will take long. | B | NetApp on-site | - | |
| 13 | Implement LS-Mirror for NFS-Versions lower than V4.1 | In case NFS V4.1 is used, we do not need LS-mirror functionality but if we use a lower Version we have to have it and we have to take care about the changing configuration behavior within the driver scripts | C | NetApp on-site |
