On Wed, Nov 27, 2019 at 12:06 PM Till Maas <t...@redhat.com> wrote: > Hi, > > Am Mi., 27. Nov. 2019 um 11:02 Uhr schrieb Edward Haas <edwa...@redhat.com > >: > > > > > +1 for a warning. > > knmstate is using libnm in a container and contacting the host NM > service though a mounted socker. > > So in their case, the versions may be different indeed. > > > > I would also like to see it added to the "capabilities" report: > > > > > https://github.com/nmstate/nmstate/blob/e90fd3e07c482ec8e2038c6c65b86809ffaba6ce/libnmstate/netinfo.py#L67 > > How do you think it should look like? Should the capabilities report > the libnm version? >
Yes, it will be nice to report the NM and libnm versions. It can even report Nmstate version and an optional schema version. Any metadata that can help the client make better decisions. > > Kind regards > Till > > > > > > > > This way the client may decide what to do with the information (like > knmstate). > > -- > Till Maas > He/His/Him > Ansible RHEL Networking System Role Maintainer > > Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, > Commercial register: Amtsgericht Muenchen, HRB 153243, > Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, > Thomas Savage > >
_______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
