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 deploying 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 presentation server:

Install the Vision.Presentation, Vision.Applications, Cluster.Master, and Cluster.Worker roles by running the following command as the root user:
```
$A1BASEDIR/bin/Package install-role Vision.Presentation, Vision.Applications, 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.
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 and 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, Vision.Applications, Cluster.Master, Cluster.Worker, Presentation.Internal, Database.Assure1
```
Prepare the microservice cluster by doing one of the following as the root user:
- If you do not already have a microservice cluster on the presentation server, create one for Vision:
```
$A1BASEDIR/bin/cluster/clusterctl create VisionCluster --no-zone --namespace a1-vision --host <pri_pres_server_host>
```
  Note:
  
  The --no-zone, --namespace, and --host options ensure that the cluster is created with the Vision namespace only, and that only the presentation server host is added to the cluster.
  
  You can optionally change the cluster name from VisionCluster to any value that makes sense for your environment.
- If you already have a microservice cluster on the presentation server, add the Vision namespace to the cluster:
```
$A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision
```

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

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

Update the Unified Assurance Helm repository:
```
a1helm repo update
```
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).
Verify that all pods are running by running the following command:
```
a1k get pods -n $VISIONNAMESPACE
```
When all pods are running, continue.
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>.
Verify that all pods are running by running the following command:
```
a1k get pods -n $VISIONNAMESPACE
```

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 collection servers:

Install the following roles on all collection servers, even those where you are not installing Vision:
```
$A1BASEDIR/bin/Package install-role Vision.Config, Cluster.Master, Cluster.Worker
```

Run the following command to update the clusters:

/opt/assure1/bin/cluster/clusterctl update-config

On each microservice cluster where the Event Canal microservice is deployed, add the Vision namespace by running the following command as the root user:
```
$A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision
```
Note:

If you only have one collection cluster, you only add the namespace once. If you have multiple collection clusters, you must run the command on a server in each cluster to add the namespace to each cluster. For example, if you have three separate clusters for three separate device zones, you must run the command three times; once for each cluster.

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

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

Update the Unified Assurance Helm repository:
```
a1helm repo update
```
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>.
Verify that all pods are running by running the following command:
```
a1k get pods -n $VISIONNAMESPACE
```

Check the Vision Event microservice logs for ERROR messages:

a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/vision-event/ {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.

Title and Copyright Information

Installation Guide

G36445-01