1. Description: Deploying Manila using the RHEL-OSP Director is not currently possible.
a.Bugzilla dependencies (if any): n/a
b.Hardware dependencies (if any): n/a
i. Date it will be upstream: January 2016
d.External links: https://review.openstack.org/#/c/188137/
e.Severity (U/H/M/L): Urgent
f.Business Priority: Must
a.Why is this needed: This is needed to showcase Manila in a resulting RHEL-OSP8 deployment and associated reference architecture.
b.What hardware is required (if any):
c.Business impact: Significant revenue impacts exist and are depending on this getting integrated into RHEL-OSP8 once it is merged upstream.
4.Primary Red Hat contact
a.Name: Mike Orazi
5.Primary Partner contact
a.Name: Dave Cain
Just opening a bug to track inclusion of Manila and NetApp Manila integration into RHEL-OSP8 as instructed in the Private Beta instructions.
I completely understand that upstream needs to merge first, but wanted to open a bug for tracking regardless.
(In reply to Dave Cain from comment #2)
> Just opening a bug to track inclusion of Manila and NetApp Manila
> integration into RHEL-OSP8 as instructed in the Private Beta instructions.
> I completely understand that upstream needs to merge first, but wanted to
> open a bug for tracking regardless.
We are tracking the manila integration in bug: 1229896
I've modified this bug title to reflect the NetApp support
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
The reason I am setting exception? is that FFE already has been granted  on the openstack-dev mailinglist to Ben Swartzlander's request. So setting the exception? flag here is just to make the BZ match reality. :)
https://review.openstack.org/#/c/354014/ and https://review.openstack.org/#/c/354019/ have merged into master rc1 before stable/newton is cut.
We need 374961 and 377179 for OOO to fully deploy manila in the overcloud. They have merged upstream.
This has been tested with the 2016-11-11.1 puddle and the NetApp Clustered Data ONTAP driver does get installed and configured successfully through Director and the TripleO Heat Templates. Any bugs found with further testing will be opened separately.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.