Telcodocs 2229 update retail VP

content/learn/vp_add_ops_to_pattern.adoc

@@ -3,7 +3,7 @@ menu:
   learn:
     parent: Validated patterns frameworks
 title: Adding Operators to the framework
-weight: 23
+weight: 26
 aliases: /ocp-framework/adding-operator-to-framework/
 ---
 
@@ -39,7 +39,7 @@ This procedure describes how subscriptions to Operators are added to the validat
 For example, if you want to deploy Advanced Cluster Management, AMQ (messaging) and AMQ Streams (Kafka) in your factory cluster, you would follow the guidance here:
 
 The assumption is there is a `values-factory.yaml` file that is used to deploy the factory cluster. The file should include the following entries:
-+
+
 [source,yaml]
 ----
 namespaces:

content/learn/vp_add_specific_ops_to_pattern.adoc

@@ -3,7 +3,7 @@ menu:
   learn:
     parent: Validated patterns frameworks
 title: Adding a specific operator to hub values file
-weight: 24
+weight: 27
 aliases: /ocp-framework/adding-specific-operator-to-hub/
 ---
 

content/patterns/multicloud-gitops/retail-managed-cluster.adoc

@@ -0,0 +1,73 @@
+---
+title: Managed cluster sites
+weight: 30
+aliases: /retail/retail-managed-cluster/
+---
+
+:toc:
+:imagesdir: /images
+:_content-type: ASSEMBLY
+include::modules/comm-attributes.adoc[]
+
+//leaving this here on purpose to test H1 headings (with ID) in assemblies and it's impact of TOC
+[id="attach-managed-cluster"]
+= Attach a managed cluster (edge) to the management hub
+
+The use of this Multicloud GitOps pattern depends on having at least one running Red Hat OpenShift cluster. 
+
+When you install the multi-cloud GitOps pattern, a hub cluster is setup. The hub cluster serves as the central point for managing and deploying applications across multiple clusters.
+
+include::modules/mcg-understanding-rhacm-requirements.adoc[leveloffset=+1]
+
+include::modules/mcg-deploying-managed-cluster-using-rhacm.adoc[leveloffset=+1]
+
+include::modules/comm-deploying-managed-cluster-using-cm-cli-tool.adoc[leveloffset=+1]
+
+include::modules/comm-deploying-managed-cluster-using-clusteradm-tool.adoc[leveloffset=+1]
+
+include::modules/comm-designate-cluster-as-managed-cluster-site.adoc[leveloffset=+2]
+
+
+== Verification
+
+. Go to your managed cluster (edge) OpenShift console and check for the `open-cluster-management-agent` pod being launched. 
+
+[NOTE]
+====
+It might take a while for the RHACM agent and `agent-addons` to launch.
+====
+
+. Check the *Red Hat OpenShift GitOps Operator* is installed. 
+
+. Launch the *Group-One OpenShift ArgoCD* console from nines menu in the top right of the OpenShift console. Verify the applications report the status `Healthy` and `Synched`.
+
+Verify that the *hello-world* application deployed successfully as follows:
+
+. Navigate to the *Networking* -> *Routes* menu options on your managed cluster (edge) OpenShift.
+
+. From the *Project:* drop down select the *hello-world* project. 
+
+. Click the *Location URL*. This should reveal the following:
++
+[source,terminal]
+----
+Hello World!
+
+Hub Cluster domain is 'apps.aws-hub-cluster.openshift.org'
+Pod is running on Local Cluster Domain 'apps.aws-hub-cluster.openshift.org'
+----
+
+Verify that the *config-demo* application deployed successfully as follows:
+
+. Navigate to the *Networking* -> *Routes* menu options on your managed cluster (edge) OpenShift.
+
+. Select the *config-demo* *Project*. 
+
+. Click the *Location URL*. This should reveal the following:
++
+[source,terminal]
+----
+Hub Cluster domain is 'apps.aws-hub-cluster.openshift.org'
+Pod is running on Local Cluster Domain 'apps.aws-hub-cluster.openshift.org'
+The secret is `secret`
+----

content/patterns/retail/_index.adoc

@@ -0,0 +1,33 @@
+---
+title: Retail
+date: 2022-12-08
+tier: tested
+summary: This pattern demonstrates a pattern that models the store side of a retail application.
+rh_products:
+- Red Hat OpenShift Container Platform
+- Red Hat Advanced Cluster Management
+- Red Hat AMQ
+industries:
+- Retail
+aliases: /retail/
+# uncomment once this exists
+# pattern_logo: retail.png
+links:
+  install: getting-started
+  help: https://groups.google.com/g/validatedpatterns
+  bugs: https://github.com/validatedpatterns/retail/issues
+# uncomment once this exists
+ci: retail
+---
+
+:toc:
+:imagesdir: /images
+:_content-type: ASSEMBLY
+include::modules/comm-attributes.adoc[]
+
+include::modules/retail-about.adoc[leveloffset=+1]
+
+include::modules/retail-architecture.adoc[leveloffset=+1]
+
+
+

content/patterns/retail/application.adoc

@@ -0,0 +1,12 @@
+---
+title: Demonstrating a retail example applications
+weight: 40
+aliases: /retail/application-demos/
+---
+
+:toc:
+:imagesdir: /images
+:_content-type: ASSEMBLY
+include::modules/comm-attributes.adoc[]
+
+include::modules/retail-example-applications.adoc[]

content/patterns/retail/cluster-sizing.adoc

@@ -0,0 +1,14 @@
+---
+title: Cluster Sizing
+weight: 60
+aliases: /retail/retail-cluster-sizing/
+---
+
+:toc:
+:imagesdir: /images
+:_content-type: ASSEMBLY
+
+include::modules/comm-attributes.adoc[]
+include::modules/retail/metadata-retail.adoc[]
+
+include::modules/cluster-sizing-template.adoc[]