I'm not too sure what you mean by "OSP image" because cinder itself does not
maintain any "images". (Maybe you are referring to container images used in
a downstream product ?)

I mostly agree with what JP explained. The driver implementations stay in
the cinder repository so the driver may be included in cinder packages built
by distributions.

However please note that a driver marked unsupported will be subject removal
in a future release. [1]

[1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Non-Compliance_Policy ,
```

If a driver CI is found non compliant:

  * A driver patch will be submitted flagging it as unsupported
      * This will cause warning messages to be logged in the c-vol log stating it is unsupported and deprecated
      * Operators will need to set enable_unsupported_drivers=True in cinder.conf or the service will fail to load
  * If the issue is not corrected before the next release, the driver will subject to removal.
    Please see the Cinder Driver Removal Policy for details

```

Thank you,
Takashi Kajinami
irc: tkajinam


On 2/1/24 16:44, Roquesalane, Jean-Pierre wrote:

Hi Tom,

 

When a driver is marked as unsupported, it doesn’t mean it’ll be removed from the cinder repository and will remain in the OSP image as well until we decide de tear down the driver directory and all related files.

 

Setting this SUPPORTED flag to False just prevent cinder to initialize the driver when services are starting. You may notice this while scrubbing into the log

 

ERROR cinder.volume.manager [-] Unsupported drivers are disabled. You can re-enable by adding enable_unsupported_driver=True to the driver section in cinder.conf

 

Hope that helps to clarify.

 

Jean-Pierre Roquesalane

SW System Sr Principal Engineer - OpenStack Champion

Dell Technologies | Security and Ecosystem Software

Mobile +33 6 21 86 79 04

Email : jeanpierre.roquesalane@dell.com

 


Internal Use - Confidential

From: Zhao, Tom <Tom.Zhao@dell.com>
Sent: Thursday, February 1, 2024 3:28 AM
To: Roquesalane, Jean-Pierre <Jeanpierre.Roquesalane@dell.com>; openstack-discuss@lists.openstack.org; Liu, Rick <Rick.Liu@dell.com>
Cc: Abhinav, Kumar <Kumar.Abhinav@Dell.com>; Hutt, Joshua <Joshua.Hutt@dell.com>; Wang, Jacob <Jacob_Wang1@Dell.com>
Subject: RE: RE: [cinder] Inactive 3rd party CIs

 

Hi Takashi,

 

Could you please also help to clarify what will happened to those drivers (bundled today in the OSP image) once these Cis are marked as unsupported? Will the drivers be deleted from the OSP image or will they still stay in the OSP image?

 

Br,

Tom

 

Internal Use - Confidential

From: Zhao, Tom
Sent: Wednesday, January 31, 2024 10:54 PM
To: Roquesalane, Jean-Pierre <Jeanpierre.Roquesalane@dell.com>; openstack-discuss@lists.openstack.org; Liu, Rick <Rick.Liu@dell.com>
Cc: Abhinav, Kumar <Kumar.Abhinav@Dell.com>; Hutt, Joshua <Joshua.Hutt@dell.com>
Subject: RE: RE: [cinder] Inactive 3rd party CIs

 

Adding @Liu, Rick into the thread as well.

 

From: Roquesalane, Jean-Pierre <Jeanpierre.Roquesalane@dell.com>
Sent: Wednesday, January 31, 2024 10:30 PM
To: openstack-discuss@lists.openstack.org
Cc: Zhao, Tom <Tom.Zhao@dell.com>; Abhinav, Kumar <Kumar.Abhinav@Dell.com>; Hutt, Joshua <Joshua.Hutt@dell.com>
Subject: RE: [cinder] Inactive 3rd party CIs

 

Thanks Takashi for driving this.

 

As far as Dell is concerned, those CIs should be marked as unsupported as they are now EOL.

 

I’ll have the CI team to take a look at the Dell PowerMax CI which is supposed to be active.

 

JP

 

Jean-Pierre Roquesalane

SW System Sr Principal Engineer - OpenStack Champion

Dell Technologies | Security and Ecosystem Software

Mobile +33 6 21 86 79 04

Email : jeanpierre.roquesalane@dell.com

 

 

Internal Use - Confidential

Dell SAS, Siège Social 1 rond point Benjamin Franklin 34000 Montpellier. Capital 1,946,545.26 Euros, 351 528 229 RCS Montpellier –APE 4651Z -TVA Intracommunautaire FR 20 351 528 229. SIRET 351 528 229 00088 Vat Number : FR 20351528229 (France) /  IT00001709997 (Italy) / ESN0012622G (Spain)