[j-nsp] How to maintain scripts
Pavel Lunin
plunin at gmail.com
Sat Jul 14 06:50:26 EDT 2018
amorsen at orion.amorsen.dk wrote:
>Maintaining scripts is a bit of a pain.
It's not maintaining scripts which is a bit of pain. It's on-box automaton
which is hell a lot of pain and there is very little reason to use it
nowadays. At least at any larger scale than a SOHO gateway for ten users,
doing something useless.
Well, op-scripts to simplify show-pipe-match for your NOC colleagues —
maybe, if you prefer to bother with this instead of something more modern
and multivendor.
Commit scripts — there is already enough ways to turn your JUNOS config
into unreadable mess of groups of interface ranges of groups with wildcards
with ten levels of spaghetti inheritance within LSYS. Commit scripts are
good to make it even worse, if you wish, but it won't make your network
happier.
Event scripts — just never ever, except you *reeeeaaally* love pain.
--
Pavel
More information about the juniper-nsp
mailing list