openstack/openstack-ansible
Code Issues Proposed changes

Delete glusterd data along with container data

Browse Source 
When a user deletes a container and selects
`force_containers_data_destroy` it makes sense to also delete gluster
data for the container as well.

Otherwise, once containers respawn, they already do have some stale
data from the previous container which may not really work out and
would require manual cleanup.

With that, when user selects to delete all container data, it's expected
that all data for container should be destryed, so that it would be
created from scratch.

Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/924994
Change-Id: I85e3768b9611e498cbfefd1e02c12c8b94a6f30b
This commit is contained in:
Dmitriy Rabotyagov 2024-07-25 10:35:56 +02:00
parent 9f5b23a2e4
commit efbea346bb
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
playbooks/containers-lxc-destroy.yml
View File

@ -77,6 +77,7 @@
- "/openstack/{{ container_name }}"
- "/openstack/backup/{{ container_name }}"
- "/openstack/log/{{ container_name }}"
- "/openstack/glusterd/{{ container_name }}"
- "/var/log/lxc/lxc-{{ container_name }}.log"
delegate_to: "{{ physical_host }}"
when: