Skip to:

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

OpenNMS system needs a unique identifier for TSaaS Communication

Description

Part of the authorization process in getting OpenNMS → Cloud Plugin → TSaaS to write data is that every OpenNMS instance writing data must be uniquely identified.

Acceptance / Success Criteria

Acceptance:

  1. Every OpenNMS instance that is connecting to TSaaS can be uniquely identified in some manner

Out of Scope:

  • The identification of other systems that might exist in a deployment (i.e. minions or sentinels).  At some point we'll need to consider an "Environment ID", but that is out of scope for this particular issue.

related to

Lucidchart Diagrams

Activity

Show:

Patrick Schweizer October 5, 2022 at 6:01 PM

I am closing this ticket:

We are dealing here with 2 related but separate issues:
1.) plugin can get the systemid via OIA from OpenNMS
2.) OpenNMS provides a unique UUID for new installs

1.) is done by https://github.com/OpenNMS/opennms-cloud-plugin/pull/29 . A user can now manually change the systemid in the database
2.) is not done. Follow up ticket:

Patrick Schweizer August 26, 2022 at 7:52 AM

PRs:

Accepted

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Fix versions

Priority

Parent

PagerDuty

Created August 25, 2022 at 3:19 PM
Updated October 25, 2022 at 5:36 PM
Resolved October 5, 2022 at 6:02 PM