Skip to:

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

Be able to disable the generation of the VMWare Topology assets

Description

On big installations with complex VMWare deployments, it takes too much time generating the requisition, and I found that the culprit for this was doing the recursive analysis to generate the VMWare Topology asset field (used to draw the VMWare Topology).

It would be very useful to be able to disable this functionality in order to accelerate the generation of the requisition.

Acceptance / Success Criteria

None

Attachments

1
  • 25 Sep 2014, 03:06 PM

Lucidchart Diagrams

Activity

Alejandro Galue October 6, 2014 at 4:14 PM

BTW, another reason for removing or disabling the VWWare Topology Assets is https://opennms.atlassian.net/browse/NMS-6299#icft=NMS-6299. The cool Topology Maps only work for Linkd, EnhancedLinkd or the SimpleTopologyProvider (only if the XML is generated on a very specific way).

Alejandro Galue September 26, 2014 at 2:14 PM

Yes, those options controls what to considering when building the topology asset. By default all of them will be included but on big and complex deployment that is far for being useful. So, you can use one of those 3 options to ignore a special kind of sources (specially the third one) to reduce the complexity of the generated topology asset.

But, in some occasions, the resulting topology is so messy that it is not useful at all, and the purpose of this issue is to provide an option to skip the generation of the topology asset (i.e. do not invest time and resources building something that probably no one is going to use, specially considering that the most expensive operation while generating the requisition is the recursive processing of all the elements on vCenter to build this topology asset for each host or vm).

Ronny Trommer September 26, 2014 at 2:09 PM

We have three options to disable VMware topology import:

topologyNetworks - Add the network information to the VMWare Topology Default: true topologyDatastores - Add the datastores information to the VMWare Topology Default: true topologyPortGroups - Add the port groups information (distributed virtual switches) to the VMWare Topology Default: false

Is this not necessary or do these options have other side effects during the import?

Alejandro Galue September 25, 2014 at 3:06 PM

The proposed patch is attached and it has been designed for 1.14.

I'm going to provide more details after having my VMWare Testing environment up and running.

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Parent

PagerDuty

Created September 25, 2014 at 3:05 PM
Updated September 21, 2021 at 9:15 PM

Flag notifications