Re: [I2rs-proto-dt] couple YANG details

["Susan Hares" <[e-mail]>]

Andy: 

 

Two options: 

1)      Ephemeral obeys the overall configuration, 

2)      Ephemeral sets its own ephemeral limit. 

 

If you do #2, then are you suggesting we put a limit in the original data model. 

 

Sue 

 

From: I2rs-proto-dt [mailto:[e-mail]] On Behalf Of Andy Bierman
Sent: Friday, October 23, 2015 11:29 AM
To: Jeffrey Haas
Cc: [e-mail]; Susan Hares
Subject: Re: [I2rs-proto-dt] couple YANG details

 

 

 

On Fri, Oct 23, 2015 at 8:19 AM, Jeffrey Haas <[e-mail]> wrote:

Andy,

On Wed, Oct 21, 2015 at 02:49:12PM -0700, Andy Bierman wrote:
> We need to figure out for each YANG constraint:
>  1) does it apply at all?
>  2) is it MUST, SHOULD, or MAY enforce?
>  3) Does the constraint apply the same in running vs. ephemeral?
>  4) Does the constraint apply to the combined panes of glass or
>      each pane independently?

I'm going to avoid answering your question to let you decide what this
functional requirement means:
Ephemeral nodes SHOULD NOT introduce their own constraints.
The presence of ephemeral nodes does not trump validation or constraints for
persistent state.

 

So if the YANG list has "max-elements 5",

and the config has 5 entries.  What happens when

5 or 10 entries are added in the ephemeral datastore?

 

 

-- Jeff

 

Andy