Skip to content

Commit 6f604e2

Browse files
Merge pull request #632 from validatedpatterns/ocaas-upd8
OCaaS Docs Update
2 parents fbd8048 + 4fb92ea commit 6f604e2

File tree

10 files changed

+9
-8
lines changed

10 files changed

+9
-8
lines changed

content/patterns/omnicloud/_index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ links:
1717
install: getting-started
1818
bugs: https://github.com/validatedpatterns-sandbox/omnicloud-as-a-service/issues
1919
feedback: https://docs.google.com/forms/d/e/1FAIpQLScI76b6tD1WyPu2-d_9CCVDr3Fu5jYERthqLKJDUGwqBg7Vcg/viewform
20+
2021
ci: omnicloud
2122
---
2223

@@ -37,7 +38,7 @@ To overcome these obstacles, organizations need an automated, self-service solut
3738

3839
Omnicloud as a Service pattern was created to address these challenges by offering Omnicloud as a Service capabilities, empowering teams to deploy OpenShift workflows quickly, consistently, and securely across multiple cloud platforms, while minimizing manual effort and accelerating time to innovation.
3940

40-
<img width="1850" height="1059" alt="image" src="https://github.com/user-attachments/assets/b0170cc5-ab50-4fb9-b645-771a26f6ddf9" />
41+
<img width="1850" height="1059" alt="image" src="/images/omnicloud/workflow.png" />
4142

4243
#### Key features of OCaaS includes
4344

content/patterns/omnicloud/getting-started.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The Omnicloud as a Service setup currently spans multiple environments, with an
5050

5151
Execution of pattern also involves importing of newly deployed cluster into RHACM, and a DevOps cartridge containing preconfigured development tools are deployed in a dedicated namespace for the developer. Additionally, an Active Directory (AD) user account is created and integrated with OpenShift to enable domain-based authentication.
5252

53-
<img width="2000" height="1125" alt="image" src="https://github.com/user-attachments/assets/4463797f-f1e5-44d9-a621-d6e85f8a91ae" />
53+
<img width="2000" height="1125" alt="image" src="/images/omnicloud/ocaas_logical.png" />
5454

5555
## Key Concepts
5656

@@ -177,21 +177,21 @@ The default login user for the AAP interface is admin, and the password is rando
177177
Follow these steps to log in to the Ansible Automation Platform using the OpenShift console:
178178

179179
1. In the OpenShift console, go to Workloads > Secrets and select the ansible-automation-platform project if you want to limit the number of secrets you can see.
180-
<img width="1897" height="622" alt="image" src="https://github.com/user-attachments/assets/1b3e9a26-36cd-4fdc-9673-8b78be9cc9bb" />
180+
<img width="1897" height="622" alt="image" src="/images/omnicloud/aap_ocp_secrets.png" />
181181

182182
Select the controller-admin-password.
183183
In the Data field click Reveal values to display the password.
184-
<img width="1206" height="515" alt="image" src="https://github.com/user-attachments/assets/6014b602-c5c5-4a1d-87ca-0f27f9b6ff63" />
184+
<img width="1206" height="515" alt="image" src="/images/omnicloud/aap_controller_secret.png" />
185185

186186
2. Under Networking > Routes, click the URL for the aap route to open the Ansible Automation Platform interface.
187187

188188
Log in using the admin user and the password you retrieved from the aap-admin-password secret. A screen similar to the following appears:
189189

190-
<img width="1918" height="1007" alt="image" src="https://github.com/user-attachments/assets/53a0d729-d6da-4af0-abc6-86376a78863f" />
190+
<img width="1918" height="1007" alt="image" src="/images/omnicloud/aap_console.png" />
191191

192192
## Automation Breakdown
193193

194-
<img width="1141" height="658" alt="image" src="https://github.com/user-attachments/assets/2192ba4a-7a3c-4fe3-931a-11cc20c6f761" />
194+
<img width="1141" height="658" alt="image" src="/images/omnicloud/directory_layout.png" />
195195

196196
## Technical Requirements
197197

@@ -204,7 +204,7 @@ branch: main
204204

205205
This pattern is currenty tested on AWS, Azure & GCP environment running with Red Hat OpenShift cluster version 4.19. The codebase utilizes the following languages and tools: Shell, Python, Makefile, and Docker
206206

207-
<img width="1902" height="835" alt="image" src="https://github.com/user-attachments/assets/c0c508d7-562a-4212-98b1-545499c859cc" />
207+
<img width="1902" height="835" alt="image" src="/images/omnicloud/ocaas_detail_workflow.png" />
208208

209209
This workflow demonstrates a robust, automated solution for self-service provisioning and de-provisioning of Red Hat OpenShift Container Platform (OCP) clusters across multiple cloud providers (e.g., Google Cloud, Azure, AWS). The automation leverages Ansible Automation Platform (AAP) to manage the deployment tasks and Red Hat Advanced Cluster Management (RHACM) to orchestrate and manage the resulting clusters. This approach enables rapid, consistent, and repeatable cluster creation on demand.
210210

@@ -266,7 +266,7 @@ For connected environments:
266266

267267
###### Table 1. Hub cluster minimum requirements
268268

269-
<img width="551" height="225" alt="image" src="https://github.com/user-attachments/assets/354621c7-8c12-4c91-aa86-4e248ba23d84" />
269+
<img width="551" height="225" alt="image" src="/images/omnicloud/cluster_sizing.png" />
270270

271271
## Getting Started
272272

162 KB
Loading
83.2 KB
Loading
113 KB
Loading
15.7 KB
Loading
154 KB
Loading
328 KB
Loading
240 KB
Loading
256 KB
Loading

0 commit comments

Comments
 (0)