What’s New in OpenNMS 1.12

Jeffrey Gehlbach

October 24, 2013

1 / 53

Agenda (1/2)

I Who is this guy?

I What is OpenNMS?

I Overview of functional areas

2 / 53

Agenda (2/2)

I Configuration helpers

I End-user helpers

I Infrastructure

I Integration

I Performance improvements

I Device coverage improvements

I Linkd improvements

I Shiny!

I Architectural

3 / 53

Who is this guy?Introducing the speaker

4 / 53

A pretty lucky humanTen fingers, ten toes, some industry experience

I NASA → Management of large IP networks

I Empire / Concord → Making and consulting on NMS

I BellSouth → Cranium formed into Bell shape

I OpenNMS Group → Met many smart and beautiful people

5 / 53

What is OpenNMSGlad you asked

I World’s First

I Enterprise-Grade

I Network Management Platform

I Developed Under the Open Source Model

6 / 53

What is OpenNMSWorld’s First

I SourceForge project number 4141

I Registered on SF March 2000

I Development started earlier

7 / 53

What is OpenNMSEnterprise-Grade

I Scalability baked into design

I Original goal: 10K node coverage

I Inspiration from OpenView NNM, Tivoli, Netcool...

I Extensible, event-driven architecture

8 / 53

What is OpenNMSNetwork Management Platform

I A platform, not an application

I Every aspect is customizable

I XML configuration

I Many APIs

9 / 53

What is OpenNMSDeveloped Under the Open Source Model

I Entire code base is GPLv3 (was GPLv2)

I The “enterprise” version is the only version

I All work done in the public SCM system

I All sponsored work goes upstream

10 / 53

Functional Areas of OpenNMS“Five halves of OpenNMS”

I Provisioning

I Service Assurance

I Performance Management

I Event Management

I Reporting, Presentation

11 / 53

Functional Areas of OpenNMSProvisioning

I Populating the model

I Nodes

I Interfaces

I Services

12 / 53

Functional Areas of OpenNMSService Assurance

I aka Polling

I “Is it up or not?”

I Wide range of services supported

I Response times may be persisted

I Outages create events, alarms

13 / 53

Functional Areas of OpenNMSPerformance Management

I Collect, store, analyze

I “How’s it running?”

I SNMP, JMX, JDBC, WMI, others...

I Resource graphs, thresholds, reports

I Thresholds create events, alarms

14 / 53

Functional Areas of OpenNMSEvent Management

I Events are currency

I Sources: Internal, SNMP traps, syslog

I Events vs. Alarms

I Notifications

I Helpdesk integrations

15 / 53

Functional Areas of OpenNMSReporting, Presentation

I Webapp central component

I Ad-hoc resource graphs

I Event, alarm browsers

I JasperReports integration

I Maps

I ReST API

16 / 53

What’s NewConfiguration Helpers

I JMX configurator

I SNMP MIB compiler

I SNMP DC configurator

I Split graphs configuration

17 / 53

What’s New: Configuration HelpersJMX Configurator

I Ein Saugblaser für JMX

I Input: host, port, credentials

I Outputs: data collection and graph definitions

I Automatic DS-name compression

I Enormous time savings realized

18 / 53

What’s New: Configuration HelpersSNMP MIB “Compiler”

I Upload MIB definitions

I Creates event and data collection definitions

I Entirely GUI work flow in webapp (Vaadin)

I Customize outputs in GUI

I No more need to edit XML files

19 / 53

What’s New: Configuration HelpersSNMP Data Collection Configurator

20 / 53

What’s New: Configuration HelpersSplit Graphs Configuration

I New etc/snmp-graph.properties.d directory

I Making graphs still sucks

I Maintaining changes now sucks less

I Mirrors data collection config split of OpenNMS 1.10

21 / 53

What’s NewEnd-User Helpers

I Nodes with pending problems

I New topographical map

I Geographical map

22 / 53

What’s New: End-User HelpersNodes with Pending Problems

I Replaces old “Nodes with Outages” box

I Reflects shift toward alarm-based work flow

I Old-schoolers can change back

23 / 53

What’s New: End-User HelpersNew Topographical Map

I Not the OpenNMS topo map of yesterday

I Requirement: “must be sexy” (Vaadin)

I Renders topologies from Linkd, but others too

I Pluggable layout algorithms

I Semantic zooming and scoping

I Integrated node, alarm browser widgets

I Apparently not completely bug-free...

24 / 53

What’s New: End-User Helpers“Bug” in new topographical map

25 / 53

What’s New: End-User HelpersGeographical Map

I Finally, a geo node-map (Vaadin, Leaflet)

I Automatically geocodes addresses in asset records

I Choose Google or OSM for map, geocoder provider

I Zoom-level-aware node grouping

I Alarm severity indication

