Skip to content

Commit 27f14e6

Browse files
authored
Merge pull request #370 from ipbabble/add-mlops-fraud-detection
updated the demo instructions.
2 parents 8d24d41 + b210c30 commit 27f14e6

22 files changed

+325
-110
lines changed

content/patterns/mlops-fraud-detection/_index.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: MLOps Fraud Detection
33
date: 2023-11-12
44
validated: false
5-
summary: This pattern demonstrates how Red Hat OpenShift AI and MLFlow can be used together to build an end-to-end MLOps platform. It demonstrates this using a credit card fraud detection use case.
5+
summary: This pattern demonstrates how {rh-oai} and MLFlow can be used together to build an end-to-end MLOps platform. It demonstrates this using a credit card fraud detection use case.
66
products:
7-
- Red Hat OpenShift Container Platform
8-
- Red Hat OpenShift AI
9-
- Red Hat Open Data Foundation
7+
- {rh-ocp}
8+
- {rh-oai}
9+
- {rh-ocp-data-first}
1010
industries:
1111
- financial services
1212
aliases: /mlops-fraud-detection/

content/patterns/mlops-fraud-detection/mfd-getting-started.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,6 @@ aliases: /mlops-fraud-detection/getting-started/
99

1010
include::modules/mfd-deploying-mfd-pattern.adoc[leveloffset=1]
1111

12-
include::modules/mfd-using-mfd-pattern.adoc[leveloffset=1]
13-
1412
= Next Steps
1513

16-
link:https://groups.google.com/g/hybrid-cloud-patterns[Help & Feedback]
17-
link:https://github.com/validatedpatterns/mlops-fraud-detection/issues[Report Bugs]
14+
* link:mfd-running-the-demo[Run the demo].
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: Running the Fraud Detection Demo
3+
weight: 10
4+
aliases: /mlops-fraud-detection/mfd-running-the-demo/
5+
---
6+
:toc:
7+
:imagesdir: /images
8+
:_content-type: ASSEMBLY
9+
include::modules/comm-attributes.adoc[]
10+
11+
include::modules/mfd-using-mfd-demo.adoc[leveloffset=1]
12+
13+
= Next Steps
14+
15+
link:https://groups.google.com/g/hybrid-cloud-patterns[Help & Feedback]
16+
link:https://github.com/validatedpatterns/mlops-fraud-detection/issues[Report Bugs]

modules/comm-attributes.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
//:experimental:
44
//:toc: macro
55
//:toc-title:
6-
//:imagesdir: images
6+
:imagesdir: ../../images
77
//:prewrap!:
88
:redhat: Red{nbsp}Hat
99
//Pattern names
@@ -139,3 +139,8 @@
139139
:AWS: Amazon Web Services (AWS)
140140
:GCP: Google Cloud Platform (GCP)
141141
:Azure: Microsoft Azure
142+
// Red Hat OpenShift AI
143+
:rh-oai: Red{nbsp}Hat OpenShift Data Science
144+
:oai: OpenShift Data Science
145+
// Icons
146+
:grid: grid.png

modules/edd-about-emerging-disease-detection.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ To demonstrate the effectiveness of the solution this pattern focuses on the spe
2424

2525
== Technology Highlights:
2626
* Event-Driven Architecture
27-
* Data Science on OpenShift
27+
* {rh-oai}
2828
* Process Automation
2929

3030
== Solution Discussion and Demonstration

modules/edd-deploying-edd-pattern.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ A number of utilities have been built by the validated patterns team to lower th
3030
. Fork the link:https://github.com/validatedpatterns/emerging-disease-detection[emerging-disease-detection] repo on GitHub. It is necessary to fork because your fork will be updated as part of the GitOps and DevOps processes.
3131
. Clone the forked copy of this repository.
3232
+
33-
[,sh]
33+
[source,terminal]
3434
----
3535
git clone [email protected]:<your-username>/emerging-disease-detection.git
3636
----
@@ -41,7 +41,7 @@ git clone [email protected]:<your-username>/emerging-disease-detection.git
4141
+
4242
You do not want to push credentials to GitHub.
4343
+
44-
[,sh]
44+
[source,terminal]
4545
----
4646
cp values-secret.yaml.template ~/values-secret.yaml
4747
vi ~/values-secret.yaml
@@ -83,7 +83,7 @@ When you edit the file you can make changes to the various DB and Grafana passwo
8383

8484
. Customize the `values-global.yaml` for your deployment
8585
+
86-
[,sh]
86+
[source,terminal]
8787
----
8888
git checkout -b my-branch
8989
vi values-global.yaml
@@ -108,7 +108,7 @@ main:
108108
operatorChannel: gitops-1.9
109109
----
110110

111-
[,sh]
111+
[source,terminal]
112112
----
113113
git add values-global.yaml
114114
git commit values-global.yaml
@@ -118,21 +118,21 @@ main:
118118
. You can deploy the pattern using the link:/infrastructure/using-validated-pattern-operator/[validated pattern operator]. If you do use the operator then skip to Validating the Environment below.
119119
. Preview the changes that will be made to the Helm charts.
120120
+
121-
[,sh]
121+
[source,terminal]
122122
----
123123
./pattern.sh make show
124124
----
125125

126126
. Login to your cluster using oc login or exporting the KUBECONFIG
127127
+
128-
[,sh]
128+
[source,terminal]
129129
----
130130
oc login
131131
----
132132
+
133133
.or set KUBECONFIG to the path to your `kubeconfig` file. For example
134134
+
135-
[,sh]
135+
[source,terminal]
136136
----
137137
export KUBECONFIG=~/my-ocp-env/auth/kubeconfig
138138
----
@@ -161,7 +161,7 @@ Emerging Disease Detection Validated Pattern are:
161161

