[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
DevOps workflow for networking
- Subject: DevOps workflow for networking
- From: hugo at slabnet.com (Hugo Slabbert)
- Date: Fri, 11 Aug 2017 08:51:25 -0700
- In-reply-to: <CAEy4ivfW+3tAOtMGDArZ1=GZ7uinXwUS=VKxT26ADDEKAHr2dg@mail.gmail.com>
- References: <CALb2afN1Dh3O7OeFQt5ZteSi+T1JS_Bx_47=ve=vhAjmEjpf8w@mail.gmail.com> <CAO0-hXbv50DdMzJ0iRvxfqjidNtgURUBjJEGiyD7NL6aZ2YBnA@mail.gmail.com> <CAEy4ivfW+3tAOtMGDArZ1=GZ7uinXwUS=VKxT26ADDEKAHr2dg@mail.gmail.com>
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 at slabnet.com
pgp key: B178313E | also on Signal
On Fri 2017-Aug-11 00:18:39 -0700, Jippen <cheetahmorph at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20170811/417b6af2/attachment.sig>