With the help of the faculty computer science we are happy to present our new venue for the OpenNMS Users Conference Europe 2015 from 28th September until 01. October. The conference is organized by the OpenNMS Foundation Europe e.V. and takes place at the University of Applied Science in Fulda.
We have prepared some workshop material for the Buero 2.0 OpenNMS Kickstart workshop in Berlin. You can browse through the slides here. Feel free to fork and edit. The graphuml files can be modified with a not-fully-free but free enough platform independent editor yED.
I’ve spend the weekend at CLT 2015 in Chemnitz. It seems this conference became THE™ Linux conference in Germany. The program was quite impressive, 6 parallel tracks filled for two days. It was the first time I had a talk in the publishing track. I decided to give a talk about our documentation project. The idea was to get some feedback and proof our decisions by talking about the ideas, motivations behind rebuilding the OpenNMS documentation. I was surprised about the audience, the room was full. Because there are no recording of the talk here is a short summary and provde some context for the slides you can download from my GitHub repo. I got in contact with a very nice guy who spend time in documentation for the Django project. Browsing through there docs, they really understood, documentation is one of the key components to make an open source project successful. He gave me some valuable hints and pointed me to the Write the Docs conference in Portland and Prag. Maybe one of the readers in the community is interested as well, so maybe we spend some time together. He pointed me also to some interesting information how to deal with multi-language documentation. They use Sphinx but what I’ve seen the concepts work in the same way for AsciiDoc.
First of all I gave a short reminder, source code is not documentation. Many people in Open Source think, publishing the source code prevents them to write documentation – this is wrong. Source code doesn’t tell you anything about motivations, concepts and ideas why you exactly solved the problem this way. Source code is the what and not the why. In real world it is obvious, I can’t pass a bridge build for pedestrians with a car – in software it isn’t – you experience it always if it’s too late. The main idea is to think about why should you write documentation? You want to enable your users to use your software in the most efficient and right way. Documentation has to build a shared understanding between the people writing software and the ones who wants to use it. For Open Source projects documentation is a key value and has a big impact about how many people use it.
There will be ALWAYS™ something to code and so it is for docs. You’ll never finish.
For this reason it make sense to set back and spend some time about thinking, to weave documentation into the development process to increase the quality of documentation. We tried also to find patterns to identify parts to create templates and tried to reuse information and make documentation more efficient. If you develop in an agile environment think about a good written user story is already 50% of documentation when it’s implemented.
We spend last year at DevJam to evaluate some tools. We have found an old DocBook based maven module. Editing DocBook is a pain in the ass, you need a quite expensive tool chain and the barrier is quite high. With AsciiDoc we found the most promising tool chain. Easy as Markdown and very feature rich. The support to get integrated in our Java based Maven build and CI environment works well and we have support in GitHub rendering and viewing the docs just in source.
In hope we can move forward to get our docs improved, it’s not perfect yet but the direction we move seems quite good.
Zusammen mit dem Büro 2.0 in Berlin geben wir einen kostenfreien Workshop mit OpenNMS. Wer interessiert ist kann sich auf der Meetup Plattform eintragen. Die Teilnahmevoraussetzungen und Details sind ebenfalls auf der Anmeldeseite im Meetup Event beschrieben.
The OpenNMS has a Dashboard feature which drives monitoring information through a surveillance view. The surveillance view is a customizable matrix build out of grouped Nodes and shows the status. The matrix view can become quite compact and is used as a driver for getting to monitoring information more quickly. The feature development progress is in JIRA in NMS-7298 and has a feature branch in GitHub with the name jira/NMS-7298.
The feature was originally implemented in GWT. The project started to introduce some new features like the “Ops Board” and the Ops Panel which are also build with Vaadin components. The focus on this project was to cleanup and modernize the code underneath and enable easier iteration on the use case “How we want to have such kind of a dashboard”. The feature is extended with modal popup windows to show alarm, notification and node details without leaving the dashboard. The RRD graphs use the same feature as in Horizon 15 and dynamically resized to the browser width of the Dashboard. It is also now possible to switch between different surveillance views for the Dashboard.
For the reason the Dashboard is mainly driven by the “Surveillance View” there is a configuration panel added, which allows to create and modify the surveillance view from the WebUI. The schema of the surveillance-view.xml file is not changed and be used and modified just in the Web UI. The attribute for refresh time in seconds was not used and is now used in the Dashboard and the single Surveillance View. It is now possible to configure different refresh intervals per Surveillance View. The order of columns and rows for the categories can be ordered. The Surveillance View selected as default is the one which is showed first getting to the Dashboard or Surveillance View page.
Manage Surveillance Views
Configure Surveillance View
To allow users or groups a different entry point to the Dashboard, it is possible to map a user or group to a Surveillance View by giving the same name. Instead the default selected Surveillance View the group one is selected. The User name based Surveillance View overwrites the group based Surveillance View.
This feature is marked to be in the coming Horizon 16 release of OpenNMS.
We are happy to announce OpenNMS 15.0.1 codename silpheed. It is strongly recommended to update. The project is in transition to migrate to Hibernate. We had found an issue where it is possible to have uncleared outages. The outage timeline didn’t showed all outages and is enhanced now to resize automatically (NMS-7438).
You can find the full list of issues and enhancements in the Release notes.
We are happy to inform you about a new release of OpenNMS 15 with codename (Sundog) is ready to install. There have been 1177 new commits since 14.0.3
You’ll also notice that this version of OpenNMS has a new name – Horizon. We’ve always thought that OpenNMS represents the best network management platform available and the name is meant to reflect that. The main improvement for the 15 release is in the WebUI. The layout for the JSP pages is moved to bootstrap. It allows a more responsive WebUI in mobile phones, tables and phablets and should also make it easier to create themes for the Web-UI. The second really cool feature is the new “Resource graph” UI. The RRD PNG graph export is now rendered to the size of the browser window.
Scalable resource graph
There are a number of bug fixes and other new features in OpenNMS. If you have an JIRA account a complete list can be found in our Jira instance. The full release note is published also in the OpenNMS wiki in New and noteworthy.
Thanks to Markus Neumann who cut and published all the OUCE videos for the OUCE 2014. You can find videos and slides in the schedule of the OUCE 2013 and OUCE 2014 conferences. Each event has a link section with the slides and a link to the YouTube video. For new videos or tutorials you can subscribe the OpenNMS YouTube channel.
Do you want to be a part of the great OpenNMS DevJam 2015? The best ways for someone to learn to develop and contribute to OpenNMS is to attend DevJam. If you want to improve your abilities and meet other OpenNMS developers from all over the world, then you need to be at OpenNMS DevJam 2015!
The OpenNMS DevJam is THE event of the year for contributors and developers of the OpenNMS Project. Contributors and developers of OpenNMS from all over the world meet at the University of Minnesota. The event is all about learn, hacking, coding, talk and fun around the OpenNMS project.