...
| Issue | Notes | Decision | |
|---|---|---|---|
| 1 | Is FDN optional? | Is it possible to register a cmHandle without an FDN? | Toine Siebelink Yes it is optional as not everyone will use it |
| 2 | In Hazelcast what is the key? | Is it the FDN or the cmHandleId? | Toine Siebelink create 2 maps:
|
| 3 | Check 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. |
| 4 | Should we persist the alternateId? | Should we modify the registry model? | Toine Siebelink Yes, the Inventory Model should update with the AlternatId as detailed below |
| 5 | Alternative ID is NOT unique! | multiple NMs might be using same subnetwork names i the FDNs and as NCMP manage multiples NM's NCMP can encounter duplicates. | kieran mccarthy FDNs will be Unique |
| 6 | Add a cm Handle with a alternate ID that is already in use (for another CM Handle) | Error report solution will be easier if we do NOT add it and treat it like a 'normal' duplicate cm handle | kieran mccarthy do not add! Rephrase error to |
| 7 |
Alternate identifiers during registration
...
| Use-case | CM Handle Id | Alternate Id | Report | Add Cm Handle | Store Alternate ID | Notes | |
|---|---|---|---|---|---|---|---|
| 1 | New registration | Duplicated | N/A | 109, CM Handle Id or Alternate ID already in use | No | No | Existing error, change message! |
| 2 | New Registration | Unique | used for other cm handle | 109, already in use | No | No | Existing error, change message! See decision on issue #4 |
| 3 | Update Registration | New | N/A | 100, does not exist | N/A | No | |
| 4 | Update Registration | Exist | already set | 111, cannot re-assign | N/A | No | New Error Code |
| 5 | Update Registration | Exist | Use by other | 111, cannot re-assign | N/A | No | New Error Code |
...