Trigger Deployment Using the tcxctl CLI

This section provides instructions to trigger the deployment of VMware Telco Cloud Service Assurance on Azure using the tcxctl CLI.

Trigger deployment using tcxctl CLI.

root [ ~/base/tcx-deployer/clis ]# ./tcxctl deploy all --name tcsa --path <$TCSA_WORK_SPACE>/
tcx-deployer --kubeconfig <your-kubeconfig-location> --registry <harbor-registry-fqdn>/
<project-name> --registry-password <harbor-registry-password> --registry-username <harbor-
registry-username> --timeout <time-in-mins>

Note: You can specify 90 minutes for the timeout value. If there is any latency in the network, you can increase this value.

After the deployment script exits, manually check the VMware Telco Cloud Service Assurance deployment status by running the following command from deployment VM.

root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct 
 OR
root [ ~/base/tcx-deployer/scripts ]# kubectl get apps

For all the apps, the reconciliation status must be successful.

root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct
NAME   STATUS            READY   MESSAGE                               AGE
tcsa   updateCompleted   True    All App CRs reconciled successfully   30h

Note: After successful deployment, you can launch the VMware Telco Cloud Service Assurance UI. For more information, see Accessing VMware Telco Cloud Service Assurance UI topic.

If all the apps are not reconciled, the deployment fails. For more information, see VMware Telco Cloud Automation Installation Issue in the VMware Telco Cloud Service Assurance Troubleshooting Guide.