6c5f2b8f69
The services-docker env files now all reside in services and became defaults. We need to delete those copies to not allow desync of contents. Depends-On: I48dd13dd574147950a8f20f39b8f5c84ca7d2c6c Depends-On: I1e264a03b10c1a5244e9a604c45c608c19037827 Change-Id: I0c343e3dd01ad864bad8c7632261c9db4b28b5df
17 lines
723 B
YAML
17 lines
723 B
YAML
---
|
|
features:
|
|
- |
|
|
Containers are now the default way of deploying. There is still a way to
|
|
deploy the baremetal services in environments/baremetal-services.yaml, but
|
|
this is expected to eventually disappear.
|
|
upgrade:
|
|
- |
|
|
Environment files originally referenced from `environments/services-docker`
|
|
should be altered to the `environments/services` paths. If some of the
|
|
deployed baremetal services need to be retained as non-containerized,
|
|
update its references to `environments/services-baremetal` instead of
|
|
`environments/services`.
|
|
|
|
.. note:: Starting from Rocky, overcloud upgrades to baremetal services
|
|
(non-containerized), or mixed services is no more tested nor verified.
|