Subject: Re: [Netconf] zerotouch/15: Enhanced script support

From: Kent Watsen <[email-masked]>
Date: Fri, 12 Aug 2016 00:45:42 +0000

This issue was discussed in Berlin.  No issues were raised then or on list.  
Hence this change is confirmed and the issue will be closed.

Thanks,
Kent

On 7/6/16, 9:23 PM, "Netconf on behalf of Kent Watsen" <[email-masked] on behalf of [email-masked]> wrote:

    So my thoughts on this are to support also a “pre-configuration-script”, but to not worry about parameters as the any such device-specific parameters can be encoded into the script itself.   Of course, I’m assuming that the script is really a script, and not a compiled executable.   If we want to support compiled executables, then parameters might be good.  Any comments?  - should we try to support compiled executables?
    
    Kent

    On 6/29/16, 7:36 PM, "Netconf on behalf of Kent Watsen" <[email-masked] on behalf of [email-masked]> wrote:
    
    https://github.com/netconf-wg/zero-touch/issues/15
    
    The current draft allows for a single script that takes no command-line parameters. On-going implementation discussions suggest that:
    
    1) there should be support to run a script both before and after the configuration is committed.
           - this means that we'd need both "pre-script" and "post-script" leaves
           - for instance:
    
    OLD:
    
                     +--ro bootstrap-information
                        +--ro boot-image
                        |  +--...
                        +--ro configuration
                        +--ro script?          string
    NEW:
    
                     +--ro bootstrap-information
                        +--ro boot-image
                        |  +--...
                        +--ro pre-configuration-script?          string
                        +--ro configuration
                        +--ro post-configuration-script?         String

    2) there should be support for passing command line parameters, so that the same script can be used on many devices. This is essentially shifting where variable bindings occur - either the NMS renders a device-specific script (incorporating device-specific values), or the device renders it (using command-line variables to know how to do the substitutions). The latter is harder on devices, but the former may enable better scalability. To implement this, we might have something like:
    
    NEW: // adding onto the above example
    
                     +--ro bootstrap-information
                        +--ro boot-image
                        |  +--...
                        +--ro pre-configuration-script
                        |  +-- script                                        string
                        |  +-- parameters                             string
                        +--ro configuration
                        +--ro post-configuration-script
                           +-- script                                        string
                           +-- parameters                             string

    Any thoughts on this one?

    Thanks,
    Kent

    _______________________________________________
    Netconf mailing list
    [email-masked]
    https://www.ietf.org/mailman/listinfo/netconf

    _______________________________________________
    Netconf mailing list
    [email-masked]
    https://www.ietf.org/mailman/listinfo/netconf