Skip to content

Commit 78d74e0

Browse files
committed
Updating troubleshooting and images
1 parent 0f69799 commit 78d74e0

File tree

2 files changed

+6
-45
lines changed

2 files changed

+6
-45
lines changed

content/patterns/medical-diagnosis/demo-script.adoc

+4-6
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: Verifying the demo
33
weight: 20
4-
title: Verifying the demo Medical diagnosis pattern
5-
weight: 20
64
aliases: /medical-diagnosis/demo/
75
---
86

@@ -29,19 +27,19 @@ We simulate the function of the remote medical facility with an application call
2927
[id="viewing-the-grafana-based-dashboard-getting-started"]
3028
== Enabling the Grafana based dashboard
3129

32-
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:
30+
The Grafana dashboard offers a visual representation of the AI/ML workflow, including CPU and memory metrics for the pod running the risk assessment application. Additionally, it displays a graphical overview of the AI/ML workflow, illustrating the images being generated at the remote medical facility.
3331

34-
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:
32+
This showcase application is deployed with self-signed certificates, which are considered untrusted by most browsers. If valid certificates have not been provisioned for your OpenShift cluster, you will need to manually accept the untrusted certificates by following these steps:
3533

36-
. 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`.
34+
. Accept the SSL certificates on the browser for the dashboard. In the {ocp} web console, go to the *Netwoorking* > *Routes* for *All Projects*. Click the URL for the `s3-rgw`.
3735
+
3836
image::../../images/medical-edge/storage-route.png[s3-rgw route]
3937
+
4038
Ensure that you see some XML and not the access denied error message.
4139
+
4240
image::../../images/medical-edge/storage-rgw-route.png[link="/images/medical-edge/storage-rgw-route.png"]
4341

44-
. 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.
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.
4543

4644
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.
4745

content/patterns/medical-diagnosis/getting-started.adoc

+2-39
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ $ python s3-create.py -b kevtest-bucket -r us-east-1 -p
124124
$ python s3-sync-buckets.py -s validated-patterns-md-xray -t kevtest-bucket -r us-east-1
125125
----
126126

127-
Note the name of the bucket for further pattern configuration. Later you will update the `bucketSource` in the `values-global.yaml` file, where there is a section for `s3:`
127+
Note the name of the bucket for further pattern configuration. Later you will update the `bucketSource` in the `values-global.yaml` file, where there is a section for `s3:`.
128128

129129
[id="preparing-for-deployment"]
130130
== Preparing for deployment
@@ -468,41 +468,4 @@ To check the various applications that are being deployed, you can view the prog
468468
Examine the `medical-diagnosis-hub` ArgoCD instance. You can track all the applications for the pattern in this instance.
469469
====
470470

471-
. Check that all applications are synchronized. There are thirteen different ArgoCD `applications` that are deployed as part of this pattern.
472-
473-
474-
475-
476-
477-
//Module to be included
478-
//:_content-type: PROCEDURE
479-
//:imagesdir: ../../../images
480-
[id="making-some-changes-on-the-dashboard-getting-started"]
481-
=== Making some changes on the dashboard
482-
483-
You can change some of the parameters and watch how the changes effect the dashboard.
484-
485-
. You can increase or decrease the number of image generators.
486-
+
487-
[source,terminal]
488-
----
489-
$ oc scale deploymentconfig/image-generator --replicas=2
490-
----
491-
+
492-
Check the dashboard.
493-
+
494-
[source,terminal]
495-
----
496-
$ oc scale deploymentconfig/image-generator --replicas=0
497-
----
498-
+
499-
Watch the dashboard stop processing images.
500-
501-
. You can also simulate the change of the AI model version - as it's only an environment variable in the Serverless Service configuration.
502-
+
503-
[source,terminal]
504-
----
505-
$ oc patch service.serving.knative.dev/risk-assessment --type=json -p '[{"op":"replace","path":"/spec/template/metadata/annotations/revisionTimestamp","value":"'"$(date +%F_%T)"'"},{"op":"replace","path":"/spec/template/spec/containers/0/env/0/value","value":"v2"}]'
506-
----
507-
+
508-
This changes the model version value, and the `revisionTimestamp` in the annotations, which triggers a redeployment of the service.
471+
. Check that all applications are synchronized. There are thirteen different ArgoCD `applications` that are deployed as part of this pattern.

0 commit comments

Comments
 (0)