Manila/SAP enterprise team
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 | Assignee | Reference | Release |
|---|---|---|---|---|---|
| 1 | Manila hierarchical port binding support | Port binding with multi-segement support | SAP | https://blueprints.launchpad.net/manila/+spec/manila-hpb-support | Newton |
| 5 | MTU Size must be definable | actual there is no way to define the MTU Size for the broadcast domain setup (NetApp driver) | SAP & NetApp | https://bugs.launchpad.net/manila/+bug/1606190 | |
| 6 | 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. | NetApp on-site | - | |
| 7 | 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 behaviour within the driver scripts | NetApp on-site | ||
| 12 | 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. | ? | https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/ha-aa-tooz-locks.html | |
| 13 | Snapshot: make it possible for users to specify "full copy clones" or "copy-on-write clones" | n 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) | ? |
