awx-ee
ansible-awx-ee
| awx-ee | ansible-awx-ee | |
|---|---|---|
| 9 | 2 | |
| 121 | 2 | |
| 2.5% | - | |
| 5.5 | 10.0 | |
| 11 days ago | over 1 year ago | |
| Dockerfile | Shell | |
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awx-ee
- Ansible Linux Docker just accepted in Awesome Docker repository
-
The Bullhorn #89 (Ansible Newsletter)
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.
-
Upgrade ansible version in awx-operator in community.vmware
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.
-
Packer in an execution environment?
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.
- Ansible-Builder - PIP looking at multiple versions
-
AWX custom EE - how can you control the version of an sible being used?
https://github.com/ansible/awx-ee is pretty much in the same boat - it just uses the development version of ansible for the EE
-
AWX v8 to 19.1.0 migration
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.
-
The module ansible.legacy.setup was redirected to ansible.windows.setup, which could not be loaded.
just notice that awxee should contain ansible.windows in version 0.2which release 4 days ago.
ansible-awx-ee
- "msg": "winrm or requests is not installed: No module named 'winrm'"
-
Upgrade ansible version in awx-operator in community.vmware
Let me fix that. FYI, you can build your own. I've added some simplified instructions + scripts here: https://github.com/aimcod/ansible-awx-ee
What are some alternatives?
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
k8awx
ansible-collection-vultr
controller_configuration - A collection of roles to manage Ansible Controller and previously Ansible Tower
ansible-inclusion - Requests to include new collections into the ansible package
Pure1-Collection - Ansible Collection for Pure Storage Pure1
ee_utilities - This ansible collection includes a number of roles and tools which can be useful for managing Ansible Execution Environments.
ansible-linux-docker - This Docker image allows to run Ansible from a Linux container. It supports Linux, Windows and MacOS target hosts.
community-topics - Discussions for Ansible Meetings