search

osism / issues

This repository is used for bug reports that are cross-project or not bound to a specific repository (or to an unknown repository).
https://www.osism.tech
1 stars 1 forks source link

create possibility to undo Openstack service rollouts #255

Closed linwalth closed 2 years ago

linwalth commented 2 years ago

Having had to roll back a service manually and then investigating the services which have rolled out config depending on the service i unrolled I feel like ultimately there ought to be a solution to undo service rollouts in a more automated and controlled way.

Necessities regarding this beyond configuration management include removing entries from the central Openstack Database, and removal of containers and container images.

https://github.com/osism/mappings is probably the place where this would start.

berendt commented 2 years ago

As a first step, I would document that first. Not sure if it is worth to automate this.

berendt commented 2 years ago

@linwalth Which services specifically did you want to roll back?

linwalth commented 2 years ago

Trove, in this case. But another usecase would be cleaning up residual service containers (and volumes!) after migrating services from one server to another. Maybe a blanket solution checking and deleting containers and volumes from servers where they are not supposed to be is more fitting than specific rollbacks.

Or I just delete the containers manually, as it is not a big and/or recurring hassle. (IMO)

berendt commented 2 years ago

Will close this in favour of #302. We need some mechanism to check and ensure that everything that should run on a system is running and everything that is running and should not be running can be removed in some way.