#awx — Public Fediverse posts

Das #awx Projekt scheint keine Releases mehr für die Community veröffentlichen zu wollen. Sorry aber wtf?
https://forum.ansible.com/t/awx-modernization-ansible-jewel/45775/6

Das #awx Projekt scheint keine Releases mehr für die Community veröffentlichen zu wollen. Sorry aber wtf?
https://forum.ansible.com/t/awx-modernization-ansible-jewel/45775/6

High temperatures (ºF) in and around Alaska on Monday. Daily record high temperatures in the eastern Aleutians, Alaska Peninsula and Kodiak Island. Somewhat colder than normal eastern Interior and Southeast as well as the Yukon Territory. #awx #weather

High temperatures (ºF) in and around Alaska on Monday. Daily record high temperatures in the eastern Aleutians, Alaska Peninsula and Kodiak Island. Somewhat colder than normal eastern Interior and Southeast as well as the Yukon Territory. #awx #weather

AWX: большой рефакторинг и потеря корпоративных функций — что происходит с проектом

Для многих технических специалистов AWX на протяжении многих лет был синонимом «бесплатного Ansible Tower» — надёжным и функциональным решением для управления Ansible-автоматизацией. Это был стандарт де-факто для тех, кто хотел получить удобство (практически) "коробочного" решения и функциональность корпоративного уровня, не вкладываясь в лицензии коммерческого решения. Однако 2 июля 2024 года вышел релиз AWX версии 24.6.1, который стал последним на данный момент выпуском проекта. С тех пор прошло более полутора лет, а новых релизов так и не появилось. В репозитории проекта на GitHub висит предупреждение: «Releases of this project are now paused during a large scale refactoring». Для сообщества, активно использующего или планирующего использовать AWX как основной инструмент централизованного управления Ansible-автоматизацией, эта ситуация вызывает закономерные вопросы: Что происходит с проектом? Есть ли у него будущее? Для конечного пользователя не совсем очевидно, но AWX не умирает, а кардинально трансформируется. В данной статье мы разберем текущую ситуацию вокруг AWX, опираясь на официальные анонсы, технические дискуссии разработчиков и статусы ключевых проектов. Проанализируем архитектурные изменения проекта. Разберемся, почему эти изменения были неизбежны, что именно было «вырезано» из проекта и что всё это значит для вас — инженеров ИТ инфраструктуры и архитекторов автоматизации, которые используют AWX в своей работе и проектах.

https://habr.com/ru/companies/astralinux/articles/1002950/

#ansible #awx #eventdriven #it_automation #Infrastructure_as_a_Code_IaC #configuration_management #devops #astra_automation #network_automation

Поднимает AWX-Ansible (AWX-Operator) под Minikube в Debian

Ранее уже писал статью о поднятии AWX-Ansible но тот способ уже не работает так как в DEV образе слишком много изменений и с стабильной версии повторно не удалось развернуть (хотя полностью DEV версия прекрасно работает).

https://habr.com/ru/articles/971102/

#awx #ansible #minikube #linux #docker #automatization

:toot: Automate smarter with Ansible and AWX!

Curious about how AWX can simplify and supercharge your Ansible automation?
Our latest blog dives into what AWX is, why it matters, and how you can get started — from setup to your first automated workflow.

👉 Read more: https://atix.de/en/blog/ansible-automation-with-awx-an-overview-and-how-to-get-started/

#Ansible #AWX #Automation #DevOps #OpenSource #ATIX

:toot: Automate smarter with Ansible and AWX!

Curious about how AWX can simplify and supercharge your Ansible automation?
Our latest blog dives into what AWX is, why it matters, and how you can get started — from setup to your first automated workflow.

👉 Read more: https://atix.de/en/blog/ansible-automation-with-awx-an-overview-and-how-to-get-started/

#Ansible #AWX #Automation #DevOps #OpenSource #ATIX