162162
. Apply the changes to your cluster
163163
+
164-
[,sh]
164+
[source,terminal]
165165
----
166166
./pattern.sh make install
167167
----
@@ -188,7 +188,7 @@ them, however you choose to deploy the pattern.
188188
Display the fully qualified domain names, and matching login credentials, for
189189
all ArgoCD instances:
190190
+
191-
[,sh]
191+
[source,terminal]
192192
----
193193
ARGO_CMD=`oc get secrets -A -o jsonpath='{range .items[*]}{"oc get -n "}{.metadata.namespace}{" routes; oc -n "}{.metadata.namespace}{" extract secrets/"}{.metadata.name}{" --to=-\\n"}{end}' | grep gitops-cluster`
194194
CMD=`echo $ARGO_CMD | sed 's|- oc|-;oc|g'`

modules/mfd-architecture.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ image::mlops-fraud-detection/mfd-reference-architecture.png[link="/images/mlops-
3131

3232
The following technologies are used in this solution:
3333

34-
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift Platform]::
34+
link:https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift Container Platform]::
3535
An enterprise-ready Kubernetes container platform built for an open hybrid cloud strategy. It provides a consistent application platform to manage hybrid cloud, public cloud, and edge deployments. It delivers a complete application platform for both traditional and cloud-native applications, allowing them to run anywhere. OpenShift has a pre-configured, pre-installed, and self-updating monitoring stack that provides monitoring for core platform components. It also enables the use of external secret management systems, for example, HashiCorp Vault in this case, to securely add secrets into the OpenShift platform.
3636

37-
https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai[Red Hat OpenShift AI]::
37+
link:https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai[Red Hat OpenShift AI]::
3838
Red Hat® OpenShift® AI is an AI-focused portfolio that provides tools to train, tune, serve, monitor, and manage AI/ML experiments and models on Red Hat OpenShift. Bring data scientists, developers, and IT together on a unified platform to deliver AI-enabled applications faster.
3939

4040
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift GitOps]::

modules/mfd-deploying-mfd-pattern.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ A number of utilities have been built by the validated patterns team to lower th
3030
. Fork the link:https://github.com/validatedpatterns/mlops-fraud-detection[mlops-fraud-detection] repo on GitHub. It is necessary to fork because your fork will be updated as part of the GitOps and DevOps processes.
3131
. Clone the forked copy of this repository.
3232
+
33-
[,sh]
33+
[source,terminal]
3434
----
3535
git clone [email protected]:<your-username>/mlops-fraud-detection.git
3636
----
@@ -41,7 +41,7 @@ git clone [email protected]:<your-username>/mlops-fraud-detection.git
4141
+
4242
You do not want to push credentials to GitHub.
4343
+
44-
[,sh]
44+
[source,terminal]
4545
----
4646
cp values-secret-mlops-fraud-detection.yaml.template ~/values-secret.yaml
4747
vi ~/values-secret.yaml
@@ -59,7 +59,7 @@ When you edit the file you can make changes to the various DB and Grafana passwo
5959

6060
. Customize the `values-global.yaml` for your deployment
6161
+
62-
[,sh]
62+
[source,terminal]
6363
----
6464
git checkout -b my-branch
6565
vi values-global.yaml
@@ -84,7 +84,7 @@ main:
8484
operatorChannel: gitops-1.9
8585
----
8686

87-
[,sh]
87+
[source,terminal]
8888
----
8989
git add values-global.yaml
9090
git commit values-global.yaml
@@ -94,21 +94,21 @@ main:
9494
. You can deploy the pattern using the link:/infrastructure/using-validated-pattern-operator/[validated pattern operator]. If you do use the operator then skip to Validating the Environment below.
9595
. Preview the changes that will be made to the Helm charts.
9696
+
97-
[,sh]
97+
[source,terminal]
9898
----
9999
./pattern.sh make show
100100
----
101101

102102
. Login to your cluster using oc login or exporting the KUBECONFIG
103103
+
104-
[,sh]
104+
[source,terminal]
105105
----
106106
oc login
107107
----
108108
+
109109
.or set KUBECONFIG to the path to your `kubeconfig` file. For example
110110
+
111-
[,sh]
111+
[source,terminal]
112112
----
113113
export KUBECONFIG=~/my-ocp-env/auth/kubeconfig
114114
----
@@ -137,7 +137,7 @@ MLOps Fraud Detection Validated Pattern are:
137137

138138
. Apply the changes to your cluster
139139
+
140-
[,sh]
140+
[source,terminal]
141141
----
142142
./pattern.sh make install
143143
----
@@ -164,7 +164,7 @@ them, however you choose to deploy the pattern.
164164
Display the fully qualified domain names, and matching login credentials, for
165165
all ArgoCD instances:
166166
+
167-
[,sh]
167+
[source,terminal]
168168
----
169169
ARGO_CMD=`oc get secrets -A -o jsonpath='{range .items[*]}{"oc get -n "}{.metadata.namespace}{" routes; oc -n "}{.metadata.namespace}{" extract secrets/"}{.metadata.name}{" --to=-\\n"}{end}' | grep gitops-cluster`
170170
CMD=`echo $ARGO_CMD | sed 's|- oc|-;oc|g'`

0 commit comments

Comments
 (0)