diff --git a/docs/docsite/rst/collections_guide/collections_installing.rst b/docs/docsite/rst/collections_guide/collections_installing.rst index 15cc9f5065..47e782b798 100644 --- a/docs/docsite/rst/collections_guide/collections_installing.rst +++ b/docs/docsite/rst/collections_guide/collections_installing.rst @@ -10,7 +10,7 @@ Installing collections Installing collections in containers ------------------------------------ -You can install collections with their dependencies in containers known as execution environments. +You can install collections with their dependencies in containers known as Execution Environments. See `Getting started with Execution Environments `_ for details. Installing collections with ``ansible-galaxy`` diff --git a/docs/docsite/rst/command_guide/index.rst b/docs/docsite/rst/command_guide/index.rst index ea647b04e6..774745eaff 100644 --- a/docs/docsite/rst/command_guide/index.rst +++ b/docs/docsite/rst/command_guide/index.rst @@ -25,4 +25,5 @@ Ansible provides ad hoc commands and several utilities for performing various op `Ansible Navigator `_ A command-line tool and a TUI that provides a convenient user interface for most of the native Ansible command-line utilities and allows to run Ansible automation content - inside containers (`execution environments `_) + inside containers (`Execution Environments `_) + diff --git a/docs/docsite/rst/getting_started_ee/build_execution_environment.rst b/docs/docsite/rst/getting_started_ee/build_execution_environment.rst index c6ec293de3..20e133c166 100644 --- a/docs/docsite/rst/getting_started_ee/build_execution_environment.rst +++ b/docs/docsite/rst/getting_started_ee/build_execution_environment.rst @@ -70,4 +70,4 @@ Proceed to :ref:`Running your EE` and test the E .. seealso:: `Running a local container registry for EE `_ - Learn how to set up a simple local registry to host your execution environment images + Learn how to set up a simple local registry to host your Execution Environment images diff --git a/docs/docsite/rst/getting_started_ee/index.rst b/docs/docsite/rst/getting_started_ee/index.rst index 1f56d4b906..69a6858d97 100644 --- a/docs/docsite/rst/getting_started_ee/index.rst +++ b/docs/docsite/rst/getting_started_ee/index.rst @@ -7,9 +7,9 @@ Getting started with Execution Environments ******************************************* You can run Ansible automation in containers, like any other modern software application. -Ansible uses container images known as execution environments (EE) that act as control nodes. +Ansible uses container images known as Execution Environments (EE) that act as control nodes. -An execution environment image contains the following packages as standard: +An Execution Environment image contains the following packages as standard: * ``ansible-core`` * ``ansible-runner`` @@ -21,7 +21,7 @@ In addition to the standard packages, an EE can also contain: * one or more Ansible collections and their dependencies * other custom components -This getting started guide shows you how to build and test a simple execution environment. +This getting started guide shows you how to build and test a simple Execution Environment. The resulting container image represents an Ansible control node that contains the standard EE packages plus the ``community.postgresql`` collection and the ``psycopg2-binary`` Python package. .. toctree:: diff --git a/docs/docsite/rst/getting_started_ee/introduction.rst b/docs/docsite/rst/getting_started_ee/introduction.rst index 3b75fac9fc..c11a825f71 100644 --- a/docs/docsite/rst/getting_started_ee/introduction.rst +++ b/docs/docsite/rst/getting_started_ee/introduction.rst @@ -1,9 +1,9 @@ .. _introduction_execution_environments: -Introduction to execution environments +Introduction to Execution Environments ====================================== -Ansible execution environments aim to resolve complexity issues and provide all the benefits you can get from containerization. +Ansible Execution Environments aim to resolve complexity issues and provide all the benefits you can get from containerization. Reducing complexity ------------------- diff --git a/docs/docsite/rst/getting_started_ee/run_community_ee_image.rst b/docs/docsite/rst/getting_started_ee/run_community_ee_image.rst index f8d30b1fc4..d4686d3261 100644 --- a/docs/docsite/rst/getting_started_ee/run_community_ee_image.rst +++ b/docs/docsite/rst/getting_started_ee/run_community_ee_image.rst @@ -41,7 +41,7 @@ Now, create a simple test playbook and run it against localhost inside the conta See the :ref:`Running your EE guide` for an example of how to run your playbook against a remote target. -Ready to learn how to build an execution environment in a few easy steps? +Ready to learn how to build an Execution Environment in a few easy steps? Proceed to the :ref:`Building your first EE`. .. seealso:: @@ -49,4 +49,4 @@ Proceed to the :ref:`Building your first EE`. `Ansible Navigator documentation `_ Learn more about the ansible-navigator utility. :ref:`The list of tools for EE` - See the list of tools you can use execution environments with. + See the list of tools you can use Execution Environments with. diff --git a/docs/docsite/rst/getting_started_ee/run_execution_environment.rst b/docs/docsite/rst/getting_started_ee/run_execution_environment.rst index 35027d6807..5207d5690a 100644 --- a/docs/docsite/rst/getting_started_ee/run_execution_environment.rst +++ b/docs/docsite/rst/getting_started_ee/run_execution_environment.rst @@ -91,14 +91,14 @@ Before you start, ensure you have the following: .. seealso:: `Execution Environment Definition `_ - More about execution environment definition file and available options. + More about Execution Environment definition file and available options. `Ansible Builder CLI usage `_ Find out more about Ansible Builder's command-line arguments. `Ansible Navigator documentation `_ Learn more about the ansible-navigator utility. :ref:`The list of tools for EE` - See the list of tools you can use execution environments with. + See the list of tools you can use Execution Environments with. :ref:`Running community EE guide` - Learn more about running the community-provided execution environment. + Learn more about running the community-provided Execution Environment. `Running a local container registry for EE `_ - Learn how to quickly set up a local container registry for your execution environments. + Learn how to quickly set up a local container registry for your Execution Environments. diff --git a/docs/docsite/rst/getting_started_ee/setup_environment.rst b/docs/docsite/rst/getting_started_ee/setup_environment.rst index 01259658a9..0720be10a7 100644 --- a/docs/docsite/rst/getting_started_ee/setup_environment.rst +++ b/docs/docsite/rst/getting_started_ee/setup_environment.rst @@ -3,7 +3,7 @@ Setting up your environment =========================== -Complete the following steps to set up a local environment for your first execution environment: +Complete the following steps to set up a local environment for your first Execution Environment: 1. Ensure the following packages are installed on your system: diff --git a/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst b/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst index d09c3fc57f..b75af7b2ec 100644 --- a/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst +++ b/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst @@ -111,7 +111,7 @@ The following variables are common for all platforms in the inventory, though th :ansible_connection: - Ansible uses the ansible-connection setting to determine how to connect to a remote device. When working with Ansible Networking, set this to an appropriate network connection option, such as``ansible.netcommon.network_cli``, so Ansible treats the remote node as a network device with a limited execution environment. Without this setting, Ansible would attempt to use ssh to connect to the remote and execute the Python script on the network device, which would fail because Python generally isn't available on network devices. + Ansible uses the ansible-connection setting to determine how to connect to a remote device. When working with Ansible Networking, set this to an appropriate network connection option, such as``ansible.netcommon.network_cli``, so Ansible treats the remote node as a network device with a limited Execution Environment. Without this setting, Ansible would attempt to use ssh to connect to the remote and execute the Python script on the network device, which would fail because Python generally isn't available on network devices. :ansible_network_os: Informs Ansible which Network platform this hosts corresponds to. This is required when using the ``ansible.netcommon.*`` connection options. :ansible_user: The user to connect to the remote device (switch) as. Without this the user that is running ``ansible-playbook`` would be used. diff --git a/docs/docsite/rst/porting_guides/porting_guide_7.rst b/docs/docsite/rst/porting_guides/porting_guide_7.rst index 636c3eeab0..afbefac876 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_7.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_7.rst @@ -872,7 +872,7 @@ dellemc.enterprise_sonic dellemc.openmanage ~~~~~~~~~~~~~~~~~~ -- Added collection metadata for creating execution environments. +- Added collection metadata for creating Execution Environments. - Refactored the Markdown (MD) files and content for better readability. - The share parameters are deprecated from the following modules - idrac_network, idrac_timezone_ntp, dellemc_configure_idrac_eventing, dellemc_configure_idrac_services, dellemc_idrac_lc_attributes, dellemc_system_lockdown_mode. - idrac_bios - The module is enhanced to support clear pending BIOS attributes, reset BIOS to default settings, and configure BIOS attribute using Redfish. diff --git a/docs/docsite/rst/reference_appendices/tower.rst b/docs/docsite/rst/reference_appendices/tower.rst index 3537d606b1..b19257a59c 100644 --- a/docs/docsite/rst/reference_appendices/tower.rst +++ b/docs/docsite/rst/reference_appendices/tower.rst @@ -7,7 +7,7 @@ Red Hat Ansible Automation Platform Red Hat Ansible Automation Platform is available on multiple cloud platforms. See `Ansible on Clouds `_ for details. -`Red Hat Ansible Automation Platform `_ (RHAAP) is an integrated solution for operationalizing Ansible across your team, organization, and enterprise. The platform includes a controller with a web console and REST API, analytics, execution environments, and much more. +`Red Hat Ansible Automation Platform `_ (RHAAP) is an integrated solution for operationalizing Ansible across your team, organization, and enterprise. The platform includes a controller with a web console and REST API, analytics, Execution Environments, and much more. RHAAP gives you role-based access control, including control over the use of securely stored credentials for SSH and other services. You can sync your inventory with a wide variety of cloud sources, and powerful multi-playbook workflows allow you to model complex processes. diff --git a/docs/docsite/rst/shared_snippets/basic_concepts.txt b/docs/docsite/rst/shared_snippets/basic_concepts.txt index 7dfb1c20fc..2920e0a23c 100644 --- a/docs/docsite/rst/shared_snippets/basic_concepts.txt +++ b/docs/docsite/rst/shared_snippets/basic_concepts.txt @@ -2,7 +2,7 @@ Control node ============ The machine from which you run the Ansible CLI tools (``ansible-playbook`` , ``ansible``, ``ansible-vault`` and others). You can use any computer that meets the software requirements as a control node - laptops, shared desktops, and servers can all run Ansible. -You can also run Ansible in containers known as `execution environments `_. +You can also run Ansible in containers known as `Execution Environments `_. Multiple control nodes are possible, but Ansible itself does not coordinate across them, see ``AAP`` for such features. diff --git a/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst b/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst index 06cbc2c377..a082de02ee 100644 --- a/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst +++ b/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst @@ -127,7 +127,7 @@ These tips apply to using Ansible, rather than to Ansible artifacts. Use Execution Environments -------------------------- -Reduce complexity with portable container images known as `execution environments `_. +Reduce complexity with portable container images known as `Execution Environments `_. Try it in staging first -----------------------