Jump to: navigation, search

Difference between revisions of "Large Scale SIG/Configure"

(FAQ)
Line 6: Line 6:
  
 
== FAQ ==
 
== FAQ ==
 +
'''Q: Which drivers or backends are recommended for use at large scale?'''
  
'''Q: Which parameters should I adjust before tackling scale ?'''
+
A:
 +
 
 +
'''Q: Which parameters should I adjust in OpenStack components before tackling scale ?'''
  
 
A:  
 
A:  
 
# Number or workers for each service
 
# Number or workers for each service
 
# DB connection (max_pool_size, max_overflow, etc.)
 
# DB connection (max_pool_size, max_overflow, etc.)
 +
 +
 +
'''Q: Which parameters should I adjust in RabbitMQ before tackling scale ?'''
 +
 +
A:
  
 
== Resources ==
 
== Resources ==

Revision as of 15:15, 16 December 2020

The first stage in the Scaling Journey is Configure.

This stage is about fine-tuning configuration options and optimizing the parameters for your OpenStack cluster, so that it can handle additional load. The default values for configuration parameters in OpenStack are not always well-suited for handling scale, and OpenStack documentation does not always indicate which parameters to adjust with scale. This page aims to help answer those early questions.

Once your cluster is properly configured to handle scale, you can go to the second stage of the Scaling Journey: Monitor.

FAQ

Q: Which drivers or backends are recommended for use at large scale?

A:

Q: Which parameters should I adjust in OpenStack components before tackling scale ?

A:

  1. Number or workers for each service
  2. DB connection (max_pool_size, max_overflow, etc.)


Q: Which parameters should I adjust in RabbitMQ before tackling scale ?

A:

Resources


Other SIG work on that stage