Развитие Ansible: от фантастического устройства до зрелой экосистемы управления ИТ-инфраструктурой

Ansible - один из самых популярных инструментов автоматизации, но многие до сих пор используют его, ограничиваясь лишь командой ansible-playbook. С 2012 года Ansible вырос из простого инструмента в мощную экосистему, решающую проблемы с зависимостями, тестированием и централизованным управлением. Если вы все еще боретесь с конфликтами версий Python на хосте или пишете Ansible-контент без тестов - эта статья для вас. Мы разберем современный инструментарий Ansible - от Execution Environments и Ansible Navigator до Event Driven Ansible и AWX. Вы узнаете, как эти компоненты превращают Ansible в полноценную платформу автоматизации, готовую справляться как с задачами небольших команд, так и с вызовами крупных компаний. А для начала немного истории, ведь название Ansible пришло к нам прямиком из научной фантастики...

https://habr.com/ru/companies/astralinux/articles/943136/

#ansible #awx #devops #execution_environment #IT_automation #Infrastructure_as_Code_IaC #configuration_management #astra_automation #eventdriven

Ich liebe es wenn ein Plan funktioniert

Ansible mit AWX !!!

#docker #awx

Wer die neueste Version von AWX betreiben möchte, braucht einen Kubernetes Cluster.

Es muss kein richtiger Kubernetes Cluster installiert werden. Ausreichend ist es mit "kind" einen kleinen Cluster aufzubauen.

Mit der Anleitung von mir klappt das Setup, da praxiserprobt.

https://wiki.unixweb.net/books/docker/page/awx-installation-auf-kvm-mit-ubuntu-24042-lts

#awx #ansible #docker #kubernetes

Wie versprochen, der erste Artikel in der "Serie" #Kubernetes, #AWX und all die Tücken 😆 Es beginnt mit der Installation eines simplen K8s Clusters auf #Proxmox in der einfachsten Form. https://blog.maurix.net/installation-eines-minimal-kubernetes-clusters

Der #awx execution environments Kaninchenbau… what have I done

#Kubernetes #Ingress und #AWX schadet Ihnen und den Menschen in Ihrer Umgebung 😅 Nach Wochen läuft der Kram endlich über HTTPS. Scheinbar ist es gar nicht so trivial OnPremise Kubernetes mit Ingress laufen zu lassen. Aber die AWX Dokumentation ist da auch gelinde gesagt so gut wie nicht vorhanden (außer, dass vieles depricated ist). Nun ja Ingress muss mit dem Parameter "hostNetwork: true" deployed werden und ohne "ingressClassName: nginx" geht da auch nix...

Now I understand why the project is lagging. There is a big refacto in progress and breaking changes for the next release.

For example, OAuth2 tokens have been removed from the CLI https://github.com/ansible/awx/pull/15647

#awx #ansible

Now I understand why the project is lagging. There is a big refacto in progress and breaking changes for the next release.

For example, OAuth2 tokens have been removed from the CLI https://github.com/ansible/awx/pull/15647

#awx #ansible

I've spent the morning to include a patch into a home-made debian package for the Ansible awx.awx collection. My patch[1] is not yet merged upstream so I had to backport to the version we use.

The latest version of AWX has been released more than a year ago. Is the project dead?

[1] https://github.com/ansible/awx/pull/15988

#awx #ansible

I've spent the morning to include a patch into a home-made debian package for the Ansible awx.awx collection. My patch[1] is not yet merged upstream so I had to backport to the version we use.

The latest version of AWX has been released more than a year ago. Is the project dead?

[1] https://github.com/ansible/awx/pull/15988

#awx #ansible

