This reverts commit d554d74bf0c6d61d63f92e1d8224881dd4fa726d.
This change is very problematic, because then the volumes will no longer be able to have API operations work on them, since the volumes are tied to a host, so when that host it down, things are bad.
We should keep this old (non-clean behaviour) and switch towards using Cinder clusters instead https://docs.openstack.org/cinder/latest/contributor/high_availability.html
This means configuring a few other things, but this is a really bad change and will break production deployments. I suggest we revert ASAP.
Change-Id: Iee54ef5feca5c8bee80aded75d2fd182a431adb3
Now `cinder-volume-worker` is set as DEFAULT.host. It results only
one host per volume service type registered regardless of replica
numbers.
To fix this, removed DEFAULT.host from default values so hostname
of pods will be used as host name.
It will produce garbage services with down state because pod name
changes every creation. To avoid this, added a cronjob for service
clean.
Change-Id: I9ec6f62105124f9088afdb231099b532fc83bb34
Defines compute kit and cinder jobs for new releases with
corresponding values overrides.
Disables compute agent list test for Wallaby since related API
is removed [0].
Since Wallaby with switch of osc to sdk '--id auto' is no longer
treated specially in 'openstack flavor create'. The same behavior
can be achieved w/o specifying --id flag for flavor creation [1].
Starting Wallaby 'nova-manage api_db version' returns init version
for empty database greater than 0 [2]. _db-sync.sh.tpl logic prior to
this commit does not work due to this. We need to either remove
(done in current commit) or justify and alter previous logic.
[0] https://review.opendev.org/749309
[1] https://review.opendev.org/750151
[2] https://opendev.org/openstack/nova/src/branch/stable/wallaby/nova/db/sqlalchemy/migration.py#L32
Change-Id: I361431d9aa8c1a06c5d59f479fb161ecd87e2ee2
Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
