Proposal for 2 properties for Nameservers

[William Kennington]

+1

On Sun, Sep 22, 2019 at 6:40 PM Manojkiran Eda <manojeda at in.ibm.com> wrote:
>
> Hi All,
>
> This mail is regarding , the proposal for adding an additional property `StaticNameservers` and also for changing the definition of the existing `Nameservers` property.
>
> - Currently, we have a single DBUS property under Ethernet interface named `Nameservers` that captures only StaticNameservers configured on the system. It does not populate the information regarding the DNS information that is obtained by DHCP server.
>
> It is also to be noted that the static & dynamic configuration can co-exist at the same time(means we might have the DNS set manually by user and also by the DHCP Server at the same time).
>
> As per the discussion with Ratan & Wak(https://gerrit.openbmc-project.xyz/#/c/openbmc/phosphor-networkd/+/24224/),we had come to a conclusion that we need have two properties in the Backend for nameservers (similar to what we have in redfish):
>
> 1. Nameservers - A read only property which captures the current nameservers on the system (which may be static or/and dynamic)
> 2. StaticNameservers - A writeable property which captures only the static nameservers.
>
> Please let me know, if anyone have concerns with this proposal.
>
> Thanks,
> Manoj
>