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
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
Re: [Engine-devel] [vdsm] Snapshots with RAM feature
On Wed, Apr 10, 2013 at 11:43:12AM +0300, Dan Kenigsberg wrote: On Wed, Apr 10, 2013 at 02:12:20AM -0400, Michal Skrivanek wrote: On 9 Apr 2013, at 10:01, Arik Hadas aha...@redhat.com wrote: Hi All, The proposed feature will make it possible to run a VM which was reverted to live snapshot or created from live snapshot with the same memory state as it was at the moment the live snapshot was taken. http://www.ovirt.org/Features/RAM_Snapshots All feedback is welcome! Nice! (I prefer to inline the document when discussing it) VDSM changes Default parameter will be added to vmSnapshot verb that maps string to string. The map will include two keys for now: 'mode' that can be mapped to 'disks_only' or 'disks_memory' to indicate if memory state should be saved. 'memVol' that will be mapped to a string that represent the two volums that will be used to save the memory state and the VM configuration. The default map will include the mapping of 'mode':'disks_only' only. If the 'mode' value in the map decribed above is 'disks_memory' the first volume in 'memVol' will be passed to libvirt in order to dump the memory to it, and the second volume in 'memVol' will be used to save the VM configuration (the same way it is done for hibernate operation). This definition of 'memVol' would not allow saving the state to another storage domain, or a direct lun or whatever. I suggest that you have two independet arguments, say memVol and vmConfVol. Both may have the standard pool-domain-image-volume quartet, or a lun specification, or a local path. On a second thought - why should we even store vmConf on vmConfVol? Why not keep it in Engine's db? Sure, we do this for hibernation. But it creates a lot of inconsistency pains. Engine sends one vmconf to vdsm, but vdsm ignores it and starts the VM with an old vmconf that was stored besides the hibernation volume. On top of this, it wastes some GiB of disk space for each snapshot. I think it is time to have Engine keep a snapshot of its vm config whenever it takes a snapshot - live or offline. Dan. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] upgrade failing with latest master
Please see what systemd has to say:
# systemctl status ovirt-engine.service
And no, I never tried to backup/restore... sorry...
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: Alon Bar-Lev alo...@redhat.com
Cc: engine-devel@ovirt.org
Sent: Friday, April 12, 2013 12:28:01 AM
Subject: Re: [Engine-devel] upgrade failing with latest master
Rebuilt the engine on my FC17 build VM with the macro file above in
/etc/rpm/
Upon attempting upgrade on my FC17 upgrade test VM:
I still get a failure to start the engine
013-04-11 16:06:37::ERROR::engine-upgrade::1328::root:: Traceback (most
recent call last):
File /bin/engine-upgrade, line 1321, in module
main(options)
File /bin/engine-upgrade, line 1293, in main
runFunc([startEngine], MSG_INFO_START_ENGINE % engineService)
File /bin/engine-upgrade, line 617, in runFunc
func()
File /bin/engine-upgrade, line 584, in startEngine
output, rc = utils.execCmd(cmdList=cmd, failOnError=True,
msg=MSG_ERR_FAILED_START_ENGINE_SERVICE)
File /usr/share/ovirt-engine/scripts/common_utils.py, line 499, in
execCmd
raise Exception(msg)
Exception: Error: Can't start ovirt-engine
Curiously is there a documented process somewhere for backing up data from
an FC17 ovirt install and doing a fresh install on a FC18 box then
restoring the FC17 database + ovirt config data?
Guessing it goes something like this: (someone please confirm)
Back up the following directories and files:
/etc/ovirt-engine
/etc/pki/ovirt-engine
/etc/pki/ovirt-engine-backups
/var/lib/ovirt-engine/backups
/var/lib/ovirt-engine/deployments
/root/.rnd
Dump a backup of the engine database
Install ovirt-engine on FC18 system
run engine-setup (answer questions same as prior install from FC17)
upon completion of engine-setup stop the engine service
restore all the above files and directories
Drop the engine databse
Restore the backed up engine database
FC17 -- FC18 upgrade = icky esp. with ovirt involved as part of the upgrade
Thus it seems the easiest way to solve this is to bite the bullet and move
to FC18 providing the backup/restore works.
- DHC
On Wed, Apr 10, 2013 at 4:02 PM, Alon Bar-Lev alo...@redhat.com wrote:
OK... the systemd macros are missing in fedora 17...
Put the following file and rebuild.
I may need to add some workaround if many people still use fedora-17 for
master.
Regards,
Alon
/etc/rpm/macros.systemd-fc18
---
%systemd_post() \
if [ $1 -eq 1 ] ; then \
# Initial installation \
/usr/bin/systemctl preset %{?*} /dev/null 21 || : \
fi \
%{nil}
%systemd_preun() \
if [ $1 -eq 0 ] ; then \
# Package removal, not upgrade \
/usr/bin/systemctl --no-reload disable %{?*} /dev/null 21 || :
\
/usr/bin/systemctl stop %{?*} /dev/null 21 || : \
fi \
%{nil}
%systemd_postun() \
/usr/bin/systemctl daemon-reload /dev/null 21 || : \
%{nil}
%systemd_postun_with_restart() \
/usr/bin/systemctl daemon-reload /dev/null 21 || : \
if [ $1 -ge 1 ] ; then \
# Package upgrade, not uninstall \
/usr/bin/systemctl try-restart %{?*} /dev/null 21 || : \
fi \
%{nil}
---
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: Alon Bar-Lev alo...@redhat.com
Cc: engine-devel@ovirt.org
Sent: Wednesday, April 10, 2013 11:59:15 PM
Subject: Re: [Engine-devel] upgrade failing with latest master
Correct, FC17
- DHC
On Wed, Apr 10, 2013 at 3:32 PM, Alon Bar-Lev alo...@redhat.com wrote:
Is this fedora 17 or 18?
I guess it is fedora 17.
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: engine-devel@ovirt.org
Sent: Wednesday, April 10, 2013 11:23:10 PM
Subject: [Engine-devel] upgrade failing with latest master
logs attached
First attempt:
2013-04-10 13:57:32::ERROR::common_utils::355::root:: YUM: FAIL:
Error in
PREUN scriptlet in rpm package
ovirt-engine-backend-3.3.0-15.fc17.noarch
2013-04-10 13:57:32::DEBUG::common_utils::347::root:: YUM: VERB:
Script
sink:
/var/tmp/rpm-tmp.J0HyUz: line 1: fg: no job control
error: %preun(ovirt-engine-backend-3.3.0-15.fc17.noarch) scriptlet
failed,
exit status 1
2013-04-10 13:57:32::DEBUG::common_utils::347::root:: YUM: VERB:
Done:
ovirt-engine-backend-3.3.0-15.fc17.noarch
Second attempt:
2013-04-10 15:12:11::DEBUG::common_utils::347::root:: YUM: VERB:
Building
transaction
2013-04-10 15:12:12::ERROR::common_utils::355::root:: YUM: FAIL:
[u'ovirt-engine-backend-3.3.0-14.fc17.noarch requires ovirt-engine =
3.3.0-14.fc17']
2013-04-10 15:12:12::DEBUG::common_utils::347::root:: YUM: VERB:
Performing
rollback
2013-04-10 15:12:12::DEBUG::common_utils::1410::root:: Locking rpms
in
