Task:
Create persistent storage for HCL Domino container.
If the production server has low utilization, create one persistent volume /local.
If the production server has high utilization, create multiple volumes as needed/utilized:
/local/notesdata
/local/translog
/local/NIF
/local/FT
/local/DAOS
Storage Notes:
- NFS (notesdata), NIF, and FT require fast storage of random (often 4k) I/O operations
- Translog requires low latency small 4k write operations continuously
- DAOS is written in 32K sequential read/write operations, read many times, and written once/few
Notes:
- The creation of one or more PVCs require a PersistentVolume (PV) to already exist of that storage type (speed, for example), but with Domino always the type ReadWriteOnce, typically mapped to GlusterFS or NAS storage.
- A ReadWriteOnce PVC can only bind to a ReadWriteOnce PV. Domino requires claims (PVCs) and Persistent volumes (PVs) be ReadWriteOnce, meaning that only one pod's container(s) have exclusive access to read and write to it. We cannot put 20 domino server PVCs in one PV. It's a one-to-one allocation.
- Once the first PVC binds to a PV, the PV is bound/taken until that PVC (e.g. Domino server/app) is destroyed.
- If there are separate binding locations (e.g. /local/notesdata, local/NIF, and local/FT, they will each be a PVC needing each a PV.
Single Domino PersistentVolumeClaim:
For a smaller server that services a smaller community, one /local PVC is sufficient.
Notes:
- To map to the PV, update the PVC to use the same storageClassName to the PV to use. The PV will be of larger size than the PVC, but because of the ReadWriteOnce, cannot be used for more than 1 PVC, so keep the PV only reasonably larger, for growth, than the PVC needed.
- To keep straight on which PVC goes with each domino server, and because the PVC name has to be unique w/in the project, we use the naming convention: mwdomNN-local-path-pvc, for the pvc, and the name of the Domino server (app) as mwdomNN-local-sc, where local is the local container mapping, and sc is the storage class that maps the PVC to its PV.
- Customize the PVC (update the namespace, the name, and the storage:
$ vi ~/mwdom01-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mwdom01-local-path-pvc
namespace: mwdom
spec:
storageClassName: mwdom01-local-sc
accessModes:
- ReadWriteOnce
volumeMode: Filesystem
resources:
requests:
storage: 24Gi
/
- Login, and create the PVC:
$ oc login -u mwadminid <host>
<enter password>
$ oc apply -f mwdom01-pvc.yaml
<confirmed created successfully>
Note:
- Confirm the PVC moves from pending and finds a suitable PV.
previous page
|