Date post: | 16-Apr-2017 |
Category: |
Technology |
Upload: | manageiq |
View: | 267 times |
Download: | 4 times |
© 2016 The OpenNMS Group, Inc.
ManageIQ Design Summit 2016
JEFF GEHLBACH
THE OPENNMS GROUP, INC
OpenNMS as Complement to ManageIQ
07 Jun 2016
© 2016 The OpenNMS Group, Inc.
YOUR SPEAKER
●C-64: 1982●Linux: 1994●IP networking: 1999●Network Management: 2000●OpenNMS: 2005●ManageIQ: 2016
© 2016 The OpenNMS Group, Inc.
NETWORK(ED) MANAGEMENT
●Network Management–Not just about network plumbing–“Network” == “everything on the other side of my keyboard”
© 2016 The OpenNMS Group, Inc.
NMS CAPABILITIES: FCAPS MODEL
●Fault●Configuration●Accounting●Performance●Security
© 2016 The OpenNMS Group, Inc.
NETWORK MANAGEMENT HISTORY
●Early proprietary platforms●Later proprietary offerings
●Early open-source tools●Later open-source & open-core offerings
●OpenNMS is unique
© 2016 The OpenNMS Group, Inc.
OPENNMS IS…
“The world’s first enterprise-grade, open-source network management platform”-Tarus Balog
(Open Source Monitoring Conference 2014; every opportunity before & since)
https://youtu.be/iwGwW3RX4y0
© 2016 The OpenNMS Group, Inc.
MANAGEIQ IS…
“The first enterprise-grade open cloud management platform”-Joe Fitzgerald
(OpenStack Summit 2014)
https://youtu.be/tT9RyViXYhI
© 2016 The OpenNMS Group, Inc.
THE COMMUNITY
●Core committers–The OpenNMS Group, Inc. (<20)–Order of the Green Polo (29)
●OpenNMS Foundation Europe e.V.●Two annual conferences–Dev-Jam (US / MN / TOG)–OUCE (EU / DE / OFE)
© 2016 The OpenNMS Group, Inc.
GOALS OF OPENNMS
●To be the de facto platform for network management.
●Two Promises
●Horizon & Meridian
© 2016 The OpenNMS Group, Inc.
OPENNMS VS. FCAPS
●Fault●Configuration●Accounting●Performance●Security
© 2016 The OpenNMS Group, Inc.
MANAGEIQ VS. FCAPS
●Fault [Compute only]●Configuration [MIQ core; Ansible]●Accounting [MIQ core via Providers]●Performance [Compute only]●Security [MIQ core via Policies]
© 2016 The OpenNMS Group, Inc.
HYPOTHESIS: BETTER TOGETHER
Fault Management Y -Configuration Management - YAccounting Management - YPerformance Management Y ~Security Management - YWorld’s First 2001 2014 (2006)Enterprise Grade Y YOpen Source AGPLv3 APLv2
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning : getting nodes, interfaces, services into and out of the system. Flexible, API-driven life-cycle management; push and pull modes of operation
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning●Fault Management : multi-protocol service-assurance polling
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning●Fault Management●Performance Management : multi-protocol metric data collection; in-line thresholding; reporting via measurements ReST service
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning●Fault Management●Performance Management●Event Management : event-driven platform; intake from without; de-duplication; correlation with JBoss Drools Expert; notifications with reusable destination paths and escalations
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning●Fault Management●Performance Management●Event Management●Topology : Pluggable providers. Link discovery via SNMP for LLDP, CDP, OSPF, IS-IS.
© 2016 The OpenNMS Group, Inc.
OPENNMS FUNCTIONAL AREAS
●Provisioning●Fault Management●Performance Management●Event Management●Topology Discovery●Web UI and ReST API : Overhauled in 2015; Bootstrap, AngularJS, CXF
© 2016 The OpenNMS Group, Inc.
OPENNMS ARCHITECTURE
Web
PersistenceRRDTool Cassandra PostgreSQL
App
JVM (1.8)
Spring Framework Karaf
Spring MVC - JEE Servlets
Bootstrap JSP ReST
AngularJS
Vaadin
Architecture
Serv
ice R
eg
istr
y -
Serv
let
Bri
dg
e
Eventd
ActiveMQ
Camel
OpenNMS Minion
Service Daemons
Hibernate
© 2016 The OpenNMS Group, Inc.
HISTORICAL ARCHITECTURE
●Sample data stored in RRD files●Operations fairly centralized●Platform running in monolithic JVM(s)●Not really cloud- or controller-aware
© 2016 The OpenNMS Group, Inc.
ARCHITECTURAL DIRECTION
●NewTS*† (Cassandra metric storage)●Minion* (Fully distributed operation)
●OSGi via Karaf (Modularize all the things!)●Kafka†, Spark Streaming (Get on the bus)●Increasingly abstract notion of controllers
†Here today *Developed in house
© 2016 The OpenNMS Group, Inc.
MIQ INTEGRATION: PROVISIONING
●MIQ lifecycle → ONMS inventory–Automate MIQ to drive OpenNMS ReST API–VMs / Instances → OpenNMS Nodes
●Fault & Performance coverage–Possible today – I even tried making it
© 2016 The OpenNMS Group, Inc.
Foreign Source: ec2-us-east-1
Foreign Source: openstack-atl-a
Foreign ID: i-8fe2ca73 Foreign ID: i-17fcdd08
Foreign ID:5437b7e0-1a8b-49d4-8e28-265812c9042b
Foreign ID:355edebb-447b-4cdc-9fcc-c72b0a4946d8
PROVISIONING INTEGRATION CONCEPT
●One foreign-source (requisition) per EMS instance
●One foreign-ID per instance●PUT / DELETE to OpenNMS Requisitions ReST service on instance create / destroy
●Very common pattern!
© 2016 The OpenNMS Group, Inc.
BUT THEN I WAS LIKE...
●Did I do this right??●Should work, given a bit more fiddling :)
●Needs refining–Sync MIQ Tags → OpenNMS Categories
–Auto-provision services according to MIQ Tags
© 2016 The OpenNMS Group, Inc.
BEYOND PROVISIONING
●New cross-cutting concern for ManageIQ●FPMProvider●Adjust billing if SLAs not met
●Many touch points●Reporting●Planning●Alerting
© 2016 The OpenNMS Group, Inc.
SDN CAPABILITIES IN PROGRESS
●SDN Underlay / Overlay–OpenDaylight Topology provider
●Project Atlas (layers)–OpenDaylight Boron can use NewTS in place of TSDR
–Partners wanted