On Wed, Nov 27, 2019 at 12:06 PM Till Maas wrote:
> Hi,
>
> Am Mi., 27. Nov. 2019 um 11:02 Uhr schrieb Edward Haas >:
> >
>
> > +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
On Sat, Nov 23, 2019 at 9:58 AM Thomas Haller via networkmanager-list <
networkmanager-list@gnome.org> wrote:
> On Fri, 2019-11-22 at 21:52 +0100, Till Maas via networkmanager-list
> wrote:
> > Hi,
> >
> > one of the Nmstate ours accidentally used Nmstate on a machine after
> > updating NM
Hello,
Due to requests from the OpenStack community, we have been asked to soften
nmstate licensing.
Re-licensing to LGPL seems to satisfy OpenStack dependency rules.
Two tickets have been opened to track this:
https://nmstate.atlassian.net/browse/NMSTATE-193
On Thu, Mar 21, 2019 at 11:02 AM Till Maas wrote:
> Hi,
>
> Am Do., 21. März 2019 um 09:16 Uhr schrieb Edward Haas >:
> >
> >
> >
> > On Wed, Mar 20, 2019 at 8:35 PM Till Maas wrote:
> >>
> >> Hi,
> >>
> >> Am Mi., 20.
On Wed, Mar 20, 2019 at 8:35 PM Till Maas wrote:
> Hi,
>
> Am Mi., 20. März 2019 um 18:13 Uhr schrieb Edward Haas via
> networkmanager-list :
> >
> >
> >
> > On Wed, Mar 13, 2019 at 3:48 PM Gris Ge via networkmanager-list <
> networkmanage
On Tue, Mar 5, 2019 at 9:35 AM Edward Haas wrote:
>
>
> On Tue, Mar 5, 2019 at 9:25 AM Gris Ge wrote:
>
>> On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote:
>> > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote:
>> > > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'.
>> >
On Tue, Mar 5, 2019 at 9:25 AM Gris Ge wrote:
> On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote:
> > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote:
> > > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'.
> > >Even the IPv4 and IPv6 route entry are mostly identical,
On Mon, Mar 4, 2019 at 6:58 PM Thomas Haller wrote:
> On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote:
> > Based on feedbacks, this is V2 scheme for review:
> >
> > ```
> > {
> > "routes": {
> > "ipv4": [ # Sorted with 'table-id' then
> > 'destination'
> >
On Fri, Mar 1, 2019 at 9:41 AM Thomas Haller wrote:
> On Thu, 2019-02-28 at 22:40 +0200, Edward Haas via networkmanager-list
> wrote:
> > Thank you Gris.
> > Comments in-line.
> >
> > On Tue, Feb 26, 2019 at 8:56 AM Gris Ge wrote:
> > > Hi Guys,
&g
On Fri, Mar 1, 2019 at 9:43 AM Thomas Haller wrote:
> Hi,
>
> On Tue, 2019-02-26 at 14:56 +0800, Gris Ge via networkmanager-list
>
> > "protocol": "dhcp", # "static" or "dhcp"
>
> "protocol" sounds a bit like iproute2's "protocol" option (struct
> rtmsg's rtm_protocol). But I
On Fri, Mar 1, 2019 at 4:34 AM Gris Ge wrote:
> On Thu, Feb 28, 2019 at 10:40:48PM +0200, Edward Haas wrote:
> >
> > What is the root level key? `routing`?
> The root level is 'ipv4-routes' and 'ipv6-routes'.
>
> Try to save a layer for user to type comparing to ['routing']['routes']
>
> The ip
Thank you Gris.
Comments in-line.
On Tue, Feb 26, 2019 at 8:56 AM Gris Ge wrote:
> Hi Guys,
>
> Could you review below schema for routing in nmstate before we start
> add routing support in nmstate?
>
> ```
>
What is the root level key? `routing`?
{
> "ipv4-routes": [# Sorted
12 matches
Mail list logo
