diff --git a/modules/chapter1/pages/section1.adoc b/modules/chapter1/pages/section1.adoc index 7441e8f..a678cb9 100644 --- a/modules/chapter1/pages/section1.adoc +++ b/modules/chapter1/pages/section1.adoc @@ -2,7 +2,7 @@ *Ansible Core*: It includes the Ansible language and runtime, a set of built-in modules and command-line tools, and a framework for extending automation with collections. -*Unified UI*: Ansible Automation Platform is a modular platform. The Unified UI give you the access to all the ansible automation platform components, such as automation controller, automation hub, Automation Analytics and Event-Driven Ansible controller. +*Unified UI*: Ansible Automation Platform is a modular platform. The Unified UI gives you access to all the ansible automation platform components, such as automation controller, automation hub, Automation Analytics and Event-Driven Ansible controller. *Automation controller / Automation execution*: The Automation controller is the command and control center for Red Hat® Ansible® Automation Platform. It includes a webUI, API, https://www.redhat.com/en/topics/security/what-is-role-based-access-control[role-based access control (RBAC), window=_blank ], a workflow visualizer, and continuous integration and continuous delivery (CI/CD) integrations to help you organize and manage automation across your enterprise. diff --git a/modules/chapter1/pages/section2.adoc b/modules/chapter1/pages/section2.adoc index 0e741ea..4566d12 100644 --- a/modules/chapter1/pages/section2.adoc +++ b/modules/chapter1/pages/section2.adoc @@ -1,9 +1,9 @@ = On-premise Installation -There are 3 different ways by which you can do the installation to your local infrastructure i.e. Rpm, Containerized, and Operator. In this, we are going to learn about the Future of Deployment method which is known as Containerized installation. The RPM installation is more or less the same and as the RPM will be getting deprecated in the future our focus will be on understanding the other 2 Containerized and Operator-based deployment. +There are 3 different ways by which you can do the installation to your local infrastructure i.e. RPM, Containerized, and Operator. In this, we are going to learn about the Future of Deployment method which is known as Containerized installation. The RPM installation is more or less the same and as the RPM will be getting deprecated in the future our focus will be on understanding the other 2 Containerized and Operator-based deployment. -System Requirement +System Requirements Since the Container and Operator-based deployment needs 3000 IOPS (input/output operations per second) compared to the VM base Deployment of 1500 IOPS please refer to the below Guides while doing the deployment: @@ -19,8 +19,8 @@ image::2.1.png[] [format="csv", options="header"] |=== Mode, Infrastructure, Description , Tested topologies -RPM, Virtual machines and bare metal, The RPM installer deploys Ansible Automation Platform on Red Hat Enterprise Linux by using RPMs to install the platform on host machines. Customers manage the product and infrastructure lifecycle., RPM growth topology/RPM mixed growth topology/RPM enterprise topology and RPM mixed enterprise topolog -Containers,Virtual machines and bare metal,The containerized installer eploys Ansible Automation Platform on Red Hat Enterprise Linux by using podman which runs the platform in containers on host machines. Customers manage the product and infrastructure lifecycle, Container growth topology and Container enterprise topology +RPM, Virtual machines and bare metal, The RPM installer deploys Ansible Automation Platform on Red Hat Enterprise Linux by using RPMs to install the platform on host machines. Customers manage the product and infrastructure lifecycle., RPM growth topology/RPM mixed growth topology/RPM enterprise topology and RPM mixed enterprise topology +Containers,Virtual machines and bare metal,The containerized installer deploys Ansible Automation Platform on Red Hat Enterprise Linux by using podman which runs the platform in containers on host machines. Customers manage the product and infrastructure lifecycle, Container growth topology and Container enterprise topology Operator,Red Hat OpenShift,Operator Red Hat OpenShift The Operator uses Red Hat OpenShift Operators to deploy Ansible Automation Platform within Red Hat OpenShift. Customers manage the product and infrastructure lifecycle,Operator growth topology and Operator enterprise topology |=== @@ -28,4 +28,4 @@ By following the tested deployment models recommended by Red Hat, organizations The RPM deployment is expected to be deprecated in the future. Therefore, this training will be primarily focused on the other two deployment methods: Containerized and Operator. -Feel free to learn more about https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/tested_deployment_models/rpm-topologies#rpm-a-env-a[RPM Tested topologies,window=_balnk]. \ No newline at end of file +Feel free to learn more about https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/tested_deployment_models/rpm-topologies#rpm-a-env-a[RPM Tested topologies,window=_blank]. \ No newline at end of file diff --git a/modules/chapter1/pages/section3.adoc b/modules/chapter1/pages/section3.adoc index af298cd..e9aed42 100644 --- a/modules/chapter1/pages/section3.adoc +++ b/modules/chapter1/pages/section3.adoc @@ -20,4 +20,4 @@ PORT,PROTOCOL,Service,Component Note: The above are default destination ports and the installer inventory listed is configurable. If you choose to configure them to suit your environment, you might experience a change in behavior. -For more information on Variables that can be used to change the port refer to the https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/planning_your_installation/index#system_requirements_for_rpm_installation[Planning your installation of Ansible Automation Platform., windows=_blank] +For more information on Variables that can be used to change the port refer to the https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/planning_your_installation/index#system_requirements_for_rpm_installation[Planning your installation of Ansible Automation Platform., window=_blank] diff --git a/modules/chapter1/pages/section4.adoc b/modules/chapter1/pages/section4.adoc index dd53402..5dd06d7 100644 --- a/modules/chapter1/pages/section4.adoc +++ b/modules/chapter1/pages/section4.adoc @@ -24,7 +24,7 @@ For cluster eg: aap1.example.org aap2.example.org -The above is a example of cluster setup and there is no need to explicitly tell the script as it will take care of it automatically. This behavior is the same for different components apart from the database. +The above is an example of cluster setup and there is no need to explicitly tell the script as it will take care of it automatically. This behavior is the same for different components apart from the database. The Containerized installation offers two types of deployment topologies from which to choose: diff --git a/modules/chapter1/pages/section5.adoc b/modules/chapter1/pages/section5.adoc index 92d9868..df1b56d 100644 --- a/modules/chapter1/pages/section5.adoc +++ b/modules/chapter1/pages/section5.adoc @@ -2,7 +2,7 @@ We will be using *Product Enablement Containerized AAP 2.5* LAB for this deployment. Please be aware that setting up a RHEL 9 system in this lab will take about ten minutes. Following that, you can proceed with the installation procedures: -The below video demonstrate the step to step guide to do the installtion of all components on a single system itslef: +The below video demonstrates the step to step guide to do the installation of all components on a single system itself: video::container_aap_lab.mp4[align="left",width=800,height=500] @@ -69,7 +69,7 @@ $ ansible-playbook -i inventory-growth ansible.containerized_installer.install . Simply use the hostname from the lab deployment login page and try to access the URL from the browser on the port *443*. -. Use the user *admin* and the *password* set during the time of installation. In the above video i set it to *redhat*. +. Use the user *admin* and the *password* set during the time of installation. In the above video I set it to *redhat*. Note: Try to use stronger password while doing the enterprise deployment diff --git a/modules/chapter1/pages/section6.adoc b/modules/chapter1/pages/section6.adoc index b26f3e3..59e4322 100644 --- a/modules/chapter1/pages/section6.adoc +++ b/modules/chapter1/pages/section6.adoc @@ -4,9 +4,9 @@ The Ansible Automation Platform Operator provides cloud-native, push-button depl Note: You can deploy multiple isolated instances of Ansible Automation Platform into the same Red Hat OpenShift Container Platform cluster by using a namespace-scoped deployment model. This approach allows you to use the same cluster for several deployments. -There are two deployment Topologies in this: +There are two deployment topologies in this: -. *Operator growth Topology*: The growth topology is intended for organizations that are getting started with Ansible Automation Platform and do not require redundancy or higher computing for large volumes of automation. This topology allows for smaller footprint deployments. +. *Operator growth topology*: The growth topology is intended for organizations that are getting started with Ansible Automation Platform and do not require redundancy or higher computing for large volumes of automation. This topology allows for smaller footprint deployments. + image::6.1.png[] + @@ -26,7 +26,7 @@ The above infrastructure topology describes an OpenShift Cluster with 3 primary + The benefits of using this topology method: -.. Designed for large-scale operations with High availability and fault tolerance. +.. Designed for large-scale operations with high availability and fault tolerance. .. Optimized for enterprise environments with strict SLAs. .. Multiple instances for each component: Automation Hub, Controller, etc. diff --git a/modules/chapter1/pages/section7.adoc b/modules/chapter1/pages/section7.adoc index 594e1a2..4bc54bc 100644 --- a/modules/chapter1/pages/section7.adoc +++ b/modules/chapter1/pages/section7.adoc @@ -6,7 +6,7 @@ The following video will provide the step-by-step guide for installing the Ansib video::operator_aap.mp4[align="center",width=800,height=500] -All the followed steps in the vidoe are shared below: +All the followed steps in the video are shared below: . Log in to the Red Hat OpenShift Container Platform. . Navigate to Operators OperatorHub. @@ -18,7 +18,7 @@ All the followed steps in the vidoe are shared below: . Select project as *aap* if it's not aap. -. There scroll to the option *Ansible Automation Platform* and click on *Create instance* which will deploy all the componenets of *AAP*. +. There scroll to the option *Ansible Automation Platform* and click on *Create instance* which will deploy all the components of *AAP*. . Provide the *Name* on which will be used to create the resources for that *AAP* like network routes,secrets. diff --git a/modules/chapter1/pages/section8.adoc b/modules/chapter1/pages/section8.adoc index e8c690e..6b89fd2 100644 --- a/modules/chapter1/pages/section8.adoc +++ b/modules/chapter1/pages/section8.adoc @@ -1,6 +1,6 @@ = Summary -- Understanding the components of Ansible Autoamtion Platform. +- Understanding the components of Ansible Automation Platform. - Getting information about the installation topologies/methods. - How to evaluate correct deployment according to the Infrastructure. - Network ports and protocols that help in the communication of AAP.