I found Squest (https://github.com/HewlettPackard/squest/) recently, which is a self-service portal built on top of #AWX #RedHat #AAP (Ansible Automation Platform). Of course I had to try this out...

@christianhuth put together a Helm chart, while I tried to get upstream's way of deploying to work (they are using an #Ansible playbook-role construct to install this into #Kubernetes).

Here is the first result, the helm-based #vagrant #libvirt setup:
https://codeberg.org/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible

(The ansible branch using upstream's deployment will follow, once I get it working with vagrant-libvirt...)

Have a lot of fun!

#DevOps #k8s #selfserviceportal #squest #hellyeah

I found Squest (https://github.com/HewlettPackard/squest/) recently, which is a self-service portal built on top of #AWX #RedHat #AAP (Ansible Automation Platform). Of course I had to try this out...

@christianhuth put together a Helm chart, while I tried to get upstream's way of deploying to work (they are using an #Ansible playbook-role construct to install this into #Kubernetes).

Here is the first result, the helm-based #vagrant #libvirt setup:
https://codeberg.org/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible

(The ansible branch using upstream's deployment will follow, once I get it working with vagrant-libvirt...)

Have a lot of fun!

#DevOps #k8s #selfserviceportal #squest #hellyeah

Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.

Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?

#InfrastructureAsCode #DevOps #hellyeah

Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.

Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?

#InfrastructureAsCode #DevOps #hellyeah

Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),

does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?

I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.

But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)

#DevOps #security #InfrastructureAsCode #Ansible

Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),

does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?

I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.

But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)

#DevOps #security #InfrastructureAsCode #Ansible

#Kubernetes Cluster auf der #Proxmox Umgebung läuft und #AWX 2.19.1 ist auch deployed… 🥳 #homelab

#Kubernetes Cluster auf der #Proxmox Umgebung läuft und #AWX 2.19.1 ist auch deployed… 🥳 #homelab

Anyone with Ansible/AWX experience accessing HTTP APIs on protected networks?

I have tried documentation, the global web and chat with colleagues. Time to bring on the fedi human search.

Using ansible on switches that require you to come from a protected network is easy, you set up your ssh command to go through a jumphost. Accessing switches or firewalls that use an HTTP API is easy, you use a package that talks to the HTTP API, probably using the httpapi package.

But an HTTP API where you need to come from a protected network? Manually it's easy, just `ssh -D` to a jumphost/bastion in the right network and tell curl to use a SOCKS proxy.

On the Ansible side though, I can't find the right place to get httpapi to go through a SOCKS proxy, and I'm not sure where's the best place to run that ssh command.

Has anyone on Fedi already solved this problem?

#Ansible #AnsibleTower #AWX

Anyone with Ansible/AWX experience accessing HTTP APIs on protected networks?

I have tried documentation, the global web and chat with colleagues. Time to bring on the fedi human search.

Using ansible on switches that require you to come from a protected network is easy, you set up your ssh command to go through a jumphost. Accessing switches or firewalls that use an HTTP API is easy, you use a package that talks to the HTTP API, probably using the httpapi package.

But an HTTP API where you need to come from a protected network? Manually it's easy, just `ssh -D` to a jumphost/bastion in the right network and tell curl to use a SOCKS proxy.

On the Ansible side though, I can't find the right place to get httpapi to go through a SOCKS proxy, and I'm not sure where's the best place to run that ssh command.

Has anyone on Fedi already solved this problem?

#Ansible #AnsibleTower #AWX

Интеграция Jira-AWX

Всем привет, меня зовут Денис, я хотел бы поделиться опытом использования AWX в рамках одной из наших потребностей. Статья может быть полезна ребятам с «инфры», если в компании используется vmware и подобное cloud решение для частого деплоя, а для всяческой бюрократии и запросов вы обращайтесь в Jira. Недавно @kuksepa выкладывала отличную статью про AWX по этому я не стану много описывать конкретно его, а постараюсь кратко описать процесс. Прошу не обращать внимание на замазанные элементы.

https://habr.com/ru/articles/876934/

#awx #jira #jira_servicedesk #git #vcenter #vsphere #cloud #deploy #ansible #terraform

