Call for Papers – OUCE 2016

Featured

The 2016 edition of the OpenNMS User Conference Europe (OUCE) will take place at University of Applied Science in Fulda.

Where do I find more information?

You find more detailed information on our conference page at https://ouce.opennms.eu

When?

Tuesday September, 13th 2016 until Thursday September, 15th 2016

Where?

Hochschule Fulda
Leipziger Straße 123
36037 Fulda, Germany

icon-car.pngKML-LogoFullscreen-LogoQR-code-logoGeoJSON-LogoGeoRSS-LogoWikitude-Logo
OUCE 2016 - Hochschule Fulda

loading map - please wait...

OUCE 2016 - Hochschule Fulda 50.565228, 9.685103

Tickets?

conference – Online Event Management with the ticketing solution from XING Events

Submit a Paper or Workshop

In order to submit your proposal, please go to the registration page, register with your email address and send us your proposal. The personal information are only used for the purpose of organizing the conference.

If you are curious about what others have already submitted, have a look at the preliminary schedule.

Your contribution matters

The conference is mainly driven by user contributtions who want to share their experience with open source monitoring solutions, especially OpenNMS. Your proposal can have any form you like, i.e.:

Regular talks
Share your experience in a user story and tell others about your way to solve a specific monitoring issue.
Workshops
Teach others about a technology, discuss a topic, ask for feedback or develop new ways to solve monitoring problems.
Community events
Bring some bottles of beer your favorite drink and help to bring the community together.

The focus of the conference covers the following topics:

Technology
Network management is hard. It has requirements to scalability and needs to integrate with a lot of other tools. If you’re building a business integration and you have extended OpenNMS, this is the track to show others what you have achieved and how OpenNMS works at its best.
Business
This track focuses on talks for people who want to share their experience using Open Source monitoring like OpenNMS in commercial environments. You can show how Open Source has effects on return of investment and total cost of ownership in your business or how you build your business in cooperation with Open Source monitoring solutions.
Projects
Everything has a start and nothing is perfect. The great thing in a community is to share knowledge and get input from others for real world use cases. If you’re building a cool solution with or around OpenNMS or with other tools and would like share it, this is the place to do so. You can inspire other people following your path and encourage developers to think about further improvements. You have the possibility to meet other people to improve your solution. Even if you have installed bleeding-edge stuff or you made some experiences in the wild network management world, please submit your talk or workshop here.

We are very flexible on the format of your submission but we recommend the following formats:

  • A regular talk should have a duration of about 45 minutes.
  • A lightning talk should not exceed 10 minutes.
  • Workshops should last for a maximum of 90 minutes. If you have special requirements, pleas let us know.
  • Other events can happen in workshop rooms or in the lounge. These events should be coordinated with the board upfront.

You have questions regarding the conference, please register at the OUCE mailing list, where you can get in contact with the organization team.

Recording

Talks will be recorded and made available on our website after the conference (unless you tell us that you’d prefer not to have them published). All recordings will be available without any special logins and will be found in our OpenNMS YouTube channel.

Who is attending?

The conferences will be attended by OpenNMS users, prospect users and open source interested folks from all over the world. You can meet OpenNMS developers as well as other experts of the network management domain.

The 2016 conference is limited to a maximum of 70 participants. The profile is ranging from system administrators to programmers to IT managers.

Call for paper proceeding

The call for paper is open until August, 1st 2016. The submitted talks will be evaluated by the conference board.

After the review period, ending August, 1st, you will get notified whether your proposal is accepted or not. Please take notice of our submission policies as well:

  • your speech will be contributed under the following license: CC BY-SA or another permissive creative commons licence
  • your speech will be harassment-free for everyone

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS Horizon 18.0.0

We welcome our new release of OpenNMS Horizon 18.0.0 with code name Tardigrade, named after a perhaps one of the most durable known organisms. This release introduces a few really cool new features.

Business Service Monitoring

To be able to get your monitored assets into Business Service related context the “Business Service Monitoring (BSM)” can be used. The goal of the Business Service Monitor is to provide a high-level correlation of business rules, and to display them in the topology map. In the BSM, you define a Business Service that encompasses a set of entities (nodes, interfaces, services, and other Business Services) and the relationships among them. The alarm states of the component entities are rolled up in a map-reduce fashion to drive a state machine. The state of a Business Service is reflected in a new type of event, and can also be visualized (along with the service hierarchy) in the existing OpenNMS topology map. A Business Service can create his own Alarms which can be used in workflows. The graph representation allows to analyze the root cause from the BSM to the technical service and the other way around – which Business Service is impacted by a specific technical service outage.

For details on using the BSM, see the User and Administrators Guide.

