-
Epic
-
Resolution: Done
-
Major
-
None
-
cnv-ansible-bindings
-
Product / Portfolio Work
-
- MUST published to ansible hub
- MUST tested by QE
-
Green
-
VIRTSTRAT-442 - Lean Ansible bindings
-
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
Customers want to use kubevirt.core in a supported way.
This is actually a two step process:
- retrieve the ansible module from Ansible Galaxy
- run it locally.
This epic should cover both aspects: Publishing in the right place (galaxy), and ensuring the playbooks run properly.
User Stories
- As an admin, I want manage my VMs using ansible, so that the management of the CNV VMs is automated similarly to the automation on other VM providers.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
- depends on
-
CNV-21978 GA: Move instancetype API to GA
-
- Closed
-
- is blocked by
-
CNV-25891 U/S: Lean Ansible bindings
-
- Closed
-
-
CNV-35151 Ansible bindings should make use of managedField annotations
-
- Closed
-
- split to
-
CNV-49536 Blog post about redhat.openshift_virtualization
-
- Refinement
-
-
CNV-36701 kubevirt.core ansible improvements 4.16
-
- Closed
-
- links to
(1 links to)