| Key: |
QB-1899
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Lukasz Guminski
|
| Votes: |
1
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 07/Jan/14 04:37 PM
Updated: 21/May/14 06:01 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
5.1.6
|
| Fix Version/s: |
5.1.25
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
To make a cloud profile usable for production, we need to be able to constrain the size of the cloud. Sometimes we have several hundreds requests in the queue, and letting QB decide on new resources, could become very costly.
You could apply Amazon scaling concepts, where an autoscaling group accepts the following parameters:
- minimal capacity
- maximal capacity
- desired capacity
- cooldown period
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AS_Concepts.html
|
|
Description
|
To make a cloud profile usable for production, we need to be able to constrain the size of the cloud. Sometimes we have several hundreds requests in the queue, and letting QB decide on new resources, could become very costly.
You could apply Amazon scaling concepts, where an autoscaling group accepts the following parameters:
- minimal capacity
- maximal capacity
- desired capacity
- cooldown period
http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AS_Concepts.html |
Show » |
|
Constraining the size of EC2 cloud