Bug 1756394

Testing will be done for Dell EMC eLab team.

Given amount of work for backport, lets not do it.
And target it for OSP16.
DellEMC can test it.

Luigi
What info do you need? Is this ready for testing?

Rajini,

The code was on stable/train, and so it's present in any of our OSP-16 releases. The feature is ready for you to test, and I believe the needinfo was to track getting your test results.

Thanks alan. We will test

Will the certification tests cover Replication?

This is still TBD, Cinder replication general feature is not currently supported, the certification details will be discussed when we will productise the feature.

Greg,
I interpret that as
1. Dell EMC will do its own validation of replication on Unity
2. There is not replication certification for OSP13-16.
3. If we want to list that as a feature for our certified driver we should add it to driver documentation for RHOSP13 and add it to certification documentation. That means 2 new BZs for it that are dependent on this one.

Right?

(In reply to arkady kanevsky from comment #12)
> Greg,
> I interpret that as
> 1. Dell EMC will do its own validation of replication on Unity
Correct

> 2. There is not replication certification for OSP13-16.
OSP 13 for sure, 16 we will need to check if that's a feature we're willing to fully support during the 16 cycle.

> 3. If we want to list that as a feature for our certified driver we should
> add it to driver documentation for RHOSP13 and add it to certification
> documentation. That means 2 new BZs for it that are dependent on this one.

This feature is driver dependent like Cinder multi attach. In order to productise full support, the general feature (cinder replication) must be supported by RH then the driver itself must support it.

Today Cinder replication is not supported by RH so even if the driver part works, the feature is not supported as RH needs to be able to _reproduce_ and fix any non driver (core) related issue.
Until the general feature is supported the only way to run this in production is to ask for a support exception.

> 
> Right?

We have tested the fix.


The image is ready: https://access.redhat.com/containers/#/registry.connect.redhat.com/dellemc/openstack-cinder-volume-dellemc/images/13.0-4-33.

Please refer https://docs.openstack.org/cinder/latest/configuration/block-storage/drivers/dell-emc-unity-driver.html to create a compressed volume.
 
Note
In Unity, only All-Flash pools support compressed volume, for the other type of pools, “‘compression_support’: False” will be returned when getting pool stats.

(overcloud) [heat-admin@elabdir83ctl0 ~]$ cinder get-pools --detail
+-----------------------------+---------------------------------+
| Property                    | Value                           |
+-----------------------------+---------------------------------+
| allocated_capacity_gb       | 0                               |
| compression_support         | True                            |

(In reply to Gregory Charot from comment #13)
> (In reply to arkady kanevsky from comment #12)
> > Greg,
> > I interpret that as
> > 1. Dell EMC will do its own validation of replication on Unity
> Correct
>
 
Validation is complete

> > 2. There is not replication certification for OSP13-16.
> OSP 13 for sure, 16 we will need to check if that's a feature we're willing
> to fully support during the 16 cycle.
> 

Can we update the new container catalog (and the certs page if applicable) to list this as a feature for the Unity Plugin?
And any other documentation for Unity in the RH docs.

> > 3. If we want to list that as a feature for our certified driver we should
> > add it to driver documentation for RHOSP13 and add it to certification
> > documentation. That means 2 new BZs for it that are dependent on this one.
> 
> This feature is driver dependent like Cinder multi attach. In order to
> productise full support, the general feature (cinder replication) must be
> supported by RH then the driver itself must support it.
> 
> Today Cinder replication is not supported by RH so even if the driver part
> works, the feature is not supported as RH needs to be able to _reproduce_
> and fix any non driver (core) related issue.
> Until the general feature is supported the only way to run this in
> production is to ask for a support exception.
> 
> > 
> > Right?

Ignore the two recent comments, they are meant for bug 1779744. For the compression feature. Sorry

PG>> Hi Arkady,

> Greg,
> I interpret that as
> 1. Dell EMC will do its own validation of replication on Unity
Correct

> 2. There is not replication certification for OSP13-16.
OSP 13 for sure, 16 we will need to check if that's a feature we're willing to fully support during the 16 cycle.

PG>>  As Greg indicated there is no CERT test because it's not a supported feature yet and based on what we know, would be a post-16.0 consideration due the the post-queens failback and other patches that landed after the initial upstream delivery of the core replication feature.

> 3. If we want to list that as a feature for our certified driver we should
> add it to driver documentation for RHOSP13 and add it to certification
> documentation. That means 2 new BZs for it that are dependent on this one.

This feature is driver dependent like Cinder multi attach. In order to productise full support, the general feature (cinder replication) must be supported by RH then the driver itself must support it.

Today Cinder replication is not supported by RH so even if the driver part works, the feature is not supported as RH needs to be able to _reproduce_ and fix any non driver (core) related issue.
Until the general feature is supported the only way to run this in production is to ask for a support exception.

PG>>  In addition to Greg's reply, I wanted to reply here after sending a recent email on the topic.  We can definitely discuss how to bring this feature to customers, it will start with this fix giving Dell the ability to test. We can discuss directly, but we would need joint access to at least one Dell backend that wants to deliver cinder replication and to discuss testing until we have it as a supported feature in a future release and certification test/plan for it.

Paul,
so how do we want to position the message for the field and the customers?
Do we go support case/support exception route?
Can we handle it for OSP13 and OSP16?
Will OSP16 fully support replications starting from OSP16.xxx?

Thanks,
Arkady

In addition,
does OSP16 certification covers replication? If not when will it be extended for it?
We can do validation of replication for Unity.
But we will need to line up which OSP version and which z-stream for it.

Thanks,
Arkady

No plan for 13, missing some key features.

16 we need to find a way to QE the general feature as well as replicating and fixing non driver related bugs. Our QE does not currently have access to HW to do so. Until then the only path is support exception.

There is no certification plans until we solve the above. This is really a matter of HW for testing and verifying bugs, we can eventually TP the feature as a mean to position the feature.

So the only way to deliver replication to customer is thru support exception?
That sucks.

If we gave you access to HW will RH be able to state that as supported feature for that HW?

RH has no industrial/automated way to test it due to lack of hardware so yes SE only for now. Even if the feature was marked tech preview, customers would need a SE for running it in production.

If our QE/Eng can have access to HW that supports replication then it would indeed greatly help productising the feature. Partners still need to go through certification as a mean to advertise that their backend is certified for this specific feature as well as their willingness to support it.

According to our records, this should be resolved by openstack-cinder-15.0.2-0.20200123220928.900f769.el8ost.  This build is available now.

Cinder replication is not supported in OSP16, moving to 17.

Why 17 and not 16.2?

Greg may have more info, but it's mainly because 16.2 will still be based on Train where we don't support cinder replication.

No plan to support cinder replication in the near futur, closing deferred to avoid possible support confusion.