@gbraad yeah, I wish #AWX / Red Hat #Ansible Automation Platform supported Forgejo webhooks, but alas, only GitHub or GitLab... :(

AWX: упрощаем работу с Ansible

Привет, на связи Ксения Кузьменко, DevOps-инженер департамента по организации выпуска продуктов YADRO. Наша DPS-команда предоставляет платформенные сервисы для 40+ команд и 1000+ пользователей внутри компании. Мы работаем с сотнями виртуальных машин в различных локациях. Каждый день прогоняем более 250 плейбуков, из них часть связаны между собой в сложные последовательности. Конечно, инструмент для упрощения работы с Ansible был в нашей дорожной карте еще на этапе планирования. Почему мы выбрали AWX, какие задачи решили и приятные «плюшки» получили, я расскажу в статье. О некоторых подводных камнях — тоже. Нужен ли AWX в вашей команде? На этот вопрос вы ответите сами, прочитав текст под катом. Я максимально подробно описала наш опыт с Ansible AWX. Если появятся вопросы — пишите в комментариях, отвечу.

https://habr.com/ru/companies/yadro/articles/866402/

#ansible #awx #devops #netbox #hashicorp_vault #restapi #webhook #rbac

Hab heute Ansible OpenSource version AWX installiert. Siehe da es lief fast auf Anhieb ohne Fehler.

#ansible #docker #awx #opensource

Hab heute Ansible OpenSource Version AWX installiert. Siehe da es lief fast auf Anhieb ohne Fehler mit existierende Ansible Playbooks.

#ansible #docker #awx #opensource

@ansible @jpmens you can find all the announcements on the AWX modernization topic in the Forum as a follow-up to the blog post you linked:

https://forum.ansible.com/tag/awx-modernization

Follow the `#awx-modernization` tag for updates when a new post goes out!

@ansible @jpmens you can find all the announcements on the AWX modernization topic in the Forum as a follow-up to the blog post you linked:

https://forum.ansible.com/tag/awx-modernization

Follow the `#awx-modernization` tag for updates when a new post goes out!

Поднимаем AWX Ansible под podman в Debian

Недавно на работе встала задача адаптировать awx ansible под podman, в процессе установки возникло множество нюансов которые подробно распишу в данной статье.

https://habr.com/ru/articles/848654/

#awx #ansible #podman #docker #linux

We've posted the latest edition of the #Ansible Bullhorn, with news on upcoming Ansible events, CFPs, and discussions on proposed collection removals from the Ansible package.
We also have the latest #AWX update on Authentication and Role-Based Access Control changes.
https://forum.ansible.com/t/the-bullhorn-154/8658

Happy reading!

We've posted the latest edition of the #Ansible Bullhorn, with news on upcoming Ansible events, CFPs, and discussions on proposed collection removals from the Ansible package.
We also have the latest #AWX update on Authentication and Role-Based Access Control changes.
https://forum.ansible.com/t/the-bullhorn-154/8658

Happy reading!

The latest edition of the #ansible Bulhorn is out, with collection updates, a call for help on Helm chart for #awx and the upcoming #London meetup! https://forum.ansible.com/t/the-bullhorn-151/8190

The latest edition of the #ansible Bulhorn is out, with collection updates, a call for help on Helm chart for #awx and the upcoming #London meetup! https://forum.ansible.com/t/the-bullhorn-151/8190

The Bullhorn #150 is out!

This week in the Ansible newsletter you will find:
* Upcoming changes to AWX UI and credential types,
* Archival of the old Google Groups mailing lists,
* New antsibull releases and
* Updates to the mysql, postgresql and clickhouse collections

Check the newsletter for details on each of the items above!

https://forum.ansible.com/t/the-bullhorn-150/8101?u=leo

#ansible #ansiblecommunity #thebullhorn #ansiblenewsletter #awx #mysql #postgresql

The Bullhorn #150 is out!

