openstack/blazar
Code Issues Proposed changes

Add namespace release note

Browse Source 
In O release, Blazar has moved all namespace from climate to blazar.
This requires users of Blazar to revise their config files because of
the namespace migration.

This patch adds a release note about upgrade and deprecation, that
climate commands and config values are supported in O but will be
removed in the P release.

Change-Id: I467b5ec65ad0bafee03590c875379663c18b1ece
Closes-Bug: #1658859
Closes-Bug: #1662734
This commit is contained in:
Masahito Muroi 2017-03-07 17:18:25 +09:00 committed by Pierre Riteau
parent 7ede6931ba
commit e0dfebda7b
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
releasenotes/notes/upgrade-info-1a5b8bfbb323d525.yaml Normal file
View File

@ -0,0 +1,13 @@
---
upgrade:
- |
All entities in the 'climate' namespace, such as those used in policy.json
and some configuration values, have moved to the 'blazar' namespace in the
Ocata release. When upgrading Blazar, please replace all configuration
values including the 'climate' string by their 'blazar' equivalent.
deprecations:
- |
Commands which have 'climate' in their name are deprecated in Ocata. They
will be completely removed in the Pike release. Instead of commands
starting with 'climate', the Blazar project supports commands starting with
'blazar' from Ocata.