Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

VMWare TopologyProvider displays the graph but selections doesn't work

Description

I've been playing with the SimpleTopologyProvider just because there are certain kind of situations on which there is no way to discover the topology through Linkd, because the network elements could not support SNMP or doesn't provide enough information to Linkd.

On those situations, you must manually provide the topology in some way.

So, I've made a XML based on org.opennms.features.topology.api.topo.WrappedGraph (using "nodes
as its namespace attribute), with the following content and place it on /opt/opennms/etc/simple-graph.xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <graph namespace="nodes"> <vertex> <iconKey>router</iconKey> <id>HQ</id> <label>HQ</label> <nodeID>44</nodeID> <ipAddr>192.168.32.99</ipAddr> <locked>false</locked> <selected>false</selected> </vertex> <vertex> <iconKey>router</iconKey> <id>Maracaibo</id> <label>Maracaibo</label> <nodeID>43</nodeID> <ipAddr>11.0.0.2</ipAddr> <locked>false</locked> <selected>false</selected> </vertex> <vertex> <iconKey>router</iconKey> <id>Valencia</id> <label>Valencia</label> <nodeID>42</nodeID> <ipAddr>12.0.0.2</ipAddr> <locked>false</locked> <selected>false</selected> </vertex> <vertex> <iconKey>router</iconKey> <id>Merida</id> <label>Merida</label> <nodeID>41</nodeID> <ipAddr>13.0.0.2</ipAddr> <locked>false</locked> <selected>false</selected> </vertex> <edge> <id>e0</id> <source>HQ</source> <target>Maracaibo</target> </edge> <edge> <id>e1</id> <source>HQ</source> <target>Valencia</target> </edge> <edge> <id>e2</id> <source>HQ</source> <target>Merida</target> </edge> <edge> <id>e4</id> <source>Valencia</source> <target>Maracaibo</target> </edge> </graph>

Then I've created the following Karaf Script in order to "enable" the SimpleTopologyProvider, and load it into Karaf:

config:edit org.opennms.features.topology.plugins.topo.simple-simple config:propset label 'My Graph' config:propset topologyLocation file:///opt/opennms/etc/simple-graph.xml config:update

On the Topology WebUI, I can see the graph exactly as I specified on the XML, but if you click on a vertex (icon on the graph), only the left panel is updated. If you click on any node displayed on the left panel, the topology graph is updated as well.

But, the tables at the bottom are not being updated. Also clicking on any link on those tables are not working either.

That doesn't happen for a topology managed by Linkd. It works fine with Linkd, I mean, click on the node on the topology automatically filter the alarms table, and the nodes table. If you do the inverse, I mean, click on any element on the alarms table or nodes table, the graph is updated.

But, as I said before, that doesn't work that way with the SimpleTopologyProvider.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Markus von Rüden July 28, 2016 at 4:23 PM

The VmwareTopologyProvider was improved with https://opennms.atlassian.net/browse/NMS-8140#icft=NMS-8140 and the SimpleTopologyProvider does not exist anmory.
I am going to close this issue as the Topology API changed dramatically.
If you feel that this issue still needs to be addressed, please reopen.

Markus von Rüden July 11, 2016 at 12:50 PM

With the latest changes in the features/atlas branch the SimpleTopologyProvider is replaced by the GraphMLTopologyProvider.
Renaming to state the fact that the "VmwareTopologyProvider" still does not support selctions.

Alejandro Galue February 16, 2016 at 10:36 AM

That's good news!

I'll love to have time to improve the Simple and VMWare topology providers.

Markus von Rüden February 16, 2016 at 10:16 AM
Edited

In the features/bsm branch I added the functionality to define which provider is capable of supporting which browsers tab (nodes, alarms, etc.).
The SimpleGraphProvider and VmwareTopologyProvider just have to implement the interface SelectionAware accordingly.
This should make things much easier.

Alejandro Galue October 6, 2014 at 4:12 PM

Based on the restrictions imposed on the way we should build the XML for the SimpleTopologyProvider in order to make it work with the Alarm/Node tables and the Status/Search Providers, I can confirm that the issue still persist on the VMWare Topology provider; i.e., it is displayed but that is the only thing you're going to have (no alarm provider or reaction when clicking on the nodes or the tables).

For the VMWare Topology, this problem is one reason for disabling the VMWare assets while discovering the VMs and Hosts through the VMWareImporter: https://opennms.atlassian.net/browse/NMS-6914#icft=NMS-6914

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

Parent

PagerDuty

Created December 11, 2013 at 9:57 AM
Updated February 14, 2018 at 7:30 PM
Resolved July 28, 2016 at 4:23 PM

Flag notifications