[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618495#comment-14618495 ] Daan Hoogland commented on CLOUDSTACK-8266: --- moving this very fine feature to 'future' as it is unplannable at best at the moment Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. -- Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Labels: gsoc2015 Fix For: Future CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14332069#comment-14332069
]
Marcus Sorensen commented on CLOUDSTACK-8266:
-
Unfortunately, I wrote it for a third party as a plugin, and they maintain the
rights to the code. However, looking at just publicly available code, you can
basically reimplement/copy the StatsCollector class, e.g.:
@Component
public class WorkloadManager extends ManagerBase implements
ComponentMethodInterceptable {
And implement the start method required by ComponentMethodInterceptable. They
in turn call an init method, but you can just implement that code in start if
you want. Look at the init method to see how to schedule the running of a class
on interval via the 'ScheduledExecutorService _executor':
_executor.scheduleWithFixedDelay(new WorkloadMonitor(), 15000L,
autoScaleStatsInterval, TimeUnit.MILLISECONDS);
And also how to fetch config parametrs that will be used as tunables for the
algorithm:
workloadActionCpuThreshold =
NumbersUtil.parseInt(configs.get(workload.action.cpu.threshold), 90);
You may want to look up the zones (via DataCenterDao?) and schedule one thread
per zone or something like that. The scheduled class should do something like
look up all enabled clusters, then go through each cluster and look at the
enabled hosts. You can fetch the stats for each host via
StatsCollector.getInstance().getHostStats(hostid).
Of course, you could also just add a few lines to init within StatsCollector
itself to schedule your class, as was done with the AutoScaleMonitor, but I'm
not sure there's any reason why these services all need to be stuffed into
StatsCollector itself. It's relatively easy to set up a standalone service and
still fetch what data you need from StatsCollector.
That's sort of the general way to get a service functioning, but the algorithm
would need to be ironed out a bit more when workign on the functional spec.
Automatic workload Management in the clusters Managed by CloudStack for
efficient host Management.
--
Key: CLOUDSTACK-8266
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266
Project: CloudStack
Issue Type: New Feature
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Management Server
Affects Versions: 4.5.0
Environment: Java, Linux, Hypervisor
Reporter: Rajesh Battala
Labels: gsoc2015
Fix For: 4.5.0
CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to
ensure proper hosts capacity are used max.
Due to some operations by user on vm's like stop/migrate/destroy hosts usage
in the clusters will be in inefficient state.
To solve this issue we can have a new Manager who will regularly checks host
capacity and implement Server Consolidtion by taking the actions:
1. Live migrate the vm's if possible along with storage. Migrate them such
that hosts are fully utilized.
2. After redistributing the vm's Shutdown the hosts which are empty.
3. When load is getting increased,power-on the hosts remotely by WOL(Wake On
Lan) mechanisam.
This idea is discussed and presented in Collab Conference 2014.
Here is the youtube link
https://www.youtube.com/watch?v=hJKdZcSpGNQ
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14328666#comment-14328666 ] Marcus Sorensen commented on CLOUDSTACK-8266: - Hi, FYI I think the metrics you need are not in the DB but available live already in StatsCollector. You can probably create a scheduled service that pulls the current host stats from memory in StatsCollector variables and tracks which ones are loaded for how long and redistributes load. I've looked into implementing this myself and actually have a basic reporting service working right now. It would be useful to implement different strategies, one to distribute load, one to consolidate and save power, etc. You probably want to start with writing up a functional spec (here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.6+Design+Documents) that outlines the ideas in this ticket and starts to solidify an implementation that the community agrees upon. Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. -- Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Labels: gsoc2015 Fix For: 4.5.0 CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14328770#comment-14328770 ] Tilak Raj Singh commented on CLOUDSTACK-8266: - Hi Marcus...Thanks for your suggestion..I have starting looking at the code of StatsCollector at https://github.com/apache/cloudstack/blob/master/server/src/com/cloud/server/StatsCollector.java and trying to understand it. Could you please share the code of the basic reporting service you have implemented so that I have have some further insights with perspective to this issue. Regards Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. -- Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Labels: gsoc2015 Fix For: 4.5.0 CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14328700#comment-14328700 ] Rajesh Battala commented on CLOUDSTACK-8266: Thanks for Nice Suggestions Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. -- Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Labels: gsoc2015 Fix For: 4.5.0 CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8266) Automatic workload Management in the clusters Managed by CloudStack for efficient host Management.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14327336#comment-14327336 ] Tilak Raj Singh commented on CLOUDSTACK-8266: - Hi Rajesh, I am interested in implementing this feature in cloudstack. I went through the video and currently am getting familiarised with the cloudstack database to gather the metrics that can be usd to support this feature Regards Automatic workload Management in the clusters Managed by CloudStack for efficient host Management. -- Key: CLOUDSTACK-8266 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8266 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server Affects Versions: 4.5.0 Environment: Java, Linux, Hypervisor Reporter: Rajesh Battala Labels: gsoc2015 Fix For: 4.5.0 CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state. To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions: 1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized. 2. After redistributing the vm's Shutdown the hosts which are empty. 3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam. This idea is discussed and presented in Collab Conference 2014. Here is the youtube link https://www.youtube.com/watch?v=hJKdZcSpGNQ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
