|
6 | 6 |
|
7 | 7 | If you've followed a link to this repository, but are not really sure what it contains |
8 | 8 | or how to use it, head over to [Ansible Edge GitOps](http://validatedpatterns.io/ansible-edge-gitops/) (which this pattern is derived from) for additional context and installation instructions |
| 9 | + |
| 10 | +## Basics & Setup |
| 11 | + |
| 12 | +This Validated Pattern lays the OTEL based infrastructure foundation to setup observability in federated and/or distributed environments. |
| 13 | +The infrastructure components are a central OpenShift Hub server with 4 edge nodes which are running as preconfigured virtual machines on OpenShift-Virtualization (OCP-V). |
| 14 | + |
| 15 | +The technology components used here are |
| 16 | +- OpenShift, |
| 17 | +- ArgoCD as OpenShift GitOps, |
| 18 | +- Hashicorp Vault, |
| 19 | +- OpenShift Virtualization, |
| 20 | +- Ansible Automation Platform, |
| 21 | +- OpenShift Data Foundations (ODF), |
| 22 | +- Red Hat Device Edge (running at the edge), |
| 23 | +- OpenTelemetry. |
| 24 | + |
| 25 | +The installation at the OpenShift hub cluster happens via Operators (subscriptions), the pattern itself (see values-hub.yaml) or via an Ansible playbook (OTEL at the edge) while the installation at the edge happens via an Ansible playbook installing an RPM: https://github.com/validatedpatterns-demos/rhvp.federated_edge_observability/blob/main/roles/otel_collector/tasks/main.yml |
| 26 | +ArgoCD is managing the applications as defined in the values-hub.yaml file. |
| 27 | + |
| 28 | +The user/password/key config happens in your user home (!) directory via the values-secret.yaml, so make sure you copy and then edit your values-secret.yaml.template to ~/values-secret.yaml. |
| 29 | + |
| 30 | +There are several different git repositories in play which serve different purposes. The multiple git repos serve the purpose of easy customization and adoption into different environments. |
| 31 | + |
| 32 | +### GitRepos setup |
| 33 | + |
| 34 | +#### Federated Edge Observability |
| 35 | +This pattern repo is the starting point and main git repo: |
| 36 | +https://github.com/validatedpatterns-sandbox/federated-edge-observability |
| 37 | + |
| 38 | +The edge node setup is stored under $patterDir/overrides/values-egv-feo.yaml |
| 39 | + |
| 40 | +#### RHVP Federated Edge Observability |
| 41 | +This pattern repo contains roles & Ansible playbooks for the edge device configuration: |
| 42 | +https://github.com/validatedpatterns-demos/rhvp.federated_edge_observability |
| 43 | + |
| 44 | +#### Config as Code |
| 45 | +This repo holds the AAP configuration |
| 46 | +https://github.com/validatedpatterns-demos/federated-edge-observability-config-as-code |
| 47 | + |
| 48 | +#### Edge Inventory |
| 49 | +This git repo holds the edge inventory |
| 50 | +https://github.com/validatedpatterns-demos/federated-edge-observability-inventory |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | + |
| 56 | + |
0 commit comments