This epic is for the nice to have, but not necessary, advanced update of the cinder services via the operator, where it can automatically decide the best moment to update the services by monitoring its status and also be able to do a rolling update.

Without this the updates are best done using a maintenance window where we know there are no requests comming in.

In theory updates should not have DB changes or new OVO or RPC versions, making this easier for updates, but reality is sometimes different, and we have to take into account that we may have those in our updating process.

If there are OVO or RPC changes we have to be careful on how the services are started, as they may start in a compatibility mode.

If we have DB changes a DB sync will be necessary before starting the services.