Autoscale bay node count when bays become overloaded

Registered by Steven Dake on 2015-01-17

When bays reach a configured threshold of cpu or memory utilization, autoscale the bay by increasing nodes dynamically to handle the increased workload. Need to add a max node count parameter to the BayModel I think as well as if scaling is set to none, automatic, or manual. A manual scale would use bay-update.

Blueprint information

Status:
Not started
Approver:
Adrian Otto
Priority:
Undefined
Drafter:
Steven Dake
Direction:
Approved
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Deferred
Milestone target:
None

Related branches

Sprints

Whiteboard

Please add a T-Shirt size estimate for implementation of this feature (S, M, L, XL)

Gerrit topic: https://review.openstack.org/#q,topic:bp/autoscale-bay,n,z

Addressed by: https://review.openstack.org/213929
    Enable ceilometer in devstack

Addressed by: https://review.openstack.org/214411
    Initialize RPC notification service

Addressed by: https://review.openstack.org/214744
    Move 'all_tenants' options to context

Addressed by: https://review.openstack.org/215335
    WIP: Implement bay monitoring and notifications

Addressed by: https://review.openstack.org/228294
    Introduce BayType that declares valid COEs

(hongbin): I am going to wait for the support of heat conditional logic [1]. Without this feature, it is infeasible to continue the implementation.

[1] https://review.openstack.org/#/c/245042/

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.