----- Original Message -----
From: "Michal Skrivanek"
<michal.skrivanek(a)redhat.com>
To: "Itamar Heim" <iheim(a)redhat.com>, users(a)ovirt.org
Cc: "Gal Hammer" <ghammer(a)redhat.com>, "Simon Grinberg"
<sgrinber(a)redhat.com>
Sent: Tuesday, April 23, 2013 9:58:57 AM
Subject: Re: [Users] forced shutdown with client agent
On Apr 22, 2013, at 23:19 , Itamar Heim <iheim(a)redhat.com> wrote:
> On 04/22/2013 01:59 PM, Michal Skrivanek wrote:
>>> >
>>> >----- Original Message -----
>>>> >>From: "Michal
Skrivanek"<michal.skrivanek(a)redhat.com>
>>>> >>To:users@ovirt.org, "Thomas
Scofield"<tscofield(a)gmail.com>,
>>>> >>"Vinzenz Feenstra"<vfeenstr(a)redhat.com>,
"Barak
>>>> >>Azulay"<bazulay(a)redhat.com>, "Gal
Hammer"<ghammer(a)redhat.com>
>>>> >>Sent: Monday, April 22, 2013 11:48:18 AM
>>>> >>Subject: Re: [Users] forced shutdown with client agent
>>>> >>
>>>> >>
>>>> >>On Apr 20, 2013, at 22:42 , Itamar Heim<iheim(a)redhat.com>
>>>> >> wrote:
>>>> >>
>>>>> >>>On 03/29/2013 04:58 AM, Thomas Scofield wrote:
>>>>>> >>>>I have run into a scenario after installing the
client
>>>>>> >>>>agent. If
>>>>>> >>>>a VM
>>>>>> >>>>is shutdown, the client agent calls the shutdown
command
>>>>>> >>>>with a 1
>>>>>> >>>>minute
>>>>>> >>>>timeout.
>>>>>> >>>>
>>>>>> >>>>Dummy-2::INFO::2013-03-28
>>>>>> >>>>14:05:21,892::vdsAgentLogic::138::root::Shutting
down
>>>>>> >>>>(timeout =
>>>>>> >>>>30,
>>>>>> >>>>message = 'System Administrator has
initiated shutdown of
>>>>>> >>>>this
>>>>>> >>>>Virtual
>>>>>> >>>>Machine. Virtual Machine is shutting down.'
>>>>>> >>>>
>>>>>> >>>>Since the shutdown command is called with time
parameter
>>>>>> >>>>the VM
>>>>>> >>>>sets the
>>>>>> >>>>/etc/nologin file. When the VM is forced down
the
>>>>>> >>>>/etc/nologin
>>>>>> >>>>file is
>>>>>> >>>>not cleared and when it comes back up only root
can login
>>>>>> >>>>until
>>>>>> >>>>the
>>>>>> >>>>/etc/nologin file is cleared.
If you don't want it setting user_shutdown_timeout to 0 should solve
this.
>>>>> >>>
>>>>> >>>hmmm, Vinzenz - should guest agent clear that on guest
>>>>> >>>startup, if
>>>>> >>>guest agent set this at shutdown?
>>>>> >>>
>>>>>> >>>>
>>>>>> >>>>Is their some some reason the shutdown time is
set to 30
>>>>>> >>>>seconds
>>>>>> >>>>(rounded up to 1 minute in the code)?
it is rounded up because unix shutdown works with minutes only. So
it's the seconds from user_shutdown_timeout is rounded up to
minutes.
The Windows one should really be 30s.
>>>>>> Are there any know issues
>>>>>> >>>>with
>>>>>> >>>>setting this to 0?
>>>> >>I wouldn't mind changing this to 0 by default if there are
no
>>>> >>objections.
>>>> >>Barak, Gal, what do you think? Do you see any strong reason
>>>> >>for
>>>> >>keeping a grace period?
>>> >
>>> >The idea was to allow a logged in user to orderly close his work
>>> >right?
>>> >For that I'm not sure that even 30 seconds is enough.
>> For that typically sysadmins use 5 or 10 minutes. 30s is
>> worthless, no one would be able to react that fast…so to me this
>> is the same as initiating shutdown right away. It's graceful
>> anyway and all common apps would save the workspace on SIGTERM
>> anyway. Well, does it even do anything on Windows?
>> That's why I'd vote for 0. And keep is configurable in case you
>> want to use it, sure.
>>
>
> do we allow users to cancel the shutdown?
nope.
It can be stopped inside the guest, well, if you manage to do that in
that short time.
From all the said above seems that indeed default shut-down time
should be 0
But we need to be able to set shut-down policy per VM/Cluster/Something
that will override the global config. One time fits all does not sound reasonable.
I would say that for Desktop use case you'll probably want to allow the User some time
to finish up things, while for Server you won't care. Etc....
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users