Ansible Collection

Collection is a data structure used to store several #202204272021 components such as 202204272036#, 202204300820#, 202205042207# (could be multiple of them), 202204300825#, documentations and tests. The components could be updated asynchronously and independently without affecting the Ansible runtime. It is usually used for #content delivery in tar ball.

A typical directory structure for collection looks like this:

collection/
  MANIFEST.json
  playbooks/
    deployment.yaml
    ...
  plugins/
  README.md
  roles/

Links to this page

Red Hat Ansible Automation Platform

Red Hat Ansible Automation Platform provides 202204272021# automation, cloud services , and content in 202204300837# which includes infrastructure like 202204081225#, cloud or container technologies (202110201636# and 202201291535#), network (CISCO) and security including devices and how they fit in the environment.
Means to Get Ansible Collections

202204300837# could be got by using the following tools:
Automation Hub

Automation Hub is a platform for sharing contents# coming from Red Hat certified partner, community and within the organisation (published but private). It can be self-hosted in an on-premise server or cloud#. It pulls the 202204300837# using 202205251152#.
Ansible Roles

Role is a disaggregated #202204272036 which is reusable and #distributable (could be seen as a collection). It has a directory structure which includes default variables, handlers and others#, metadata (dependencies which could be fetched by 202205051149#), tasks, 202205051607#, and tests, shown as below:
Ansible Execution Environment (EE)

EE is a #202202211633 image, commonly referred to as Universal Base Image, built by Ansible Builder that incorporates 202204300837#, libraries and core# (any version of it). It replaces the Python virtual environment (virtualenv). It could be run by #202204300954.

#data-structure #automation