Add integration for manila-netapp backend
Bug #1618479 reported by
Marios Andreou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Marios Andreou |
Bug Description
this is for tracking the work needed to land manila-netapp for newton
currently tht https:/
This includes a tidy up puppet-tripleo side for removing the duplication of config.
description: | updated |
Changed in tripleo: | |
milestone: | newton-3 → newton-rc1 |
importance: | Undecided → High |
Changed in tripleo: | |
milestone: | newton-rc1 → newton-rc2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/354019 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=98b47767478 eda2c940098217e 93ec3567fa9f36
Committed: https:/
Submitter: Jenkins
Branch: master
commit 98b47767478eda2 c940098217e93ec 3567fa9f36
Author: marios <email address hidden>
Date: Thu Aug 11 14:30:04 2016 +0300
Add NetApp Manila driver integration and tidy up generic
Enables configuring a NetApp backend for the Manila service /review. openstack. org/#/c/ 188138/
This was created based on the review at
https:/
This makes the netapp and generic backends disabled by default manila- backend- *.yaml. A backend is then
in the services/
enabled via backend-specific environment files, which will set
any config parameters and enable that backend.
It is expected that multiple manila backend specific environment
files might be specified simultaneously.
Finally generic and manila config is split into separate
service files rather than using manila-base for all the things.
Co-Authored-By: Ryan Hefner <email address hidden> 9badddea5d16550 aa18bff8418 c1c3382c2d0e0d6 028928fd943
Co-Authored-By: Ben Swartzlander <email address hidden>
Closes-Bug: 1618479
Depends-On: Ic6f8e8d27ca20b
Change-Id: I35fce32d0f6a5c