Disable Paunch by default on the Undercloud

Disabling Paunch on the Undercloud has proven to be stable enough over
the last weeks, we can safely make it the default to move forward.

Depends-On: I707b2f66eb947d64ef6a21238dc26c81575be2c7
Change-Id: I8822b3515046a4263242d5e1249bb9bac8d80d91
This commit is contained in:
Emilien Macchi 2019-12-28 18:11:34 -05:00
parent d8e0c5389c
commit dafacfcbf7
2 changed files with 8 additions and 1 deletions

View File

@ -0,0 +1,7 @@
---
features:
- |
Paunch is now disabled by default when the Undercloud is deployed
and upgraded. Containers will be started by Ansible and not Paunch
anymore. One can enable Paunch again with undercloud_enable_paunch
set to True.

View File

@ -285,7 +285,7 @@ class UndercloudConfig(StandaloneConfig):
help=_('Enable or disable SELinux during the '
'deployment.')),
cfg.BoolOpt('undercloud_enable_paunch',
default=True,
default=False,
help=_('Enable or disable Paunch to manage '
'containers.')),
cfg.BoolOpt('undercloud_update_packages',