Skip to content

Commit 71c3b0c

Browse files
kquinn1204kquinn1204
committed
more updates 2
1 parent b807195 commit 71c3b0c

File tree

2 files changed

+139
-0
lines changed

2 files changed

+139
-0
lines changed

‎modules/retail-example-applications.adoc‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
:_content-type: PROCEDURE
2+
:imagesdir: ../../../images
3+
4+
[id="deploying-mcg-pattern"]
5+
= Demonstrating Retail example applications
6+
7+
Up until now the Retail validated pattern has focused primarily on
8+
successfully deploying the architectural pattern. Now it is time to see
9+
the actual applications running as we have deployed them.
10+
11+
If you have already deployed the hub cluster, then you have already seen
12+
several applications deployed in the OpenShift GitOps console. If you
13+
haven’t done this then we recommend you deploy the hub after you have
14+
setup the Quay repositories described below.
15+
16+
== Ordering Items at the Coffeeshop
17+
18+
The easiest way to get to the coffeeshop store page is from the
19+
OpenShift Console Menu Landing Page entry:
20+
21+
link:/images/retail/retail-v1-console-menu.png[image:/images/retail/retail-v1-console-menu.png[retail-v1-console-menu]
22+
23+
1. Click the *Quarkus Coffeeshop Landing Page* link will bring you to
24+
this page:
25+
+
26+
link:/images/retail/retail-v1-landing-page.png[image:/images/retail/retail-v1-landing-page.png[retail-v1-landing-page]
27+
28+
2. Select either the `Store Web Page` or "`TEST Store Web Page`"
29+
links brings you to a screen that looks like this:
30+
+
31+
link:/images/retail/retail-v1-store-page.png[image:/images/retail/retail-v1-store-page.png[retail-v1-store-page]
32+
+
33+
[NOTE]
34+
====
35+
The applications are initially identical. The `TEST`" site is
36+
deployed to the `quarkuscoffeeshop-demo` namespace; the regular Store
37+
site is deployed to the `quarkuscoffeeshop-store` namespace.
38+
39+
Each store requires supporting services, in PostgreSQL and Kafka. In our
40+
pattern, PostgreSQL is provided by the Crunchy PostgreSQL operator, and
41+
Kafka is provided by the Red Hat AMQ Streams operator. Each instance,
42+
the regular instance and the TEST instance, has its own instance of each
43+
of these supporting services it uses.
44+
====
45+
46+
47+
. Order by clicking the `Place an Order` button on the front page. The
48+
menu should look like this:
49+
+
50+
link:/images/retail/retail-v1-store-web-menu.png[image:/images/retail/retail-v1-store-web-menu.png[retail-v1-store-web-menu]]
51+
52+
. Click the `Add` button next to a menu item; the item name will appear.
53+
Add a name for the order:
54+
55+
link:/images/retail/retail-v1-order-p1.png[image:/images/retail/retail-v1-order-p1.png[retail-v1-order-p1]]
56+
57+
You can add as many orders as you want. On your last item, click the
58+
"`Place Order`" button on the item dialog:
59+
60+
link:/images/retail/retail-v1-place-order.png[image:/images/retail/retail-v1-place-order.png[retail-v1-place-order]]
61+
62+
As the orders are serviced by the barista and kitchen services, you can
63+
see their status in the "`Orders`" section of the page:
64+
65+
link:/images/retail/retail-v1-orders-status.png[image:/images/retail/retail-v1-orders-status.png[retail-v1-orders-status]
66+
67+

‎modules/retail-understanding-rhacm-requirements.adoc‎

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
:_content-type: CONCEPT
2+
:imagesdir: ../../images
3+
4+
[id="understanding-acm-requirements-managed-cluster"]
5+
= Understanding Red Hat Advanced Cluster Management requirements
6+
7+
By default, Red Hat Advanced Cluster Management (RHACM) manages the `clusterGroup` applications that are deployed on all clusters.
8+
9+
Add a `managedClusterGroup` for each cluster or group of clusters that you want to manage by following this procedure.
10+
11+
.Procedure
12+
13+
. Switch to your locally created feature branch by running the following command:
14+
+
15+
[source,terminal]
16+
----
17+
$ git checkout my-branch main
18+
----
19+
20+
. In the `value-hub.yaml` file, a `managedClusterGroup` `raleigh` already exists as shown in this yaml extract:
21+
+
22+
[source,yaml]
23+
----
24+
managedClusterGroups:
25+
raleigh:
26+
name: store-raleigh
27+
helmOverrides:
28+
# Values must be strings!
29+
- name: clusterGroup.isHubCluster
30+
value: "false"
31+
clusterSelector:
32+
matchLabels:
33+
clusterGroup: store-raleigh
34+
matchExpressions:
35+
- key: vendor
36+
operator: In
37+
values:
38+
- OpenShift
39+
----
40+
+
41+
The YAML file segment defines the `raleigh` managed cluster group, which deploys `clusterGroup` applications on clusters labeled with `clusterGroup=store-raleigh`. The clusterSelector ensures that only clusters with the `clusterGroup=store-raleigh` label and the `vendor=OpenShift` label are included in this group. Specific subscriptions, Operators, applications, and projects for this clusterGroup are managed through the values-store-raleigh.yaml file..
42+
43+
. To add a new `managedClusterGroup`, add a new entry to the `managedClusterGroups` block in the `values-hub.yaml` file as follows:
44+
+
45+
[source,yaml]
46+
----
47+
charlotte:
48+
name: store-charlotte
49+
helmOverrides:
50+
- name: clusterGroup.isHubCluster
51+
value: "false"
52+
clusterSelector:
53+
matchLabels:
54+
clusterGroup: store-charlotte
55+
matchExpressions:
56+
- key: vendor
57+
operator: In
58+
values:
59+
- OpenShift
60+
----
61+
+
62+
[NOTE]
63+
====
64+
The `charlotte` cluster group is managed separately, using its own `values-store-charlotte.yaml` file.
65+
====
66+
67+
. Make a copy of the `values-store-raleigh.yaml` file and name it `values-store-charlotte.yaml`. Update the file with the appropriate values for the `charlotte` cluster group.
68+
69+
[IMPORTANT]
70+
====
71+
Ensure that you commit the changes and push them to GitHub so that GitOps can fetch your changes and apply them.
72+
====

0 commit comments

Comments
 (0)