Trigger Deployment Using the Installation Script on demo footprint using the tcxctl CLI
tcxctl
CLI This section provides instructions to trigger the deployment of VMware Telco Cloud Service Assurance on demo footprint using the
tcxctl
CLI.- Run the below command, to trust the Harbor Self-signed certificate:trust anchor /etc/docker/certs.d/<HarborIP>/ca.crt
- Iftrustcommand is not available, then installp11-kit-trustpackage which containstrustcommand.
If you do not want to specify the registry user name and password in the installation script, perform Docker login. To login to Docker, run the following command:
docker login <harbor-fqdn>
Ensure that the
--registry-password
does not have the comma character in it. If the comma is used, escape it using the backslash.Trigger deployment using
tcxctl
CLI.
root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/clis root [ ~/base/tcx-deployer/clis ]# ./tcxctl deploy all --name tcsa --path $TCSA_WORK_SPACE/tcx-deployer --kubeconfig /root/.kube/<cluster-name> --registry <HarborIP>/tcx --registry-password TCXAdmin123 --registry-username admin --registry-cert /etc/docker/certs.d/<HarborIP>/ca.crt --timeout <time-in-mins>
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 [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct OR root [ ~/tcx-deployer/scripts ]# kubectl get apps
For all the apps, the reconciliation status must be successful.
root [ ~/tcx-deployer/scripts ]# kubectl get tcxproduct NAME STATUS READY MESSAGE AGE tcsa updateCompleted True All App CRs reconciled successfully 30h
After successful deployment, you can launch the VMware Telco Cloud Service Assurance UI. For more information, see Accessing UI topic.