Inquiry on Integrating Ansible with Vendor-Specific Cinder Driver Code
Hello Moderators, We maintain a substantial body of open-source Ansible code (certified by Red Hat as a collection) for IBM Storage Virtualize, which we believe could directly benefit the Cinder driver roadmap. I’d like to understand whether it is technically and architecturally acceptable to invoke Ansible scripts from within a vendor-specific Cinder driver. Specifically: * Are there any guidelines or constraints on integrating external automation tools (like Ansible) within a Cinder driver implementation? * Is there any official documentation on the acceptance of such cross-language or framework integrations (e.g., calling Ansible from Python)? Your guidance would be greatly appreciated to ensure any contributions align with community standards and best practices. Thank you! Sumit K Gupta sumit.gupta16@ibm.com Senior Storage Leader, IBM
On 2025-06-21 12:47:57 +0000 (+0000), Sumit Gupta wrote: [...]
I’d like to understand whether it is technically and architecturally acceptable to invoke Ansible scripts from within a vendor-specific Cinder driver. [...]
Not speaking on behalf of the Cinder maintainers, but you might also want to consider what the licensing for that addition would look like. For example, do you foresee that the driver implementation would include any Ansible callbacks or server-side actions, and are those derivative works of GPL code in Ansible itself? If so, that would not be acceptable for direct inclusion in OpenStack (whether in Cinder or any other component): https://governance.openstack.org/tc/reference/licensing.html -- Jeremy Stanley
participants (2)
-
Jeremy Stanley
-
Sumit Gupta