Thank you very much, for the detailed guidance on the cross-project workflow between Cinder, os-brick, and Nova. It helps clarify the path forward, especially regarding the release cycle timing. To provide a brief overview of the proposed InfoScale integration: Cinder: The changes include a new driver class to support InfoScale as a storage backend. Os-brick: The changes include a new "InfoScale Connector" class. All heavy lifting for volume attachment/detachment will be encapsulated here to keep the Nova-side changes minimal. Nova: The changes include a new Libvirt volume driver. This will utilize the os-brick connector to handle volume operations (attach/detach/extend) and will not require any changes to the existing XML generation workflow or the core volume API. I understand that we have missed the deadlines for the 2026.1 cycle. We will target the 2026.2 cycle instead and will begin preparing the Gerrit reviews for early feedback once the master branch opens. As recommended, I will join the #openstack-nova IRC channel and will include this topic to get early feedback as well. Regarding the third-party CI for Cinder, I’ll ensure our plan includes validation for the associated Nova changes as well. Much Appreciated, @Sean Mooney!