Hello Vendors,
This is related to the original discussion on the ML thread[1].
We have noticed that a lot of the drivers don't have their CI reported on a patch in 2024. Based on the last CI report that I checked[2], the number comes out to be 32 though it's not an accurate measure of the inactivity in the project.
The following cases are possible: 1. The driver that doesn't have active CI reporting is already marked unsupported 2. The driver is supported but CI is not actively maintained 3. The CI information is not accurate in the wiki page
If it's case 2, vendors should look into their CI and fix it else the driver will be marked unsupported in the current or upcoming release.
If it's case 3, make sure to have updated CI info in the wiki page. Let's take an example of the HPE driver. The last seen status is shown as:
last seen: 2016-08-09
but the driver is actively reporting on patches. The issue here is either:
1. The CI name in the volume driver is not pointing to the correct wiki page[3] 2. The wiki page does not have correct information about CI[4]
Vendors should look into updating their CI related information before the midcycle-2, which is going to be held on 14th Feb, 2024 from 1400-1600 UTC[5]. Since we only have the cireport[2] as the source of truth, we will be looking at the vendor drivers that don't have a recent last seen date and start marking them unsupported during the midcycle-2.
Any query is welcome on this thread or during the midcycle-2 topic discussion.
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [2] http://cinderstats.ivehearditbothways.com/cireport.txt [3] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/drivers... [4] https://wiki.openstack.org/wiki/ThirdPartySystems/HPE_Storage_CI [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
Thanks Rajat Dhasmana