[ovirt-users] 答复: How power-saving schedule policy applied?

Tue Jan 9 07:55:09 UTC 2018

Hi Martin, Karli

Thank a lot for your help.

According to your instruction, I added two parameters into cluster configuration, as below.

1)      enable power cycling mechanisms

2)      reserve one host standing by

My test bed:

3 hosts which are real servers, cloudstack01/cloudstack03/cloudstack04. 

Heavy load on cloudstack01, 21 vms

Light load on cloudstack03, 1 vms

No thing on cloudstack04

When I shut down the last vm on cloudstack03(because I can’t migrate it to cloudstack01, I guess the load is already exceeding the threshold), the cloudstack04 goes to ‘maintenance’ then goes to ‘down’ state. Yepp, POWER SAVING.

I tried further test:

Set ‘HostInReserve’ to 0. Bingo, cloudstack03 goes down as expected.

But when I launch a new VM I get an error popup dialog which inform me that there isn’t enough memory resource to start a new VM. Is it normal way that power saving mechanism works? Can’t power saving policy scheduling module wake up a host to launch VM automatically?

Also, Is there any timeline base power saving policy I can apply? Like from 8’clock AM to 6’clock PM, 10 hosts up, 6’clock PM to next 8’clock AM, just keep 3 hosts alive.  

Best regards

Alex

发件人: Martin Sivak [mailto:msivak at redhat.com] 
发送时间: 2018年1月8日 19:43
收件人: Karli Sjöberg <karli at inparadise.se>
抄送: Alex Shen <alex at bill-jc.com>; users <users at ovirt.org>
主题: Re: [ovirt-users] How power-saving schedule policy applied?

Hi,

and here is a fresh screenshot just for you :)

You need to edit the cluster, select scheduling policy tab and add two parameters to your Power saving policy. One enables the power cycling mechanisms and the second one (HostsInReserve) controls how many empty hosts are allowed to stay up. When the host is not empty anymore a new one will be started.

Best regards

--

Martin Sivak

SLA / oVirt

On Mon, Jan 8, 2018 at 12:29 PM, Karli Sjöberg <karli at inparadise.se <mailto:karli at inparadise.se> > wrote:

Den 8 jan. 2018 12:07 skrev Alex Shen <alex at bill-jc.com <mailto:alex at bill-jc.com> >:

Hi,

I’m wondering how to apply power-saving schedule in ovirt cluster(version is 4.2.0.2-1.el7.centos)? Is there any instruction or manual with UI snapshots guidance? That will be appreciated. 

I’ve configed all host with ipmilan protocol and test ok. I suppose that power saving policy should converge VMs into hosts one by one. Something like that. From the beginning, all hosts are in ‘power off’ state, if a VM launch, power saving scheduling module should power on one host, and assign VM into that host. With many VMs activated, exceeding the threshold, power saving scheduling module should turn on another host…

Jepp, that's basically how it works:)

/K

If anyone had played power saving scheduling policy, please share me your scenarios or some hints. Thanks a lot.

Alex

 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 

无病毒。 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> www.avast.com 

_______________________________________________ 
Users mailing list 
Users at ovirt.org <mailto:Users at ovirt.org>  
http://lists.ovirt.org/mailman/listinfo/users 

_______________________________________________
Users mailing list
Users at ovirt.org <mailto:Users at ovirt.org> 
http://lists.ovirt.org/mailman/listinfo/users

---
Avast 防毒软件已对此电子邮件执行病毒检查。
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180109/734a1f06/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 65536 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180109/734a1f06/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 74207 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180109/734a1f06/attachment-0001.png>