nanog mailing list archives
Re: DevOps workflow for networking
From: Leo Bicknell <bicknell () ufp org>
Date: Fri, 11 Aug 2017 09:34:41 -0700
In a message written on Fri, Aug 11, 2017 at 08:51:25AM -0700, Hugo Slabbert wrote:
Possibly a minor nit, but if the devices "don't directly support automation", how is the "D" part of "CI/CD" accomplished there? `integration -ne deployment`. Do you mean something like "there is no API or e.g. netconf interface, but they can generate config off-box, scp it, and `copy start run` to load"?
More or less. I've worked at places that do this sort of thing. 1) Download config from box. 2) Run script to determine changes necesary to config. 3) Load changes. 4) Download config again. 5) Re-run the script to determine changes necessary, verify there are none. For a lot of the devices with a Cisco-IOS like interface it's not even hard. Generate a code snippet: config terminal interface e0 description bar end write mem Then tftp the config to a server, have the script see e0 has description bar. -- Leo Bicknell - bicknell () ufp org PGP keys at http://www.ufp.org/~bicknell/
Attachment:
signature.asc
Description:
Current thread:
- DevOps workflow for networking Kasper Adel (Aug 09)
- Re: DevOps workflow for networking Andrew Latham (Aug 10)
- Re: DevOps workflow for networking Raymond Burkholder (Aug 10)
- Re: DevOps workflow for networking Joe Hamelin (Aug 10)
- Re: DevOps workflow for networking Jippen (Aug 11)
- Re: DevOps workflow for networking Hugo Slabbert (Aug 11)
- Re: DevOps workflow for networking Leo Bicknell (Aug 11)
- Re: DevOps workflow for networking Saku Ytti (Aug 11)
- Re: DevOps workflow for networking Tom Beecher (Aug 11)
- Re: DevOps workflow for networking Jippen (Aug 11)
- Re: DevOps workflow for networking Andrew Latham (Aug 24)