Hey Simon, Thanks very much for responding. Yeah I understand that Portworx is a Kubernetes storage solution. The use case that I am looking at involves OpenStack StarlingX project. OpenStack Starlingx Project ( https://starlingx.io ) is an integration solution that deploys - Kubernetes on bare metal, and - then containerized OpenStack (via openstack-helm) on top of Kubernetes ... providing a solution for both hosting containerized workloads via Kubernetes and hosting virtual machine workloads via OpenStack, with the same underlying physical infrastructure. We/StarlingX are looking at supporting Portworx as a storage cluster solution for StarlingX's Kubernetes cluster, in either of the following two scenarios: 1.) a portworx storage cluster running on an external / separate K8S cluster, and StarlingX's K8S Storage cluster integrating the public K8S CSIs for portworx in order to leverage the external portworx storage cluster for backing K8S PVCs 2.) the user of StarlingX purchases a license for portworx and runs it directly on the StarlingX K8S cluster ... and uses the integrated public K8S CSIs for portworx in order to leverage the now internal portworx storage cluster for backing K8S PVCs. HOWEVER, we/StarlingX would also like that our containerized OpenStack (running on top of the StarlingX K8S Cluster), and OpenStack Cinder specifically, to be able to leverage the external or internal portworx storage cluster for backing Cinder Volumes and Backups. We are taking a similar approach with ROOK. But there are some users of StarlingX that prefer Portworx over Rook. ??? So is there no supported mechanism for an OpenStack cloud to use an external portworx storage cluster as the storage backend for Cinder ??? Greg. -----Original Message----- From: Simon Dodsley <simon@purestorage.com> Sent: Sunday, February 16, 2025 4:08 AM To: openstack-discuss@lists.openstack.org Subject: Re: [cinder] Support for Portworx CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Given Portworx is a Kubernetes storage solution, there is no Cinder integration. Portworx create PVs and PVCs from a storage pool that can be created from local disk, SAN disk, or NAS disk. It is completely vendor agnostic when it comes to the underlying disk creating the storage pool. I'm not sure I understand the use case where a Portworx storage pool would be used as a basis to a Cinder backend. If you have Pure Storage systems, then you would use the Pure FlashArray Cinder driver. Simon