I don't really have an opinion regarding icons, but maybe another idea here would be to provide a detailed explanation in the confirmation dialog of what's about to happen since it could lead to data loss (unless you follow John's solution of the management server having to be stopped, which seems like a lot of work in a multi-management server environment).
On Thu, Mar 20, 2014 at 11:29 AM, Brian Federle <[email protected]>wrote: > >> the Reset Vm option is presented as a button unlike the icons > > I think this was because all the other icons we tried to represent this > with were too confusing to users -- they were clicking on 'reset VM' > thinking it was 'reboot VM' -- then as a last minute fix the decision was to > just to show a text label. > > Any ideas from anyone on what would be a good icon representation? > > -Brian > > On Mar 19, 2014, at 3:02 PM, Alena Prokharchyk < > [email protected]> wrote: > > > 1) Didn't notice "the elephant" - that the Reset Vm option is presented > as > > a button unlike the icons for other options. UI folks - Brian/Jessica- > why > > we decided to represent this option differently in the UI? > > > > 2) Mike, I've looked at the code and the history. We've always allocated > a > > new volume during the vm restore call. Hari, can you please confirm that > > this feature you wrote, was designed to work this way > > > > > > -Alena. > > > > > > On 3/19/14, 2:41 PM, "Mike Tutkowski" <[email protected]> > wrote: > > > >> To clarify: Reboot VM seemed to keep the VM running and just reboot the > >> OS. > >> > >> Reset VM seemed to shut the VM down and then re-start it (with the same > >> root disk for the OS). > >> > >> > >> On Wed, Mar 19, 2014 at 3:40 PM, Mike Tutkowski < > >> [email protected]> wrote: > >> > >>> I could be wrong, but I thought as recently as 4.3 that Reset VM > >>> essentially stopped and then re-started the VM with the same root disk. > >>> > >>> It seemed to differ from Reboot VM only in the sense that the VM was > >>> never > >>> technically stopped (the OS inside the VM was just rebooted). > >>> > >>> > >>> On Wed, Mar 19, 2014 at 3:38 PM, Mike Tutkowski < > >>> [email protected]> wrote: > >>> > >>>> I'm using XenServer 6.1 hosts (two of them) in this case. > >>>> > >>>> > >>>> On Wed, Mar 19, 2014 at 3:37 PM, Mike Tutkowski < > >>>> [email protected]> wrote: > >>>> > >>>>> Yeah, stopping and restarting works fine...as does, I believe, > >>>>> rebooting > >>>>> the VM. > >>>>> > >>>>> Right below Reboot VM, there is a Reset VM option. > >>>>> > >>>>> If that means "re-install," then we probably should clean up the old > >>>>> root disk. > >>>>> > >>>>> > >>>>> On Wed, Mar 19, 2014 at 3:30 PM, Alena Prokharchyk < > >>>>> [email protected]> wrote: > >>>>> > >>>>>> don¹t see ³Reset Vm² option in UI; do you mean ³Reboot instance²? > >>>>>> I¹ve > >>>>>> just tried that, as well as calling stop/startVM from the UI. The Vm > >>>>>> boots > >>>>>> up with its original disk. > >>>>>> > >>>>>> I¹m having Xen/Nfs, not sure it matters > >>>>>> > >>>>>> -Alena. > >>>>>> > >>>>>> On 3/19/14, 2:19 PM, "Mike Tutkowski" <[email protected] > > > >>>>>> wrote: > >>>>>> > >>>>>>> I didn't look into what the GUI calls, but I invoked the Reset VM > >>>>>> option > >>>>>>> in > >>>>>>> the GUI. > >>>>>>> > >>>>>>> Thanks > >>>>>>> > >>>>>>> > >>>>>>> On Wed, Mar 19, 2014 at 3:17 PM, Alena Prokharchyk < > >>>>>>> [email protected]> wrote: > >>>>>>> > >>>>>>>> Mike, just to confirm - did you call > >>>>>>>> stopVirtualMachine/startVirtualMachine apis? > >>>>>>>> > >>>>>>>> -alena. > >>>>>>>> > >>>>>>>> On 3/19/14, 1:55 PM, "Mike Tutkowski" > >>>>>> <[email protected]> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> I noticed today while running through some test cases for 4.4 > >>>>>> that > >>>>>>>>> resetting a VM does not work as expected. > >>>>>>>>> > >>>>>>>>> Instead of the typical stop and re-start behavior where the VM is > >>>>>>>> booted > >>>>>>>>> back up using the same root disk, the VM gets a new root disk > >>>>>> when > >>>>>> it > >>>>>>>> is > >>>>>>>>> booted back up. > >>>>>>>>> > >>>>>>>>> Can anyone confirm this finding for me with his or her setup? > >>>>>>>>> > >>>>>>>>> Thanks! > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> *Mike Tutkowski* > >>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.* > >>>>>>>>> e: [email protected] > >>>>>>>>> o: 303.746.7302 > >>>>>>>>> Advancing the way the world uses the > >>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play> > >>>>>>>>> *(tm)* > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> *Mike Tutkowski* > >>>>>>> *Senior CloudStack Developer, SolidFire Inc.* > >>>>>>> e: [email protected] > >>>>>>> o: 303.746.7302 > >>>>>>> Advancing the way the world uses the > >>>>>>> cloud<http://solidfire.com/solution/overview/?video=play> > >>>>>>> *(tm)* > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> *Mike Tutkowski* > >>>>> *Senior CloudStack Developer, SolidFire Inc.* > >>>>> e: [email protected] > >>>>> o: 303.746.7302 > >>>>> Advancing the way the world uses the > >>>>> cloud<http://solidfire.com/solution/overview/?video=play> > >>>>> *(tm)* > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> *Mike Tutkowski* > >>>> *Senior CloudStack Developer, SolidFire Inc.* > >>>> e: [email protected] > >>>> o: 303.746.7302 > >>>> Advancing the way the world uses the > >>>> cloud<http://solidfire.com/solution/overview/?video=play> > >>>> *(tm)* > >>>> > >>> > >>> > >>> > >>> -- > >>> *Mike Tutkowski* > >>> *Senior CloudStack Developer, SolidFire Inc.* > >>> e: [email protected] > >>> o: 303.746.7302 > >>> Advancing the way the world uses the > >>> cloud<http://solidfire.com/solution/overview/?video=play> > >>> *(tm)* > >>> > >> > >> > >> > >> -- > >> *Mike Tutkowski* > >> *Senior CloudStack Developer, SolidFire Inc.* > >> e: [email protected] > >> o: 303.746.7302 > >> Advancing the way the world uses the > >> cloud<http://solidfire.com/solution/overview/?video=play> > >> *(tm)* > > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: [email protected] o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
