[LWN Logo]
[Timeline]
From: "Shane O'Donnell" <shaneo@opennms.org>
To: <general@opennms.org>
Subject: OpenNMS: OpenNMS Update v1.22
Date: Tue, 22 Aug 2000 17:12:23 -0400

================
 OpenNMS Update
================
Vol 1., Issue 22
================

In this week's installment...

 - Project Status
   - Boulevard of Broken Arms
   - New CVS Module - XML
   - Events II - Electric Boogaloo
   - Coding Projects Underway
 - The Wish List

================
Project Status
================

Boulevard of Broken Arms:

Well, he tells us he fell on it wrong while playing "Ultimate Frisbee", but
word on the street has it that he owes some people some money and they sent
him a message. Either way, our illustrious lead coder and spec wonk (Weave)
has a broken arm.

Rest assured, he's still working, but when your brain thinks at 100 mph and
you type at 2 wpm, it's frustrating for everyone.

So, I've been picking up some slack on some of the day-to-day stuff that
Weave does (sys admin stuff, CVS maintenance, general bitching and moaning),
and he's been working on healing. Needless to say, this has hampered our
productivity. We're still moving, just not as fast as we'd like to.

Sheesh...seems like we just went through this with a stomach virus. I'm
beginning to suspect hypochondria...


New CVS Module -- XML:

We're partially restructuring CVS to consolidate all of the XML and DTD
files into one module, named (appropriately enough) "xml".

We're in the process of doing some additional clean-up and cross-checking of
some of the dependencies, so if you've got builds that are currently failing
(based on CVS exports), this may be why.


Events II - Electric Boogaloo:

With the completion of Rick's phase of the events effort, Steve has stepped
back into the picture and wrapped some of our collective thoughts into a
neat little package and called it documentation on eventsd version 1.0G

The new events doc is available for download from the web server at
http://www.opennms.org/devdocs/

Note that this document replaces any previous event documentation as well as
the old "eventSubsystem.gif" diagram.


Coding Projects Underway:

 * Events -- Rolling again. Sowmya's all over this one.

 * discovery/capsd -- Internal testing is complete. Our one-armed code
reviewer is looking at this.

 * AWT < - > SWING Conversion -- Still in preliminary phases. Waiting on an
update from the community. Low priority item.

 * icmpd/Perl -- No update.

 * Service Control Manager -- Development underway. Current implementation
parses the config file. It's a start.

 * Bug fixes for jReporter -- Development underway. Expected complete this
week.

 * Extractors -- Initial coding is underway. Jacinta owns this one.
Currently handles blind passing of SQL query.


===============
The Wish List
===============

"What doesn't kill us makes us stronger, but it can sure screw with your
typing." - Friedrich Nietzsche, by way of Brian Weaver

Well, Weave has managed to shirk some coding duties, so we could certainly
use your help. Read the following options and let us know where you can
help! On behalf of the one-armed wonder, Thanks!

 - Architects needed to provide some input on standard events, how they are
defined, and what is necessary. Read up on the events subsystem in Steve's
new doc and join the fun on the "events" mailing list.
- Anybody interested in pitching in on adding SNMPv3 functionality to jSNMP?
- Parsing masters needed to implement the upcoming "Filtering" spec
- Java coders need to grab the event correlation spec and bring it to life.
- Anybody out there keeping up with OpenJMS? Keep us posted!


=====================
On theorems, and such
=====================

There were three Medieval kingdoms on the shores of a lake. There was an
island in the middle of the lake, which the kingdoms had been fighting over
for years. Finally, the three kings decided that they would send their
knights out to do battle, and the winner would take the island.

The night before the battle, the knights and their squires pitched camp and
readied themselves for the fight.

The first kingdom had 12 knights, and each knight had 5 squires, all of whom
were busily polishing armor, brushing horses, and cooking food. The second
kingdom had 20 knights, and each knight had 10 squires. Everyone at that
camp was also busy preparing for battle.

At the camp of the third kingdom, there was only one knight, with his
squire. This squire took a large pot and hung it from a looped rope in a
tall tree. He busied himself preparing the meal, while the knight polished
his own armor.

When the hour of the battle came, the three knights sent their squires out
to fight (this was too trivial a matter for the knights to join in). The
battle raged, and when the dust cleared, the only person left was the lone
squire from the third kingdom, having defeated the squires from the other
two kingdoms.

This just proved that the squire of the high pot and noose is equal to the
sum of the squires of the other two sides.

Come on. We're all math geeks here. Relax!


Shane O.
========
Shane O'Donnell
OpenNMS
shaneo@opennms.org
http://www.opennms.org

= = = = = = = OpenNMS.org List Message = = = = = = = = =
To unsubscribe from this list, send a message with a body of
"unsubscribe general <email>" to majordomo@opennms.org.