nanog mailing list archives
Re: DevOps workflow for networking
From: Hugo Slabbert <hugo () slabnet com>
Date: Fri, 11 Aug 2017 08:51:25 -0700
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"?
-- Hugo Slabbert | email, xmpp/jabber: hugo () slabnet com pgp key: B178313E | also on Signal On Fri 2017-Aug-11 00:18:39 -0700, Jippen <cheetahmorph () gmail com> wrote:
To be honest, most companies I've worked at have moved to amazon, where the networking stack has APIs. I've also seen folks who use CI/CD pipelines to generate configuration files for devices that don't directly support automation.
Attachment:
signature.asc
Description: Digital signature
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)