http://localhost:8080/openshift_netapp/4.persistence/index.html Key Terms StorageClass - Describes and classifies storage that can be requested. ContainerStorageInterface - Enables storage vendors to develop a plugin once and have it work across a number of container orchestration (CO) systems. Trident - An open-source project that NetApp maintains for application container persistent storage. PersistentVolume - A piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using Storage Classes PersistentVolumeClaim - A request for storage by a user, specifying information like size and access mode Hugo en-us Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/ext_netapp_trident/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/ext_netapp_trident/index.html Before storage can be dynamically provisioned a storage class and the matching container storage interface CSI must be deployed to the cluster. This is typically performed once for the entire cluster and centrally managed by systems administrators. For the purpose of this lab we have already deployed the Trident CSI, the documentation outlining that process can be found here. Once the CSI has been created we will need to configure a tridentbackend. This tells Trident how to connect to the NetApp backend and what type of volumes to provision. A single Kubernetes cluster can have multiple tridentbackends, each of which can be used to create a Storage Class. http://localhost:8080/openshift_netapp/4.persistence/storage_classes/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/storage_classes/index.html Let’s take a quick look at our Storage Classes. oc get sc You’ll see storage classes listed along with their provisioner. The storage class can be named whatever the system adminsitrator who created it prefers but the provisioner describes the technical backbone behind it, in this case you’ll notice the netapp-cloud-csi storage class is provisioned by the netapp.io/trident provisioner. In production you may have mutliple storage classes using the same provisoner. For example, you may define storage classes for different reliability or performance levels that are all provisioned on the same infrastructure. Alternatively you may have one set of storage classes which are provisioned on Cloud Volumes and another set which are provisioned on local NetApp storage, all of which would use the same provisioner. http://localhost:8080/openshift_netapp/4.persistence/provision_and_mount/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/provision_and_mount/index.html Recall from lab 4 that our Nexus instance lost our repository when we restarted the pod. We’re going to fix that by mounting a PersistentVolume on our NetApp to the directory where Nexus stores repository data. Let’s start by browsing over to our App in the Openshift Console. Return to the topology view by clicking Workloads -> Topology then selecting your workspace project. Select the Nexus deployment then click the “nexus” link to open the DeploymentConfig. http://localhost:8080/openshift_netapp/4.persistence/lifecycle_revisited/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/lifecycle_revisited/index.html Our volume is simply presented within the pod like any other mount. For example, open a terminal back into your pod and run the following mount | grep sonatype-work You’ll see a line that says something along the lines of the following 10.1.0.4:/trident--demo-myuser-nexus-storage-69339 on /sonatype-work type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.1.0.4,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr=10.1.0.4) Let’s test it out Now we’ll browse back over to our Nexus console at https://nexus--workspace.apps.aegis-core.fdlabs.dev/nexus/ and repeat the steps from Lab 3 to create a new hosted repository. http://localhost:8080/openshift_netapp/4.persistence/snapshots/index.html Tue, 05 May 2020 13:15:09 -0400 http://localhost:8080/openshift_netapp/4.persistence/snapshots/index.html NetApp has the capability to snapshot volumes and revert back to those snapshots without taking the volume down. Let’s use the capability to resolve an issue introduced by a user who accidentally deletes an import file from our repository. Before we break anything we’ll need to take a snapshot of our volume. Now lets browse back over to our Nexus repository, click on “Repositories” in the menu on the left, then select our repository from the list and open the “Browse Storage” tab.