Enable the Shared File Systems service (manila) to provision remote, shareable file systems, known as shares. Shares provide POSIX-compliant storage that multiple compute instances or containers can mount simultaneously with read/write access.
Before you begin
- You have planned networking for the Shared File Systems service. For more information, see Storage planning.
About this task
When you enable the Shared File Systems service, you can configure the service with the following back ends:
- Red Hat Ceph Storage CephFS
- Red Hat Ceph Storage CephFS-NFS
- NFS or CIFS through third party vendor storage systems
Procedure
-
Open your
OpenStackControlPlane CR file, openstack_control_plane.yaml, and add the following parameters to the spec section to enable the Shared File Systems service:
spec:
...
manila:
enabled: true
apiOverride:
route: {}
template:
databaseInstance: openstack
secret: osp-secret
manilaAPI:
replicas: 3
override:
service:
internal:
metadata:
annotations:
metallb.universe.tf/address-pool: internalapi
metallb.universe.tf/allow-shared-ip: internalapi
metallb.universe.tf/loadBalancerIPs: 172.17.0.80
spec:
type: LoadBalancer
manilaScheduler:
replicas: 3
manilaShares:
share1:
networkAttachments:
- storage
replicas: 0 # backend needs to be configured
Note You must configure a back end for the Shared File Systems service. If you do not configure a back end for the Shared File Systems service, then the service is deployed but not activated (replicas: 0).
-
Update the control plane:
$ oc apply -f openstack_control_plane.yaml -n openstack
-
Wait until RHOCP creates the resources related to the
OpenStackControlPlane CR. Run the following command to check the status:
$ oc get openstackcontrolplane -n openstack
The OpenStackControlPlane resources are created when the status is "Setup complete".
Tip Append the -w option to the end of the get command to track deployment progress.