Ansible automation hub is a portal that is a container image repository serving cloud
environments and is synchronized with the automation controller through a container
registry credential. Is this synchronization, with the automation controller, something
that has to be manually configured, or is it preconfigured with the installation of AAP?
@Trevor -
Very good questions. So you also need to understand differences in the hosted Automation Hub from Red Hat and the private automation hub that you are hosting locally as part of AAP installation.
When installing AAP, if you use the bundled installer, the provided execution environment images are uploaded to private automation hub, and providing the inventory is configured correctly, the automation controller pieces are configured and know about private automation hub and can pull the container images at-will based on the pull policy.
However, private automation hub is not initially setup to synchronize container images or collections with Red Hat or Ansible Galaxy. It is possible to set that up so that private automation hub is pulling down the container images. Likewise, the defined execution environment images on automation controller have a "pull" policy set and this determines if new container images are pulled down and how they get pulled down. If the policy is "missing" then a container image is only pulled down to controller when it is missing. If the policy is set to "always" it will always pull the container image from the source repository. Keep in mind, if your source repository is private automation hub, it may still be pulling an old image down (again depending on how the setup was initially done from the inventory file).
@Trevor -
Very good questions. So you also need to understand differences in the hosted Automation Hub from Red Hat and the private automation hub that you are hosting locally as part of AAP installation.
When installing AAP, if you use the bundled installer, the provided execution environment images are uploaded to private automation hub, and providing the inventory is configured correctly, the automation controller pieces are configured and know about private automation hub and can pull the container images at-will based on the pull policy.
However, private automation hub is not initially setup to synchronize container images or collections with Red Hat or Ansible Galaxy. It is possible to set that up so that private automation hub is pulling down the container images. Likewise, the defined execution environment images on automation controller have a "pull" policy set and this determines if new container images are pulled down and how they get pulled down. If the policy is "missing" then a container image is only pulled down to controller when it is missing. If the policy is set to "always" it will always pull the container image from the source repository. Keep in mind, if your source repository is private automation hub, it may still be pulling an old image down (again depending on how the setup was initially done from the inventory file).
Thank you Travis for another knowledge elevating reply!
There's so much packed into this condensed response!!!
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.