Page Comparison

...

Verifying the RKE2 and Rancher deployment

1. Log Verify if you are able to log in to the Rancher UI using the username and password you configured at the time of deployment.

2. Validate In the Rancher UI, 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 In the Rancher UI, click the menu icon at the top left corner, and then click Local.

   2. 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.

      

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

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

   2. Go to Workloads Workload > Pods.

   3. In the Namespaces dropdown menu, select cattle-system.
      This lists all the pods in the cattle-system namespace.

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

      

Verifying the deployment of Adeptia Connect

...

application

1. Validate if the Adeptia Connect helm is deployed.

   1. Log in to the Rancher UI.

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

   3. Go to Apps > Installed Apps.

   4. In the Installed Apps, verify if the chart entry for adeptia-connect is in Deployed state.

      

2. Check the status of the deployed pods of adeptia-connect.

   1. Log in to the Rancher UI.

   2. Anchor
      stepsaThroughcsteps aThroughc

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

   3. Go to Workloads Workload > Pods.

   4. In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.

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

      

3. Check the logs to see the status of each microservice the pods by following the steps given below.

   1. Follow the steps from a through cd.

   2. Click on the more options icon of a pod and select view logsagainst the pod whose status you want to view, and then click View Logs.

      

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

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

   5. Search for message “Microservice started successfully” in each pod logs except to validate if the pod was started successfully.
      The screenshot given below is an example that shows the status of the Runtime pod.

      Image Added

      Note: The status of runtime deployment manager and rabbitmq pods .

      Image Removed

      Note: This screenshot is reference from runtime pod

   Verify shared Runtime pod is launched and running

   1. Pod could not be viewed in their respective logs.

4. Follow the steps given below to check the status of the shared Runtime pod.

   1. Follow the steps from a through d.

   2. Verify if the pod for ac-runtime microservice is present and is in running Running state.

      

5. Access the adeptia-connect application UI and login to the Verify if you are able to log in to the Adeptia Connect application.

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

      Image Removed

   2. Enter the username & password

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

6. Verify Verify if the shared NFS volumes are attached with required pods

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

   .

   1. Log in to the Rancher UI.

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

   3. Go to Workload > Deployments.

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

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

   6. Click on config

      Image Removed

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

      Image Removed

   8. Verify Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.

   9. Click the deployment (link in the name column) for which you want to check the mounted volumes.

   10. Select Config at the top-right corner.

       Image Added

   11. Click Storage.
       A list of all the volumes that are mounted to the pods is displayed.

       Image Added

   12. Check if the shared NFS volumes are attached to below following pods:

       1. Runtimeruntime

       2. Eventevent

       3. Archival archival and cleanup

       4. Portalportal

       5. Webrunnerwebrunner

       6. Listener

...

1. 1. 1. listener

Verifying the deployment of EFK

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 Removed

   User is able to login to Kibana UI.

2. Open the browser and enter EFK access domain.

Login using elastic user(password is

the EFK services pods'.

1. Log in to the Rancher UI.

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

3. Go to Workload > pods.

4. In the Namespaces dropdown menu, select logging.

5. Verify if all the pods are in Running state.

   Image Added

3. Verify if you are able to log in to the Kibana UI using the username elastic and the password you configured at the time of deployment

   )

   Index .

4. Verify if the index pattern for all microservices should be is listed in kibana Kibana UI.

   1. Login Log in to kibana the Kibana UI.

   2. Click on more option button the menu icon at top left corner > .

   3. Click Discover.

   4. Click on kibana the Kibana index pattern dropdown.

   5. Dropdown should contain Verify if the list of all the microservices deployed in adeptia-connect namespace is displayed.

      

Verify user account id (UID)

...