[As a contributor]
If not, does it become a configuration error if a
line card is inserted to which the configuration can not be applied?
>>> As above, this question doesn't directly apply.
>>>
>>> But a similar question might be: what would happen if the configuration
>>> had previ
On 12/02/2016 08:19, Juergen Schoenwaelder wrote:
On Thu, Feb 11, 2016 at 02:52:27PM +, Robert Wilton wrote:
On 11/02/2016 09:29, Juergen Schoenwaelder wrote:
We are discussing this text:
D. The configuration protocol MUST specify how configuration
errors are handled
On Thu, Feb 11, 2016 at 02:52:27PM +, Robert Wilton wrote:
>
> On 11/02/2016 09:29, Juergen Schoenwaelder wrote:
> >We are discussing this text:
> >
> >D. The configuration protocol MUST specify how configuration
> >errors are handled. Errors SHOULD be handled by semantic
On 11/02/2016 09:29, Juergen Schoenwaelder wrote:
On Wed, Feb 10, 2016 at 05:45:10PM +, Robert Wilton wrote:
On 10/02/2016 12:51, Juergen Schoenwaelder wrote:
On Mon, Feb 08, 2016 at 05:50:00PM +, Gert Grammel wrote:
Hi Juergen,
I think the indentation in our emails play havoc whi
On Wed, Feb 10, 2016 at 05:45:10PM +, Robert Wilton wrote:
>
>
> On 10/02/2016 12:51, Juergen Schoenwaelder wrote:
> >On Mon, Feb 08, 2016 at 05:50:00PM +, Gert Grammel wrote:
> >>Hi Juergen,
> >>
> >>I think the indentation in our emails play havoc which is confusing me
> >>too. The key
On 10/02/2016 12:51, Juergen Schoenwaelder wrote:
On Mon, Feb 08, 2016 at 05:50:00PM +, Gert Grammel wrote:
Hi Juergen,
I think the indentation in our emails play havoc which is confusing me
too. The key point I am making is:
The mapping of what is called intended-config onto data store
On 10/02/2016 15:46, Kent Watsen wrote:
If there was a way that YANG patch (or equivalent) were able to return
both old and new values (in the same tree) then I think that would be
better. I don't think that such as solution would be specific to the
opstate requirements and may be useful m
>If there was a way that YANG patch (or equivalent) were able to return
>both old and new values (in the same tree) then I think that would be
>better. I don't think that such as solution would be specific to the
>opstate requirements and may be useful more generally.
Already the RPC acce
On 10/02/2016 12:42, Juergen Schoenwaelder wrote:
On Mon, Feb 08, 2016 at 04:59:42PM +, Robert Wilton wrote:
So if in my 1 million XML elements one has not been applied, how do I
find out efficiently in your encoding?
By using 'diff-cfg-only' option of the parameter,
you would get 3 or
On Mon, Feb 08, 2016 at 05:50:00PM +, Gert Grammel wrote:
> Hi Juergen,
>
> I think the indentation in our emails play havoc which is confusing me
> too. The key point I am making is:
>
> The mapping of what is called intended-config onto data stores would
> deserve more detailed discussion.
On Mon, Feb 08, 2016 at 04:59:42PM +, Robert Wilton wrote:
> >So if in my 1 million XML elements one has not been applied, how do I
> >find out efficiently in your encoding?
> By using 'diff-cfg-only' option of the parameter,
> you would get 3 or 4 leaves per mismatching node: (intended valu
Robert Wilton wrote:
> Hi Martin,
>
> On 08/02/2016 14:38, Martin Bjorklund wrote:
> > Robert Wilton wrote:
> >> Hi,
> >>
> >> On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
> >>> On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
> 2. Personally, for a datastore solution, I
Hi Juergen,
I think the indentation in our emails play havoc which is confusing me
too. The key point I am making is:
The mapping of what is called intended-config onto data stores would
deserve more detailed discussion. It seems the authors of
draft-kwatsen-netmod-opstate-02.txt had in mind to
On 08/02/2016 16:31, Juergen Schoenwaelder wrote:
On Mon, Feb 08, 2016 at 01:30:02PM +, Robert Wilton wrote:
Hi,
On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
2. Personally, for a datastore solution, I would prefer if th
On Mon, Feb 08, 2016 at 02:53:57PM +, Gert Grammel wrote:
>
>
> >This is not what is being proposed. We always had
> >
> >[candidate] -> [running] -> operational state
> >
> >(and I mark configuration data stores in []). Both [candidate] and
> >[running] have the same configuration data model
On Mon, Feb 08, 2016 at 01:30:02PM +, Robert Wilton wrote:
> Hi,
>
> On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
> >On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
> >>2. Personally, for a datastore solution, I would prefer if the new
> >>datastore was for the intended con
Hi Martin,
On 08/02/2016 14:38, Martin Bjorklund wrote:
Robert Wilton wrote:
Hi,
On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
2. Personally, for a datastore solution, I would prefer if the new
datastore was for the intended
On 2016-05-02 18:34, "netmod on behalf of Juergen Schoenwaelder"
wrote:
>On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
>>
>> 2. Personally, for a datastore solution, I would prefer if the new
>> datastore was for the intended configuration, and that the applied
>> configuratio
Robert Wilton wrote:
> Hi,
>
> On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
> > On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
> >> 2. Personally, for a datastore solution, I would prefer if the new
> >> datastore was for the intended configuration, and that the applied
> >>
Hi,
On 05/02/2016 17:34, Juergen Schoenwaelder wrote:
On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
2. Personally, for a datastore solution, I would prefer if the new
datastore was for the intended configuration, and that the applied
configuration was stored in the same datasto
On 2/5/16, 7:20 AM, "Gert Grammel" wrote:
>Hi Kent,
>
>On P.7 the current draft says: "Any rollback that may occur will restore
>both the intended and the applied configurations to their previous states."
>
>It is not clear to me to which phase of the configuration this statement
>refers to.
On Fri, Feb 05, 2016 at 05:22:03PM +, Robert Wilton wrote:
>
> 2. Personally, for a datastore solution, I would prefer if the new
> datastore was for the intended configuration, and that the applied
> configuration was stored in the same datastore (running?) as all the
> rest of the operati
Hi Kent, and other authors,
I've taken a quick look through this draft, and hence have a few
comments/questions below. Some of these comments are the same that I
made in reference to the previous version of this draft.
1. Minor nit: I think that the key point of this solution is that it is
Hi Kent,
On P.7 the current draft says: "Any rollback that may occur will restore
both the intended and the applied configurations to their previous states."
It is not clear to me to which phase of the configuration this statement
refers to. In draft-ietf-netmod-opstate-reqs-04, Asynchronous oper
Hi All,
I didn’t receive the usual announcement CC-ed to the netmod list, so I’m
replying to this one sent to the id-announce list instead.
Anyway, this morning I posted -01 of this draft and then shortly after -02 to
fix some cleanup items I only noticed after -01 was posted :ooops:
Either
25 matches
Mail list logo
