I think it makes a lot of sense to make this configurable. However, I
wonder if we should consider making it a collection with a priority levels
instead of a single enum. I can envision a need for someone to say, "Use
NTP when it's available, but if the network is down then use the host."

While we're on the subject, has anyone ever taken a look at using roughtime
on a BMC? I imagine it could a really valuable extension to
phosphor-time-manager some time in the future.
https://blog.cloudflare.com/roughtime/

Regards,
Richard

On Tue, Oct 6, 2020 at 10:40 AM Velumani T-ERS,HCLTech <velumanit@hcl.com>
wrote:

> Classification:
>
> Hi Team,
>
>
>
> We wanted to add another time sync method in phosphor-time-manager to get
> the time from the host and set it to BMC. To have this option configurable
> I propose a dbus property in the time interface(given below). Please
> provide your feedback/comments.
>
>
>
>
> https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Time/Synchronization.interface.yaml
>
> enumerations:
>
>     - name: Method
>
>       description: >
>
>         Possible methods of time synchronization.
>
>       values:
>
>         - name: NTP
>
>           description: >
>
>             Sync by using the Network Time Protocol.
>
>         - name: Manual
>
>           description: >
>
>             Sync time manually.
>
>          - name: HostSync
>
>           description: >
>
>             Sync the time from host.
>
>
>
> Regards,
>
> Velu
> ::DISCLAIMER::
> ------------------------------
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or may contain
> viruses in transmission. The e mail and its contents (with or without
> referred errors) shall therefore not attach any liability on the originator
> or HCL or its affiliates. Views or opinions, if any, presented in this
> email are solely those of the author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification, distribution and / or
> publication of this message without the prior written consent of authorized
> representative of HCL is strictly prohibited. If you have received this
> email in error please delete it and notify the sender immediately. Before
> opening any email and/or attachments, please check them for viruses and
> other defects.
> ------------------------------
>