in OpenNMS • Control workflow with filter • Longterm performance data collection • Service assurance for VMs and ESX health status • Visualize VMware topology Introduction
by the vCenter • Detection of the management interface for Host-System • VMware related information, e.g. VMware topology, is stored in asset fields Introduction
Underlying OS for vCenter • Authentication methods • ESX Host operating system versions • API calls which require additional communication for authentication • Side effects from non-perfect functional ADS setups Why is it hard?
the 3rd party libraries ViJava and Sblime • Algorithms for the import • Algorithms for performance data collection • Workflows to model the synchronization behavior Why is it hard?
flexibility manipulating the requisition before import with Groovy scripts • Free provisiond from 3rd party dependencies • Simplify code for JUnit test environment around Provisioned • Allow faster iteration for fixing import issues Move from integrated URL requisition in Provisiond to to “Inventory Integration Service” Roadmap
- External dependencies in OpenNMS! - Changes require a full release cycle of the whole OpenNMS project! - Hard to write JUnit tests, mocking vCenter with versions is quite impossible
Alarmd VMware vCenter - Standardized API! - Provides public integration interface via ReST and XML data model! - Hardening and Unit-Testing is easier - ReST API calls! - XML requisition data model
Alarmd VMware vCenter - Standardized API! - Provides public integration interface via ReST and XML data model! - Hardening and Unit-Testing is easier - Changes don’t affect core project —> faster iteration! - Less complex code surrounded easier to test! - Fast development cycle - ReST API calls! - XML requisition data model Poor mans adaption of ETL Extract, Transform, Load