A containerized Aria Operations Management Pack has the following two components:

  1. .pak file which contains static resources like dashboards and images.

  2. adapter container image that runs on the cloud proxy VM to fetch data from the TCA appliance.

Note:

You can download the .pak file from the VMware market place.

In deployments where Aria Operations is connected to the internet, after the .pak file is downloaded, the adapter container image is downloaded by the cloud proxy from a public image repository. You can change the image repository that a given Aria Operations instance points to by navigating to Administration > Global Settings > System Settings > Docker image default registry URL.

Use the URL vmwaresaas.jfrog.io/tca-docker-dev-docker-local for deployments that can connect to the internet.

In the scenarios where Aria Operations is deployed in an airgap environment, the container image must be uploaded to an image repository (for example, Harbor) from where the cloud proxy can download the container image.

Upload container image to harbor hosted in airgap environment (Aria Operations and harbor are in same airgap environment)

  1. Note the of DIGEST value in TelcoCloudAutomation.conf file from the marketplace files.

  2. SSH into jump box which has internet connectivity and connectivity to the airgap environment.

    1. Docker pull vmwaresaas.jfrog.io/tca-docker-dev-docker-local/tca-vrops-mgmt-pack@<<digest value>>

    2. Note the IMAGE ID of the above image what was downloaded.

    3. docker tag <<IMAGE ID>> <<image_repo_ip:port>>/tca-vrops-mgmt-pack/tca-vrops-mgmt-pack:vrops-1-0-0

      • Example: docker tag e970cd69b0b2 1.2.3.4:8043/tca-vrops-mgmt-pack/tca-vrops-mgmt-pack:vrops-1-0-0

    4. docker tag <<IMAGE ID>> <<image_repo_ip:port>>/tca-vrops-mgmt-pack/tca-vrops-mgmt-pack:vrops-1-0-0

      • Example: docker push 1.2.3.4:8043/tca-vrops-mgmt-pack/tca-vrops-mgmt-pack:vrops-1-0-0

      This will push the container to the image repository.

If you encounter any untrusted certificate issues while pushing from jumpbox to remote registry using docker due to certificate issues, perform the following steps:

  1. Run vi /etc/docker/daemon.json.

  2. Add insecure-registries : [airgaphost:port].

  3. Restart docker.

Change registry URL in Aria Operations

To change the registry URL in Aria Operations:

  1. In Aria Operations, navigate to Administration > Global Settings > System settings.

  2. Change Docker image registry URL to the harbor value (For example, 1.2.3.4:8043/tca-vrops-mgmt-pack).

Add harbor url to daemon.json in cloud proxy instance

If the harbor instance is using a self-signed certificate, the docker daemon running in the proxy instance must skip certificate checks so that the docker image can be downloaded on the cloud proxy.

  1. vi /etc/docker/daemon.json.

  2. Add insecure-registries : [airgaphost:port].

  3. Restart docker.

Note:

Cloud proxy can get disconnected when the above process is complete. To bring back the cloud proxy to an online state, follow the troubleshooting steps mentioned in Cloud Proxy Troubleshooting.