Proposal for 2 properties for Nameservers
Johnathan Mantey
johnathanx.mantey at intel.com
Tue Sep 24 04:30:48 AEST 2019
I agree with adding this to DBus.
On 9/22/19 6:39 PM, Manojkiran Eda 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
>
--
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey at intel.com <mailto:johnathanx.mantey at intel.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190923/5040090c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190923/5040090c/attachment.sig>
More information about the openbmc
mailing list