26 / 53

What’s New: End-User HelpersGeographical Map Eye-Candy

27 / 53

What’s NewInfrastructure

I Access Point Monitor

I VMware Integration

28 / 53

What’s New: InfrastructureAccess Point Monitor

I Intelligently monitors WiFi APs

I Vendors: Aruba, Motorola, others?

I Talks SNMP to controllers, not directly to APs

I APs still appear as regular nodes

I Community contribution!

29 / 53

What’s New: InfrastructureVMware Integration

I Uses vSphere native SOAP and CIM APIs

I Provisioning: Just point at vSphere server

I Topology: Gathered automatically

I Polling: Health indicators on hosts, VMs

I Data Collection: So much stuff!

I Community contribution!

30 / 53

What’s New: Infrastructure: VMwareProvisioning Conceptual Diagram

31 / 53

What’s New: Infrastructure: VMwareVMware Service Assurance

32 / 53

What’s New: Infrastructure: VMwareFurther Reading

I Academic paper (Deutsch)

33 / 53

What’s NewIntegration

I Syslog northbounder

I Jira ticketer (updated)

I Drools in ticketing (new)

I Remedy ticketer (new)

34 / 53

What’s New: IntegrationSyslog Northbounder

I First of many planned “Northbounders”

I Alarm-centric, rather than event-tied

I Multiple configurable destinations

I UDP, TCP transports supported

I JMS, HTTP northbounders partially done

35 / 53

What’s New: IntegrationUpdated Jira Ticketer

I Now uses Jira 5.x+ ReST API

I No more need to make stubs from WSDL

I Now approximately 5000% easier to set up

36 / 53

What’s New: IntegrationDrools in Ticketing

I Brings Drools to OpenNMS’ Ticketd

I Codify business processes

I Assign tickets to users

37 / 53

What’s New: IntegrationNew Remedy Ticketer

I Uses Remedy ARS SOAP API

I Create requests from alarms

I Automatic or manual operation

38 / 53

What’s NewPerformance Improvements

I Provisioning performance

I Event handling

39 / 53

What’s New: Performance ImprovementsProvisioning

I Unncessary disk I/O eliminated

I Big improvement with huge requisitions

I May break some “clever” provisioning scripts

I Use the provisioning ReST service instead!

40 / 53

What’s New: Performance ImprovementsEvent Handling

I Event queue length now boundable

I Still unbounded by default

I Most won’t notice

I If your use case is event-heavy, see me

41 / 53

What’s NewDevice Coverage Expanded (1/2)

I ACME Packet

I Allot

I BladeNetwork

I Cisco TelePresence

I Ericsson Juniper Networks GGSN

I Ericsson IPWorks

42 / 53

What’s NewDevice Coverage Expanded (2/2)

I Isilon (EMC)

I Pingtel

I VMware CIM

I VMware VirtualCenter 2.5

I VMware vCenter 4.1 and 5.0

43 / 53

What’s NewLinkd Improvements

I New: Link data exposed via ReST service

I New: OSPF discovery

I New: LLDP discovery

I Many fixes to corner cases

I Battle-proven: Juniper, T-Systems

44 / 53

What’s NewShiny!

I Near Real Time Graphing

45 / 53

What’s New: Shiny!Near Real Time Graphing

I Take any SNMP-derived graph to redline

I Configurable interval down to 250ms

I SNMP operations are server side

I Data plotted in browser via D3.js

I GSoC 2012 project!

46 / 53

What’s New: Shiny!Near Real Time Graphing

47 / 53

What’s NewBoring Architectural Stuff

I Java >= 6 required

I OSGi / Karaf

I Spring Framework 3.0

I Spring Security 3.1

48 / 53

What’s New: ArchitecturalJava >= 6 Required

I Java 6 EOL actually past...

I Oracle and OpenJDK builds work

I Oracle 7 JDK recommended (I know...)

I OpenJDK 8 shows great promise

49 / 53

What’s New: ArchitecturalOSGi / Karaf

I New technology in our stack

I Solves many long-standing problems

I Enables much greater modularity

I Just some bits run in Karaf in 1.12

I Next major release will be 100% OSGi

50 / 53

What’s New: ArchitecturalSpring Framework 3.0

I Dependency injection framework

I Long-standing part of our stack

I OpenNMS 1.10 used Spring 2.5

I You won’t notice the change

51 / 53

What’s New: ArchitecturalSpring Security 3.1

I AAA toolkit and framework

I Long-standing part of our stack

I OpenNMS 1.10 used Spring Security 2.0

I You won’t notice the change

I Unless you use LDAP, AD, RADIUS for AAA (see me)

52 / 53

Conclusion, QuestionsThanks for your time!

@opennms / @jeffgdotorg

#opennms / jeffg

53 / 53