Installing Vision on a Single Server
You can install all Oracle Communications Unified Assurance Vision components on a single server, in a single server installation of Unified Assurance.
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.
To install Vision on a single server:
-
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
-
Switch to the assure1 user and create the following environment variables:
su - assure1 export VISIONNAMESPACE=a1-vision export WEBFQDN=<WebFQDN>
where <WebFQDN> is the fully-qualified domain name of the primary presentation server for the cluster.
-
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 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
When all pods are running, continue.
-
Check the Vision Event microservice logs for ERROR messages:
a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/vision-event/ {print $1;exit}') -n $VISIONNAMESPACE
-
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
When all pods are running and there are no error messages, the Vision installation is complete. You can access Vision in the Unified Assurance UI by selecting Vision from the Analytics menu.