consumingPatterns content

Author: day0hero

documentation/modules/ROOT/assets/images/consuming-common-solution-layering-modular.png

@@ -34,7 +34,14 @@
 ** xref:tiers.adoc#resources[Additional Resources]
 
 // Chapter 5 - Creating and Consuming Patterns
-* xref:creatingPatterns.adoc[5. Creating Validated Patterns]
+* xref:consumingPatterns.adoc[5. Validated Patterns]
+** xref:consumingPatterns.adoc[Consuming a Validated Pattern]
+*** xref:consumingPatterns.adoc#objectives[Topic Objectives]
+*** xref:consumingPatterns.adoc#workflow[Deployment Workflow]
+*** xref:consumingPatterns.adoc#layering[Solution Layering]
+*** xref:consumingPatterns.adoc#multiArgos[Multiple Argo's]
+*** xref:consumingPatterns.adoc#exercises[Exercies]
+** xref:creatingPatterns.adoc[Creating Validated Patterns]
 ** xref:creatingPatterns.adoc#objectives[Topic Objectives]
 ** xref:creatingPatterns.adoc#technology[Core Products and Technology]
 *** xref:creatingPatterns.adoc#exercises[Exercies]

documentation/modules/ROOT/assets/images/consuming-common-solution-layering.png

@@ -1,5 +1,66 @@
-== Consuming Patterns
-
+== Consuming Validated Patterns
 include::_attributes.adoc[]
 
 include::main@vp-workshop:ROOT:partial$topicHeader.adoc[]
+
+* Validated Pattern Deployment workflow
+* Describing a pattern
+* Using the patterns operator
+** And the patterns.sh script
+* Preparing your environment
+* Understand our base pattern
+* To fork or not to fork
+
+== Validated Pattern workflow
+[#workflow]
+
+Let's dive into what happens when we deploy a pattern! Take a look at the following graphic to see what is deployed on the `hub` clusterGroup cluster.
+
+image::consuming-vpWorkflow-hub.png[Hub Cluster]
+
+1. The patterns operator deploys an instance of {rh-gitops} and creates the initial application
+2. ArgoCD then deploys the operators, namespaces, projects and applications defined in the values files
+3. If deploying across multiple clusters, the framework uses {rhacm} policies to create the instance of {rh-gitops} on the remote cluster
+
+INFO: `values-hub.yaml` is the primary values file for the `hub` cluster
+
+IMPORTANT: Deploying the pattern through the OpenShift Console or via `pattern.sh` will deploy the patterns operator.
+
+image::consuming-vpWorkflow-managedCluster.png[Managed Cluster]
+
+1. When a managed cluster is joined to {rhacm} it needs to have a clusterGroup label applied to it for the correct policies and applications to be deployed.
+2. {rhacm} will confirm the cluster is managed then deploy a rhacm agent 
+3. A placement policy is then deployed to the managed cluster which installs an instances of {rh-gitops}
+4. The managed cluster's instance of ArgoCD will then deploy the resources declared in `values-clustergroup.yaml`
+
+=== Element Layering 
+[#layering]
+
+The base component of every Validated Pattern is `common` - which is a link:https://github.com/validatedpatterns/common[Github Repo]
+
+image::consuming-common.png[common]
+
+Without further configuration, common is acutally quite boring. So let's add another layer! 
+
+Your specific industry or use-case is layered into the framework and utilizes the underlying common. In this example the solution includes a bespoke application, cloud-native cluster storage, {rhacs}, and an enterprise container registry. The framework will deploy and configure these components through Helm charts, kustomize manifests or Ansible if necessary.
+
+image::consuming-common-solution-layering.png[]
+
+What if we wanted to swap these products out with a similar or like-in-kind solution? The workflow remains the same:
+
+- remove the undesired application declaration
+- declare the new application in your values file
+- declare where the helm charts reside (path, repo)
+
+The following graphic illustrates swapping components in the framework:
+
+image::consuming-common-solution-layering-modular.png[]
+
+[#multiArgos]
+
+You may be asking yourself ... 
+
+image::consuming-multipleArgos.png
+
+
+

documentation/modules/ROOT/assets/images/consuming-common.png

@@ -11,6 +11,9 @@ include::main@vp-workshop:ROOT:partial$topicHeader.adoc[]
 * Understand our base pattern
 * To fork or not to fork
 
-== Core Products and Technologies
-[#technology]
+== Validated Pattern workflow
+[#workflow]
 
+Let's dive into what happens when we deploy a pattern! Take a look at the following graphic to see what is deployed on the `hub` clusterGroup cluster.
+
+image::creating-vpWorkflow-managedCluster.png[]