[195482] in North American Network Operators' Group
Re: DevOps workflow for networking
daemon@ATHENA.MIT.EDU (Tom Beecher)
Fri Aug 11 16:54:31 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <20170811155125.GD29045@bamboo.slabnet.com>
From: Tom Beecher <beecher@beecher.cc>
Date: Fri, 11 Aug 2017 16:53:29 -0400
To: Hugo Slabbert <hugo@slabnet.com>
Cc: NANOG list <nanog@nanog.org>, Joe Hamelin <joe@nethead.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
The same way we've done it for years ; really hacky expect scripts. :)
On Fri, Aug 11, 2017 at 11:51 AM, Hugo Slabbert <hugo@slabnet.com> 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"?
>
> --
> 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.
>>
>
