10:05 a.m.
Hi all,
Edit running vm feature is targeted to 3.5
The feature would allow editing a vm while it is running.
Please review the feature page and share your thoughts:
http://www.ovirt.org/Features/Edit_Running_VM
Thanks!
Omer.
10:24 a.m.
1) In the event some items can be applied immediately, while others require a restart,
would it be possible to highlight not only the immediate items, but also state which items
won't take affect immediately?
2) On the restart action, is it a simple VM reboot, or does it need to be a cold boot for
the changes? (ie: Power Off VM, Power On VM)
----- Original Message -----
From: "Omer Frenkel" <ofrenkel(a)redhat.com>
To: devel(a)ovirt.org
Sent: Tuesday, April 8, 2014 10:05:05 AM
Subject: [Devel] Edit running vm feature
Hi all,
Edit running vm feature is targeted to 3.5
The feature would allow editing a vm while it is running.
Please review the feature page and share your thoughts:
http://www.ovirt.org/Features/Edit_Running_VM
Thanks!
Omer.
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
2:15 a.m.
----- Original Message -----
From: "Scott Herold" <sherold(a)redhat.com>
To: "Omer Frenkel" <ofrenkel(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Tuesday, April 8, 2014 6:24:43 PM
Subject: Re: [Devel] Edit running vm feature
1) In the event some items can be applied immediately, while others require a
restart, would it be possible to highlight not only the immediate items, but
also state which items won't take affect immediately?
the problem is that most fields won't take affect immediately,
so it can be a long list, so i preferred not to specify all in this dialog.
2) On the restart action, is it a simple VM reboot, or does it need
to be a
cold boot for the changes? (ie: Power Off VM, Power On VM)
it has to be cold boot, as engine need to send new configuration to vdsm.
----- Original Message -----
> From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> To: devel(a)ovirt.org
> Sent: Tuesday, April 8, 2014 10:05:05 AM
> Subject: [Devel] Edit running vm feature
>
> Hi all,
>
> Edit running vm feature is targeted to 3.5
> The feature would allow editing a vm while it is running.
>
> Please review the feature page and share your thoughts:
>
> http://www.ovirt.org/Features/Edit_Running_VM
>
> Thanks!
> Omer.
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
5:54 a.m.
[top posting]
1) Is there a table of all the fields in the dialog, and the capabilities?
2) there are cases in which the user would like to decide (or maybe he doesn't have
permissions to do it): i.e. hot-plug: immediate or next run; (future) pin 2 host, now (now
= invoke migration), or next run.
----- Original Message -----
From: "Omer Frenkel" <ofrenkel(a)redhat.com>
To: "Scott Herold" <sherold(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 10:15:11 AM
Subject: Re: [Devel] Edit running vm feature
----- Original Message -----
> From: "Scott Herold" <sherold(a)redhat.com>
> To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> Cc: devel(a)ovirt.org
> Sent: Tuesday, April 8, 2014 6:24:43 PM
> Subject: Re: [Devel] Edit running vm feature
>
> 1) In the event some items can be applied immediately, while others require
> a
> restart, would it be possible to highlight not only the immediate items,
> but
> also state which items won't take affect immediately?
>
the problem is that most fields won't take affect immediately,
so it can be a long list, so i preferred not to specify all in this dialog.
> 2) On the restart action, is it a simple VM reboot, or does it need to be a
> cold boot for the changes? (ie: Power Off VM, Power On VM)
>
it has to be cold boot, as engine need to send new configuration to vdsm.
> ----- Original Message -----
> > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > To: devel(a)ovirt.org
> > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > Subject: [Devel] Edit running vm feature
> >
> > Hi all,
> >
> > Edit running vm feature is targeted to 3.5
> > The feature would allow editing a vm while it is running.
> >
> > Please review the feature page and share your thoughts:
> >
> > http://www.ovirt.org/Features/Edit_Running_VM
> >
> > Thanks!
> > Omer.
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
6:02 a.m.
----- Original Message -----
From: "Gilad Chaplik" <gchaplik(a)redhat.com>
To: "Omer Frenkel" <ofrenkel(a)redhat.com>
Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 1:54:35 PM
Subject: Re: [Devel] Edit running vm feature
[top posting]
[why?]
1) Is there a table of all the fields in the dialog, and the capabilities?
no
2) there are cases in which the user would like to decide (or maybe
he
doesn't have permissions to do it): i.e. hot-plug: immediate or next run;
(future) pin 2 host, now (now = invoke migration), or next run.
this is exactly why we have the dialog (there is a mockup in the wiki)
the dialog will specify the fields that the user can decide upon and let him choose.
----- Original Message -----
> From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> To: "Scott Herold" <sherold(a)redhat.com>
> Cc: devel(a)ovirt.org
> Sent: Wednesday, April 9, 2014 10:15:11 AM
> Subject: Re: [Devel] Edit running vm feature
>
>
>
> ----- Original Message -----
> > From: "Scott Herold" <sherold(a)redhat.com>
> > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > Cc: devel(a)ovirt.org
> > Sent: Tuesday, April 8, 2014 6:24:43 PM
> > Subject: Re: [Devel] Edit running vm feature
> >
> > 1) In the event some items can be applied immediately, while others
> > require
> > a
> > restart, would it be possible to highlight not only the immediate items,
> > but
> > also state which items won't take affect immediately?
> >
>
> the problem is that most fields won't take affect immediately,
> so it can be a long list, so i preferred not to specify all in this dialog.
>
> > 2) On the restart action, is it a simple VM reboot, or does it need to be
> > a
> > cold boot for the changes? (ie: Power Off VM, Power On VM)
> >
>
> it has to be cold boot, as engine need to send new configuration to vdsm.
>
> > ----- Original Message -----
> > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > To: devel(a)ovirt.org
> > > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > > Subject: [Devel] Edit running vm feature
> > >
> > > Hi all,
> > >
> > > Edit running vm feature is targeted to 3.5
> > > The feature would allow editing a vm while it is running.
> > >
> > > Please review the feature page and share your thoughts:
> > >
> > > http://www.ovirt.org/Features/Edit_Running_VM
> > >
> > > Thanks!
> > > Omer.
> > > _______________________________________________
> > > Devel mailing list
> > > Devel(a)ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> >
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
6:04 a.m.
----- Original Message -----
From: "Omer Frenkel" <ofrenkel(a)redhat.com>
To: "Gilad Chaplik" <gchaplik(a)redhat.com>
Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 2:02:49 PM
Subject: Re: [Devel] Edit running vm feature
----- Original Message -----
> From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> Sent: Wednesday, April 9, 2014 1:54:35 PM
> Subject: Re: [Devel] Edit running vm feature
>
> [top posting]
[why?]
>
> 1) Is there a table of all the fields in the dialog, and the capabilities?
no
Can we have one?
> 2) there are cases in which the user would like to decide (or maybe he
> doesn't have permissions to do it): i.e. hot-plug: immediate or next run;
> (future) pin 2 host, now (now = invoke migration), or next run.
>
this is exactly why we have the dialog (there is a mockup in the wiki)
the dialog will specify the fields that the user can decide upon and let him
choose.
Realized that post sending the email, sorry for missing that... :-/
>
> ----- Original Message -----
> > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > To: "Scott Herold" <sherold(a)redhat.com>
> > Cc: devel(a)ovirt.org
> > Sent: Wednesday, April 9, 2014 10:15:11 AM
> > Subject: Re: [Devel] Edit running vm feature
> >
> >
> >
> > ----- Original Message -----
> > > From: "Scott Herold" <sherold(a)redhat.com>
> > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > Cc: devel(a)ovirt.org
> > > Sent: Tuesday, April 8, 2014 6:24:43 PM
> > > Subject: Re: [Devel] Edit running vm feature
> > >
> > > 1) In the event some items can be applied immediately, while others
> > > require
> > > a
> > > restart, would it be possible to highlight not only the immediate
> > > items,
> > > but
> > > also state which items won't take affect immediately?
> > >
> >
> > the problem is that most fields won't take affect immediately,
> > so it can be a long list, so i preferred not to specify all in this
> > dialog.
> >
> > > 2) On the restart action, is it a simple VM reboot, or does it need to
> > > be
> > > a
> > > cold boot for the changes? (ie: Power Off VM, Power On VM)
> > >
> >
> > it has to be cold boot, as engine need to send new configuration to vdsm.
> >
> > > ----- Original Message -----
> > > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > To: devel(a)ovirt.org
> > > > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > > > Subject: [Devel] Edit running vm feature
> > > >
> > > > Hi all,
> > > >
> > > > Edit running vm feature is targeted to 3.5
> > > > The feature would allow editing a vm while it is running.
> > > >
> > > > Please review the feature page and share your thoughts:
> > > >
> > > > http://www.ovirt.org/Features/Edit_Running_VM
> > > >
> > > > Thanks!
> > > > Omer.
> > > > _______________________________________________
> > > > Devel mailing list
> > > > Devel(a)ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > >
> > >
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
>
7:05 a.m.
[top posting]
To make things easier for the user we could enable the immediate fields while the VM is
up, all other field could be disabled until the VM is down, since they will only apply in
the next run (the user will need update them while the VM is down).
This will be super easy for the user to understand, no need for warnings or other
indications.
----- Original Message -----
From: "Gilad Chaplik" <gchaplik(a)redhat.com>
To: "Omer Frenkel" <ofrenkel(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 2:04:10 PM
Subject: Re: [Devel] Edit running vm feature
----- Original Message -----
> From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> To: "Gilad Chaplik" <gchaplik(a)redhat.com>
> Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> Sent: Wednesday, April 9, 2014 2:02:49 PM
> Subject: Re: [Devel] Edit running vm feature
>
>
>
> ----- Original Message -----
> > From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> > Sent: Wednesday, April 9, 2014 1:54:35 PM
> > Subject: Re: [Devel] Edit running vm feature
> >
> > [top posting]
>
> [why?]
>
> >
> > 1) Is there a table of all the fields in the dialog, and the
> > capabilities?
>
> no
Can we have one?
>
> > 2) there are cases in which the user would like to decide (or maybe he
> > doesn't have permissions to do it): i.e. hot-plug: immediate or next run;
> > (future) pin 2 host, now (now = invoke migration), or next run.
> >
>
> this is exactly why we have the dialog (there is a mockup in the wiki)
> the dialog will specify the fields that the user can decide upon and let
> him
> choose.
Realized that post sending the email, sorry for missing that... :-/
>
> >
> > ----- Original Message -----
> > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > To: "Scott Herold" <sherold(a)redhat.com>
> > > Cc: devel(a)ovirt.org
> > > Sent: Wednesday, April 9, 2014 10:15:11 AM
> > > Subject: Re: [Devel] Edit running vm feature
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Scott Herold" <sherold(a)redhat.com>
> > > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > Cc: devel(a)ovirt.org
> > > > Sent: Tuesday, April 8, 2014 6:24:43 PM
> > > > Subject: Re: [Devel] Edit running vm feature
> > > >
> > > > 1) In the event some items can be applied immediately, while others
> > > > require
> > > > a
> > > > restart, would it be possible to highlight not only the immediate
> > > > items,
> > > > but
> > > > also state which items won't take affect immediately?
> > > >
> > >
> > > the problem is that most fields won't take affect immediately,
> > > so it can be a long list, so i preferred not to specify all in this
> > > dialog.
> > >
> > > > 2) On the restart action, is it a simple VM reboot, or does it need
> > > > to
> > > > be
> > > > a
> > > > cold boot for the changes? (ie: Power Off VM, Power On VM)
> > > >
> > >
> > > it has to be cold boot, as engine need to send new configuration to
> > > vdsm.
> > >
> > > > ----- Original Message -----
> > > > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > > To: devel(a)ovirt.org
> > > > > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > > > > Subject: [Devel] Edit running vm feature
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Edit running vm feature is targeted to 3.5
> > > > > The feature would allow editing a vm while it is running.
> > > > >
> > > > > Please review the feature page and share your thoughts:
> > > > >
> > > > > http://www.ovirt.org/Features/Edit_Running_VM
> > > > >
> > > > > Thanks!
> > > > > Omer.
> > > > > _______________________________________________
> > > > > Devel mailing list
> > > > > Devel(a)ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > >
> > > >
> > > _______________________________________________
> > > Devel mailing list
> > > Devel(a)ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> >
>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
7:10 a.m.
----- Original Message -----
From: "Kobi Ianko" <kobi(a)redhat.com>
To: "Gilad Chaplik" <gchaplik(a)redhat.com>
Cc: "Omer Frenkel" <ofrenkel(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 3:05:17 PM
Subject: Re: [Devel] Edit running vm feature
[top posting]
To make things easier for the user we could enable the immediate fields while
the VM is up, all other field could be disabled until the VM is down, since
they will only apply in the next run (the user will need update them while
the VM is down).
This will be super easy for the user to understand, no need for warnings or
other indications.
iiuc this is the feature: to enable to edit fields while the VM is up.
for my other 2 previous comments:
- the table can be shared by several maintainers
- it would be _very_ nice to cross possible actions with MLA (really useful in
userportal).
----- Original Message -----
> From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> Cc: devel(a)ovirt.org
> Sent: Wednesday, April 9, 2014 2:04:10 PM
> Subject: Re: [Devel] Edit running vm feature
>
> ----- Original Message -----
> > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > To: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> > Sent: Wednesday, April 9, 2014 2:02:49 PM
> > Subject: Re: [Devel] Edit running vm feature
> >
> >
> >
> > ----- Original Message -----
> > > From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> > > Sent: Wednesday, April 9, 2014 1:54:35 PM
> > > Subject: Re: [Devel] Edit running vm feature
> > >
> > > [top posting]
> >
> > [why?]
> >
> > >
> > > 1) Is there a table of all the fields in the dialog, and the
> > > capabilities?
> >
> > no
>
> Can we have one?
>
> >
> > > 2) there are cases in which the user would like to decide (or maybe he
> > > doesn't have permissions to do it): i.e. hot-plug: immediate or next
> > > run;
> > > (future) pin 2 host, now (now = invoke migration), or next run.
> > >
> >
> > this is exactly why we have the dialog (there is a mockup in the wiki)
> > the dialog will specify the fields that the user can decide upon and let
> > him
> > choose.
>
> Realized that post sending the email, sorry for missing that... :-/
>
> >
> > >
> > > ----- Original Message -----
> > > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > To: "Scott Herold" <sherold(a)redhat.com>
> > > > Cc: devel(a)ovirt.org
> > > > Sent: Wednesday, April 9, 2014 10:15:11 AM
> > > > Subject: Re: [Devel] Edit running vm feature
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Scott Herold" <sherold(a)redhat.com>
> > > > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > > Cc: devel(a)ovirt.org
> > > > > Sent: Tuesday, April 8, 2014 6:24:43 PM
> > > > > Subject: Re: [Devel] Edit running vm feature
> > > > >
> > > > > 1) In the event some items can be applied immediately, while
others
> > > > > require
> > > > > a
> > > > > restart, would it be possible to highlight not only the
immediate
> > > > > items,
> > > > > but
> > > > > also state which items won't take affect immediately?
> > > > >
> > > >
> > > > the problem is that most fields won't take affect immediately,
> > > > so it can be a long list, so i preferred not to specify all in this
> > > > dialog.
> > > >
> > > > > 2) On the restart action, is it a simple VM reboot, or does it
need
> > > > > to
> > > > > be
> > > > > a
> > > > > cold boot for the changes? (ie: Power Off VM, Power On VM)
> > > > >
> > > >
> > > > it has to be cold boot, as engine need to send new configuration to
> > > > vdsm.
> > > >
> > > > > ----- Original Message -----
> > > > > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > > > To: devel(a)ovirt.org
> > > > > > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > > > > > Subject: [Devel] Edit running vm feature
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Edit running vm feature is targeted to 3.5
> > > > > > The feature would allow editing a vm while it is running.
> > > > > >
> > > > > > Please review the feature page and share your thoughts:
> > > > > >
> > > > > > http://www.ovirt.org/Features/Edit_Running_VM
> > > > > >
> > > > > > Thanks!
> > > > > > Omer.
> > > > > > _______________________________________________
> > > > > > Devel mailing list
> > > > > > Devel(a)ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > > >
> > > > >
> > > > _______________________________________________
> > > > Devel mailing list
> > > > Devel(a)ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > >
> > >
> >
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
7:36 a.m.
----- Original Message -----
From: "Gilad Chaplik" <gchaplik(a)redhat.com>
To: "Kobi Ianko" <kobi(a)redhat.com>
Cc: "Omer Frenkel" <ofrenkel(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 3:10:52 PM
Subject: Re: [Devel] Edit running vm feature
----- Original Message -----
> From: "Kobi Ianko" <kobi(a)redhat.com>
> To: "Gilad Chaplik" <gchaplik(a)redhat.com>
> Cc: "Omer Frenkel" <ofrenkel(a)redhat.com>, devel(a)ovirt.org
> Sent: Wednesday, April 9, 2014 3:05:17 PM
> Subject: Re: [Devel] Edit running vm feature
>
> [top posting]
> To make things easier for the user we could enable the immediate fields
> while
> the VM is up, all other field could be disabled until the VM is down, since
> they will only apply in the next run (the user will need update them while
> the VM is down).
> This will be super easy for the user to understand, no need for warnings or
> other indications.
>
iiuc this is the feature: to enable to edit fields while the VM is up.
exactly
for my other 2 previous comments:
- the table can be shared by several maintainers
- it would be _very_ nice to cross possible actions with MLA (really useful
in userportal).
i dont see the motivation to create a static table that will be outdated the second its
done.
i dont have a way to auto generate it, and i wouldnt want to try and update it all the
time.
>
>
> ----- Original Message -----
> > From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > Cc: devel(a)ovirt.org
> > Sent: Wednesday, April 9, 2014 2:04:10 PM
> > Subject: Re: [Devel] Edit running vm feature
> >
> > ----- Original Message -----
> > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > To: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > > Cc: "Scott Herold" <sherold(a)redhat.com>, devel(a)ovirt.org
> > > Sent: Wednesday, April 9, 2014 2:02:49 PM
> > > Subject: Re: [Devel] Edit running vm feature
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > Cc: "Scott Herold" <sherold(a)redhat.com>,
devel(a)ovirt.org
> > > > Sent: Wednesday, April 9, 2014 1:54:35 PM
> > > > Subject: Re: [Devel] Edit running vm feature
> > > >
> > > > [top posting]
> > >
> > > [why?]
> > >
> > > >
> > > > 1) Is there a table of all the fields in the dialog, and the
> > > > capabilities?
> > >
> > > no
> >
> > Can we have one?
> >
> > >
> > > > 2) there are cases in which the user would like to decide (or maybe
> > > > he
> > > > doesn't have permissions to do it): i.e. hot-plug: immediate or
next
> > > > run;
> > > > (future) pin 2 host, now (now = invoke migration), or next run.
> > > >
> > >
> > > this is exactly why we have the dialog (there is a mockup in the wiki)
> > > the dialog will specify the fields that the user can decide upon and
> > > let
> > > him
> > > choose.
> >
> > Realized that post sending the email, sorry for missing that... :-/
> >
> > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > > To: "Scott Herold" <sherold(a)redhat.com>
> > > > > Cc: devel(a)ovirt.org
> > > > > Sent: Wednesday, April 9, 2014 10:15:11 AM
> > > > > Subject: Re: [Devel] Edit running vm feature
> > > > >
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > > From: "Scott Herold" <sherold(a)redhat.com>
> > > > > > To: "Omer Frenkel" <ofrenkel(a)redhat.com>
> > > > > > Cc: devel(a)ovirt.org
> > > > > > Sent: Tuesday, April 8, 2014 6:24:43 PM
> > > > > > Subject: Re: [Devel] Edit running vm feature
> > > > > >
> > > > > > 1) In the event some items can be applied immediately,
while
> > > > > > others
> > > > > > require
> > > > > > a
> > > > > > restart, would it be possible to highlight not only the
immediate
> > > > > > items,
> > > > > > but
> > > > > > also state which items won't take affect immediately?
> > > > > >
> > > > >
> > > > > the problem is that most fields won't take affect
immediately,
> > > > > so it can be a long list, so i preferred not to specify all in
this
> > > > > dialog.
> > > > >
> > > > > > 2) On the restart action, is it a simple VM reboot, or does
it
> > > > > > need
> > > > > > to
> > > > > > be
> > > > > > a
> > > > > > cold boot for the changes? (ie: Power Off VM, Power On VM)
> > > > > >
> > > > >
> > > > > it has to be cold boot, as engine need to send new configuration
to
> > > > > vdsm.
> > > > >
> > > > > > ----- Original Message -----
> > > > > > > From: "Omer Frenkel"
<ofrenkel(a)redhat.com>
> > > > > > > To: devel(a)ovirt.org
> > > > > > > Sent: Tuesday, April 8, 2014 10:05:05 AM
> > > > > > > Subject: [Devel] Edit running vm feature
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Edit running vm feature is targeted to 3.5
> > > > > > > The feature would allow editing a vm while it is
running.
> > > > > > >
> > > > > > > Please review the feature page and share your
thoughts:
> > > > > > >
> > > > > > > http://www.ovirt.org/Features/Edit_Running_VM
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Omer.
> > > > > > > _______________________________________________
> > > > > > > Devel mailing list
> > > > > > > Devel(a)ovirt.org
> > > > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > Devel mailing list
> > > > > Devel(a)ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > > >
> > > >
> > >
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
>
3664
days inactive
3665
days old
8 comments
4 participants
participants (4)
-
Gilad Chaplik -
Kobi Ianko -
Omer Frenkel -
Scott Herold