Creating a Local Edition Cluster
Navigate to the appropriate folder, depending on whether you are deploying in a single Azure region or a single Azure VM.
Run the following command to create the
TIBCO Cloud™ API Management - Local Edition cluster:
./create-tml-cluster.sh
Sample output (abbreviated):
storageclass "sql-storage-0" created storageclass "log-storage-0" created storageclass "nosql-storage-0" created storageclass "cache-storage-0" created service "cass-svc-0" created configmap "nosql-property-map" created statefulset "cass-set-0" created cass-set-0-0 0/1 Pending 0 0s cass-set-0-0 0/1 ContainerCreating 0 22s cass-set-0-0 0/1 Running 0 2m cass-set-0-0 1/1 Running 0 2m cass-set-0-1 0/1 Pending 0 1s cass-set-0-0 1/1 Running 0 2m cass-set-0-1 0/1 ContainerCreating 0 7s cass-set-0-0 1/1 Running 0 5m cass-set-0-1 1/1 Running 0 2m cass-set-0-0 1/1 Running 0 6m cass-set-0-1 1/1 Running 0 4m cass-set-0-2 1/1 Running 0 1m service "cm-svc-0" created deployment "cm-deploy-0" created cm-deploy-0-5fd6df9477-gg7rq 0/2 ContainerCreating 0 1s cm-deploy-0-5fd6df9477-gg7rq 1/2 Running 0 1m cm-deploy-0-5fd6df9477-gg7rq 2/2 Running 0 1m service "log-svc-0" created configmap "log-property-map" created statefulset "log-set-0" created log-set-0-0 0/1 Pending 0 1s log-set-0-0 0/1 ContainerCreating 0 23s log-set-0-0 1/1 Running 0 1m log-set-0-1 1/1 Running 0 1m service "mysql-svc-0" created configmap "sql-property-map" created statefulset "mysql-set-0" created mysql-set-0-0 0/1 Pending 0 1s mysql-set-0-0 0/1 ContainerCreating 0 23s mysql-set-0-0 1/1 Running 0 1m service "cache-svc-0" created configmap "cache-property-map" created statefulset "cache-set-0" created cache-set-0-0 0/1 Pending 0 1s cache-set-0-1 0/1 Pending 0 1s cache-set-0-2 0/1 Pending 0 1s cache-set-0-0 0/1 ContainerCreating 0 52s cache-set-0-1 0/1 ContainerCreating 0 52s cache-set-0-2 0/1 ContainerCreating 0 52s cache-set-0-0 1/1 Running 0 1m cache-set-0-1 1/1 Running 0 1m cache-set-0-2 1/1 Running 0 1m service "tm-svc" created configmap "tm-property-map" created deployment "tm-deploy-0" created tm-deploy-0-6794464d9d-26q9m 0/1 Pending 0 0s tm-deploy-0-6794464d9d-6xhwd 0/1 Pending 0 0s tm-deploy-0-6794464d9d-q25ns 0/1 Pending 0 0s tm-deploy-0-6794464d9d-26q9m 0/1 ContainerCreating 0 6s tm-deploy-0-6794464d9d-6xhwd 0/1 ContainerCreating 0 6s tm-deploy-0-6794464d9d-q25ns 0/1 ContainerCreating 0 6s tm-deploy-0-6794464d9d-26q9m 1/1 Running 0 34s tm-deploy-0-6794464d9d-6xhwd 1/1 Running 0 34s tm-deploy-0-6794464d9d-q25ns 1/1 Running 0 34s
To verify the deployment in the Azure Kubernetes Cluster, run the following command,
kubectl get podsSample output:
AME READY STATUS RESTARTS AGE cache-set-0-0 1/1 Running 0 9m cache-set-0-1 1/1 Running 0 9m cache-set-0-2 1/1 Running 0 9m cass-set-0-0 1/1 Running 0 20m cass-set-0-1 1/1 Running 0 18m cass-set-0-2 1/1 Running 0 15m cm-deploy-0-5fd6df9477-gg7rq 2/2 Running 0 14m log-set-0-0 1/1 Running 0 12m log-set-0-1 1/1 Running 0 12m mysql-set-0-0 1/1 Running 0 11m tm-deploy-0-6794464d9d-26q9m 1/1 Running 0 8m tm-deploy-0-6794464d9d-6xhwd 1/1 Running 0 8m tm-deploy-0-6794464d9d-q25ns 1/1 Running 0 8m
Copyright © 2022. Cloud Software Group, Inc. All Rights Reserved.