Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-25891

U/S: Lean Ansible bindings

XMLWordPrintable

    • us-lean-ansible-bindings
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • no qe, no ux
      • upstream repository with lean ansible bindings to cover:
        • in-guest provisioning enablement
          • inventory
          • example how to make the VM accessible for Ansible and ssh
        • vm provisioning enablement
          • instanceType based, assuming volume inference
          • examples for windows with sysprep, multi nic
      • designed around simplicity and easy to maintain
      • published to ansible galaxy
      • targeting certification, but not supported
      Show
      no qe, no ux upstream repository with lean ansible bindings to cover: in-guest provisioning enablement inventory example how to make the VM accessible for Ansible and ssh vm provisioning enablement instanceType based, assuming volume inference examples for windows with sysprep, multi nic designed around simplicity and easy to maintain published to ansible galaxy targeting certification, but not supported
    • Green
    • To Do
    • CNV-25890 - Lean Ansible bindings
    • CNV-25890Lean Ansible bindings
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      2023-11-06: upstream work done...

      Show
      2023-11-06: upstream work done...
    • ---
    • ---

      Goal

      Create easy to maintain and highly auotmated ansible bindings in upstream.
      It should be an almost noop for CNV.

      Red Hat IT is looking for this, and there is no good alternative for them.

      User Stories

      • As an admin, I want manage my VMs using ansible, so that the managment of the CNV VMs is automated similar 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

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) <link to GitHub Issue>
      DEV Upstream documentation merged <link to meaningful PR>
      DEV gap doc updated <name sheet and cell>
      DEV Upgrade consideration <link to upgrade-related test or design doc>
      DEV CEE/PX summary presentation label epic with cee-training and add a <link to your support-facingĀ preso>
      QE Test plans in Polarion <link or reference to Polarion>
      QE Automated tests merged <link or reference to automated tests>
      DOC Downstream documentation merged <link to meaningful PR>

              fmatousc@redhat.com Felix Matouschek
              fdeutsch@redhat.com Fabian Deutsch
              Andrew Block, Felix Matouschek, Guido Grazioli
              Dominik Holler Dominik Holler
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: