Re: [NGO] external module properties

[Phil Shafer <phil at juniper.net>]

"David Harrington" writes:
>Each of these components might support different revisions of the same
>module, depending on the vendor model and release.

I agree this is a thorny problem and one that will likely become
more commonplace.  I don't have a good answer, so here's a bad one ;^)

If you have instance-specific modules, you'd use "augments" to add
the new bits.  Something like:

     augments /interfaces/interface/unit {
         when "../type == 'sonet'";
         leaf new-stuff { ... }
     }

To support multiple revisions, you'd need something like
this in your hierarchy, like:

    augments whatever {
         when "../version > '2008-04-01'";
         ...
    }

Then netconf core component could handle the insertion (on output)
and checking (in input) of this version element.

Thanks,
 Phil
_______________________________________________
NGO mailing list
NGO at ietf.org
https://www.ietf.org/mailman/listinfo/ngo