Bug 1808570

Summary: [Backport][RHOSP16.1] Backport [VxFlexOS] cinder driver features
Product: Red Hat OpenStack Reporter: Rajini Karthik <rajini.karthik>
Component: openstack-cinderAssignee: Pablo Caruana <pcaruana>
Status: CLOSED ERRATA QA Contact: Tzach Shefi <tshefi>
Severity: medium Docs Contact: Chuck Copello <ccopello>
Priority: medium    
Version: 16.0 (Train)CC: abishop, amcleod, arkady_kanevsky, dcadzow, dcain, gael_rehault, Ivan.Pchelintsev, jvisser, kholtz, kurt_hey, mburns, morazi, pcaruana, pgrist, rajini.karthik, sputhenp, vladislav.belogrudov
Target Milestone: betaKeywords: FeatureBackport, OtherQA, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-cinder-15.1.1-0.20200427123444.0aceffb.el8ost Doc Type: Release Note
Doc Text:
This update includes the following enhancements: + - Support for revert-to-snapshot in VxFlex OS driver - Support for volume migration in VxFlex OS driver - Support for OpenStack volume replication v2.1 in VxFlex OS driver - Support for VxFlex OS 3.5 in the VxFlex OS driver
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-29 07:50:57 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1595325, 1715964    

Description Rajini Karthik 2020-02-28 20:31:29 UTC
Description of problem:
Backport these to RHOSP 16.1
Here is the list of features for VxFlex OS cinder driver:
•	Add support for VxFlex OS 3.5 to VxFlex OS driver: https://review.opendev.org/#/c/705176
•	Add OpenStack volume replication v2.1 support in VxFlex OS driver: https://review.opendev.org/#/c/707390


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rajini Karthik 2020-03-13 16:44:03 UTC
Two more to backport..

Add support for volume migration in VxFlex OS driver - https://review.opendev.org/#/c/711624/

Add revert to snapshot support in VxFlex OS driver - https://review.opendev.org/#/c/712622/

Comment 2 Luigi Toscano 2020-03-17 10:37:41 UTC
All the changes seems to be driver specific. Given their size and impact, it is unlikely they are going to be backported upstream.

Comment 3 Rajini Karthik 2020-04-17 12:13:39 UTC
Everything has been merged upstream in USSURI. Can we start the backports?

Comment 4 John Visser 2020-04-17 18:13:33 UTC
Hi Rajini, the backports can start.  As you are no doubt aware, these will be downstream backports.  Pablo @pcaruana will help, please coordinate with him and Alan @abishop.

Comment 5 Rajini Karthik 2020-04-22 16:21:40 UTC
Thanks John

Comment 7 Alan Bishop 2020-04-28 15:18:50 UTC
Thanks, Ivan. Even if the upstream community rejects the patches on stable/train, we are working on downstream backports for osp-16.1

Comment 14 Rajini Karthik 2020-05-20 18:51:03 UTC
The blueprint for vxflexos tripleo integration is https://review.opendev.org/#/c/724301/

Comment 16 Rajini Karthik 2020-05-29 12:31:21 UTC
Looks like these patches are already merged downstream
What is expected of the upstream patches on the stable/train?
Should we abandon them? if so when?
https://review.opendev.org/#/c/723825
https://review.opendev.org/#/c/723826
https://review.opendev.org/#/c/723827
https://review.opendev.org/#/c/723828

Comment 17 Alan Bishop 2020-05-29 13:09:23 UTC
If the patches can be backported upstream then they should be backported upstream. Reducing the number of downstream patches really helps minimize the complexity of maintaining a long term OSP release.

The next step is to see what the stable core team feels about backporting them to a stable branch, so maybe ping them on irc (or this might be a good virtual hallway discussion during next week's PTG). The fact that the DellEMC_VxFlexOS CI jobs are all passing is encouraging. If the first patch n the sequence is rejected then you can immediately abandon the others.

@Derek, as Pablo noted this is a FeatureBackport. In this instance, this BZ *is* the RFE, and the scope is limited to the Dell EMC cinder driver. We don't require (or want) a separate BZ per patch when the patches represent a single functional set.

Comment 18 Vladislav Belogrudov 2020-06-23 08:24:51 UTC
The upstream backports have been rejected for all the reviews, we cannot go upstream route. Can you please proceed with the downstream backporting?

Comment 19 Pablo Caruana 2020-06-23 13:35:42 UTC
(In reply to Vladislav Belogrudov from comment #18)
> The upstream backports have been rejected for all the reviews, we cannot go
> upstream route. Can you please proceed with the downstream backporting?

Hello Vladislav,  not sure if you being aware, but  Backports were perfomed already and  current status is ON_QA. If  everythings goes well and no regression detected,  it would be included in openstack-cinder-15.1.1-0 package and laters when the errata being published.
Regards,
Pablo.

Comment 20 arkady kanevsky 2020-06-23 14:12:41 UTC
Thanks Pablo.
I suggest we do 2 things:
1. deprecate all 4 upstream backports since they are no longer needed and they had been backported to 16.
2. change this BZ to 16.1

Thanks,
Arkady

Comment 21 Rajini Karthik 2020-06-30 18:15:00 UTC
Will this be available in 16.0 zStream? or 16.1 GA?

Comment 22 Ken Holtz 2020-06-30 20:09:10 UTC
(In reply to Rajini Karthik from comment #21)
> Will this be available in 16.0 zStream? or 16.1 GA?

Rajini, 

I expect this to be in the 16.1 GA and not in the 16.0 Z-stream. Is it needed there?

Comment 24 Paul Grist 2020-07-21 16:30:31 UTC
Can we get confirmation this is in 16.1 RC can can be tested by Dell-EMC?

Comment 26 Pablo Caruana 2020-07-21 18:46:23 UTC
(In reply to Paul Grist from comment #24)
> Can we get confirmation this is in 16.1 RC can can be tested by Dell-EMC?

I can confirm there are in the 16.1 RC.

Comment 29 errata-xmlrpc 2020-07-29 07:50:57 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-2020:3148