Installing Vision on Multiple Servers

You can install Oracle Communications Unified Assurance Vision components on multiple servers.

The Vision and Vision Web microservices must be deployed to a presentation server. The Vision Event microservice can be deployed to any server. This document describes it to a collection server.

Before beginning the steps in this procedure, ensure you have met all prerequisites described in Vision Installation Prerequisites.

Note:

In the commands, a1k is an alias for the standard kubectl commands and a1helm is an alias for the standard helm commands. These must be run as the assure1 user.

Installing Vision Presentation Server Components

To install the Vision and Vision UI microservices on presentation servers, do the following on the primary and redundant presentation servers:

  1. Install the Vision.Presentation, Cluster.Master, and Cluster.Worker roles by running the following command as the root user:

    $A1BASEDIR/bin/Package install-role Vision.Presentation, Cluster.Master, Cluster.Worker

    You will see an error about the Presentation.Internal role, regardless of whether you installed it using SetupWizard on this presentation server as part of the initial Unified Assurance installation.

  2. Confirm that this is an internal presentation server. Then install the roles, including their dependencies, by running the following command as the root user:

    Caution:

    Run the following command on an internal presentation server only, where the Presentation.Internal, Database.Assure1 roles have already been installed. The command includes these roles to pass dependency checks, but to avoid breaking your system, you must not install these roles on any other server type.

    $A1BASEDIR/bin/Package install-role Vision.Presentation, Cluster.Master, Cluster.Worker, Presentation.Internal, Database.Assure1

  3. Add the Vision namespace to the microservice cluster by running the following command as the root user:

    $A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision

  4. Switch to the assure1 user and create the following environment variables:

    su - assure1
export VISIONNAMESPACE=a1-vision
export WEBFQDN=<Primary Presentation Web FQDN>

  5. Update the Unified Assurance Helm repository:

    a1helm repo update

  6. Deploy the Vision microservice:

    a1helm install <microservice-release-name> assure1/vision -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN

    where <microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (vision) unless you are deploying multiple instances of the microservice to the same cluster.

  7. Verify that all pods are running by running the following command:

    a1k get pods -n $VISIONNAMESPACE

    When all pods are running, continue.

  8. Deploy the Vision Web microservice:

    a1helm install <microservice-release-name> assure1/vision-web -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN

    Oracle recommends using the microservice name (vision-web) for <microservice-release-name>.

  9. Verify that all pods are running by running the following command:

    a1k get pods -n $VISIONNAMESPACE

  10. Check the Vision Web microservice logs for ERROR messages:

    a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/vision-web/ {print $1;exit}') -n $VISIONNAMESPACE

The Vision and Vision Web microservice installation is complete. Proceed to Installing Vision Collection Server Components.

Installing Vision Collection Server Components

To install the Vision Event microservice on a collection server:

  1. Install the Vision.Config, Cluster.Master, and Cluster.Worker roles by running the following command as the root user:

    $A1BASEDIR/bin/Package install-role Vision.Config, Cluster.Master, Cluster.Worker

  2. Add the Vision namespace to the microservice cluster by running the following command as the root user:

    $A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision

  3. Switch to the assure1 user and create the following environment variables:

    su - assure1
export VISIONNAMESPACE=a1-vision
export WEBFQDN=<Primary Presentation Web FQDN>

  4. Update the Unified Assurance Helm repository:

    a1helm repo update

  5. Deploy the Vision Event microservice:

    a1helm install <microservice-release-name> assure1/vision-event -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN

    Oracle recommends using the microservice name (vision-event) for <microservice-release-name>.

  6. Verify that all pods are running by running the following command:

    a1k get pods -n $VISIONNAMESPACE

  7. Check the Vision Event microservice logs for ERROR messages:

    a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/assure1-consumer/ {print $1;exit}') -n $VISIONNAMESPACE
a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/event-consumer/ {print $1;exit}') -n $VISIONNAMESPACE
a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/event-enrichment/ {print $1;exit}') -n $VISIONNAMESPACE

The Vision installation is complete. You can access Vision in the Unified Assurance UI by selecting Vision from the Analytics menu.