openstack
/
paunch
Code Issues Proposed changes

Officially deprecate Paunch 

Paunch has been replaced by tripleo_container_manage role in
tripleo-ansible  during Ussuri cycle.

It is not tested anymore in this version and will be removed one day.

It it strongly encouraged to switched to the Ansible role to manage
containers; which should be the default if you deploy TripleO from
master at this time.

If you get the warning, it's possible that a parameter (EnablePaunch) is
set to True; while the default was switched.

Paunch will remain supported in Ussuri and backward, but not in Victoria
and forward.

Change-Id: I2be96c5929f0602296c8f2cebb65b755a2178195
This commit is contained in:
Emilien Macchi 2020-04-16 17:35:10 -04:00
parent 21c32c8c60
commit 3349a62393
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
paunch/builder/base.py
View File

@ -43,6 +43,9 @@ class BaseBuilder(object):
'tripleo-ansible, paunch CLI can not be used.')
raise RuntimeError(msg)
self.log.warning('Paunch is deprecated and has been replaced by '
'tripleo_container_manage role in tripleo-ansible.')
def apply(self):
stdout = []

12
releasenotes/notes/deprecated-e6b67591cda93422.yaml Normal file
View File

@ -0,0 +1,12 @@
---
prelude: >
Paunch has been replaced by tripleo_container_manage role in
tripleo-ansible during Ussuri cycle.
It is not tested anymore in this version and will be removed one day.
It it strongly encouraged to switched to the Ansible role to manage
containers; which should be the default if you deploy TripleO from
master at this time.
If you get the warning, it's possible that a parameter (EnablePaunch) is
set to True; while the default was switched.
Paunch will remain supported in Ussuri and backward, but not in Victoria
and forward.