aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristian Schwede <cschwede@redhat.com>2017-02-16 15:42:25 +0000
committerChristian Schwede <cschwede@redhat.com>2017-02-16 15:44:00 +0000
commit1edfb6fec2346cb5be310a7e601666d42a51d0e8 (patch)
treebbdbb201da706fa39adbefbb67e9525dd0a70d31
parentb323f8a16035549d84cdec4718380bde3d23d6c3 (diff)
Add missing releasenotes for Swift ring management
Change-Id: Ifef3e6f661d0094ebcc587fd6c1d0783a92ada3f
-rw-r--r--releasenotes/notes/swift-ring-keeper-c04b440d7d5ce13f.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/swift-ring-keeper-c04b440d7d5ce13f.yaml b/releasenotes/notes/swift-ring-keeper-c04b440d7d5ce13f.yaml
new file mode 100644
index 00000000..e9974a20
--- /dev/null
+++ b/releasenotes/notes/swift-ring-keeper-c04b440d7d5ce13f.yaml
@@ -0,0 +1,9 @@
+---
+fixes:
+ - |
+ Swift rings created or updated on the overcloud nodes will now be
+ stored on the undercloud at the end of each deployment. They will be
+ retrieved before any deployment update, and by doing this the Swift
+ rings will be in a consistent state across the cluster all the time.
+ This makes it possible to add, remove or replace nodes without
+ manual operator interaction.