Bug 1319901

Summary:	Document how to deploy and scale swift and manage swift rings
Product:	Red Hat OpenStack	Reporter:	Dougal Matthews <dmatthew>
Component:	documentation	Assignee:	Don Domingo <ddomingo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Radek Bíba <rbiba>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	adahms, ddomingo, dmacpher, dmatthew, jslagle, rbiba, sasha, srevivo
Target Milestone:	ga	Keywords:	Documentation
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-11 23:49:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1310865
Bug Blocks:

Description Dougal Matthews 2016-03-21 18:44:15 UTC

Deploying and scaling swift requires some manual steps. This is outlined in this upstream patch. https://review.openstack.org/#/c/293311/

We need to document this process for OSP8.

Let me know what other details you need.

Comment 2 Andrew Dahms 2016-03-21 22:04:54 UTC

Updated release flags and priority.

Comment 6 Dan Macpherson 2016-03-22 01:24:23 UTC

@dmatthew, just for clarification, what's the difference between the ring that the director creates vs the one that you manually create?

Comment 7 Dan Macpherson 2016-03-22 01:30:22 UTC

@dmatthew, also does this only affect OSP8, or does it affect previous OSP7 Overclouds?

Comment 9 Dougal Matthews 2016-03-22 07:55:26 UTC

Don - Yes, this is a workaround for a bug in director.

(In reply to Dan Macpherson from comment #6)
> @dmatthew, just for clarification, what's the difference between the ring
> that the director creates vs the one that you manually create?

I don't have enough swift knowledge to answer this in as much detail as you might need. However, the primary issue is that new Swift nodes when scaling up will not be added to the existing Swift Ring. It seems that new Rings may be created and the state of Swift then becomes unclear.

I think there may also be a problem with the defaults of the ring that director creates.

If that doesn't help, I would recommend needinfo'ing cschwede. He has a good understanding of this issue.


(In reply to Dan Macpherson from comment #7)
> @dmatthew, also does this only affect OSP8, or does it affect previous OSP7
> Overclouds?

I believe this will also affect OSP7. This is a limitation that has always existed in upstream TripleO since initial Swift Ring support was added and still does.

Comment 14 Mike McCune 2016-03-28 22:27:32 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 16 Don Domingo 2016-03-31 02:28:50 UTC

*** Bug 1322614 has been marked as a duplicate of this bug. ***

Comment 17 Andrew Dahms 2016-05-03 13:13:18 UTC

Assigning Radek as the QA contact.

Radek - can you take a look at the changes for this bug?

Comment 18 Radek Bíba 2016-05-04 09:03:31 UTC

Looks great.

Comment 19 Andrew Dahms 2016-07-11 23:49:50 UTC

This content is live on the Customer Portal.

Closing.