[cleanup_openstack] enhance cleanup for infrastructure reuse #3473
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7eaaa34d066444eba0136148611369dc ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 57s |
@eshulman2 (I deleted the previous comment because I completely misunderstood your question, sorry Ella 🙇🏻 ) BTW I want to keep use that role, i just tried to address some aspects:
I don't know if all of this will lead to a bulletproof procedure but i heard some feedback about the reliability of this cleanup procedure and i'd like to improve it. Any kind of suggestion is more than welcome though! |
rebtoor
changed the title
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/384b0a9282964a6cad26847d17890532 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 02s |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/689e395593904c7180a66b83f187edee ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 41m 30s |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d0f82689056044bab35e7d66f2f7c30d ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 46m 37s |
rebtoor
force-pushed
the
OSPRH-21759
branch
6 times, most recently
from
16471c0 to
bf9b991
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/131597c22c9049c281ec693790095b54 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 49m 05s |
rebtoor
force-pushed
the
OSPRH-21759
branch
2 times, most recently
from
ef442aa to
83afa3d
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6749298792164c1fb3eb416ca5225304 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 05s |
Enhance the cleanup_openstack role to support infrastructure reuse by cleaning up OpenStack resources while preserving the OpenShift cluster infrastructure. This enables faster test cycles by avoiding full infrastructure reprovisioning. Changes: - Add cleanup-openstack-for-reuse.yml playbook for direct use - Add cleanup_crs_direct.yaml to delete OpenStack CRs directly from cluster - Add cleanup_openstack_api.yaml to delete OpenStack API resources (servers, networks, volumes, etc.) before CR deletion to prevent orphaned resources - Add cleanup_storage.yaml to clean up PVCs, secrets, ConfigMaps, and PVs - Add cleanup_namespaces.yaml to optionally delete empty namespaces - Add common.yaml to eliminate code duplication (kubeconfig/auth params) - Add clean-config-drives-only.yml playbook to clean config drive ISO files for infrastructure reuse (prevents conflicts when reusing VMs) - Refactor CR deletion patterns to use loops, reducing code duplication - Fix execution order: API resources are deleted first while control plane is still running, then CRs are deleted - Preserve infrastructure operators (NMState, MetalLB, OLM) for cluster reuse - Add configurable variables for granular cleanup control - Update README with comprehensive documentation - Update dictionary with new terms from documentation Related: OSPRH-21759 Signed-off-by: Roberto Alfieri <[email protected]>
2 participants
Enhance the cleanup_openstack role to support infrastructure reuse by
cleaning up OpenStack resources while preserving the OpenShift cluster
infrastructure. This enables faster test cycles by avoiding full
infrastructure reprovisioning.
Changes:
networks, volumes, etc.) before CR deletion to prevent orphaned resources
is still running, then CRs are deleted
Assisted-By: Cursor AI Assistant
Related: OSPRH-21759