Vision Multi Server Install Guide¶
Roles¶
The Vision.Presentation, Cluster.Master and Cluster.Worker roles must be installed on the Presentation server(s):
$A1BASEDIR/bin/Package install-role Vision.Presentation, Cluster.Master, Cluster.Worker
The Vision.Config, Cluster.Master and Cluster.Worker roles must be installed on the Collection server(s):
$A1BASEDIR/bin/Package install-role Vision.Config, Cluster.Master, Cluster.Worker
Note
These roles can also be added during installation of a new server by specifying them to SetupWizard.
Deploy the Vision Backend and Web UI¶
Presentation Server¶
-
A microservice cluster and namespace is needed for the Vision UI.
-
If a cluster already exists on the server, the namespace can be added to the existing cluster:
$A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision
-
If a cluster needs to be created and it will only be used for Vision on the presentation server(s), the
no-zone
option should be used:$A1BASEDIR/bin/cluster/clusterctl create --host <SERVER FQDN> --namespace a1-vision --no-zone
-
Otherwise, a cluster must be created if one does not already exist. See the Microservice Cluster Setup guide.
-
-
Switch to the assure1 user and setup the variables used in the rest of steps:
su - assure1 export VISIONNAMESPACE=a1-vision export WEBFQDN=<Primary Presentation Web FQDN>
-
Ensure the helm repo is up-to-date:
a1helm repo update
-
Deploy the Vision core backend apps:
a1helm install vision assure1/vision -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN
-
The following can be used to verify the pods are running. Do not proceed until all show as Running:
a1k get pods -n $VISIONNAMESPACE
-
Deploy the Vision Web UI:
a1helm install vision-web assure1/vision-web -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN
-
The following can be used to verify the pods are running. Do not proceed until all show as Running:
a1k get pods -n $VISIONNAMESPACE
-
The following can be used to check the web UI logs and verify there are no ERROR messages:
a1k logs $(a1k get pods -n $VISIONNAMESPACE | awk '/vision-web/ {print $1;exit}') -n $VISIONNAMESPACE
-
Repeat steps 1 - 8 for the Redundant Presentation server (can be skipped if a redundant presentation server does not exist).
Collection Server¶
-
A microservice cluster and namespace is needed for the Vision applications.
-
If a cluster already exists on the server, the namespace can be added to the existing cluster:
$A1BASEDIR/bin/cluster/clusterctl add namespace --namespace a1-vision
-
Otherwise, a cluster must be created if one does not already exist. See the Microservice Cluster Setup guide.
-
-
Switch to the assure1 user and setup the variables used in the rest of steps:
su - assure1 export VISIONNAMESPACE=a1-vision export WEBFQDN=<Primary Presentation Web FQDN>
-
Ensure the helm repo is up-to-date:
a1helm repo update
-
The pulsar and event-canal microservices are required if they have not been already installed. Please install them before continuing.
-
The Apache Pulsar microservice is a multi-tenant, high-performance solution for server-to-server messaging. Additional information is available in the Apache Pulsar microservice documentation.
-
The Assure1 Event Canal microservice provides the foundation for streaming analytics of events. Additional information is available in the Assure1 Event Canal microservice documentation.
-
-
Deploy the Vision event apps:
a1helm install vision-event assure1/vision-event -n $VISIONNAMESPACE --set global.imageRegistry=$WEBFQDN
-
The following can be used to verify the pods are running. Do not proceed until all show as Running:
a1k get pods -n $VISIONNAMESPACE
-
The following can be used to check the application logs and verify there are no 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
Access the Vision UI¶
-
Log in to the Assure1 UI.
-
Vision can be accessed by clicking on the Vision link that is under Analytics:
Analytics -> Vision