...
Chiradeep, CloudStack PMC, has a vision to improve my hacking with some new changes below:
+ Need to remove Load Balancing feature from AutoScaling. That’s very simple to do.
+ Need to use SNMP for monitoring not only instance-level but also application-level.
+ Also, supporting well KVM hypervisor
The idea is that the monitoring (WHAT to monitor and HOW to monitor) is separate from the autoscaling decision.
...
- communicates with CS MS to perform scale-up/scale-down
Design Architecture
API change
+ AutoScale API: keep the same
- createConditionCmd, listConditionCmd, deleteConditionCmd
- createPolicyCmd, listPolicyCmd, deletePolicyCmd
- createProfileCmd, listProfileCmd, deleteProfileCmd
- createGroupCmd, listGroupCmd, deleteGroupCmd, disableGroupCmd, enableGroupCmd
+ Monitor API:
- addMonitorDeviceCmd
- request parameter:
- physical n/w id (required) - id of the physical n/w to which MonitorDevice is associated with
- mgmt. ip (required) - IP address for connecting to MonitorDevice
- username (required) - Username for connecting to MonitorDevice
- password (required) - Password for the above username
- response:
- deviceId
- deviceName
- physical n/w id
- providerName
- removeMonitorDeviceCmd
- request parameter:
- response
- boolean (success / failure)
- listMonitorDeviceCmd
- request parameter
- deviceId (optional)
- physical n/w id (optional)
- response
- deviceId
- deviceName
- physical n/w id
- providerName
+ HTTP request from CS to Monitor device
- sendConfiguration
- request parameter
- counterName (required) - type of parameter need to monitor
- response
- boolean (success / failure)
- queryPerformanceData
- request parameter
- total_vm
- foreach vm
- duration (required) - time range, in second, to monitor. It need to calculate the average value
- counterName (required)
- vm IP address (required)
- response
- foreach vm
- counterName
- average value in duration
Interface
AutoScaling service
Image Added
Monitoring service
Image Added