Jump to: navigation, search

Difference between revisions of "Auto-scaling SIG"

(add community resources and clarify scope)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Auto-scaling SIG ==
 
== Auto-scaling SIG ==
  
'''Status''': In review
+
This SIG is formed. Please go to following sites for more information (No plan to keep updating this WIKI page)
 +
* document: https://docs.openstack.org/auto-scaling-sig
 +
* storyboard: https://storyboard.openstack.org/#!/project/openstack/auto-scaling-sig
 +
* git repo: https://opendev.org/openstack/auto-scaling-sig
 +
 
  
 
'''Original proposal''': http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001656.html
 
'''Original proposal''': http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001656.html
Line 16: Line 20:
 
=== Goals ===
 
=== Goals ===
 
* Set up SIG, init doc, meeting, ml
 
* Set up SIG, init doc, meeting, ml
* Create Forum and Auto-scaling SIG PTG sessions
+
* Create Forum and Auto-scaling SIG PTG sessions - done, https://etherpad.openstack.org/p/DEN-auto-scaling-SIG
 +
* Collect use cases for Auto-Scaling in OpenStack
 +
* Improve documentation for Auto-Scaling features in various OpenStack services
 +
* Foster cross-project communication and development of Auto-Scaling features
  
 
=== Getting Involved ===
 
=== Getting Involved ===
Line 28: Line 35:
 
* [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss openstack-discuss mailing list]; use the <code>[auto-scaling]</code> tag
 
* [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss openstack-discuss mailing list]; use the <code>[auto-scaling]</code> tag
 
* IRC channel: #openstack-auto-scaling on [http://freenode.net/ Freenode] IRC
 
* IRC channel: #openstack-auto-scaling on [http://freenode.net/ Freenode] IRC
* Regular IRC meetings have not been arranged yet
+
* Regular IRC meetings 0900 and 2300 UTC on even weeks on IRC #openstack-auto-scaling [https://review.opendev.org/#/c/656810/]
 
* [https://review.openstack.org/#/q/project:openstack/auto-scaling-sig patch reviews] (gerrit)
 
* [https://review.openstack.org/#/q/project:openstack/auto-scaling-sig patch reviews] (gerrit)
 +
* [https://opendev.org/openstack/auto-scaling-sig Git repository for SIG] (more content coming soon)
  
 
=== SIG Chairs ===
 
=== SIG Chairs ===
Line 45: Line 53:
 
=== Past events ===
 
=== Past events ===
  
 +
* Superuser article, Sept 2018
 +
** [https://superuser.openstack.org/articles/how-to-auto-scale-a-self-healing-cluster-with-heat/ How to auto scale a self healing cluster with Heat]
 
* Events at Berlin Forum, November 2018
 
* Events at Berlin Forum, November 2018
 
** [https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Autoscaling Integration, improvement, and feedback]
 
** [https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Autoscaling Integration, improvement, and feedback]
 +
* Events at Denver OpenInfra Summit and PTG, April 2019
 +
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23379/how-blizzard-entertainment-uses-autoscaling-with-overwatch (presentation) How Blizzard uses Auto-scaling with Overwatch]
 +
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23291/scaling-should-be-easy-and-automatic-heat-and-monasca (workshop) Scaling should be Easy and Automatic]
 +
** [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto-Scaling SIG PTG etherpad]
  
 
=== Project liasons ===
 
=== Project liasons ===
 
This is a good idea, but we need some more discussion on who and how we can bridge this system up.
 
This is a good idea, but we need some more discussion on who and how we can bridge this system up.

Latest revision as of 04:26, 1 August 2019

Auto-scaling SIG

This SIG is formed. Please go to following sites for more information (No plan to keep updating this WIKI page)


Original proposal: http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001656.html

Mission

This SIG aims to improve the experience of developing, operating, and using auto-scaling and its related features (like metering, cluster schedule, life cycle management), and to coordinate efforts across projects and communities (like k8s cluster auto-scaling on OpenStack). The SIG also provides a central place to put tests, documentations, and even common libraries for auto-scaling features.

The SIG is expected to focus more on auto-scaling user workloads; however work on auto-scaling infrastructure is also welcome, especially considering that user workloads in an undercloud are actually infrastructure in the corresponding overcloud.

Background

OpenStack provides multiple methods to auto-scale your cluster (Like using Heat AutoScalingGroup, Senlin Cluster, etc.). However without general coordination across projects, it may not be easy for users and ops to achieve auto-scaling on OpenStack. Developers tend to be focused on individual projects rather than cross-project integration. Most of the components required by auto-scaling already exist within OpenStack, but we need to provide a more simple way for users and ops to adopt auto-scaling. And allowing developers to coordinate together instead of implement something all over again.

Goals

  • Set up SIG, init doc, meeting, ml
  • Create Forum and Auto-scaling SIG PTG sessions - done, https://etherpad.openstack.org/p/DEN-auto-scaling-SIG
  • Collect use cases for Auto-Scaling in OpenStack
  • Improve documentation for Auto-Scaling features in various OpenStack services
  • Foster cross-project communication and development of Auto-Scaling features

Getting Involved

We're currently working on a structure to make everyone more easier to getting involved. Our initial git repository, documentation, and other information will be up soon.

Community Infrastructure / Resources

SIG Chairs

  • Rico Lin
  • Duc Truong
  • Zane Bitter

We welcome anyone who willing to join and help. And we surely are willing to re-elect chairs as soon as we got our init setup done.

Upcoming events

TBD

Past events

Project liasons

This is a good idea, but we need some more discussion on who and how we can bridge this system up.