Hello,
for me this would be ok.
--
Tomasz Kuzemko
tom...@kuzemko.net
W dniu 26.01.2014 09:38, Leif Hedstrom pisze:
On Jan 25, 2014, at 7:29 PM, Tomasz Kuzemko <tom...@kuzemko.net> wrote:
Hello,
I use show:alarms in a monitoring script to check if there was any alarm
triggered. Is there some other way to do it not using traffic_shell?
I was thinking of moving a couple of these "status" like commands into
traffic_line. So e,g.
traffic_line -a
would produce identical output to the old show:alarms command . Would that be
acceptable for now?
Long term I wish to implement all the mgmt APIs for scripted languages , but
it's a lot more work. And I do feel that e.g. show:alarms functionality should
be in traffic_line anyways .
Thoughts?
-- Leif
--
Tomasz Kuzemko
tom...@kuzemko.net
W dniu 25.01.2014 14:37, Leif Hedstrom pisze:
Hi all,
I’ve written a replacement for traffic_shell, entirely in Perl using our Perl
Admin module. This has two benefits:
1) It eliminates a huge dependency on TCL (and readline or similar lib),
leaving only the hash TCL code left.
2) I feel it makes for a more manageable tool, that we can now improve / work
on more easily.
The downside is that we lose the ability to write TCL script using the
traffic_shell interpreter. I honestly don’t feel this being a huge problem,
particularly if we focus efforts on getting the MgmtAPI’s into modern scripting
languages.
The new version is virtually identical to the old version, with one small
exception; show:alarms does not work. It does mean that in order to use
traffic_shell, you must have Perl installed.
Thoughts? I’d like to land this for v5.0.0.
— Leif
