Pure Service Orchestrator (PSO) delivers storage-as-a-service for containers, giving developers the agility of public cloud with the reliability and security of on-premises infrastructure.
Smart Provisioning
PSO automatically makes the best provisioning decision for each storage request – in real-time – by assessing multiple factors such as performance load, the capacity and health of your arrays, and policy tags.
Elastic Scaling
Uniting all your Pure FlashArray™ and FlashBlade™ arrays on a single shared infrastructure, and supporting file and block as needed, PSO makes adding new arrays effortless, so you can scale as your environment grows.
Transparent Recovery
To ensure your services stay robust, PSO self-heals – so you’re protected against data corruption caused by issues such as node failure, array performance limits, and low disk space.
-
- CentOS 7
- CoreOS (Ladybug 1298.6.0 and above)
- RHEL 7
- Ubuntu 16.04
- Ubuntu 18.04
-
- Refer to the README for the type of PSO installation required
-
- Latest linux multipath software package for your operating system (Required)
- Latest Filesystem utilities/drivers (XFS by default, Required)
- Latest iSCSI initiator software for your operating system (Optional, required for iSCSI connectivity)
- Latest NFS software package for your operating system (Optional, required for NFS connectivity)
- Latest FC initiator software for your operating system (Optional, required for FC connectivity, FC Supported on Bare-metal K8s installations only)
-
- The FlashArray and/or FlashBlade should be connected to the compute nodes using Pure's best practices
* Please see release notes for details
PSO can be used with any of the following hardware appliances and associated minimum version of appliance code:
- Pure Storage FlashArray (minimum Purity code version 4.8)
- Pure Storage FlashBlade (minimum Purity version 2.2.0)
PSO can be deployed via an Operator or from the Helm chart.
PSO has Operator-based install available for both its FlexVolume plugin and CSI plugin. This install method does not need Helm installation.
The Pure Flex Operator is supported for OpenShift and Kubernetes.
Pure Flex Operator is now the preferred installation method for FlexVolume on OpenShift version 3.11 and higher.
For installation, see the Flex Operator Documentation or the CSI Operator Documentation..
pure-k8s-plugin deploys PSO FlexVolume plugin on your Kubernetes cluster.
pure-csi deploys PSO CSI plugin on your Kubernetes cluster.
Install Helm by following the official documents:
-
For Kubernetes
https://docs.helm.sh/using_helm#install-helm -
For OpenShift
https://blog.openshift.com/getting-started-helm-openshift/
Starting OpenShift 3.11 the preferred installation method is using the PSO Operator. Follow the instructions in the operator directory.
In order to enable Tiller (the server-side component of Helm) to install any type of service across the entire cluster, it's required to grant Tiller a cluster-admin role.
After the Helm installation, configure the cluster admin role for the service account of Tiller. You will need to determine the correct service account.
# For K8s with example service account "{TILLER_NAMESPACE}:default"
kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=${TILLER_NAMESPACE}:default
# For Openshift version < 3.11:
oc adm policy add-cluster-role-to-user cluster-admin system:serviceaccount:${TILLER_NAMESPACE}:tillerFor more details, please see https://docs.helm.sh/using_helm/
Refer to the k8s-plugin README or the csi-plugin README for further installation steps.
We welcome contributions. The PSO Helm Charts project is under Apache 2.0 license. We accept contributions via GitHub pull requests.
For filing bugs, suggesting improvements, or requesting new features, please open an issue.