Actions
Tracker #22024
closedAnsible as a Remote Execution provider
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Description
Tracker for making Ansible as a Remote Execution provider - not just making the provider itself but all that should be done to ship it successfully.
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Bug #22021: Import roles from Ansible Galaxy added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocks Bug #22022: Provide a set of defined templates for the REX provider added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocks deleted (Bug #22022: Provide a set of defined templates for the REX provider)
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Bug #22022: Provide a set of defined templates for the REX provider added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Bug #22023: Documentation on how to write JobTemplates for Ansible added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Feature #22018: Change PlayHostRoles to rely on REXCore provider added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Feature #13812: Remote execution provider added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Bug #22019: Change PlayHostsRoles to rely on REXCore provider added
Updated by Daniel Lobato Garcia about 7 years ago
- Blocked by Bug #22020: Change PlayHostgroupRoles to rely on REXCore provider added
Updated by Marek Hulán about 7 years ago
Few thoughts:
Do we also need some changes on hammer side? Perhaps a story to support user input in inventory file, making sure concurrency and effective user still works as expected. The ansible job template should probably be a playbook without hosts line, perhaps we should have some validation there?
Updated by Daniel Lobato Garcia over 6 years ago
- Status changed from New to Closed
This has already been merged
Actions