Overview
We need to add a feature or role to our openshift virtualization migration collection that provides the ability to dynamically generate an Ansible inventory of all Virtual Machines deployed within a specific target OpenShift cluster.
Problem Statement
Currently, setting up an inventory using the redhat.openshift.openshift_virtualization plugin requires manual configuration and lacks a standardized, automated way within our collection to scope the inventory to a specific cluster context. To scale our Migration Factory workflows, the collection needs to inherently support generating or templating inventories targeted at a specific cluster.
Proposed Solution
Introduce a mechanism (such as a dedicated role, playbook, or inventory template) within the collection that automates the generation of a cluster-specific inventory.
The implementation should:
- Allow specifying a target cluster's connection details as variables.
- Generate a functional inventory configuration using the
redhat.openshift.openshift_virtualization plugin tailored to that specific cluster.
- Provide clean mapping so that the resulting inventory accurately reflects all OpenShift Virtualization workloads (VMs/VMIs) running on that specific cluster.
Technical Requirements
- Create a role or template within the collection to output/handle cluster-scoped dynamic inventory configurations.
- Ensure it integrates seamlessly with AAP (Ansible Automation Platform) credential types for OpenShift/Kubernetes clusters.
Acceptance Criteria
Overview
We need to add a feature or role to our
openshift virtualization migrationcollection that provides the ability to dynamically generate an Ansible inventory of all Virtual Machines deployed within a specific target OpenShift cluster.Problem Statement
Currently, setting up an inventory using the
redhat.openshift.openshift_virtualizationplugin requires manual configuration and lacks a standardized, automated way within our collection to scope the inventory to a specific cluster context. To scale our Migration Factory workflows, the collection needs to inherently support generating or templating inventories targeted at a specific cluster.Proposed Solution
Introduce a mechanism (such as a dedicated role, playbook, or inventory template) within the collection that automates the generation of a cluster-specific inventory.
The implementation should:
redhat.openshift.openshift_virtualizationplugin tailored to that specific cluster.Technical Requirements
Acceptance Criteria