<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 12/19/19 1:29 AM, Kun Yi wrote:<br>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
      </div>
    </blockquote>
    <br>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Wed, Dec 18, 2019 at 7:02
            AM vishwa <<a href="mailto:vishwa@linux.vnet.ibm.com"
              target="_blank" moz-do-not-send="true">vishwa@linux.vnet.ibm.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div bgcolor="#FFFFFF">
              <p>Hello community,<br>
              </p>
              <p>Would be really great if there is any feedback on this.</p>
              <p>Have a happy holidays !!<br>
              </p>
              <p>!! Vishwa !!</p>
              <div>On 12/11/19 3:24 PM, vishwa wrote:<br>
              </div>
              <blockquote type="cite">
                <div>On 12/11/19 12:17 AM, Pine, Kathryn ElaineX wrote:<br>
                </div>
                <blockquote type="cite">
                  <div>
                    <p><span style="color:windowtext">></span><b> Do
                        we need this going forward ?</b>: I am being
                      asked by UX team about the need of this and I
                      mentioned I would get the community feedback on
                      this. Although, I feel this level of granularity
                      gives control over how we can manage time, it
                      would not justify the complexity if the customers
                      don't appreciate it. Removing the TimeOwner would
                      make the code a lot simpler.</p>
                    <p class="MsoNormal"><span style="color:windowtext">Hi,</span></p>
                    <p class="MsoNormal"><span style="color:windowtext"> </span></p>
                    <p class="MsoNormal"><span style="color:windowtext">I
                        am coming from the UX side of how we set the
                        date time settings page up for phosphor-webui
                        downstream recently. We switched our page to use
                        Redfish, here’s how ours is set up now:</span></p>
                    <p class="MsoNormal"><span style="color:windowtext"> </span></p>
                    <p class="MsoNormal"><span style="color:windowtext">There
                        is no longer a “time owner” and the setting is
                        either:</span></p>
                    <p class="MsoNormal"><span style="color:windowtext">NTPEnabled:
                        true or false</span></p>
                    <p class="MsoNormal"><span style="color:windowtext">If
                        false, we are not allowing the user to set the
                        time, because the BMC is synching from the host
                        time and therefore any settings we made to the
                        time on the BMC would be overwritten. </span></p>
                    <p class="MsoNormal"><span style="color:windowtext">If
                        true, we use the NTP server(s) the user
                        provides.</span></p>
                    <p class="MsoNormal"><span style="color:windowtext"> </span></p>
                    <p class="MsoNormal"><span style="color:windowtext">We
                        are testing this currently.</span></p>
                  </div>
                </blockquote>
                <div><br>
                  Hi, Thank you for the response. From what I
                  interpreted:<br>
                  <br>
                </div>
                <div>- TimeOwner is not settable via GUI<br>
                  - Irrespective of NTP setting, the user is not allowed
                  to set the time on BMC<br>
                  - BMC is syncing the time from Host.<br>
                     - This means, the current TimeOwner is "Host" and
                  NTP is off. Is that being set as default ?<br>
                </div>
                <div><br>
                  I am requesting for feedback from the community on the
                  need of TimeOwner feature that we have in Settings and
                  timemanager code.<br>
                </div>
                <div><br>
                  !! Vishwa !!<br>
                </div>
                <blockquote type="cite">
                  <div>
                    <p class="MsoNormal"><span style="color:windowtext"><a
name="m_-4131239486451252847_m_691753059126936336______replyseparator"
                          moz-do-not-send="true"></a></span></p>
                  </div>
                </blockquote>
              </blockquote>
            </div>
          </blockquote>
        </div>
        My 2cents here along with a few questions:
        <div>- how does the current time manager interact
          with systemd-timesyncd?<br>
        </div>
      </div>
    </blockquote>
    <div><br>
      TimeManager interacts with systemd-timedated, which in turn
      engages systemd-timesync on setting <strong>NTP </strong>policy.<br>
<a class="moz-txt-link-freetext" href="https://www.freedesktop.org/software/systemd/man/systemd-timesyncd.service.html">https://www.freedesktop.org/software/systemd/man/systemd-timesyncd.service.html</a><span
        class="command"><strong></strong></span><br>
      <br>
    </div>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>- From my experience, BMC time can drift a lot easily and
            it is more useful to have the BMC time synced externally</div>
        </div>
      </div>
    </blockquote>
    <div><br>
      This is a discussion point for using / not using NTP. It would not
      impact TimeOwner<br>
<a class="moz-txt-link-freetext" href="https://github.com/openbmc/phosphor-time-manager/blob/master/README.md">https://github.com/openbmc/phosphor-time-manager/blob/master/README.md</a><br>
      <br>
    </div>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>- Whether NTP or host time is preferred should be left to
            the platform designer to decide</div>
        </div>
      </div>
    </blockquote>
    <div><br>
      If the setting is NTP, then Host can not set the time on BMC
      unless the Owner is SPLIT.<br>
      I believe, you are saying more from a NTP / Non NTP as opposed to
      TimeOwner ?<br>
      <br>
    </div>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>- sounds like it would be more straightforward to have
            the 'Owner' reflect one time source: NTP/IPMI/Redfish<br
              clear="all">
          </div>
        </div>
      </div>
    </blockquote>
    <div><br>
      This is part of TimeSynchronization. TimeOwner is another layer on
      who owns the time as opposed to how the time is set.<br>
      Hopefully the README I pointed to before would help.<br>
    </div>
    <div><br>
      Thank you,<br>
      !! Vishwa !!<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGMNF6VnZdkWPUuZR2yThm43gCwxXDu0AVOJ3Wmi5UvOw2s9Sw@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>
            <div><br>
            </div>
            -- <br>
            <div dir="ltr">
              <div dir="ltr">Regards,
                <div>Kun</div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>