.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.41.2.
.TH EUSCALE-CREATE-AUTO-SCALING-GROUP "1" "August 2013" "euca2ools 3.0.1" "User Commands"
.SH NAME
euscale-create-auto-scaling-group \- Create a new auto-scaling group
.SH SYNOPSIS
euscale\-create\-auto\-scaling\-group \fB\-l\fR LAUNCHCONFIG \fB\-M\fR COUNT \fB\-m\fR COUNT
[\-\-default\-cooldown SECONDS]
[\-\-desired\-capacity COUNT]
[\-\-grace\-period SECONDS]
[\-\-health\-check\-type {EC2,ELB}]
[\-\-load\-balancers ELB1,ELB2,...]
[\-\-placement\-group PLACEMENTGROUP]
[\-\-tag "k=VALUE, id=VALUE, t=VALUE, v=VALUE, p={true,false}"]
[\-\-termination\-policies POLICY1,POLICY2,...]
[\-\-vpc\-zone\-identifier ZONE1,ZONE2,...]
[\-z ZONE1,ZONE2,...]
[\-\-region USER@REGION | \fB\-U\fR URL]
[\-I KEY_ID] [\-S KEY] [\-\-debug]
[\-\-debugger] [\-\-version] [\-h]
ASGROUP
.SH DESCRIPTION
Create a new auto\-scaling group
.SS "positional arguments:"
.TP
ASGROUP
name of the new auto\-scaling group (required)
.SS "optional arguments:"
.TP
\fB\-l\fR LAUNCHCONFIG, \fB\-\-launch\-configuration\fR LAUNCHCONFIG
name of the launch configuration to use with the new
group (required)
.TP
\fB\-M\fR COUNT, \fB\-\-max\-size\fR COUNT
maximum group size (required)
.TP
\fB\-m\fR COUNT, \fB\-\-min\-size\fR COUNT
minimum group size (required)
.TP
\fB\-\-default\-cooldown\fR SECONDS
amount of time, in seconds, after a scaling activity
completes before any further trigger\-related scaling
activities may start
.TP
\fB\-\-desired\-capacity\fR COUNT
number of running instances the group should contain
.TP
\fB\-\-grace\-period\fR SECONDS
number of seconds to wait before starting health
checks on newly\-created instances
.TP
\fB\-\-health\-check\-type\fR {EC2,ELB}
service to obtain health check status from
.TP
\fB\-\-load\-balancers\fR ELB1,ELB2,...
comma\-separated list of load balancers to use
.TP
\fB\-\-placement\-group\fR PLACEMENTGROUP
placement group in which to launch new instances
.TP
\fB\-\-tag\fR "k=VALUE, id=VALUE, t=VALUE, v=VALUE, p={true,false}"
attributes of a tag to affect. Tags follow the
following format: "id=resource\-name, t=resource\-type,
k=tag\-key, v=tag\-val, p=propagate\-at\-launch\-flag",
where k is the tag's name, v is the tag's value, id is
a resource ID, t is a resource type, and p is whether
to propagate tags to instances created by the group. A
value for 'k=' is required for each tag. The rest are
optional. This argument may be used more than once.
Each time affects a different tag.
.TP
\fB\-\-termination\-policies\fR POLICY1,POLICY2,...
ordered list of termination policies. The first has
the highest precedence.
.TP
\fB\-\-vpc\-zone\-identifier\fR ZONE1,ZONE2,...
comma\-separated list of subnet identifiers. If you
specify availability zones as well, ensure the
subnets' availability zones match the ones you
specified
.TP
\fB\-z\fR ZONE1,ZONE2,..., \fB\-\-availability\-zones\fR ZONE1,ZONE2,...
comma\-separated list of availability zones for the new
group (required unless subnets are supplied)
.TP
\fB\-\-region\fR USER@REGION
name of the region and/or user in config files to use
to connect to the service
.TP
\fB\-U\fR URL, \fB\-\-url\fR URL
auto\-scaling service endpoint URL
.HP
\fB\-I\fR KEY_ID, \fB\-\-access\-key\-id\fR KEY_ID
.HP
\fB\-S\fR KEY, \fB\-\-secret\-key\fR KEY
.TP
\fB\-\-debug\fR
show debugging output
.TP
\fB\-\-debugger\fR
launch interactive debugger on error
.TP
\fB\-\-version\fR
show the program's version and exit
.TP
\fB\-h\fR, \fB\-\-help\fR
show this help message and exit