noctool-devel

noctool-devel@common-lisp.net

30 discussions

[noctool-devel] SNMP, again...
by Ingvar 19 Oct '09

19 Oct '09

Almost managed to load the relevant biots and bobs to have a play. Note "almost". We're still at a stage where published tarballs ain't cutting it and not everything is ASDF-INSTALLable. At the moment the latest tarball is ANS.1 v4.5, but it seems as if there's a check when you load the SNMP package, checking for ASN.1 v4.x (x >= 14). Now, I'll have abnother poke, for sure, maybe tomorrow, since I picked whatever was on the last line of the SourceForge download matrix and if the versions are listed in alphabetical order, 4.14 will be before 4.5 so... But, yes, it's slowly moving forward again. //Ingvar

3 4

[noctool-devel] New CLUSTER macro! And a WITH-FORMAT to go with it!
by Ingvar 19 Feb '09

19 Feb '09

The cluster config macro has had some problems, in that it can do one thing (and one thing only), normally the name, numbered in the normal style. So, in a fit of "let's make this better and trivially nestable", I cooked up a new cluster macro. It's subtly different from the old one, but configs that use the non-complicated version of the old one should work identically under the new one. (cluster (<fmt-string> <low> <high> &key c-fmt name counter) <stanza to be repeated>) :name <name> specifys a symbol to be replaced, instead of the default NAME :c-fmt decides if a conversion from C-style format to lisp style format should happen (still defaults to true, but by happy co-incidence, the ~-style lisp arguments are NOT mangled by the C-style conversion, strictly speaking a bug, but maybe not worth fixing at the moment) :counter is NEW, this specifies a counter to be sequentially set from low to high in the expansion. This defaults to a gensym, so cannot be used without specifying it. (with-format ((sym1 fmt1 vars1... ) (sym2 fmt2 vars2 ...)) <config stanza>) Like LET, only, eh, thing... I also cooked up an example (in test-files/nested-cluster.cfg): (cluster ("" 1 2 :counter a) (cluster ("" 1 2 :counter b) (with-format ((name "node~d-cpu~d" a b) (ip-addr "172.23.~d.~d" a b)) (machine name linux-host (user "testuser") (ip ip-addr))))) Somewhat annoyingly, when I test-ran this I noticed that our post-creation clean-up for EQUIPMENT objects is a bit... aggressive. When created from a config stanza, the ONLY thing specified is the name, all else is (eventually) done with (setf *config-object* 'slot-to-set <value>) or pushing things onto the monitor list, as it were. While the clean-up done in the initialize-after method is good, I am wondering if it may be worth creating a new "post-config-cleanup" GF and move the relevant clean-up bits to there, as I actually had to re-define the :after method t do nothing to be able to run my tests (it's vastly easier to use example names to see if things work or not, when one doesn't actually have a cluster at hand). //Ingvar

1 0

[noctool-devel] Oooh! Shiny! [ predictive models of future behaviour ]
by Ingvar 29 Jan '09

29 Jan '09

Found the following after discussing the Snooper model for predicting "a run on this port was made on $Date" and I suspect it MAY, possibly, be worth considering for alert thingbobs in NOCtool: http://www.usenix.org/events/lisa2000/full_papers/brutlag/brutlag_html/inde… //Ingvar

2 3

[noctool-devel] DISK-MONITOR class question
by Jim Prewett 21 Jan '09

21 Jan '09

Hi All, I'm cureous as to why the DISK-MONITOR class has the slots: DISK-USED & INODES-USED whose accessors are DISK-FREE and INODES-FREE and initargs are :DISK-FREE and :INODES-FREE. This seems a *tad* confusing to me, especially whereas df reports used blocks and available blocks and the DISK-USED slot seems to be storing the *free* blocks. The INODES-USED slot seems to be, at this point, unused, so I'm not sure if it is also backwards :) The naming does seem a bit strange as well. :) Jim James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

2 1

[noctool-devel] Hm, may be time for a SLIGHT network protocol design
by Ingvar 01 Jan '09

01 Jan '09

Seems SHA1 is "recommended to be discontinued in 2010", since it is expected that the MD5 collision theories/algorithms can be partially re-used. Investigoating options at the moment (SHA256 may be a contender). //Ingvar

1 0

[noctool-devel] Hm, mudballs?
by Ingvar 08 Dec '08

08 Dec '08

Is it worth considering making a mudballs install/build thingy for NOCtool? More info at http://mudballs.com/ //Ingvar

2 1

[noctool-devel] more config file fun!
by Jim Prewett 02 Dec '08

02 Dec '08

Hey All, I have a cluster where the nodes are named: r1i[0-1]n[0-10] Any thoughts on how to write a (short) config file? For now, I've defined 2 CLUSTERs: r1i0n[0-10] and r1i1n[0-10] but thats somewhat combersome! :P Thanks, Jim James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

1 0

[noctool-devel] Playing around with SNMP, again...
by Ingvar 11 Aug '08

11 Aug '08

Unfortunately, I have hot two snags in the last 20-odd minutes. Snag primo: It doesn't work to simply asdf-install:install the package. It relies on the *load-pathname* of the .asd file being the same as the file residing in the source directory (simple fix, wrap it in a truename call to resolve symlinks). Snag secundo: There's a peppering of calls to USOCKET:MAKE-DATAGRAM-SOCKET and that is a call that my latest USocket version has No Seen<tm> (0.3.7, freshly asdf-installed, specially). That's as far as I've managed to make it. //Ingvar

2 1

[noctool-devel] average "monitor"
by Jim Prewett 28 Jul '08

28 Jul '08

Hello, I'm wondering if anyone has any thoughts on how one might make an "monitor" that represents the average of several other monitors. I'm looking at http://meta.rocksclusters.org/ganglia/ right now where they display a graph of the average load over some 450+ machines. How might you implement something like that in NOCtool? Thanks, Jim p.s. anyone seen any "good" monitoring UIs? something they like... I can't say I ever really have :P James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

2 1

[noctool-devel] proposed patch to image library
by Jim Prewett 21 Jul '08

21 Jul '08

Hi All, Attached, find a patch to the image libray that adds the method write-gif-to-stream. This probably could have been more generically written so as to accomodate PNGs as well. So, do with it what you will... Jim p.s. what is the appropriate channel for discussing the image library? James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

noctool-devel