Versions Compared

Old Version 35

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version 36

changes.mady.by.user Toine Siebelink

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


IssueNotes Decision
1Is FDN optional?Is it possible to register a cmHandle without an FDN?

Toine Siebelink Yes it is optional as not everyone will use it

2In Hazelcast what is the key?Is it the FDN or the cmHandleId?

Toine Siebelink create 2 maps:

  1. alternate id → cm-handle-id
  2. cm-handle-id → alternate id
3Check alternateId in 'updatedCmHandles'Assuming updatedCHandle should NOT be used to correct/change the AlternateId for a CmHandleId

Alternate IDs are immutable once they are set.
However if a previously created CM Handle's alternate ID is not defined then an update should be possible.
The only way to change this value is to delete the current CM Handle and then re-register it.

4Should we persist the alternateId?Should we modify the registry model?

Toine Siebelink Yes, the Inventory Model should update with the AlternatId as detailed below

5Alternative ID is NOT unique!multiple ENMS NMs might ne be using same subnetwork names i the FDNs and thus as NCMP manage multiples ENMS NM's NCMP can encounter duplicates.

kieran mccarthy explained. Agreed actions:

  1. cm handle Cm Handle ID remains populated with unique hash values (see assumption #3)
    (client side might need to update current algorithm to include ENM NM Name in the hash calculation)
  2. When an interface uses a non-unique alternative id the operation wil be rejected. A detailed impact analysis for each existing and proposed interface is needed. kieran mccarthy will work with Levente Csanyi to describe these impacts, agree how to handle and agree on possible (changes in) characteristics requirements of the impacted interface methods

...