You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Grafana dashboard is a visual representation of the AI/ML workflow. It provides the CPU and Memory metrics for the pod running the risk assessment application. The dashboard also provides visual representation of the AI/ML workflow from the images being generated at the remote medical facility. Carry out the following steps to view the dashboard:
26
31
27
-
== Objectives
32
+
This showcase application is deployed using self-signed certificates that are untrusted by our browser. Unless you have provisioned valid certificates for your OpenShift cluster you must accept the invalid certificates for:
28
33
29
-
In this demo you will complete the following:
34
+
. Accept the SSL certificates on the browser for the dashboard. In the {ocp} web console, go to the Routes for *All Projects*. Click the URL for the `s3-rgw`.
* Update the pattern repo with your cluster values
33
-
* Deploy the pattern
34
-
* Access the dashboard
42
+
. While still looking at Routes, change the project to `xraylab-1`. Click the URL for the `image-server`. Ensure that you do not see an access denied error message. You must to see a `Hello world` message.
35
43
36
-
[id="getting-started"]
44
+
This showcase application does not have access to a x-ray machine hanging around that we can use for this demo, so one is emulated by creating an s3 bucket and hosting the x-ray images within it. In the "real world" an x-ray would be taken at an edge medical facility and then uploaded to an OpenShift Data Foundations (ODF) S3 compatible bucket in the Core Hospital, triggering the AI/ML workflow.
37
45
38
-
== Getting Started
46
+
To emulate the edge medical facility we use an application called `image-generator` which (when scaled up) will download the x-rays from s3 and put them in an ODF s3 bucket in the cluster, triggering the AI/ML workflow.
39
47
40
-
* Follow the link:../getting-started[Getting Started Guide] to ensure that you have met all of the pre-requisites
41
-
* Review link:../getting-started/#preparing-for-deployment[Preparing for Deployment] for updating the pattern with your cluster values
48
+
Turn on the image file flow. There are couple of ways to go about this.
42
49
43
-
[NOTE]
44
-
====
45
-
This demo begins after `./pattern.sh make install` has been executed
46
-
====
47
-
48
-
[id="demo"]
49
-
50
-
== Demo
51
-
52
-
Now that we have deployed the pattern onto our cluster, we can begin to discover what has changed, and then move onto the dashboard.
53
-
54
-
[id="admin-view"]
55
-
56
-
=== Administrator View - Review Changes to cluster
57
-
58
-
Login to your cluster's console with the `kubeadmin` user
59
-
60
-
Let's check out what operators were installed - In the accordion menu on the left:
If you started with a new cluster then there were no layered products or operators installed. With the Validated Patterns framework we describe or declare what our cluster's desired state is and the GitOps engine does the rest. This includes creating the instance of the operator and any additional configuration between other API's to ensure everything is working together nicely.
75
-
76
-
77
-
[id="dev-view"]
78
-
79
-
=== Developer View - Review Changes to cluster
80
-
81
-
Let’s switch to the developer context by click on `Administrator` in the top left corner of the accordion menu then click `Developer`
Look at all of the resources that have been created for this demo application. What we see in this interface is the collection of all components required for this AI/ML workflow to properly execute. There are even more resources and configurations that get deployed but because we don't directly interact with them we won't worry too much about them. The take away here is when you utilize the framework you are able to build in automation just like this which allows your developers to focus on their important developer things.
90
-
91
-
92
-
[id="certificate-warn"]
93
-
94
-
=== Invalid Certificates
95
-
96
-
We are deploying this demo using self-signed certificates that are untrusted by our browser. Unless you have provisioned valid certificates for your OpenShift cluster you must accept the invalid certificates for:
97
-
98
-
* image-server | xraylab-1 namespace
99
-
* s3-rgw | openshift-storage namespace
100
-
* grafana | xraylab-1 namespace
101
-
102
-
[source,shell]
103
-
----
104
-
IMAGESERVER_ROUTE=https://$(oc get route -n xraylab-1 image-server -o jsonpath='{.spec.host}')
105
-
106
-
echo $IMAGESERVER_ROUTE
107
-
108
-
S3RGW_ROUTE=https://$(oc get route -n openshift-storage s3-rgw -o jsonpath='{.spec.host}')
109
-
110
-
echo $S3RGW_ROUTE
111
-
112
-
GRAFANA_ROUTE=https://$(oc get route -n xraylab-1 grafana -o jsonpath='{.spec.host}')
113
-
114
-
echo $GRAFANA_ROUTE
115
-
----
116
-
117
-
[WARNING]
118
-
119
-
====
120
-
You must accept the security risks / self signed certificates before scaling the image-generator application
121
-
====
122
-
123
-
[id="scale-up"]
124
-
125
-
=== Scale up the deployment
126
-
127
-
As we mentioned earlier, we don't have an x-ray machine hanging around that we can use for this demo, so we emulate one by creating an s3 bucket and hosting the x-ray images within it. In the "real world" an x-ray would be taken at an edge medical facility and then uploaded to an OpenShift Data Foundations (ODF) S3 compatible bucket in the Core Hospital, triggering the AI/ML workflow.
128
-
129
-
To emulate the edge medical facility we use an application called `image-generator` which (when scaled up) will download the x-rays from s3 and put them in an ODF s3 bucket in the cluster, triggering the AI/ML workflow.
130
-
131
-
Let's scale the `image-generator` deploymentConfig up to start the pipeline
132
-
133
-
[NOTE]
134
-
====
135
-
Make sure that you are in the `xraylab-1` project under the `Developer` context in the OpenShift Console
136
-
====
137
-
138
-
In the Topology menu under the Developer context in the OpenShift Console:
50
+
. Go to the {ocp} web console and change the view from *Administrator* to *Developer* and select *Topology*. From there select the `xraylab-1` project.
139
51
140
-
* Search for the `image-generator` application in the Topology console
52
+
. Right-click on the `image-generator` pod icon and select `Edit Pod count`.
. test. Accept the SSL certificates on the browser for the dashboard. In the {ocp} web console, go to the Routes for *All Projects*. Click the URL for the `s3-rgw`.
. While still looking at Routes, change the project to `xraylab-1`. Click the URL for the `image-server`. Ensure that you do not see an access denied error message. You must to see a `Hello World` message.
. Turn on the image file flow. There are couple of ways to go about this.
468
-
+
469
-
You can go to the {ocp} web console and change the view from *Administrator* to *Developer* and select *Topology*. From there select the `xraylab-1` project.
0 commit comments