openstack/python-tripleoclient
Code Issues Proposed changes

Mark upgrade_cleanup option as experimental

Browse Source 
The feature doesn't work now, the upgrade_tasks that take care of the
cleanup are being refactored by the Upgrade team. The current status of
this feature is that the upgrade will fail in some of the tasks, and
also the tasks aren't idempotent (for the ones which worked).

Until we stabilize it, let's mark it as experimental.

Related-Bug: #1774219
Change-Id: I38c411cae75c419af18a654c741a014502ecd292
This commit is contained in:
Emilien Macchi 2018-05-30 08:26:03 -07:00
parent 4ad7dff959
commit 328b0f53f1
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
releasenotes/notes/undercloud_cleanup-e52612bfd2ff4148.yaml
View File

@ -4,3 +4,4 @@ features:
The new option "upgrade_cleanup" is set to False by default but when
set to True, it'll cleanup the packages and configurations installed
on the undercloud after an upgrade.
This feature is experimental now and should be used for testing only.

5
tripleoclient/config/undercloud.py
View File

@ -284,8 +284,9 @@ class UndercloudConfig(StandaloneConfig):
cfg.BoolOpt('upgrade_cleanup',
default=False,
help=_(
'Whether to clean undercloud rpms after an upgrade'
' to a containerized undercloud.')),
'(Experimental) Whether to clean undercloud rpms '
'after an upgrade to a containerized '
'undercloud.')),
cfg.ListOpt('enabled_hardware_types',
default=['ipmi', 'redfish', 'ilo', 'idrac'],
help=_('List of enabled bare metal hardware types '