Trigger Deployment Using the Installation Script on Production Footprint

This section provides instructions to trigger the deployment of VMware Telco Cloud Service Assurance on production footprint using the installation script.
  • Run the below command, to trust the Harbor Self-signed certificate:
    trust anchor /etc/docker/certs.d/<HarborIP>/ca.crt
    • If the
      trust
      command is not available, then install
      p11-kit-trust
      package, which contains
      trust
      command.
If you do not want to specify the registry user name and password in the installation script, perform registry login by running the following command:
docker login <harbor-fqdn> --compat-auth-file=/root/.docker/config.json
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 the installation script
export TCSA_WORK_SPACE=/root/base root [ ~ ]# cd $TCSA_WORK_SPACE/tcx-deployer/scripts root [ ~/base/tcx-deployer/scripts ]# ./installTCSA.sh --kubeconfig <your-kubeconfig-location> --registry-cert <harbor-registry-cert-path> --registry <harbor-registry-fqdn>/<project-name> --registry-password <harbor-registry-password> --registry-username <harbor-registry-username> --timeout <timeout in minute>
  • Ensure that the
    --registry-password
    is passed inside single quotation if you are passing this to the installation script.
  • The
    <project-name>
    specified in the registry URL will be automatically created with the same name in Harbor registry during deployment.
  • You can specify 120 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 -A OR root [ ~/base/tcx-deployer/scripts ]# kubectl get apps -A
For all the apps, the reconciliation status must be successful.
root [ ~/base/tcx-deployer/scripts ]# kubectl get tcxproduct -A NAME STATUS READY MESSAGE AGE tcsa updateCompleted True All App CRs reconciled successfully 12h tps-tcx-platform-services updateCompleted True All App CRs reconciled successfully 13h