- Recorded Demo
- What Next
This Validated Pattern is based on a demo implemetation of an automated data pipeline for chest Xray analysis previously developed by Red Hat. The original demo can be found here. It was developed for the US Department of Veteran Affairs.
This validated pattern includes the same functionality as the original demonstration. The difference is that we use the GitOps to deploy most of the components which includes operators, creation of namespaces, and cluster configuration. Using GitOps provides a much more efficient means of doing continuous deployment.
The Validated Pattern includes:
- Ingest chest Xrays into an object store based on Ceph.
- The Object store sends notifications to a Kafka topic.
- A KNative Eventing Listener to the topic triggers a KNative Serving function.
- An ML-trained model running in a container makes a risk of Pneumonia assessment for incoming images.
- A Grafana dashboard displays the pipeline in real time, along with images incoming, processed and anonymized, as well as full metrics.
This pipeline is showcased in this video.
- How to use a GitOps approach to keep in control of configuration and operations
- How to centrally manage multiple medical diagnosis facilities using GitOps.
- How to deploy AI/ML technologies for medical diagnosis using GitOps from data center to the edge.
- Red Hat OpenShift Container Platform (Kubernetes++)
- Red Hat Advanced Cluster Management (Open Clutser Management)
- Red Hat OpenShift GitOps (ArgoCD)
- Red Hat Quay (Container image registry)
- Red Hat AMQ Streams (Apache Kafka Event Broker)
- Grafana dashboard (OpenShift Grafana Operator)
- Open Data Hub
- S3 storage
At a high level this requires a management hub, for the applications and GitOps management, and infrastructure that extends to more than one managed clusters running for medical facilities on private or public clouds.
Components are running on OpenShift either at the data center or at the medical facility (or public cloud running OpenShift).
In the Medical Diagnosis architecture there are two logical sites.
- The Management Hub. This is where the multiple managed clusters deployed on clouds (public or private) are managed. Application and configuration code is workied on here and deployed to the other managed clusters. There is one management hub.
- The Managed Cluster. This is where new applications, updates and operational changes are deployed for the business. There are more than one managed clusters.
The diagram below shows the components that are deployed with the various networks that connect them.
The diagram below shows the components that are deployed with the the data flows and API calls between them.
- Getting started deploy the management hub using Helm and GitOps
- Add a managed cluster to deploy the managed cluster piece using ACM
- Visit the repo