Allow per service configuration option to keep its systemd service unmanaged by tripleo-container-manager
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Opinion
|
Wishlist
|
Bogdan Dobrelya | ||
Bug Description
It may be a good idea to create a facility to ignore unmanned systemd units for service containers. While keeping its corresponding containers under configuration, no service nor the container should be started/enabled in that mode.
That would allow users to manually disable some non-A/A or non H/A services in systemd, like cinder-volume with some 3rd party drivers, or just putting individual services into maintenance without touching the full node. And still having its containers configs/images up to date and be ready for enablement, once the time comes.
That could be a service-specific config option in containers config, like 'managed: true' by default, and controlled via a corresponding Heat parameter, e.g. CinderVolumeUnm
| Bogdan Dobrelya (bogdando) wrote | #1 |
| Changed in tripleo: | |
| importance: | Undecided → Medium |
| milestone: | none → victoria-3 |
| summary: |
Allow per service configuration option to keep its systemd service - unmanaged + unmanaged by tripleo-container-manager |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in tripleo: | |
| importance: | Medium → Wishlist |
| tags: | added: queens-backport-potential train-backport-potential ussuri-backport-potential |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to paunch (stable/ussuri) | #2 |
| Changed in tripleo: | |
| status: | New → In Progress |
| assignee: | nobody → Bogdan Dobrelya (bogdando) |
| Bogdan Dobrelya (bogdando) wrote | #3 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to paunch (stable/train) | #4 |
| tags: | removed: queens-backport-potential |
| OpenStack Infra (hudson-openstack) wrote Fix merged to paunch (stable/ussuri) | #5 |
| tags: | added: in-stable-ussuri |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on paunch (stable/train) | #6 |
| Changed in tripleo: | |
| milestone: | victoria-3 → wallaby-1 |
| Changed in tripleo: | |
| status: | In Progress → Opinion |
In systemd, the analogue is disabled state, which is honored and not enforced.
In pacemaker, the analogue is unmanaged state, which is also honored.
So making our systemd-based local container manager tooling honoring the unmanaged state seems natural to me.