Configure VMware Telco Cloud Automation Control Plane (TCA-CP).

Prerequisites

You must have selected VMware Telco Cloud Automation - Control Plane as the role and activated it.

Note:
  • Import self-signed certificates from the Administration > Trusted CA Certificates tab.
  • Active Directory is not supported for TCA-CP.

Procedure

  1. In the system location screen, enter the location where you are deploying the system.

    Select the nearest major city to where the VMware Telco Cloud Automation system, is geographically located. VMware Telco Cloud Automation sites are represented visually in the Dashboard.

  2. Click Continue.
    A screen appears prompting you for a system name.
  3. Enter the system name, and click Continue.
    A screen appears prompting you to select the cloud instance type.
  4. Select the cloud instance to which TCA-CP is connected: vSphere, vCloud Director, VMware Integrated OpenStack, or Kubernetes. Click Continue.
    Note: TCA-CP can connect to only one cloud instance per deployment.
  5. Enter the configuration details of the selected cloud instance.
    After entering the information, click Continue to proceed to the next screen.

    Cloud Instance

    Configuration Parameters

    vSphere
    1. Enter the vCenter Server and NSX details:
      1. vCenter Server
        • vCenter URL
        • User name
        • Password
      2. Enter the NSX details:
        • NSX URL
        • User name
        • Password
    2. Enter the SSO details:
      • vCenter Server or Platform Services Controller URL
    3. Enter the VMware vSphere role-mapping details.
    4. Enter the vRealize Orchestrator details.

    VMware Cloud Director
    1. Enter the VMware Cloud Director details.
      • VMware Cloud Director URL
      • System Administrator user name
      • System Administrator password
    2. Enter the vCenter Server and NSX details.
      Note: TCA-CP fetches the vCenter Server and NSX URLs automatically.
      1. vCenter Server
        • User name
        • Password
      2. NSX
        • User name
        • Password
    3. Enter the AMQP details:
      Note: TCA-CP fetches the AMQP parameters automatically. Edit the parameters as appropriate.
      • AMQP Hostname
      • Port
      • vHost
      • User name
      • Password
      • Use SSL
    4. Enter the vRealize Orchestrator details.

    VMware Integrated OpenStack
    1. Skip the OMS configuration.
    2. Enter the Keystone URL and port number.
    3. Enter the Domains and Projects details:
      Note: You can add Multiple VMware Integrated OpenStack Domains and Projects.
      1. Add New Domain.

        For each Domain, provide the following details.

      • Domain Name (select from drop-down)
      • User name
      • Password
      • Projects (optional)

        For each Domain, you can add multiple Projects.

        • Project Name (select from drop-down)
        • User name
        • Password
    4. Enter the vCenter and NSX details:
      1. vCenter Server
        • vCenter URL
        • User name
        • Password
      2. NSX
        • NSX URL
        • User name
        • Password
      Note: If you have configured VMware Integrated OpenStack with multiple compute vCenter Servers, add all the vCenter Servers to TCA-CP.
    5. By default, external access to RabbitMQ Advanced Message Queuing Protocol (AMQP) is disabled in VMware Integrated OpenStack. To enable RabbitMQ, perform the following steps:
      1. Log in to the OMS server through SSH and run the following command:
        kubectl edit service rabbitmq -n openstack
      2. Update the type from ClusterIP to NodePort.
      3. Fetch the port number on which RabbitMQ is running. Run the following command:
        kubectl get svc -n openstack  | grep 'rabbitmq '| awk {'print$5'} | cut -d'/' -f1| cut -d':' -f2
      4. The user name to enter into RabbitMQ is rabbitmq.
      5. To fetch the password, run the following command: 
        kubectl -n openstack get secret managedpasswords -o yaml  | grep rabbit_password | awk {'print $2'} | base64 –decode
        The vHost value is / always.
    6. Enter the vRealize Orchestrator details.

    Kubernetes
    1. URL - Kubernetes Master API Server URL.
    2. Cluster Name - Logical name that uniquely identifies this cluster.
    3. Kubernetes Configuration - The kubeconfig YAML file for authentication.
    4. Enter the vRealize Orchestrator details.

    Microsoft AKS

    1. Select TCA instance type to configure as Microsoft AKS.

    2. Provide the following details:

      1. Cluster Name - The name assigned to a specific cluster during cluster creation

      2. User Name - Service principal (App Registration) Id.

      3. Password - Client secret associated with the Service Principal.

      4. Resource Group - A logical container for organizing and managing Azure resources.

      5. Tenant Id - A unique identifier for the Azure tenant. Every Azure account is associated with a specific tenant.

      6. Subscription Id - A unique identifier for the Azure subscription.
  6. Review the system summary information.
    The system verifies the configuration and then generates a configuration summary.
  7. To reload the system, click Restart.
    It can take several minutes to reinitialize the system completely. During this process, the appliance management interface is not available.
    To schedule a restart, click Restart Later.

Results

After the system reloads, it displays the appliance management dashboard. For more information about the dashboard, see Understanding the Appliance Management Dashboard.

What to do next

For information on using VMware Telco Cloud Automation, see the VMware Telco Cloud Automation User Guide.