What is PersistentVolume?
A PersistentVolume is a piece of storage in a cluster. You can store your application data into this volume. After you deploy an application, the different components of application run inside separate Pods. A Pod is a process running inside the cluster. For Pods to start using the volume, it must be claimed with its claim reference for the PersistentVolumeClaim.
What is PersistentVolumeClaim?
A PersistentVolumeClaim is the request for storage from the user to the PersistentVolume. The claim searches for the volume based on the specification you mentioned in the claim such as size, access modes, reference name and so on and binds the claim with the volume.
Creating PersistentVolume for Cloud Application Business Insights
To install Cloud Application Business Insights application (ICABI) on IBM Cloud Private (ICP), you must create PersistentVolumes. To store the application data into the database, create PersistentVolume and refer it to icabi-db-storage claim. To store the Connector data, create a PersistentVolume and refer it to icabi-connector-storage claim.
A PersistentVolume object is a storage resource in cluster. Storage must be provisioned by creating PersistentVolume objects from sources such as GCE Persistent Disk, AWS Elastic Block Store (EBS), and Network File System (NFS), iSCSI, or a cloud-provider-specific storage system.
Note: You can choose any storage type to create the PersistentVolume.
Before you Begin
Ensure to load, tag and push the database, UI, Connector, and optionally Cloud App Management Service Data Collector Docker images to IBM Cloud Private private Docker registry to install the Cloud Application Business Insights on IBM Cloud Private.
For more information, see:
Follow these steps to create PersistentVolume using Network File System server:
Note: Create two .yaml files, one for database and another for Connector.
1. Create .yaml files and place it on the machine from where you plan to deploy your application.
2. Copy the following code snippet in the .yaml files and modify the <claim_ reference_name> and <namespace_name> parameter:
For database, modify <claim_reference_name> as icabi-db-storage and <namespace_name> as icabi
For Connector, modify <claim_reference_name> as icabi-connector-storage and <namespace_name> as icabi
3. Run the following command to create the configured PersistentVolumes by using kubectl uility, as follows:
kubectl -f apply $<file-path>/persistent-volume-db.yaml
kubectl -f apply $<file-path>/persistent-volume-connector.yaml
4. To check if the PersistentVolume is in bound state with PersistentVolumeCliam, run the following command:
kubectl get pv task-pv-volume
The PersistentVolumeClaims for database and Connector are provided in the installation package. The Kubernetes control plane looks for a PersistentVolume that satisfies the claim’s requirements. The control plane finds a suitable PersistentVolume and binds the claim to the volume. Hence, in the output for this command the status of PersistentVolume must be in Bound state.
What to do next
Install the Could Application Business Insights by using standard deployment or advanced deployment.
For more information, see Cloud Application Business Insights deployment options.