Bug 1391111

Summary: Document best practices for Swift to avoid bottlenecks
Product: Red Hat OpenStack Reporter: Christian Schwede (cschwede) <cschwede>
Component: documentationAssignee: Don Domingo <ddomingo>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kovar <pkovar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: cpaquin, cschwede, ddomingo, pkovar, srevivo
Target Milestone: ---Keywords: Documentation
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1415536 (view as bug list) Environment:
Last Closed: 2017-07-17 07:04:23 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:

Description Christian Schwede (cschwede) 2016-11-02 15:12:06 UTC
This is basically a follow up to https://bugzilla.redhat.com/show_bug.cgi?id=1381721.

The default deployment settings might not be sufficient when running larger deployment workloads, because many services are running on the same system disk on the controller nodes (ie MariaDB, RabbitMQ & Swift; with more data written to Swift in OSP10).

Therefore we need some best practices / recommendations especially for Swift to be included in our downstream documentation. 

I proposed some best practices upstream: https://review.openstack.org/#/c/389351/

http://docs-draft.openstack.org/51/389351/3/check/gate-tripleo-docs-docs-ubuntu-xenial/ecf7299//doc/build/html/advanced_deployment/deploy_swift.html#best-practices

These should be included in our downstream documentation.

Comment 8 Petr Kovar 2017-01-31 14:17:34 UTC
Thanks, Don.