Jump to: navigation, search

Manila/SAP enterprise team

< Manila
Revision as of 08:33, 8 August 2016 by Bernd.herth (talk | contribs) (Open Topics:)

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 Volumes based on Snapshots are bound to the source pool. Over the lifetime of a project the need may arise to migrate the volumes to other backends. The first step towards this is to break the dependency from the source i.e. break the "copy-on-write-clones" C  ?
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. C  ? https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/ha-aa-tooz-locks.html
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