TELCODOCS-2203 updating federated edge 1

Author: kquinn1204

content/patterns/federated-edge-observability/_index.adoc

@@ -0,0 +1,50 @@
+== Federated Edge Observability
+
+=== Background
+
+Organizations are interested in accelerating their deployment speeds and
+improving delivery quality in their Edge environments, where many
+devices may not fully or even partially embrace the GitOps philosophy.
+Further, there are VMs and other devices that can and should be managed
+with Ansible. This pattern explores some of the possibilities of using
+an OpenShift-based Ansible Automated Platform deployment and managing
+Edge devices, based on work done with a partner in the Chemical space.
+
+This pattern uses OpenShift Virtualization (the productization of
+Kubevirt) to simulate the Edge environment for VMs.
+
+==== Solution elements
+
+* How to use a GitOps approach to manage virtual machines, either in
+public clouds (limited to AWS for technical reasons) or on-prem
+OpenShift installations
+* How to integrate AAP into OpenShift
+* How to manage Edge devices using AAP hosted in OpenShift
+
+==== Red Hat Technologies
+
+* Red Hat OpenShift Container Platform (Kubernetes)
+* Red Hat Ansible Automation Platform (formerly known as "`Ansible
+Tower`")
+* Red Hat OpenShift GitOps (ArgoCD)
+* OpenShift Virtualization (Kubevirt)
+* Red Hat Enterprise Linux 9
+
+==== Other Technologies this Pattern Uses
+
+* Hashicorp Vault
+* External Secrets Operator
+* OpenTelemetry
+* Grafana
+* Mimir
+
+=== Architecture
+
+Similar to other patterns, this pattern starts with a central management
+hub, which hosts the AAP and Vault components, and the observability
+collection and visualization components.
+
+=== What Next
+
+* link:getting-started[Getting Started: Deploying and Validating the
+Pattern]

content/patterns/federated-edge-observability/ansible-automation-platform.adoc

@@ -0,0 +1,78 @@
+== Ansible Automation Platform
+
+=== How to Log In
+
+The default login user is `+admin+` and the password is generated
+randomly at install time; you will need the password to login in to the
+AAP interface. You do not have to log in to the interface - the pattern
+will configure the AAP instance; the pattern retrieves the password
+using the same technique as the `+ansible_get_credentials.sh+` script
+described below. If you want to inspect the AAP instance, or change any
+aspects of its configuration, there are two ways to login and look at
+it. Both mechanisms are equivalent; you get the same password to the
+same instance using either technique.
+
+=== Via the OpenShift Console
+
+In the OpenShift console, navigate to Workloads > Secrets and select the
+"`ansible-automation-platform`" project if you want to limit the number
+of Secrets you can see.
+
+link:/images/ansible-edge-gitops/ocp-console-secrets-aap-admin-password.png[image:/images/ansible-edge-gitops/ocp-console-secrets-aap-admin-password.png[secrets-navigation]]
+
+The Secret you are looking for is in the `+ansible-automation-platform+`
+project and is named `+controller-admin-password+`. If you click on it,
+you can see the Data.password field. It is shown revealed below to show
+that it is the same as what is shown by the script method of retrieving
+it below:
+
+link:/images/ansible-edge-gitops/ocp-console-aap-admin-password-detail.png[image:/images/ansible-edge-gitops/ocp-console-aap-admin-password-detail.png[secrets-detail]]
+
+=== Via https://github.com/validatedpatterns/ansible-edge-gitops/blob/main/scripts/ansible_get_credentials.sh[ansible_get_credentials.sh]
+
+With your KUBECONFIG set, you can run
+`+./scripts/ansible-get-credentials.sh+` from your top-level pattern
+directory. This will use your OpenShift cluster admin credentials to
+retrieve the URL for your Ansible Automation Platform instance, as well
+as the password for its `+admin+` user, which is auto-generated by the
+AAP operator by default. The output of the command looks like this (your
+password will be different):
+
+[source,text]
+----
+./scripts/ansible_get_credentials.sh
+[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match
+'all'
+
+PLAY [Install manifest on AAP controller] ******************************************************************************
+
+TASK [Retrieve API hostname for AAP] ***********************************************************************************
+ok: [localhost]
+
+TASK [Set ansible_host] ************************************************************************************************
+ok: [localhost]
+
+TASK [Retrieve admin password for AAP] *********************************************************************************
+ok: [localhost]
+
+TASK [Set admin_password fact] *****************************************************************************************
+ok: [localhost]
+
+TASK [Report AAP Endpoint] *********************************************************************************************
+ok: [localhost] => {
+    "msg": "AAP Endpoint: https://controller-ansible-automation-platform.apps.mhjacks-aeg.blueprints.rhecoeng.com"
+}
+
+TASK [Report AAP User] *************************************************************************************************
+ok: [localhost] => {
+    "msg": "AAP Admin User: admin"
+}
+
+TASK [Report AAP Admin Password] ***************************************************************************************
+ok: [localhost] => {
+    "msg": "AAP Admin Password: CKollUjlir0EfrQuRrKuOJRLSQhi4a9E"
+}
+
+PLAY RECAP *************************************************************************************************************
+localhost                  : ok=7    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
+----