New autoscaling policy: scheduled action in response to predictable work load changes
Currently the scale up/down action is activated by metrics from OS::Ceilometer:
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Haiyang DING
- Direction:
- Needs approval
- Assignee:
- Haiyang DING
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Thomas Herve
Related branches
Related bugs
Sprints
Whiteboard
Here are some of my thoughts on this resource:
----
HOT syntax
heat_template_
…
resource:
…
scheduled_
type: OS::Heat:
properties:
auto_
desired_capacity: Integer
end_time: Time_in_UTC_format
max_size: Integer
min_size: Integer
start_time: Time_in_UTC_format
recurrence: String_
----
Properties:
auto_scaling_
AutoScaling group ID to which the scheduled policy is assigned.
Type: String
Required property
desired_capacity:
The number of VMs that should be running after the scheduled action is triggered.
Type: Integer
Optional property
end_time:
The time in the form of UTC for the actions defined in this policy to end.
Type: String. Should be in UTC format
Optional property
max_size:
The maximum number of VMs belonging to the AutoScaling group when the scheduled policy is applied.
Type: Integer
Optional property
min_size:
The minimum number of VMs belonging to the AutoScaling group when the scheduled policy is applied.
Type: Integer
Optional property
start_time:
The time in the form of UTC for the actions defined in this policy to start.
Type: String. Should be in UTC format
Optional property
recurrence:
The time in UTC that recurring actions described in this policy will start in future.
Type: String. Should be in Cron format. (http://
Optional property
PS: The OpenStack Mistral project provides task scheduling services, so should we integrate with Mistral? Maybe we need a discussion.