Hey Ulf, “Master is a mess!”

So, Brozow (The Nog) and I are headed back to my first station in Fulda, Germany. This was a planned trip but a conversation I recently had with my first mentor, Ronny (Indigo), reminded him of this famous scene from the movie Pulp Fiction.

Ronny’s concern, about the code in Master, is due to having just delivered a LOT of code in a very short amount of time to one of our commercial customers. I’ve noticed that these custom development projects are always very stressful but really benefit the community. The downside is that the code needs a lot clean up work and we really need to get busy on documentation.

Ronny expressed that Master wasn’t up to a standard for running in production and that the code his from his team in Germany was very fragile and, more importantly, the new OSGi environment in OpenNMS is too confusing to expect the community to follow and make contributions. Hence, “The Wolf” analogy: “Ronny, I’m bringing Brozow in a couple of weeks to help fix this situation.”

If you haven’t been “Inside OpenNMS” or plugged into the Git repo’s notifications, you’re probably unaware that the OpenNMS code base is getting a forklift upgrade to an OSGi framework (Karaf) and a new set of GUI tools have been added to the Web-UI architecture: D3.js, Vaadin, and JUNG. OSGi has been added to make the OpenNMS architecture more modular and, therefore, pluggable and the GUI tools have been added in support of a new topology-based UI.

The new UI was has been designed to support semantic and contextual panning and zooming. This is very similar to the behavior when navigating geographical maps (i.e. Google Maps) but when viewing a network topology map. It is a very exciting project for OpenNMS and I have decided that the next stable release will finally be christened “2.0!”

More to come on the OSGi and topology UI news but I’m off to a very busy trip to Europe and, yes Ronny, I’m bringing the Wolf!

Ulf