Gang – we’ve been having some issues with clamav on the OpenNMS server today. The way our mail server is configured, incoming mail gets passed to amavisd and then on to clamav before being delivered. When clam dies, mail starts to queue.
We hope it is fixed, now. Sorry for the inconvenience, and thanks to Eric for fixing it.
Today I took some time off to try and wade through my e-mails. My Inbox is my “to do” list, and I’ll answer an e-mail much faster than pretty much anything else.
However, my Inbox was over 550 messages strong, the oldest from more than a year ago, so something needed to be done. I am now under 100, but too tired to go on today, so if you got a reply from me to an e-mail you sent five months ago, let me apologise once again.
I was surprised that a number of the e-mails were from people wanting support for a particular platform. When I listed out the platforms we will support starting in 1.1.3 I was surprised at the number:
- Solaris 8 and 9, both SPARC and x86
- Mac OSX (Panther)
- Debian, woody and sid
- Red Hat 7, 8, and 9
- Mandrake 8 and 9
- Fedora Core 1
- CentOS (equivalent to RHES 3)
And I have probably forgotten a few. These platforms will be supported via our “lynx installer”. Why did we choose these? Well, our support customers pay us to (grin).
Here is a list of the platforms I hope to have out for 1.2, but no promises:
Until then, we should build on all of those platforms, so if you happen to get it running please drop me and/or the list a note with your process and we’ll try to get it on the web page.
Okay, we’re down to about 28 bugs blocking 1.1.3. Thanks to everyone who looked into helping, and to those that contributed patches.
If nothing comes up, we should be able to tag 1.1.3 this week or next. Stay tuned.
Okay, I’ve been heads down on 1.1.3/1.2 and ignoring the list, but I hear talk that folks are looking for a “roadmap”. This is something I sent around internally, and it is subject to heavy changes, but I thought I’d share it for what it is worth.
Here is a draft of the roadmap for OpenNMS, represented by pairs of version numbers reflecting the development/production cycle for each release.
Note that this list is by no means exhaustive, and represents the main points I want to cover.
Timeframe: As soon as possible
- This is almost complete. All the features are basically in, but many things are broken.
I have been spending time in Bugzilla cleaning things up so that I can set up a “blocker”
bug that will track when we can release 1.1.3.
- Installer: We need to fix the installer to handle the install more cleanly.
- Documentation: The documentation needs a lot of work. I want to sequester myself for a week
and fix this.
In the “would be nice” category:
- Performance enhancements to data collection
- Support for the latest Java: 1.4.2, as well as IBM’s SDK.
- OpenNMS on a disk: Using White Dwarf, support OpenNMS as a single CD iso.
Ok, I know they are way late in coming, but Debian unstable packages for OpenNMS 1.1.2 are now available for your apt-get upgrade/install ‘ing pleasure.
Detailed installation instructions can be found here, but in a nutshell you just need to:
- Meet the java dependency by installing one of j2sdk1.4 or java-virtual-machine or java2-runtime
- Add the OpenNMS repository to sources.list, (deb http://debian.opennms.org/ debian/opennms unstable)
- apt-get update ; apt-get install opennms
Due to much “brokenness” between OpenNMS and Sid at the time of the 1.1.2 release, I opted to hold off on building any 1.1.2 packages for Debian unstable and concentrate my efforts on the Woody packages. Afterwards, and with the impending release of 1.1.3, skipping 1.1.2 and waiting for the new release sounded like a Good Idea(tm), I have since learned that it is not wise to count unhatched chickens.
My apologies to the Debian user-base, and I promise from here-on-out that I will try to be more timely.