network.base
controller_configuration
network.base | controller_configuration | |
---|---|---|
2 | 25 | |
11 | 254 | |
- | 2.0% | |
6.5 | 9.0 | |
6 days ago | 4 days ago | |
YAML | ||
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
network.base
-
The Bullhorn #106 (Ansible Newsletter)
We would have a major release for network.base - the attribute action is renamed to operation.
-
Network Automation - Keeping Source of Truth in Sync
I also started porting this into the network. It makes multivendor stuff a whole lot easier: https://github.com/redhat-cop/network.base
controller_configuration
-
The Bullhorn #114 (Ansible Newsletter)
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 Bullhorn #106 (Ansible Newsletter)
The controller_configuration collection version 2.4.0 has been released.
-
The Bullhorn #101 (Ansible Newsletter)
The Infra config as Code collection group will have a Public Office hours meeting on May 11th at 9am EST/1pm UTC. Details here.
-
Ansible Collection ideas (UNI thesis)
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.
-
What is "best"? One playbook doing everything, or many playbooks doing one thing each, or somewhere in between?
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.
- AAP 2.2 And Builder/Navigator
-
The Bullhorn #89 (Ansible Newsletter)
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
-
The Bullhorn #82 (Ansible Newsletter)
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.
- Migrate from Tower to Ansible Automation Platform
-
Federated AWX Installations
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.
What are some alternatives?
nautobot-app-data-validation-engine - Data validation rules engine app to easily codify corporate data standards
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.
ansible.scm - An ansible collection for prescriptive retrieval and publish using git
semaphore - Modern UI for Ansible
netapp.um_info - Ansible collection to support retrieving data from NetApp Unified Manager.
CommunityScrapers - This is a public repository containing scrapers created by the Stash Community.
community-topics - [Moved to Ansible Forum] Discussions for Ansible Community Meetings
community.hashi_vault - Ansible collection for managing and working with HashiCorp Vault.
ansible-build-data - Holds generated but persistent results from building the ansible community package
ee_utilities - This ansible collection includes a number of roles and tools which can be useful for managing Ansible Execution Environments.