aca8b5fd6f
With I918b6c16db6ed70d9ad612aecd7af7d725520f7b we moved the ovn-dbs creation out of the ephemeral ovn_dbs_init_bundle container and on to the host. We left the ovn_dbs_init_bundle container around and kept the tag ovn_dbs_remove_old_cruft for it. This is because with that tag we historically triggered the needed code to make sure to handle the transition from a deployment where ovn-dbs used the internal_api VIP to the (current) deployment where ovn-dbs uses its own VIP. Since ovn-dbs has its own VIP starting with train, we can now safely drop this container. Change-Id: I5d5df3948964c28f53eda0ba5a966c824012bd4c |
||
|---|---|---|
| .. | ||
| ovn-controller-container-puppet.yaml | ||
| ovn-dbs-container-puppet.yaml | ||
| ovn-dbs-pacemaker-puppet.yaml | ||
| ovn-metadata-container-puppet.yaml | ||