-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Implement service/container cleanup after they're removed
-
Tech Debt
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
In Progress
-
Proposed
-
rhos-ops-day1day2-edpm
-
Proposed
-
0% To Do, 100% In Progress, 0% Done
-
-
-
-
EDPM Sprint 13, EDPM Sprint 14
-
2
This is required when a service/container has already been deployed, but has to be removed as part of update/upgrade or redeployment when the service is dropped.
We had this feature[1] in TripleO where we used to compare the new and the old config and remove all containers not in the new config (orphaned) managed by tripleo/paunch. Now that we manage every service separately there is no single place to get the new config to be deployed. We need a way to identify which all services/containers should be cleaned up and remove them during deployment/update/upgrade.