Check SNO Deployment is Finished

In the previous section we have learned how to follow the cluster deployment process, but the cluster finished its deployment doesn’t mean that the SNO deployment is complete.

We say that the SNO deployment finished when the SNO cluster has been deployed and day2 configurations have been applied. In this section we will learn how to verify that the configs have been applied and our sno-abi is ready to run 5G RAN workloads.

Check SNO Deployment has Finished via the WebUI

  1. Access the RHACM WebUI and login with the OpenShift credentials.

  2. Once you’re in, click on Infrastructure → Clusters. You will see a screen like the one below, notice that there is a label saying ztp-done for the SNO ABI cluster (that means ztp pipeline has finished):

    RHACM SNO ABI ztp-done

  3. Additionally, we can verify that all policies are compliant for our sno-abi cluster and also the image-based installed sno-ibi. On the RHACM WebUI go to Governance → Policies and you will see the following screen where we can see all policies are green:

    Applying policies on sno-abi can take up to 15 minutes after cluster has been fully deployed.

    Notice that the sno-ibi node was already deployed and configured with the telco RAN DU profile previously in Deploying an Image Based Install Cluster. So it is ready to run telco CNF applications as well.

    RHACM SNO ABI policies done
    See that the policies in the Governance section are also compliant for the sno-ibi cluster even they were not applied via RHACM Policies. They were included in the seed image that was used to provision it and afterwards executed the reconfiguration process using the configuration ISO.

  4. At this point the sno-abi is ready to run 5G RAN workloads too.

Check SNO Deployment has Finished via the CLI

Below commands must be executed from the workstation host if not specified otherwise.

  1. Check the ManagedCluster for SNO ABI cluster (including its labels). You should see the ztp-done label, just as we saw in the WebUI.

    oc --kubeconfig ~/hub-kubeconfig get managedcluster sno-abi --show-labels
    NAME   HUB ACCEPTED   MANAGED CLUSTER URLS                      JOINED   AVAILABLE   AGE    LABELS
sno-abi   true           https://api.sno-abi.5g-deployment.lab:6443   True     True        122m   <OMITTED_LABELS>,ztp-done=

  2. Check the policies are compliant for our SNO cluster.

    oc --kubeconfig ~/hub-kubeconfig -n sno-abi get policies
    Applying policies on sno-abi can take up to 15 minutes after cluster has been fully deployed. 
    NAME                                        REMEDIATION ACTION   COMPLIANCE STATE   AGE
ztp-policies.common-config-policies         inform               Compliant          74m
ztp-policies.common-subscription-policies   inform               Compliant          74m
ztp-policies.du-sno-group-policies          inform               Compliant          74m
ztp-policies.du-sno-sites-sites-policy      inform               Compliant          74m

  3. At this stage both sno-abi and sno-ibi OpenShift Single-Node clusters are ready to run 5G RAN workloads.