3.4. Persistent storage using Cinder

Procedure

1. Save your object definition to a file.

   cinder-persistentvolume.yaml

   apiVersion: "v1"
   kind: "PersistentVolume"
   metadata:
     name: "pv0001" 1
   spec:
     capacity:
       storage: "5Gi" 2
     accessModes:
       - "ReadWriteOnce"
     cinder: 3
       fsType: "ext3" 4
       volumeID: "f37a03aa-6212-4c62-a805-9ce139fab180" 5

   1

   The name of the volume that is used by persistent volume claims or pods.

   2

   The amount of storage allocated to this volume.

   3

   Indicates cinder for Red Hat OpenStack Platform (RHOSP) Cinder volumes.

   4

   The file system that is created when the volume is mounted for the first time.

   5

   The Cinder volume to use.

   重要

   Do not change the fstype parameter value after the volume is formatted and provisioned. Changing this value can result in data loss and pod failure.

2. Create the object definition file you saved in the previous step.

   $ oc create -f cinder-persistentvolume.yaml

Procedure

1. Create a service account and add it to the SCC:

   $ oc create serviceaccount <service_account>

   $ oc adm policy add-scc-to-user <new_scc> -z <service_account> -n <project>

2. In your application’s deployment configuration, provide the service account name and securityContext:

   apiVersion: v1
   kind: ReplicationController
   metadata:
     name: frontend-1
   spec:
     replicas: 1  1
     selector:    2
       name: frontend
     template:    3
       metadata:
         labels:  4
           name: frontend 5
       spec:
         containers:
         - image: openshift/hello-openshift
           name: helloworld
           ports:
           - containerPort: 8080
             protocol: TCP
         restartPolicy: Always
         serviceAccountName: <service_account> 6
         securityContext:
           fsGroup: 7777 7

   1

   The number of copies of the pod to run.

   2

   The label selector of the pod to run.

   3

   A template for the pod that the controller creates.

   4

   The labels on the pod. They must include labels from the label selector.

   5

   The maximum name length after expanding any parameters is 63 characters.

   6

   Specifies the service account you created.

   7

   Specifies an fsGroup for the pods.