ElasticSearch 1.x Event Forwarder

We have added the possibility to forward OpenNMS Events and Alarms into ElasticSearch for analyzing and plotting with other tools like Kibana or Grafana. For more details see the Admin Guide. Big thank you to our community contributor Umberto Nicoletti started this thing.

OpenNMS Properties are modular

Now most properties set in the opennms.properties file can be instead overriden by creating a file in the ${OPENNMS_HOME}/etc/opennms.properties.d directory. It makes it maintenance friendlier and makes it easier to use configuration management tools like SaltStack, Ansible, Chef or Puppet.

Notification for Slack and Mattermost

With the new notification strategies it is now possible to send monitoring notifications to Slack and Mattermost.

OpenNMS Plugin Manager

An API for adding 3rd-party “plugins” to OpenNMS. The core of a tool for adding plugins into OpenNMS has been included in Horizon 18. This provides a set of tools for finding and adding plugins to be loaded into the OpenNMS OSGi container.

Requisition UI improvements

A huge number of improvements have gone into the requisition UI. Also, the old “Quick-Add Node” functionality has been reimplemented using the same backend as the requisition UI.

“Scan Report” Remote Poller GUI

A new front-end for the remote poller that lets you perform a single scan and get a pass/fail report in a GUI has been added. You can enable this alternate UI with the “-s” option on the remote poller CLI.

Topology UI Updates

As part of the BSM work, the topology UI has been vastly improved for both performance and usability.

TSRM Ticketing Plugin

We have added a new Ticketing Plugin for IBM Tivoli Service Request Manager (TSRM).
Information on configuring the TSRM ticketing plugin can be found in the Administrators Guide.

Collect anonymous usage statistics

To get a better idea of how to estimate hardware requirements and the performance characteristics of OpenNMS, we wrote a tool to occasionally submit anonymous diagnostic information about your OpenNMS install. It will submit information like the number of nodes, alarms, etc. as well as some basic system information to our servers for statistical reasons.

When a user with the Admin role logs into the system for the first time, they will be prompted as to whether or not they want to opt-in to publish these statistics. Statistics will only be published once an Administrator has opted-in.
These statistics are visualized on stats.opennms.org.

OpenNMS Data Source is Grafana 3 compliant

We have uploaded the OpenNMS Data Source to Grafana Plugin Platform which allows now easy setup and install with a simple sudo grafana-cli plugins install opennms-datasource.

Vagrant Boxes Refreshed

We have updated the Vagrant boxes which are uploaded to the Atlas Platform. They are updated with latest Horizon 18 and pre-configured Grafana 3 as a test, dev or play environment.

Beside that there are lot of bugs fixed and you can find all of it more detailed in our Release Note.

Happy Updating and Thank you to all contributors to make this great release happen.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

DevJam 2016 – Travel Bursary

Do you want to be a part of the great OpenNMS DevJam 2016? The best way 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 2016!

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 to learn, hack, code, talk and have fun around the OpenNMS project.

When?
Sunday, July 24, 2016 through Saturday, July 30, 2016

Where?
University of Minnesota – Mark G. Yudof Hall
220 Delaware St. SE
Minneapolis, MN 55455

More details?
http://www.opennms.org/wiki/Dev-Jam_2016

If you need to convince your manager? Mike Huot wrote a proposal which can help you to get there.

Deadline for the proposal is 31st May 2016.

The OpenNMS Group, Inc and the OpenNMS Foundation Europe e.V. support volunteers who have no financial or commercial background with a travel bursary for the conference. What you create should be under a free license and publicly available. If you want to apply for the DevJam 2016 Travel Bursary please fill the following form:

Fields marked with an * are required

Give a short title for your DevJam 2016 project?

Give us a description about how you would like spent the time in the week with OpenNMS contributors and developers. Do you want to start, learn or contribute? You can be creative in how you want to help in the OpenNMS project. Your results should be public available and should be under a free license.

Submit your proposal to the board members of the OpenNMS Foundation Europe e.V.

Hope see you soon at DevJam 2016 in Twin Cities

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 17.1.1

We welcome our new release of OpenNMS Horizon 17.1.1 with code name Glenmorangie, named after a whiskey distillery in Tain, Scotland. This is a bug fix release. The most noteworthy bug fixed is regarding ACL support which was broken and caused Web UI failures.

This release adds a little but useful enhancement. Instead of connecting to TCP 5817 and using send-event.pl it is now possible to send events to OpenNMS through ReST. Otherwise GitHub introduced Pull Request Templates a few weeks ago which have added to improve our pull request workflow. If you think it is more annoying then helpful, please don’t hesitate and give us feedback.

