Bug 1469441

Summary:	[RFE][Swift] Set partition power based on number of disks
Product:	Red Hat OpenStack	Reporter:	Christian Schwede (cschwede) <cschwede>
Component:	puppet-swift	Assignee:	Christian Schwede (cschwede) <cschwede>
Status:	CLOSED NOTABUG	QA Contact:	Mike Abrams <mabrams>
Severity:	low	Docs Contact:
Priority:	low
Version:	14.0 (Rocky)	CC:	cschwede, jjoyce, jschluet, sclewis, slinaber, tvignaud
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	cschwede: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-24 12:21:46 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:	1469435
Bug Blocks:

Description Christian Schwede (cschwede) 2017-07-11 09:35:41 UTC

As an operator with a lot of storage nodes/disks, I want the partition power for Swift to be larger than today.

Today the partition power in director installations is fixed to 10. This is most 
likely fine for most standard installations; however if there is a large number of disks and/or storage nodes, it might not be sufficient and should be larger by default. There is an option to define this during the initial deployment, but operators might not be aware of this and therefore it should be set based on the number of available disks.

See https://access.redhat.com/articles/2745961 for some best practice numbers.

Comment 5 Christian Schwede (cschwede) 2020-08-24 12:21:46 UTC

Closing this BZ. We have a doc section covering this (https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/deployment_recommendations_for_specific_red_hat_openstack_platform_services/svc-objectstorage#svc-objectstorage-partition), and in case of very large Swift clusters operators need to decide which partition power is the right one. This should likely not be automated. Additionally, the upstream bug has been abandoned as well.