Deploying Telco Cloud Automation 3.2 – Part 1

In this post, I’ll walk you through the deployment of Telco Cloud Automation (TCA) version 3.2 as part of a TCP 5.0 setup.

  1. Before deploying the TCA appliance, make sure there’s an NTP and DNS server already configured in your network.
  2. Below are the hardware requirements according to Broadcom

In my setup, I’m deploying TCA directly on vCenter Server 8.0.
I’ve downloaded the OVA file: VMware-Telco-Cloud-Automation-3.2.0-24287523.ova.

Providing Name for the Manager VM

Selecting a cluster or a host to deploy

We need to deploy TCA manager first

Selecting the desired datastore and Thin provisioning to save space

Selecting the network

Providing password for the root, admin and tca user . in order to manage and do the initial configuration we need the tca user

Providing IP info for the first network adapter, be careful here if you provide the secondary IP address in a same range as the primary one after deployment the deployment script (deplpy-tca.sh) will be failed and sometime get ” Failed to start tca deployment service” . I face this issue and spend some time on that. In my case just providing Primary IP was enough.

NTP and DNS are mandatory for the deployment

After powering it on, it may take some time for all services to become fully operational.
You can check their status using the following command:

kubectl get deployments -n tca-mgr --watch 
or
kubectl get deployments -n tca-mgr

As you see all the containers are up

Lets check login into management (https://192.168.5.190:9443/login.jsp) via tca/passowrd credential

Select your location:

Settin a System name or leave it to be selected automatically:

Selecting Authentication provider, I would go with vCenter

In the next step you need to provide the SSO / PSC URL in my case it would be vCenter server URL:

I skip the log management for now

Now I’m done with initial configuration

Leave a Reply

Your email address will not be published. Required fields are marked *

5 + = 14