Auto-Scale Groups

There are two settings for scaling on Cycle:

  1. Through the container config.
  2. Through infrastructure auto-scale groups.

To dive deeper on either topic please see the links above, but from a high level these infrastructure auto-scale groups provide the mechanism that will add (and remove) additional compute resources to the cluster.

Auto-Scale Dashboard

To manage auto-scale groups, head over to the auto-scale dashboard.

To get there:

  1. Select the Infrastructure tab from the main, left-hand navigation.
  2. Select the Auto-Scaling tab from the infrastructure sub-navigation.
auto-scale navigation

Create Auto-Scaling Group

Click the Add button to open the Create Auto-Scaling Group modal. From here a user can add the settings most appropriate for their group.

Auto-Scaling Create Form
FieldDescription
NameThe name of the auto-scaling group.
IdentifierA unique resource identifier for the auto-scaling group, important for CLI operations.
ClusterThe infrastructure cluster with which the auto-scaling group is associated.
Scale UpThe settings and conditions for adding more servers to the auto-scaling group.
Scale DownThe settings and conditions for reducing the number of servers and managing server TTLs.

Deployable Infrastructure

Users can add server models to the deployable infrastructure page and give each model a priority. This list of deployable infrastructure is what Cycle uses when a scaling event comes in that requires infrastructure to be added.

The Add Model button will open a wizard, from which users can add their choices. Also, entries on this page can be edited after created.

Settings

Name and Identifier can be changed in the basic settings, but cluster cannot. For users who have not configured the Scale Up or Scale Down settings during create, those can be toggled and configured here as well.

The Scale Up settings for an auto-scaling group set the upper limit of how many servers can be created to support scaling demands for containers in the group.

The Scale Down settings expose a few more options.

FieldDescription
Min TTLThe minimum amount of time a server must remain online before it can be removed.
Inactivity PeriodThe period of time a server can remain idle (without activity) before it is removed.
Scale Down MethodThe strategy used for scaling down servers, such as Last-In-First-Out (LIFO), First-In-First-Out (FIFO), or Default.