Re: [Engine-devel] watchdog
On 04/11/2013 03:54 PM, Laszlo Hornyak wrote: 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? connected by spice? by vnc to host or to guest? by rdp? by remote debugging to it from a remote machine, by someone developing on it with ssh, etc... i agree the general use case you are describing make sense, but i rather we model scheduling decisions directly if/where possible ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
- Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel ovirt.org Sent: Sunday, April 14, 2013 5:04:55 PM Subject: Re: [Engine-devel] watchdog On 04/11/2013 03:54 PM, Laszlo Hornyak wrote: 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? connected by spice? by vnc to host or to guest? by rdp? by remote debugging to it from a remote machine, by someone developing on it with ssh, etc... i agree the general use case you are describing make sense, but i rather we model scheduling decisions directly if/where possible Some parts of this thread are looking for perfection and on the way creating additional tasks and reviewing cycles that are only remotely related to the watchdog device; Yes, we should try and reduce the existing differentiation between desktop and a server. No, this feature is not about closing that gap. Watchdog device is about handling guest crash. I strongly suggest that merging desktop and server dialogues will be done as a different feature. The watchdog feature will take one step in the 'right' direction- adding the (currently missing) HA tab into the desktop dialog based on current design. Doron ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
On 04/14/2013 05:59 PM, Doron Fediuck wrote: - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel ovirt.org Sent: Sunday, April 14, 2013 5:04:55 PM Subject: Re: [Engine-devel] watchdog On 04/11/2013 03:54 PM, Laszlo Hornyak wrote: 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? connected by spice? by vnc to host or to guest? by rdp? by remote debugging to it from a remote machine, by someone developing on it with ssh, etc... i agree the general use case you are describing make sense, but i rather we model scheduling decisions directly if/where possible Some parts of this thread are looking for perfection and on the way creating additional tasks and reviewing cycles that are only remotely related to the watchdog device; Yes, we should try and reduce the existing differentiation between desktop and a server. No, this feature is not about closing that gap. Watchdog device is about handling guest crash. I strongly suggest that merging desktop and server dialogues will be done as a different feature. The watchdog feature will take one step in the 'right' direction- adding the (currently missing) HA tab into the desktop dialog based on current design. 1. it is a different task. 2. i'm suggesting you can drop the code doing that distinction for the watchdog in this patch. Doron ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
- Original Message - From: Michal Skrivanek mskri...@redhat.com To: Yair Zaslavsky yzasl...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 5:29:53 PM Subject: Re: [Engine-devel] watchdog On 11 Apr 2013, at 12:26, Yair Zaslavsky yzasl...@redhat.com wrote: - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@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 lhorn...@redhat.com To: Tomas Jelinek tjeli...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:25:28 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:02:16 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@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? IMHO if we want some new behavior/policy there should be a new corresponding property, not desktop/server. That can be quite misleading and I would rather see it go away. Other than use it as a set of default values Sure, let's call it something else, but this is a typical behavior expected from the desktop/server property. So what we are going to do is that remove the property and throw away all the related data, while when (if ever) we get the new property (behaveAsDesktop, notUsedWhenNotConnected, whatever we call it) the users of the system will set this property for the VM's that used to be desktops. We could save that work for the users. Also, it may appear to be an edge-case, but for a good scheduling in my opinion this is important. - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
Laszlo Hornyak píše v Pá 12. 04. 2013 v 08:07 -0400: - Original Message - From: Michal Skrivanek mskri...@redhat.com To: Yair Zaslavsky yzasl...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 5:29:53 PM Subject: Re: [Engine-devel] watchdog On 11 Apr 2013, at 12:26, Yair Zaslavsky yzasl...@redhat.com wrote: - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@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 lhorn...@redhat.com To: Tomas Jelinek tjeli...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:25:28 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:02:16 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@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? IMHO if we want some new behavior/policy there should be a new corresponding property, not desktop/server. That can be quite misleading and I would rather see it go away. Other than use it as a set of default values Sure, let's call it something else, but this is a typical behavior expected from the desktop/server property. Well there could be property with different default values for desktop and servers, couldn't it? ;) Think about memory overcommit or default disk allocation for example. David So what we are going to do is that remove the property and throw away all the related data, while when (if ever) we get the new property (behaveAsDesktop, notUsedWhenNotConnected, whatever we call it) the users of the system will set this property for the VM's that used to be desktops. We could save that work for the users. Also, it may appear to be an edge-case, but for a good scheduling in my opinion this is important. - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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
Re: [Engine-devel] watchdog
Hi, Isnt someone already working on removing the UI distinction between server and desktop? However the desktop/server distinction could be useful for scheduling information, I hope that will remain. - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
- Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:02:16 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@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. - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
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 lhorn...@redhat.com To: Tomas Jelinek tjeli...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:25:28 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:02:16 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@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. - Original Message - From: Itamar Heim ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
- Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@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 lhorn...@redhat.com To: Tomas Jelinek tjeli...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:25:28 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Tomas Jelinek tjeli...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 11, 2013 10:02:16 AM Subject: Re: [Engine-devel] watchdog - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@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 ih...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow acath...@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] watchdog
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.
- Original Message -
From: Yair Zaslavsky yzasl...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: Laszlo Hornyak lhorn...@redhat.com, engine-devel
engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 12:26:35 PM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@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 lhorn...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:25:28 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:02:16 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Laszlo Hornyak lhorn...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: engine-devel engine-devel@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 ih...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow
acath...@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@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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing
Re: [Engine-devel] watchdog
- Original Message -
From: Laszlo Hornyak lhorn...@redhat.com
To: Yair Zaslavsky yzasl...@redhat.com
Cc: Tomas Jelinek tjeli...@redhat.com, engine-devel
engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 1:57:04 PM
Subject: Re: [Engine-devel] watchdog
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.
Used is a more general term than someone is connected to - for example, you
may have a machine running some internal calculation which takes a considerable
amount of time, and you may have a user
that performs ssh to that machine (let's say once in an hour) and runs some
utility that reports the status of the calculation.
}
Therefore desktops on the same host with no console connection, they may be
better candidates for migration. You can connect to servers.
- Original Message -
From: Yair Zaslavsky yzasl...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: Laszlo Hornyak lhorn...@redhat.com, engine-devel
engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 12:26:35 PM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@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 lhorn...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:25:28 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:02:16 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Laszlo Hornyak lhorn...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: engine-devel engine-devel@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 ih...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow
acath...@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@ovirt.org
http://lists.ovirt.org/mailman
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 yzasl...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: Laszlo Hornyak lhorn...@redhat.com, engine-devel
engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 12:26:35 PM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@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 lhorn...@redhat.com
To: Tomas Jelinek tjeli...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:25:28 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, April 11, 2013 10:02:16 AM
Subject: Re: [Engine-devel] watchdog
- Original Message -
From: Laszlo Hornyak lhorn...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: engine-devel engine-devel@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 ih...@redhat.com
To: Laszlo Hornyak lhorn...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, Andrew Cathrow
acath...@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@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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] watchdog
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] watchdog patchset
Hi, The watchdog patch was broken down into a patchset: http://gerrit.ovirt.org/13057 http://gerrit.ovirt.org/13058 http://gerrit.ovirt.org/13059 http://gerrit.ovirt.org/13060 You are welcome to review it, it is working, however due to internal changes it is being completely rewritten. Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Doron Fediuck dfedi...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, February 11, 2013 9:56:42 AM Subject: Re: [Engine-devel] Watchdog support Feature Hi Doron, If the watchdog is set to action=reset and you break the kernel, the VM will stay in UP state while waiting for the watchdog to reset the VM, and will still be in UP state while rebooting. So in theory engine will not be notified about a crash. This behavior is different when the action=poweroff because the watchdog will really put the VM in a Down state and it is engine's job to restart it if HA as soon as it receives the notification from VDSM. Thanks. Just note that poweroff requires guest co-operation which we loose when kernel crashes. That's why it's not recommended. - Original Message - From: Doron Fediuck dfedi...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Sunday, February 10, 2013 4:40:29 PM Subject: Re: [Engine-devel] Watchdog support Feature Hi Laszlo, Looks very useful. Any thoughts on what engine will do while if the VM is defined as HA while the watchdog is resetting it? - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Wednesday, February 6, 2013 11:25:03 AM Subject: Re: [Engine-devel] Watchdog support Feature Hi everyone, I hope everyone is satisfied with the spec, please read it through for the last time and I will move it to implementation phase soon. Thx, Laszlo - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 3:19:57 PM Subject: Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
Hi Doron, If the watchdog is set to action=reset and you break the kernel, the VM will stay in UP state while waiting for the watchdog to reset the VM, and will still be in UP state while rebooting. So in theory engine will not be notified about a crash. This behavior is different when the action=poweroff because the watchdog will really put the VM in a Down state and it is engine's job to restart it if HA as soon as it receives the notification from VDSM. - Original Message - From: Doron Fediuck dfedi...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Sunday, February 10, 2013 4:40:29 PM Subject: Re: [Engine-devel] Watchdog support Feature Hi Laszlo, Looks very useful. Any thoughts on what engine will do while if the VM is defined as HA while the watchdog is resetting it? - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Wednesday, February 6, 2013 11:25:03 AM Subject: Re: [Engine-devel] Watchdog support Feature Hi everyone, I hope everyone is satisfied with the spec, please read it through for the last time and I will move it to implementation phase soon. Thx, Laszlo - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 3:19:57 PM Subject: Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
Hi everyone, I hope everyone is satisfied with the spec, please read it through for the last time and I will move it to implementation phase soon. Thx, Laszlo - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 3:19:57 PM Subject: Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Dave Allan dal...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, January 28, 2013 7:23:25 PM Subject: Re: [Engine-devel] Watchdog support Feature On Fri, Jan 25, 2013 at 08:34:27AM -0800, Itamar Heim wrote: On 24/01/2013 06:19, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel looks like a nice, simple, addition. dave, anyone more intimate with the watchdog worth giving another look? I had a look at the ovirt feature page and asked some libvirt folks as well, and it all looks good to me except that the libvirt documentation says that an event when watchdog fires will be added in the future. That event has been added. The watchdog should work pretty much identically to the physical world: configure the virtual watchdog card in the guest hardware description and install the watchdog daemon in the guest. Dave Thanks Dave. Do you happen do know why the shutdown action is not recommended? ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
On Tue, Jan 29, 2013 at 08:06:44AM -0500, Doron Fediuck wrote: - Original Message - From: Dave Allan dal...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, January 28, 2013 7:23:25 PM Subject: Re: [Engine-devel] Watchdog support Feature On Fri, Jan 25, 2013 at 08:34:27AM -0800, Itamar Heim wrote: On 24/01/2013 06:19, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel looks like a nice, simple, addition. dave, anyone more intimate with the watchdog worth giving another look? I had a look at the ovirt feature page and asked some libvirt folks as well, and it all looks good to me except that the libvirt documentation says that an event when watchdog fires will be added in the future. That event has been added. The watchdog should work pretty much identically to the physical world: configure the virtual watchdog card in the guest hardware description and install the watchdog daemon in the guest. Dave Thanks Dave. Do you happen do know why the shutdown action is not recommended? Yes--it requires guest cooperation which it's unlikely to get if the guest has gotten into a state where the watchdog fires. Dave ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Dave Allan dal...@redhat.com To: Doron Fediuck dfedi...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Tuesday, January 29, 2013 2:42:42 PM Subject: Re: [Engine-devel] Watchdog support Feature On Tue, Jan 29, 2013 at 08:06:44AM -0500, Doron Fediuck wrote: - Original Message - From: Dave Allan dal...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, January 28, 2013 7:23:25 PM Subject: Re: [Engine-devel] Watchdog support Feature On Fri, Jan 25, 2013 at 08:34:27AM -0800, Itamar Heim wrote: On 24/01/2013 06:19, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel looks like a nice, simple, addition. dave, anyone more intimate with the watchdog worth giving another look? I had a look at the ovirt feature page and asked some libvirt folks as well, and it all looks good to me except that the libvirt documentation says that an event when watchdog fires will be added in the future. That event has been added. The watchdog should work pretty much identically to the physical world: configure the virtual watchdog card in the guest hardware description and install the watchdog daemon in the guest. Dave Thanks Dave. Do you happen do know why the shutdown action is not recommended? Yes--it requires guest cooperation which it's unlikely to get if the guest has gotten into a state where the watchdog fires. Dave Yep, the guest kernel should handle an ACPI signal. I don't know in what circumstances would that work, but vdsm does not support it either, so that decision is already made. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: Dave Allan dal...@redhat.com, Doron Fediuck dfedi...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Tuesday, January 29, 2013 4:18:53 PM Subject: Re: [Engine-devel] Watchdog support Feature - Original Message - From: Dave Allan dal...@redhat.com To: Doron Fediuck dfedi...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Tuesday, January 29, 2013 2:42:42 PM Subject: Re: [Engine-devel] Watchdog support Feature On Tue, Jan 29, 2013 at 08:06:44AM -0500, Doron Fediuck wrote: - Original Message - From: Dave Allan dal...@redhat.com To: Itamar Heim ih...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, January 28, 2013 7:23:25 PM Subject: Re: [Engine-devel] Watchdog support Feature On Fri, Jan 25, 2013 at 08:34:27AM -0800, Itamar Heim wrote: On 24/01/2013 06:19, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel looks like a nice, simple, addition. dave, anyone more intimate with the watchdog worth giving another look? I had a look at the ovirt feature page and asked some libvirt folks as well, and it all looks good to me except that the libvirt documentation says that an event when watchdog fires will be added in the future. That event has been added. The watchdog should work pretty much identically to the physical world: configure the virtual watchdog card in the guest hardware description and install the watchdog daemon in the guest. Dave Thanks Dave. Do you happen do know why the shutdown action is not recommended? Yes--it requires guest cooperation which it's unlikely to get if the guest has gotten into a state where the watchdog fires. Dave Yep, the guest kernel should handle an ACPI signal. I don't know in what circumstances would that work, but vdsm does not support it either, so that decision is already made. Makes sense, thanks. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Michael Pasternak mpast...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Sunday, January 27, 2013 9:27:54 AM Subject: Re: [Engine-devel] Watchdog support Feature On 01/24/2013 04:19 PM, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel Definitely nice feature, but i have a question for [1], won't it cause slow responsive guests (on highly loaded hosts) to constantly reboot? i.e it's understood that 'reboot' is a goal of this feature, but endless reboot of pinned-to-host guests for instance won't do any good right?, my point is: should watchdog 'action' have extra logic for guest-policy like placement for instance? [1] watchdog model=i6300esb action=reset/ -- Michael Pasternak RedHat, ENG-Virtualization RD Michael, good question. The device itself will not be added by default, and there are a few other actions which can be used (default action is none). So this will be in use only by someone who expects it to reboot. Additionally the watchdog is configurable to fire according to the internal drivers settings, so softdog may be configured to trigger the watchdog by several indicators and not only cpu load / time. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Itamar Heim ih...@redhat.com To: Yaniv Kaul yk...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 5:54:12 PM Subject: Re: [Engine-devel] Watchdog support Feature On 24/01/2013 07:55, Yaniv Kaul wrote: Are all watchdogs available to all operating systems? ask libosinfo :) Ric' Jones has a known post about it[1]. If you look into it[2], you can see a few Linux distro's are supported (Red Hat, Debian Suse) plus I was able to get it in Fedora's default repo. For Microsoft OS's you may download drivers from Intel's web site. [1] http://rwmj.wordpress.com/2010/03/03/what-is-a-watchdog/#comment-4959 [2] http://watchdog.git.sourceforge.net/git/gitweb.cgi?p=watchdog/watchdog;a=tree ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
On 01/24/2013 04:19 PM, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel Definitely nice feature, but i have a question for [1], won't it cause slow responsive guests (on highly loaded hosts) to constantly reboot? i.e it's understood that 'reboot' is a goal of this feature, but endless reboot of pinned-to-host guests for instance won't do any good right?, my point is: should watchdog 'action' have extra logic for guest-policy like placement for instance? [1] watchdog model=i6300esb action=reset/ -- Michael Pasternak RedHat, ENG-Virtualization RD ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
On 24/01/2013 06:19, Laszlo Hornyak wrote: Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel looks like a nice, simple, addition. dave, anyone more intimate with the watchdog worth giving another look? ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] Watchdog support Feature
Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
- Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 4:19:57 PM Subject: [Engine-devel] Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Although I'm sure you're aware of it - I'm reminding you that you should handle backward compatibility for this feature - So you should have an entry at vdc_options for this + use the FeatureEnabled infra Regarding the action types at db - I would suggest sticking to varchar. Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
Hi Yair, - Original Message - From: Yair Zaslavsky yzasl...@redhat.com To: Laszlo Hornyak lhorn...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 5:01:28 PM Subject: Re: [Engine-devel] Watchdog support Feature - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 4:19:57 PM Subject: [Engine-devel] Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! Although I'm sure you're aware of it - I'm reminding you that you should handle backward compatibility for this feature - So you should have an entry at vdc_options for this + use the FeatureEnabled infra Good point, thx! Regarding the action types at db - I would suggest sticking to varchar. Well, at the moment all enums are stored as int, so varchar too will be something new. Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
On 24/01/13 17:53, Omer Frenkel wrote: - Original Message - From: Laszlo Hornyak lhorn...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, January 24, 2013 4:19:57 PM Subject: [Engine-devel] Watchdog support Feature Hi, Watchdog support in engine will add watchdog to the ovirt UI and REST API. Watchdog cards will be mainly used in HA vm's. http://www.ovirt.org/Features/Watchdog_engine_support Your feedback is welcome! IIUC, this is a device in vdsm, which means it will be stored in vm-devices table once the vm is run, right? if so, no need for the boolean in the vm table, just manage the device for it as other devices.. Are all watchdogs available to all operating systems? Y. Thank you, Laszlo ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Watchdog support Feature
On 24/01/2013 07:55, Yaniv Kaul wrote: Are all watchdogs available to all operating systems? ask libosinfo :) ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
