Bug 1523864

Summary: [Tracking] Support IPv6 for VNX and Unity Manila Drivers
Product: Red Hat OpenStack Reporter: ryan.genato
Component: openstack-manilaAssignee: Tom Barron <tbarron>
Status: CLOSED ERRATA QA Contact: Dustin Schoenbrun <dschoenb>
Severity: medium Docs Contact: Don Domingo <ddomingo>
Priority: medium    
Version: 13.0 (Queens)CC: abishop, acanan, achernet, arkady_kanevsky, joflynn, jschluet, marjones, pgrist, rajini.karthik, sclewis, scohen, smerrow, tbarron, vimartin
Target Milestone: z2Keywords: FutureFeature, OtherQA, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.4-20.el7ost puppet-tripleo-8.3.4-6.el7ost puppet-manila-12.4.0-2.el7ost openstack-manila-6.0.1-2.el7ost Doc Type: Release Note
Doc Text:
This update adds support for use of Manila IPv6 export locations and access rules with Dell-EMC Unity and VNX back ends.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 16:32:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1468020    
Bug Blocks: 1419948, 1519552, 1639594    

Description ryan.genato 2017-12-08 20:57:59 UTC
Description of problem:
IPv6 support for the VNX Manila driver and Cinder Manila driver will be provided in OpenStack Queens. As we have missed the window for promotion into the OSP13 base release it is requested that these drivers be supported by Red Hat OpenStack Platform 14.

Version-Release number of selected component (if applicable):
VNX Manila Driver: 6.0.0
Unity Manila Driver: 4.0.0

Additional info:
IPv6 support is driven significantly by a request from a large shared customer between Red Hat and Dell EMC. This customer intends to make use of IPv6 and requires its infrastructure to support the protocol accordingly.

Comment 7 Tom Barron 2018-03-14 15:40:05 UTC
These TripleO changes would also seem to be required?

https://review.openstack.org/#/c/538147/

https://review.openstack.org/#/c/538146/

Adding these to the external tracker and moving state back to ON_DEV until they are merged.  If someone knows better and the tripleO changes are not actually needed for V6 deployment (they add v6 options) then please remove them from the tracker and move back to POST.

Comment 13 Alan Bishop 2018-05-04 18:54:54 UTC
Adding upstream puppet-manila gerrit for VNX

Comment 14 Alan Bishop 2018-05-04 19:27:33 UTC
Adding upstream tripleo-heat-templates gerrit for Unity

Comment 16 Paul Grist 2018-05-22 22:50:08 UTC
Patches are in stable queens and will come into the first errata update and didn't make the GA release.

Comment 18 Alan Bishop 2018-06-21 15:44:07 UTC
I just did a test of upstream stable/queens using tripleo-quickstart, and there's a problem. Like many storage backends, Manila's VNX and Unity backends rely on code in puppet-triple to essentially "bind" TripleO Heat parameters to the puppet-manila inputs that configure the backend.

The upstream patches added 3 new parameters (1 for IPv6 and 2 that control SSL certificates) to tripleo-heat-templates and puppet-manila. Unfortunately, the puppet-tripleo piece is missing, and so the THT values are never passed to puppet-manila.

This means the puppet-manila default values cannot be overridden. As things stand now, the VNX and Unity backends will be configured as follows:

- IPv6 support is enabled
- SSL cert verification is disabled

The key point is, these settings currently cannot be modified using the TripleO parameters.

Comment 19 Sean Merrow 2018-06-21 15:47:30 UTC
Rajini, can you comment or reach out internally?

Comment 20 Rajini Karthik 2018-06-21 18:21:09 UTC
Will work with alan on this. Will be submitting the missing patches soon

Comment 21 Rajini Karthik 2018-06-21 18:30:20 UTC
We need 4 patches (on master, and all 4 backported to stable/queens)
1. puppet-tripleo for vnx
2. puppet-tripleo for unity
3. tht for vnx
4. tht for unity

Comment 27 Joanne O'Flynn 2018-08-15 09:56:40 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 29 Rajini Karthik 2018-08-28 13:41:57 UTC
The IPv6 issue described in this bug has been verified with Manila deployment for VNX/Unity by Dell EMC.

Comment 30 Sean Merrow 2018-08-28 14:03:11 UTC
Marking as Partner Verified as per OtherQA keyword and comment #29 from partner.

Comment 32 errata-xmlrpc 2018-08-29 16:32:35 UTC
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.

https://access.redhat.com/errata/RHBA-2018:2573