3:54 p.m.
Hi,
It is not really an optimization based only on console connection. In my opinion this
should be a decision factor when determining which VM to migrate from an overloaded host.
If it is a desktop and no console connection, then it is better candidate than a desktop
with console connection or a server with or without console connection. Basically this
logic would just want to minimize the pain caused by the short lag when a VM is live
migrated.
Can I assume that a Desktop is only used when a console is connected?
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Laszlo Hornyak" <lhornyak(a)redhat.com>
Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com>, "engine-devel"
<engine-devel(a)ovirt.org>
Sent: Thursday, April 11, 2013 1:10:04 PM
Subject: Re: [Engine-devel] watchdog
On 04/11/2013 01:57 PM, Laszlo Hornyak wrote:
> No what I meant is that
> if the VM is a server {
> not having a console connection to it does not mean that it is not used.
> }
>
> Therefore desktops on the same host with no console connection, they may be
> better candidates for migration. You can connect to servers.
I'd actually like to lose the distinction between server and desktop
other than a set of optimizations.
i.e., if there is an optimization you want to make based on console
being connected, model that and ask for that specifically (maybe I use
desktop differently than you think)
>
> ----- Original Message -----
>> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
>> To: "Tomas Jelinek" <tjelinek(a)redhat.com>
>> Cc: "Laszlo Hornyak" <lhornyak(a)redhat.com>,
"engine-devel"
>> <engine-devel(a)ovirt.org>
>> Sent: Thursday, April 11, 2013 12:26:35 PM
>> Subject: Re: [Engine-devel] watchdog
>>
>>
>>
>> ----- Original Message -----
>>> From: "Tomas Jelinek" <tjelinek(a)redhat.com>
>>> To: "Laszlo Hornyak" <lhornyak(a)redhat.com>
>>> Cc: "engine-devel" <engine-devel(a)ovirt.org>
>>> Sent: Thursday, April 11, 2013 11:33:19 AM
>>> Subject: Re: [Engine-devel] watchdog
>>>
>>> Good that you have come up with this! So we will make sure to keep this
>>> info.
>>> Thnx for coming up with it!
>>>
>>> ----- Original Message -----
>>>> From: "Laszlo Hornyak" <lhornyak(a)redhat.com>
>>>> To: "Tomas Jelinek" <tjelinek(a)redhat.com>
>>>> Cc: "engine-devel" <engine-devel(a)ovirt.org>
>>>> Sent: Thursday, April 11, 2013 10:25:28 AM
>>>> Subject: Re: [Engine-devel] watchdog
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: "Tomas Jelinek" <tjelinek(a)redhat.com>
>>>>> To: "Laszlo Hornyak" <lhornyak(a)redhat.com>
>>>>> Cc: "engine-devel" <engine-devel(a)ovirt.org>
>>>>> Sent: Thursday, April 11, 2013 10:02:16 AM
>>>>> Subject: Re: [Engine-devel] watchdog
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Laszlo Hornyak" <lhornyak(a)redhat.com>
>>>>>> To: "Itamar Heim" <iheim(a)redhat.com>
>>>>>> Cc: "engine-devel" <engine-devel(a)ovirt.org>
>>>>>> Sent: Thursday, April 11, 2013 9:56:32 AM
>>>>>> Subject: Re: [Engine-devel] watchdog
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Isnt someone already working on removing the UI distinction
between
>>>>>> server
>>>>>> and desktop?
>>>>> Indeed :)
>>>>>
>>>>>>
>>>>>> However the desktop/server distinction could be useful for
scheduling
>>>>>> information, I hope that will remain.
>>>>> There will be a combo box: "optimized for server/desktop".
That one
>>>>> will set up the dialog like you would open the new server/desktop
>>>>> today.
>>>>> But you will be able to change them - it will be just some sugar.
But
>>>>> there
>>>>> is no reason
>>>>> why would we enforce the disabling the e.g. soundcard for server.
By
>>>>> default
>>>>> we will, but
>>>>> you can enable it if you want.
>>>>
>>>> Ok, so in engine we will still have the VmType in vmStatic?
>>>>
>>>> I think it would make sense to use it in scheduling / load balancing
>>>> - if a VM is a desktop and no user is connected to the console, then
the
>>>> VM
>>>> is not in use, therefore it is a good candidate for saving power
>>>> (hibernate,
>>>> migrate, shutdown, or any other bad things that can happen to a VM)
>>>> - if a VM is a server, usually no user connected, but it may still be
>>>> used
>>>> through its network. Therefore it may not be a good candidate to
>>>> migrate.
>>
>> is this indeed a valid assumption ("if VM is a server..." ) that a
user
>> will
>> less connect to it?
>>
>>
>>>>
>>>>>
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>> From: "Itamar Heim" <iheim(a)redhat.com>
>>>>>>> To: "Laszlo Hornyak" <lhornyak(a)redhat.com>
>>>>>>> Cc: "engine-devel" <engine-devel(a)ovirt.org>,
"Andrew Cathrow"
>>>>>>> <acathrow(a)redhat.com>
>>>>>>> Sent: Wednesday, April 10, 2013 9:38:15 PM
>>>>>>> Subject: Re: [Engine-devel] watchdog
>>>>>>>
>>>>>>> On 04/10/2013 04:59 PM, Laszlo Hornyak wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> A new version of the watchdög feature is available in
gerrit:
>>>>>>>>
>>>>>>>> http://gerrit.ovirt.org/13057 - db
>>>>>>>> http://gerrit.ovirt.org/13058 - bll
>>>>>>>> http://gerrit.ovirt.org/13059 - frontend
>>>>>>>> http://gerrit.ovirt.org/13060 - rest
>>>>>>>>
>>>>>>>> http://www.ovirt.org/Features/Watchdog_engine_support
>>>>>>>>
>>>>>>>> Since the last update the patchset has gone through
major changes
>>>>>>>> to
>>>>>>>> meet
>>>>>>>> the new architectureal and functional requirements.
>>>>>>>> Also because of the rewrite this is again a preview
version under
>>>>>>>> testing
>>>>>>>> with some missing functionality, therefore I
re-introduced the
>>>>>>>> [wip]
>>>>>>>> flag
>>>>>>>> on it.
>>>>>>>>
>>>>>>>> Thx,
>>>>>>>> Laszlo
>>>>>>>> _______________________________________________
>>>>>>>> Engine-devel mailing list
>>>>>>>> Engine-devel(a)ovirt.org
>>>>>>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>>>>>>
>>>>>>>
>>>>>>> just a thought after looking at the feature page having
different
>>>>>>> HA
>>>>>>> dialog for server/desktop - I'd consider removing the
distinction
>>>>>>> between desktop and server in the GUI wrt HA (i.e., just
both have
>>>>>>> same
>>>>>>> set of options)
>>>>>>>
>>>>>>> (not blocking for this patch)
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Engine-devel mailing list
>>>>>> Engine-devel(a)ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>>>>
>>>>>
>>>>
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>
>>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>