Stopping and Starting the Cluster while Keeping the Cluster State Intact

It is possible to stop and start a cluster while keeping the cluster state intact.

Stopping a Cluster

To stop the Mashery Local cluster, run the 'stop-tml-cluster.sh' script:

For example: 
user-MBP:manifest-single-zone user$ ./stop-tml-cluster.sh
secret "cm-property" deleted
secret "cm-jks" deleted
secret "cm-crt" deleted
secret "cm-key" deleted
deployment.apps "cm-deploy-0" deleted
secret "tm-property" deleted
secret "tm-jks" deleted
deployment.apps "tm-deploy-0" deleted
secret "cache-property" deleted
statefulset.apps "cache-set-0" deleted
secret "sql-property" deleted
statefulset.apps "mysql-set-0" deleted
secret "log-property" deleted
statefulset.apps "log-set-0" deleted
secret "nosql-property" deleted
statefulset.apps "cass-set-0" deleted
service "cm-svc-0" deleted
service "tm-svc" deleted
service "cache-svc-0" deleted
service "mysql-svc-0" deleted
service "log-svc-0" deleted
service "cass-svc-0" deleted

Persistent Volumes Check

Persistent volumes should be in 'Bound' state after stopping the cluster.

For example: 
user-MBP:manifest-single-zone user$ kubectl get pvc 
NAME                   STATUS          VOLUME        CAPACITY         ACCESSMODES        STORAGECLASS          AGE cachevol-cache-set-0-0 Bound  cache-1-local-pv-node-1   2Gi              RWO            cache-storage-class     9m logvol-log-set-0-0     Bound  log-1-local-pv-node-1     2Gi              RWO            log-storage-class      11m nosqlvol-cass-set-0-0  Bound  cass-1-local-pv-node-1    2Gi              RWO            nosql-storage-class    13m sqlvol-mysql-set-0-0   Bound  db-1-local-pv-node-1      2Gi              RWO            sql-storage-class      10m

Starting a Cluster

To start the Mashery Local cluster, run the 'start-tml-cluster.sh' script:

For example: 
user-MBP:manifest-single-zone user$ ./start-tml-cluster.sh 
 
Starting cassandra service.
service/cass-svc-0 created
Deploying cassandra pods.
secret/nosql-property created
statefulset.apps/cass-set-0 createdcass-set-0-0   0/1     Running   0          10scass-set-0-0   0/1     Running   0          15scass-set-0-0   1/1     Running   0          20sStarting CM service.
service/cm-svc-0 created
Deploying CM pods.
secret/cm-property created
secret/cm-jks created
secret/cm-crt created
secret/cm-key created
deployment.apps/cm-deploy-0 createdcm-deploy-0-86c7d7dcbf-zz7kt   1/1     Running   0          10s
 
Starting log service.
service/log-svc-0 created
Deploying log pods.
secret/log-property created
Error from server (AlreadyExists): secrets "log-resource" already exists
statefulset.apps/log-set-0 createdlog-set-0-0                    0/1     ContainerCreating   0          0slog-set-0-0                    1/1     Running   0          5s
 
Starting DB service.
service/mysql-svc-0 created
Deploying DB pods.
secret/sql-property created
statefulset.apps/mysql-set-0 createdmysql-set-0-0                  0/1     ContainerCreating   0          1smysql-set-0-0                  1/1     Running   0          6s
 
Starting memcache service.
service/cache-svc-0 created
Deploying memcache pods.
secret/cache-property created
statefulset.apps/cache-set-0 createdcache-set-0-0                  0/1     ContainerCreating   0          0scache-set-0-0                  1/1     Running   0          5s