This week in the Ansible newsletter you will find:
* Upcoming changes to AWX UI and credential types,
* Archival of the old Google Groups mailing lists,
* New antsibull releases and
* Updates to the mysql, postgresql and clickhouse collections

Check the newsletter for details on each of the items above!

https://forum.ansible.com/t/the-bullhorn-150/8101?u=leo

#ansible #ansiblecommunity #thebullhorn #ansiblenewsletter #awx #mysql #postgresql

Latest edition of the Bullhorn is out with important updates for awx operator - https://forum.ansible.com/t/the-bullhorn-147/7614
#awx #ansible

Latest edition of the Bullhorn is out with important updates for awx operator - https://forum.ansible.com/t/the-bullhorn-147/7614
#awx #ansible

Important changes coming to the #awx-operator install methods. Read on if you use this for your #awx installs - https://forum.ansible.com/t/upcoming-changes-to-awx-operator-installation-methods/7598

#ansible

latest forum post is up about the changes that could come to #awx take a peak and discuss them there if you have thoughts. https://forum.ansible.com/t/refactoring-awx-into-a-pluggable-service-oriented-architecture/7404 @ansible

📯 The Bullhorn issue 144 is now available! Check the new update on the future of AWX, the latest releases of antsibull-docs and the amazon.aws collection as well as a few events happening this week!

Read all about it here:
https://forum.ansible.com/t/the-bullhorn-144

#ansible #ansiblecommunity #newsletter #thebullhorn #awx #aws

Yo #awx and #ansible heads. I'm running into this problem with #awx and #saml where the reply address is being handed over to azure as a http address instead of a https ( which it is configured to).. Is this a nginx-ingress controller thing. Do I have a cached config somewhere. This damn k8 thing is such a bitch to try to troubleshoot!

@AndreasDavour @ansible No Ansible community replacement to my knowledge, and development ceased November 30, 2022.

Donning my former hat as a Red Hat solution architect, I would guess the suggested choice is ServiceNow with Ansible Spoke. Granted ASC never made it beyond Tech Preview, so the customer impact was likely minimal.

I don't know of any other platform that integrates with #AWX / #AnsibleController like this, so it's either a DIY job or pay another business for the integration.

Continuing on with #Ansible #AWX at work today. After making the necessary pod resource adjustments, it was able to successfully sync the large #NetBox inventory, to then I created "Constructed" (subset really) version of the inventory for a particular #datacenter, which also worked flawlessly. I have one more day of trying to get it to execute literally any playbook from a particular #git repo before the sprint ends, and have to shelve this till next month.

Tomorrow I also have #physical and #mental #health related #therapy appointments which will eat a number of hours into my day, and will possibly eliminate any chance of having #adhd levels of (hyper)focusing.

Spent quite a bit of time today resolving issues in #NetBox, custom #Ansible #Python inventory code, and #AWX. It's very interesting what's involved in turning a series of playbooks into a collection, and separating the inventory into a separate component of AWX, along with fighting #Kubernetes to ensure it allocates enough pod resources so it doesn't go "out of memory" when generating a big inventory.

Low temperatures Saturday night/Sunday morning in and around Alaska. Most areas near to a bit above normal. #awx #weather

#Ansible #AWX looks great in Safari

Had to change the config, now I wait for Ansible to run again. I swear to you all I started using Kube and avoiding Ansible for this very reason. #ansible #awx

Mild sense does it make now. It is running Ansible to install AWX….very odd #ansible #awx

I find it annoying that #ansible #awx is installed using an operator. What are people doing that they would adding or removing AWX instances so that an operator makes sense vs a normal Helm based workflow? What am I missing?

AWX 24.1.0 is out and fresh off the presses! py 3.9 -> 3.11 upgrade included as well as other fixes and new metrics support in awx-operator @ansible #ansible #awx https://forum.ansible.com/t/announcing-awx-24-1-0-and-awx-operator-2-14-0/4581