Skip to:

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

Populate Velocloud Partner Requisition with Gateway Nodes

Description

  • model Velocloud Gateway entities as OpenNMS Nodes

  • model Velocloud Gateway IP addresses as OpenNMS IP Interfaces

  • model Velocloud Gateway binary statuses as OpenNMS Services (do not implement the monitor itself - see https://opennms.atlassian.net/browse/NMS-14594#icft=NMS-14594)

  • model Velocloud Gateway Roles as OpenNMS meta-data

  • model Velocloud Gateway node metadata and assets

capture all 3 identifiers for each Velocloud Gateway as OpenNMS Node meta-data

Lucidchart Diagrams

Activity

Alberto September 29, 2022 at 1:29 PM

merged to main

Jeff Gehlbach September 9, 2022 at 3:11 PM

Sorry I'm just now seeing this . Let's discuss after DevJam.

Alberto September 2, 2022 at 12:11 PM
Edited

Hi  I'm not sure what would be a gateway role since there is no role association in the gateway info.

There are a few endpoints that associate roles to users but I wouldn't know which one is the right type. 

I can probably can get users associated to an enterprise (the partner enterprise) and then get their roles and asscoiate this to  the gateway but not sure if this is the right way. What do you think?

Found the role field in the gateways response.

Still I'd like to know what should be considered an asset in a Node.

 

 

Done

Details

Assignee

Reporter

Story Points

Sprint

Priority

Parent

PagerDuty

Created August 2, 2022 at 1:34 PM
Updated January 25, 2023 at 9:33 PM
Resolved September 29, 2022 at 1:29 PM