Bug 1323681 - Backport Allow option to disable Swift ring management
Summary: Backport Allow option to disable Swift ring management
Keywords:
Status: CLOSED DUPLICATE of bug 1321088
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 7.0 (Kilo)
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 12:25 UTC by Pablo Caruana
Modified: 2019-11-14 07:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-26 13:38:56 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 295314 0 None None None 2016-04-04 12:42:41 UTC

Description Pablo Caruana 2016-04-04 12:25:28 UTC 
Description of problem:

 There are quite a few cases where it is useful to disable ring building on the nodes. For example: - using different weights, regions, and zones - replacing a node in an existing Swift cluster - adding a new node to an existing cluster - using storage policies and therefore multiple rings - using different nodes and disks for account, container and object servers This patch allows it to disable ring building. Rings need to be maintained manually then, and copied to all storage and proxy nodes within a cluster. 

Version-Release number of selected component (if applicable):
OSP director 7.3 tripleo templates.

Additional info:
https://review.openstack.org/#/c/295314/
Comment 2 Dave Maley 2016-04-26 13:38:56 UTC 

*** This bug has been marked as a duplicate of bug 1321088 ***
Note You need to log in before you can comment on or make changes to this bug.