Page Comparison

...

1. Log in to the Rancher UI using the username and password you configured at the time of deployment.

2. Validate if the Rancher cluster is listed in Clusters table with the name local at the home page.

   

3. Verify if all the attached nodes to the cluster are up and running by following the steps given below.

   1. Click the menu icon at the top left corner, and then click Local.

   2. Go to Local > Click Nodes.

   3. Verify if all the nodes are in Active state and the roles assigned to each of them is set to Control Plane, Etcd.

      Image RemovedImage Added

4. Check the status of the Rancher pods by following the steps given below.

   1. Click the menu icon at the top left corner, and then click Local.

   2. Go to Local > Workloads > Pods.

   3. In the namespace dropdown (at top aligned to centre) Namespaces dropdown menu, select cattle-system.
      All the listed pod in This lists all the pods in the cattle-system namespace should be in running .

   4. Validate if all the listed pods are in Running state.

      Image RemovedImage Added

...

Verifying Adeptia Connect deployment

1. Validate helm deployment status for adeptia-connect

   1. From rancher UI click on more option button at top left corner > Local > Apps > Installed Apps

   2. In the Installed Apps chart entry for adeptia-connect application should be shown with status deployed.

      Image RemovedImage Added

2. Verify the status of deployed pods for adeptia-connect

   1. From rancher UI click on more option button at top left corner > Local > Workloads > pods

   2. From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).

   3. All the listed pods should be in running status.

      Image RemovedImage Added

3. Verify the logs of each pods

   1. From rancher UI click on more option button at top left corner > Local > Workloads > pods

   2. From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).

   3. Click on more options icon of a pod and select view logs.

      Image RemovedImage Added

   4. Search for message “Microservice started successfully” in each pod logs except runtime deployment manager and rabbitmq pods.

      Image RemovedImage Added

      Note: This screenshot is reference from runtime pod

4. Verify shared Runtime pod is launched and running

   1. From rancher UI click on more option button at top left corner > Local > Workloads > pods

   2. From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).

   3. Pod for ac-runtime microservice is present and in running state

      Image RemovedImage Added

5. Access the adeptia-connect application UI and login to the application.

   1. Open the browser and enter adeptia-connect domain.

      Image RemovedImage Added

   2. Enter the username & password

   3. User should successfully navigate to home page after successful sign in operation.

6. Verify shared NFS volumes are attached with required pods

   1. From rancher UI click on more option button at top left corner > Local > Workloads > Deployments.

   2. From the namespace dropdown (at top aligned at centre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).

   3. Click on name link of required deployment(On which we need to verify the mounted volumes)

   4. Click on config

      Image RemovedImage Added

   5. Click on storage > It will list down all the mounted volumes to the pods

      Image RemovedImage Added

   6. Verify the shared NFS volumes are attached to below pods:

      1. Runtime

      2. Event

      3. Archival and cleanup

      4. Portal

      5. Webrunner

      6. Listener

...

1. Check the status of pods running for EFK service

   1. From rancher UI click on more option button at top left corner > Local > Workloads > pods

   2. From the namespace dropdown (at top aligned at entre) select logging namespace.

   3. All pods should be in running state in logging namespace

      Image RemovedImage Added

2. User is able to login to Kibana UI.

   1. Open the browser and enter EFK access domain.

   2. Login using elastic user(password is configured at the time of deployment)

3. Index pattern for all microservices should be listed in kibana UI.

   1. Login to kibana UI

   2. Click on more option button at top left corner > Discover

   3. Click on kibana index pattern dropdown.

   4. Dropdown should contain list of microservices deployed in adeptia-connect namespace

      Image RemovedImage Added

Verify user account id(UID)

1. Check the allocation of UID “1000“ on cluster nodes.

   1. Login into the Jumpbox and access cluster node(VM) using the below command.

      Code Block
      ssh <nodename/IP>

   2. View passwd file using the below command and verify the user associated with UID “1000“.

      Code Block
      sudo cat /etc/passwd

      Refer to the below screenshot

      Image RemovedImage Added

...