Use case 3: Snapshot with PowerFlex CSI
Use case 3: Snapshot with PowerFlex CSI
-
This use case describes how to take a screenshot with PowerFlex CSI:
- Pod 1 is deployed with MySQL database, and a PVC volume is provisioned in the lab environment.
- A sales database is created by logging in to the MySQL instance
- Fresh data is inserted into the sales database
- A snapshot of Pod 1 is created
- MySQL Database is deployed in Pod 2
- A snapshot of Pod 1 to Pod 2 is attached.
- Database queries validate the attached snapshot on Pod 2.
- The following YAML file is used to deploy the MySQL Database Pod 1 with the PVC:
apiVersion: v1
kind: Service
metadata:
name: mysql
spec:
ports:
- port: 3306
selector:
app: mysql
clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mysql
spec:
selector:
matchLabels:
app: mysql
strategy:
type: Recreate
template:
metadata:
labels:
app: mysql
spec:
containers:
- image: mysql:5.6
name: mysql
env:
# Use secret in real usage
- name: MYSQL_ROOT_PASSWORD
value: password
ports:
- containerPort: 3306
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: mysql-pv-claim
- The following YAML file is used to provision the PVC:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mysql-pv-claim
spec:
storageClassName: vxflexos
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 8Gi
- The following figure shows the deployed MySQL Pod 1 with PVC:
Figure 26. Pod 1 MySQL Deployment with PVC volume
- Logged in to the MySQL instance and created a database that is named sales, as shown in the following figure:
Figure 27. Create Sales database
- The values are inserted to the sales database, and a snapshot is created for the MySQL Pod 1.
- The following YAML file is used to create a snapshot of the PVC:
apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshot
metadata:
name: mysql-pv-claim-snap1
namespace: default
spec:
volumeSnapshotClassName: vxflexos-snapclass
source:
persistentVolumeClaimName: mysql-pv-claim
- The following YAML file is used to deploy the MySQL Database Pod 2 with PVC:
apiVersion: v1
kind: Service
metadata:
name: mysql-2
spec:
ports:
- port: 3307
selector:
app: mysql
clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mysql-2
spec:
selector:
matchLabels:
app: mysql
strategy:
type: Recreate
template:
metadata:
labels:
app: mysql
spec:
containers:
- image: mysql:5.6
name: mysql
env:
# Use secret in real usage
- name: MYSQL_ROOT_PASSWORD
value: password
ports:
- containerPort: 3307
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: mysql-pv-claim-snap1
- The following YAML file is used for provisioning the persistent volume claim:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mysql-pv-claim-snap1
spec:
storageClassName: vxflexos
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 8Gi
- During the PVC provisioning, Pod 2 is provisioned using the Pod 1 Snapshot as follows:
Figure 28. Pod 2 Deployment
- Database queries are run on Pod 2 to validate database entries as shown in the following figure:
Figure 29. Attached Pod 1 PVC to Pod 2
- The sales database with the entries can be retrieved on Pod 2.