mugithi / meetup-may-15-18

PLAN OF THE DAY

Address

675 Campbell Technology Parkway, Campbell CA, Suite 100

Wireless

• SSID: DT-Meetup
• Password: dasher@meetup

Agenda

5:30 PM: Social Networking:

6:00 – 6:30 PM: Isaack

• Different container storage options available today (Q1 2018) for the - enterprise storage administrator
• The current state of Kubernetes Project and Storage (Storage SIG)
• Kubernetes Flex Volumes and CSI
• Helm chart - on-prem variable - cloud variable
• Demo of Kubernetes Flex Volumes with an Enterprise Storage Array
• Dynamic provisioning
• Cloning workflow of production MYSQL databases for test & dev use case

7:00 - 7:30: Josh

• Managing Kubernetes on AWS the easy way

Pizza and Beer will be provided

At the end of the meetup we will be raffling away Google AYI kits

MEETUP DORY IMPLEMENTATION

1. Installation documentation

Link to Isaack's guide Installation documentation

2. Installed components

• The kube-storage-controller(FlexVolume)

kubectl get po --namespace=kube-system | grep kube-storage-controller

• Tailing the logs

kubectl log kube-storage-controller-doryd-d4676c4db-jvhtm -n kube-system -f

MEETUP DEMO

1. Inspect the Nimble storage kubernetes storage class

---
# Source: meetup/templates/mysql-db-storageclass.yaml
apiVersion: storage.k8s.io/v1beta1
kind: StorageClass
metadata:
  name: wordpress-meetup
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: hpe.com/nimble
parameters:
    thick: "false"
    dedupe: "false"
    perfPolicy: "SQL Server"
    destroyOnRm: "true"
    mountConflictDelay: "30"
    folder: "kubernetes"
    protectionTemplate: "Retain-30Daily"

2. Create the storage class that references Nimble Storage

kubectl apply -f part1/wordpress-storage-class.yaml

3. Inspect the Storage class

• Review the storage class to be created

kubectl get storageclass 
kubectl edit storageclass wordpress-meetup
kubectl describe sc  wordpress-meetup

• Review the Nimble

Path to Nimble URL

3. Inspect the helm chart that is being used to deploy initial chart

• path to meetup-helm-chart
• Review that there is NO storageClass defined in the helm chart - needs to be pre-created
• Review the values enviroment option , dc1 (hardcoded) and aws

4. Perform the helm chart dry run to see the output

helm install --name meetup-demo-01 --dry-run --debug meetup-helm-chart

5. Install the helm chart

• Before installating the chart review logs on the kube-controller and search for

kubectl log kube-storage-controller-doryd-d4676c4db-jvhtm -n kube-system -f

action=POST path=http://unix/VolumeDriver.Create payload

• Install the helm chart with the dc1 enviromental variable set

helm install --name wordpress-meetup-01  --set environment="dc1" meetup-helm-chart

7. Review the volumes that are created

• Review the PVC and PV created

kubectl get persistentvolumeclaim
kubectl edit pvc <pvcname>

• Review the PV

kubectl get pv
kubectl edit pv <pvname>

• Log into the master and review the docker volume

docker volume ls

docker volume inspect <dockervolume>

8. Review the Volume Created on the Nimble

Path to Nimble URL

6. Navigate to the application URL

kubectl get svc

Cloning

1. Determine the volume you are going to clone

kubectl get pvc

2. Add that to the clone storage class

• path to meetup-helm-chart

3. Deploy a new database

kubectl apply -f part2/clone-wordpress-db.yaml