You can find all the details in our Release Notes and wish you happy updating.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – Ubuntu 14.04.4 LTS / CentOS 7.2.1511 and Horizon 17.1.0 Vagrant Box Update

We have updated our Vagrant box hosted on the Atlas platform with latest OpenNMS Horizon 17 pre-configured with RRDtool. This is also the first VirtualBox image which comes with a pre-installed Grafana 2.6 with the Grafana OpenNMS Plugin data source.

Ubuntu 14 LTS based image

vagrant init opennms/vagrant-opennms-ubuntu-stable
vagrant up --provider

CentOS 7.2 based image

vagrant init opennms/vagrant-opennms-centos-stable
vagrant up --provider

If you run the default Vagrant box it uses a NAT interface. To have access to the running application from your box just add the following lines in your Vagrantfile:

config.vm.network "forwarded_port", guest: 8980, host: 8980
config.vm.network "forwarded_port", guest: 3000, host: 3000

You want to build the box for a different provider than VirtualBox with packer just fork or contribute to the opennms-packer repository.

gl & hf

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – Ubuntu Vagrant Box Update

We have updated our Vagrant box hosted on the Atlas platform with latest OpenNMS Horizon 17 pre-configured with RRDtool. This is also the first VirtualBox image which comes with a pre-installed Grafana 2.5 and has the Grafana OpenNMS Plugin as data source installed and is ready to be used. All you have to do is run

vagrant init opennms/vagrant-opennms-ubuntu-stable
vagrant up

If you run the default Vagrant box it uses a NAT interface. To have access to the running application from your box just add the following lines in your Vagrantfile:

config.vm.network "forwarded_port", guest: 8980, host: 8980
config.vm.network "forwarded_port", guest: 3000, host: 3000

You want to build the box for a different provider than VirtualBox with packer just fork or contribute to the opennms-packer repository.

We have added a also a quick install script for Debian and Ubuntu.

gl & hf

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 17

We welcome our new release of OpenNMS Horizon 17 with code name Glen Moray.

Like a good single malt Scotch whiskey it took some time to get the release out – but we think waiting was worth it. The most obvious change is the a more slimmed down web app layout.

home-modified

We have added a new visual component to show alarms and outages in a heat map which can be used as an additional component on the start page or as a full screen view.

Screen Shot 2015-12-02 at 23.22.48

The JMX data collection configuration tool is reworked and improved. It allows to interactively create your data collection configuration for your Java applications with JMX.

Screen Shot 2015-12-02 at 23.26.03

The documentation is improved and we have removed unnecessary modules and focus on Release Notes, Installation Guide, User Guide, Administration Guide and Developer Guide.
We moved the content how to develop new documentation from the Documentation Guide to a Developers Guide section.

The distributed components with OpenNMS Minion is introduced in the admin area.

Important to notice Linkd with the SVG map is removed. Enhanced Linkd with Topology view is now the new default.

Otherwise real SSO via Kerberos (SPNEGO) and LDAP is enabled we integrate now with OTRS-3.1+ Ticket system.

We added a JMS Alarm Northbounder to make it easier to integrate OpenNMS in larger management application stacks.

A lot of improvements to the Grafana support was made. We support now the version 2.5.0 of Grafana. The OpenNMS Grafana Data Source allows filtering and trending performance data and the Newts integration is improved.

We have added support for following devices:

  • Added trap support for Infoblox devices
  • Adding SNMP traps for Raytheon NXU-2A
  • Add A10 AX load balancer trap events
  • Add Force10 Traps
  • Event definition for Juniper screening SNMP traps
  • Event definiton file for DSVIEW-TRAP-MIB
  • Trap definition files for Evertz Multiframe and Modules
  • Trap and data collection definitions for Ceragon FibeAir 1500
  • New (additional) event file for NetApp filer
  • New Fortinet datacollection / graph definition
  • Event and data collection support for Didactum Sensors
  • Add Juniper SRX flow performance monitoring and default thresholds
  • Dell Equallogic Events
  • Add Sonicwall Firewall Events

For more details you can go to our Release Notes.

Looking forward to upgrade my systems and Happy Upgrading

gl & hf

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Security] – Java RMI exploitation

We got noticed from one of mailing list readers about a security issue. This article explains this issue in all details.

The research shows that it is possible to execute code on the OpenNMS server remotely due to a bug in the Apache commons library, which OpenNMS uses. There are two types of issues, one is remotely exploitable code and the other is local privilege escalation. Firewalling TCP port 1099 changes the attack vector into a local privilege escalation. The issue with local privilege escalation has still to be investigated. Make sure you allow only IPv4 localhost and IPv6 ::1 to access TCP port 1099.

For security issues we have a contact address which you can find in the Contact Us section on http://www.opennms.org.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr