openstack/auto-scaling-sig
Code Issues Proposed changes
7018ada28f
auto-scaling-sig/use-cases/autoscale-compute-custom-metrics.rst
Joseph Davis 8e2ce29cdf Capture initial set of Use Cases 
Pulling from the etherpad at the Denver 2019 PTG and inserting in
to the template format.  Much more detail can be fleshed out, but
this gives a framework to start.

Change-Id: If15093cb80f1230f3a626253676c88d162cbb2b2
Story: 2005751
Task: 33433
2019-05-30 12:00:06 +01:00

3.1 KiB
Raw Blame History

Auto-scale Compute based on Custom Metrics from Applications

As a user of OpenStack I want to define a logical group of compute resources which are increased or decreased automatically based on metrics which are emitted from an application running in the cloud.

Problem description

An Application developer will define metrics which their application can emit to a Monitoring Service. This could be a report of RPS from a web application. Or information about distribution of objects reported by Swift. The Monitoring Service would generate alarms based on the metrics or report them to a Decision Service for analysis. Commands would be passed to an Orchestration Engine to scale up or down.

This use case was called out in the Denver 2019 PTG - https://etherpad.openstack.org/p/DEN-auto-scaling-SIG

OpenStack projects used

  • ...
  • ...

Inputs and decision-making

Auto-scaling

Existing implementation(s)

  • Monasca and Heat

    Monasca can receive metrics from an application and generate alarms if a metric exceeds a threshold. The alarm notification can then trigger a Heat template and scale the topology appropriately.

  • <TODO: record other options>

Future work

Dependencies