controller_configuration VS awx-ee

infra.controller_configuration 2.5.1 has been released. This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules.

The controller_configuration collection version 2.4.0 has been released.

The Infra config as Code collection group will have a Public Office hours meeting on May 11th at 9am EST/1pm UTC. Details here.

one thing is to play to what you know. Also know that collections can be roles, modules, or both. A few biased collections to look at to see the difference would be infra.controller_configuration - a set of roles to implement either the awx.awx collection or ansible.controller collection for doing configuration as code.

multiple collections with grouped roles, then playbooks to execute those roles as needed. You can also do role include like dispatch here to make it more flexible.

The infra collections have had recent updates: * infra.ah_configuration 1.1.0 Automation hub and galaxy_ng configuration. Majorly improved testing and as a result of fixes all modules and roles work on the last 3 versions of galaxy_ng and Automation Hub. * infra.controller_configuration 2.2.5 Various fixes and additions and improvements to collection, including methods to export configuration files from controller to be used by the collection. * infra.ee_utilities 2.0.6 Updated several bugs and add ability to use types in collection requirements for building execution environments

All of the collections in this group have recently released changes. This includes: * infra.controller_configuration 2.1.9 released to be compatible with recently added AWX changes. Changelog here. * infra.ah_configuration 0.9.2 Automation hub and galaxy_ng configuration. Fixed various major errors, including a major publishing error. Changelog here. * infra.ee_utilities 2.0.1 Updated to add several use cases to Execution Environment Creation. * infra.aap_utilities 2.2.2 Update to OCP installer to allow individual components.

For the server configuration, its on the kubernetes side, however for the AWX configuration of projects, job templates, credentials and the like is the redhat_cop.controller_configuration collection. It uses the awx.awx collection or the ansible.controller configuration to interact with the API to manage things in AWX. The collections are built to work with Ansible Automation Controller, but 99.9% of the time its going to work with AWX.

We are looking to upgrade our default awx-ee image to CentOS Stream 9 in the near future. We have an image built with that as a base, pushed to quay at quay.io/ansible/awx-ee:stream9-pre - Please test it out! We welcome any feedback in the Ansible AWX Matrix channel or as an issue on the ansible/awx-ee repository.

I figured it out. I grabbed the run.sh file from https://github.com/ansible/awx-ee and put it in the repo pulled from your github. Now it runs fine and I am uploading my own custom ee as we speak. Actually, I was so slow at typing that the image finished uploading. :) Going to test it now.

Take a look at AWX-EE, https://github.com/ansible/awx-ee, everything you need to build your own custom EE is there. I've built numerous custom EEs, including one that does something similar to what you described. The EE generates a new image for GCP based on the template we sent in a variable, push it to GCR once built, launch a new instance using that image. The image has ansible playbook in its startup script to bring up our application for testing.

https://github.com/ansible/awx-ee is pretty much in the same boat - it just uses the development version of ansible for the EE

I'm currently going from 15 to 19 with our test instance, and it's generally going alright, although I'm still figuring out exactly how to build our custom Execution Environment image out of fork from https://github.com/ansible/awx-ee.

just notice that awxee should contain ansible.windows in version 0.2which release 4 days ago.