On 05/02/2026 14:20, Alokedip Choudhuri wrote:

Hello Everyone,

We are working on contributing a new Cinder driver for *Infoscale*. This implementation requires coordinated changes across three projects to support the full attachment lifecycle:

1.

*Cinder:* The core driver implementation.

2.

*os-brick:* The connector APIs have been implemented there

3.

*Nova:* New driver implementation to support the required operations like, "attach, detach, extend" for the volumes provisioned through the InfoScale Backend.

if it was just the cinder and os-brick change then a cidner spec or specless blueprint depenign on there prefence would be all that is requred depending on the scope of the nova chagne you may need a spec. if you are not plannign to change the volume api in https://github.com/openstack/nova/tree/master/nova/virt/libvirt/volume and just add a new driver that might be ok specless but i would suggested adding this topic ot the next nova irc meeting or poping into the #openstack-nova irc channel to get feedback early

We have already registered blueprints for this work:

*

*Cinder Blueprint:* https://blueprints.launchpad.net/cinder/+spec/infoscale-cinder-driver

*

*Nova Blueprint:* https://blueprints.launchpad.net/nova/+spec/infoscale-nova-driver

lookign at what is described in ^ if most of the implemention is hidden in os-brick and you do not need to modify the xml generation at all jsut implemention the volume api that is probably something that could be specless but for 2026.2 not 2026.1 we are well past the spec and blueprint approval deadline for this cycle which was December 4th this cycle instead of milestone 2 which woudl have been January 8th we will hit feature feeze for 2026.1 on febuary 26th but the master branch tecnically opens for 2026.2 develokpme on march 12 once we 12th once RC1 is released. you could start preparing the reivew before then however if you wanted. cinder has a requirement that new driver have third party ci i belive. it woudl be nice if that ci could also validate change to this code in nova.

Since this is a cross-project effort, I would appreciate guidance on the preferred workflow for submitting patches across multiple repositories to ensure a smooth integration.

Looking forward to your feedback and suggestions.

Thanks & Regards Alokedip