At SUSE we've implemented a module on Salt called ansiblegate which allows to run and manage your Ansible clusters using Salt.
This a very powerful module that bring lot of value to Salt when the users are planning on migrating or starting to use Salt and they already have an existing Ansible infrastructure.
Some of the key values of the ansiblegate module are:
- Allow to run Ansible modules on minions.
- Re-use the Ansible inventory to run Salt actions on Ansible-managed nodes.
- Manage your Ansible infrastructure using Salt. Even to run your Ansible playbooks.
- Allow working in a hybrid infrastructure where Salt and Ansible can coexist.
- Bring Salt cool features like real time monitoring and event-driven orchestration to Ansible-managed nodes.
During last SUSECon19 we made a presentation titles "How to smootly migrate from Ansible to Salt" where we explained multiple scenarios and did some demos using ansiblegate. You can see the video at https://www.youtube.com/watch?v=tC9Bkesr2zU
The goals of this HW project are:
- Fix some bugs that prevents "ansiblegate" to run smootly on Salt 2019.2.0.
- Write some articles and make a screencast to show how cool this is and to spread the knowledge.
Looking for hackers with the skills:
This project is part of:
Hack Week 18
Activity
Comments
-
over 6 years ago by PSuarezHernandez | Reply
Fixed the issues with "ansiblegate" on 2019.2.0: https://github.com/saltstack/salt/pull/53661
The console recording will be uploaded soon!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/