Request for Feedback :: Time Mode setting in timemanager

[Brad Bishop]

> On Feb 18, 2020, at 3:25 PM, Patrick Williams <patrick at stwcx.xyz> wrote:
> 
> On Tue, Feb 18, 2020 at 09:40:53AM -0500, Brad Bishop wrote:
>> 
>> 
>>> On Feb 18, 2020, at 7:56 AM, Vishwanatha Subbanna <vishwa at linux.vnet.ibm.com> wrote:
>>> However, if the user changes the setting when the Host is booting, timemanager puts them in deferred state. Meaning, timemanager does not take the settings into effect until the Host is powered off.
>> 
>> Can you elaborate on why it does this?
>> 
>>> 
>>> So, if someone wants to move from [Manual] to [NTP] or vice-versa, when the Host is [On], they need to [power-off] the Host and power it back on.
>> 
>> This seems less than ideal?  Would you agree?
>> 
>>> 
>>> This design was chosen because we wanted to give priority to Host.
>> 
>> What does it mean to give priority to the Host?  Are you trying to hide time changes in the time from the host?  Why?
>> 
>>> Some of us are asking me if we can make a change to take the setting changes in effect immediately, not caring the state of the Host.
>> 
>> Without additional background this is what seems intuitive to me.
>> 
> 
> Most of these design points came from considering how it might be best
> for a cloud provider, like Rackspace, we were originally designing some
> of this code for.
> 
> If I'm leasing the host processor from you, I don't necessarily trust
> your time infrastructure and might want to use my own.

Agreed but what does this have to do with what is going on, on the BMC?