[Engine-devel] Setting cluster CPU

Michal Skrivanek michal.skrivanek at redhat.com
Mon Dec 9 18:37:00 UTC 2013



> On 09 Dec 2013, at 18:58, Oved Ourfalli <ovedo at redhat.com> wrote:
> 
> 
> 
> ----- Original Message -----
>> From: "Michal Skrivanek" <michal.skrivanek at redhat.com>
>> To: "Sandro Bonazzola" <sbonazzo at redhat.com>, "Roy Golan" <rgolan at redhat.com>
>> Cc: "engine-devel" <engine-devel at ovirt.org>
>> Sent: Monday, December 9, 2013 5:50:49 PM
>> Subject: Re: [Engine-devel] Setting cluster CPU
>> 
>> 
>>> On Dec 9, 2013, at 16:01 , Sandro Bonazzola <sbonazzo at redhat.com> wrote:
>>> 
>>> Hi,
>>> I'm trying to set the cluster CPU type while adding the first host to the
>>> Default cluster.
>>> 
>>> I know how to set the CPU type on a new cluster, since I'll do that in AIO
>>> plugin.
>>> But I'm not sure to understand how to set the CPU on an existing cluster.
>>> 
>>> Should it be enough to specify cpu arg while adding the host to the
>>> cluster?
>>> (before adding an host, cpu is None on the cluster)
>>> Because I'm trying to do that without success (obtaining a sandybridge
>>> cluster while specifying westmere cpu).
>> 
>> The CPU should be set from the first host if None. That is needed for the PPC
>> support. Roy, we talked about it recently, where are we with this patch.
> 
> We already support modifying the CPU level of an existing cluster. If changing it to a higher level then we just change it.
> If changing it to a lower level, and there are running VMs on the cluster, then we warn the user that some VMs might not be migrate-able, as we added a scheduling filter to filter out hosts with improper CPU level.
> 
> Unless I'm missing something, that covers the use-case, isn't it?

Not sure. I thought this is None to something, where it should work automatically without specifying anything. Just add an operational host

> 
>> Thanks,
>> michal
>> 
>>> 
>>> Michael, can you take a look at http://gerrit.ovirt.org/22129 and advise?
>>> 
>>> 
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>> 
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>> 



More information about the Engine-devel mailing list