Jump to: navigation, search

Difference between revisions of "Large Scale SIG"

Line 15: Line 15:
 
For each step the SIG will collect frequently-asked questions and answers, articles, presentations. When documentation or tools are missing, we help to produce them.  
 
For each step the SIG will collect frequently-asked questions and answers, articles, presentations. When documentation or tools are missing, we help to produce them.  
  
=== Stage 1: Configure ===
+
==== Stage 1: Configure ====
 
Tune configuration options and optimize the parameters for your OpenStack cluster, so that it can handle additional load.
 
Tune configuration options and optimize the parameters for your OpenStack cluster, so that it can handle additional load.
  
 
See [[Large_Scale_SIG/Configure]] for more details !
 
See [[Large_Scale_SIG/Configure]] for more details !
  
=== Stage 2: Monitor ===
+
==== Stage 2: Monitor ====
 
Meaningful monitoring of your cluster to detect strain and limits.
 
Meaningful monitoring of your cluster to detect strain and limits.
  
 
See [[Large_Scale_SIG/Monitor]] for more details !
 
See [[Large_Scale_SIG/Monitor]] for more details !
  
=== Stage 3: Scale up ===
+
==== Stage 3: Scale up ====
 
As you reach those limits, what can be done to handle more load within one cluster.
 
As you reach those limits, what can be done to handle more load within one cluster.
  
 
See [[Large_Scale_SIG/ScaleUp]] for more details !
 
See [[Large_Scale_SIG/ScaleUp]] for more details !
  
=== Stage 4: Scale out ===
+
==== Stage 4: Scale out ====
 
Past a given scale, you will have to scale out to multiple clusters, regions, cells or zones. What are the available options?
 
Past a given scale, you will have to scale out to multiple clusters, regions, cells or zones. What are the available options?
  
 
See [[Large_Scale_SIG/ScaleOut]] for more details !
 
See [[Large_Scale_SIG/ScaleOut]] for more details !
  
=== Stage 5: Upgrade and maintain ===
+
==== Stage 5: Upgrade and maintain ====
 
Once you have scaled out, how to do you effectively upgrade and maintain your deployment?
 
Once you have scaled out, how to do you effectively upgrade and maintain your deployment?
  
 
See [[Large_Scale_SIG/UpgradeAndMaintain]] for more details !
 
See [[Large_Scale_SIG/UpgradeAndMaintain]] for more details !
 +
 +
 +
== Other ==
 +
 +
==== Ceph and OpenStack ====
 +
Ceph is very commonly associated with OpenStack, which raises a number of questions.
 +
 +
See [[Large_Scale_SIG/CephAndOpenStack]] for more details !
  
  
Line 44: Line 52:
 
The Large Scale SIG will use mostly asynchronous communications means: discussions on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss openstack-discuss mailing-list] using the [largescale-sig] prefix, and various etherpads. Occasionally we may leverage the #openstack-operators IRC channel for synchronous discussion.
 
The Large Scale SIG will use mostly asynchronous communications means: discussions on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss openstack-discuss mailing-list] using the [largescale-sig] prefix, and various etherpads. Occasionally we may leverage the #openstack-operators IRC channel for synchronous discussion.
  
=== IRC Meeting ===
+
==== IRC Meeting ====
 
The Large Scale SIG meets on IRC typically every two weeks:
 
The Large Scale SIG meets on IRC typically every two weeks:
 
* Current [http://eavesdrop.openstack.org/#Large_Scale_SIG_Meeting IRC meeting schedule]
 
* Current [http://eavesdrop.openstack.org/#Large_Scale_SIG_Meeting IRC meeting schedule]
Line 50: Line 58:
 
* Past meetings [http://eavesdrop.openstack.org/meetings/large_scale_sig/ summary and logs]
 
* Past meetings [http://eavesdrop.openstack.org/meetings/large_scale_sig/ summary and logs]
  
=== Future events ===
+
==== Future events ====
 
* tbd
 
* tbd
  
=== Past events ===
+
==== Past events ====
 
* Project Teams Gathering meetings Wednesday Oct 28 7UTC-8UTC and 16UTC-17UTC: see https://etherpad.opendev.org/p/wallaby-ptg-largescale-sig
 
* Project Teams Gathering meetings Wednesday Oct 28 7UTC-8UTC and 16UTC-17UTC: see https://etherpad.opendev.org/p/wallaby-ptg-largescale-sig
 
* Open Infrastructure Summit, virtual, Oct 20, 2020 (forum session): see https://etherpad.opendev.org/p/vSummit2020_OpenStackScalingStory
 
* Open Infrastructure Summit, virtual, Oct 20, 2020 (forum session): see https://etherpad.opendev.org/p/vSummit2020_OpenStackScalingStory
 
* OpenDev (virtual), June 2020
 
* OpenDev (virtual), June 2020
 
* Open Infrastructure Summit, Shanghai, Nov 4, 2019 (forum session): see https://etherpad.openstack.org/p/PVG-large-scale-SIG
 
* Open Infrastructure Summit, Shanghai, Nov 4, 2019 (forum session): see https://etherpad.openstack.org/p/PVG-large-scale-SIG

Revision as of 14:42, 12 February 2021

Status: Active

Chairs:

 Belmiro Moreira <belmiro.moreira@cern.ch>
 Gene Kuo <ching.kuo@linecorp.com>
 Thierry Carrez <thierry@openstack.org>

The aim of the group is to facilitate running OpenStack at large scale, answer questions that OpenStack operators have as they need to scale up and scale out, and help address some of the limitations operators encounter in large OpenStack clusters.


The Scaling Journey

The work of the group is organized along the various stages in the scaling journey for someone growing an OpenStack deployment. That path was successfully traveled by many before, . The job of the SIG is to extract that knowledge and provide answers for those who come next.

For each step the SIG will collect frequently-asked questions and answers, articles, presentations. When documentation or tools are missing, we help to produce them.

Stage 1: Configure

Tune configuration options and optimize the parameters for your OpenStack cluster, so that it can handle additional load.

See Large_Scale_SIG/Configure for more details !

Stage 2: Monitor

Meaningful monitoring of your cluster to detect strain and limits.

See Large_Scale_SIG/Monitor for more details !

Stage 3: Scale up

As you reach those limits, what can be done to handle more load within one cluster.

See Large_Scale_SIG/ScaleUp for more details !

Stage 4: Scale out

Past a given scale, you will have to scale out to multiple clusters, regions, cells or zones. What are the available options?

See Large_Scale_SIG/ScaleOut for more details !

Stage 5: Upgrade and maintain

Once you have scaled out, how to do you effectively upgrade and maintain your deployment?

See Large_Scale_SIG/UpgradeAndMaintain for more details !


Other

Ceph and OpenStack

Ceph is very commonly associated with OpenStack, which raises a number of questions.

See Large_Scale_SIG/CephAndOpenStack for more details !


Join the SIG!

The Large Scale SIG will use mostly asynchronous communications means: discussions on the openstack-discuss mailing-list using the [largescale-sig] prefix, and various etherpads. Occasionally we may leverage the #openstack-operators IRC channel for synchronous discussion.

IRC Meeting

The Large Scale SIG meets on IRC typically every two weeks:

Future events

  • tbd

Past events