Versions Compared

Key

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

...

#IssueNotes Decision
1Type of Interface REST or KafkaREST
  1. easier/cheaper
  2. possibly (complete) re-use of (inventory) existing interface
  3. well documented by OpenAPI
  4. support test stubs (contract testing)

Kafka

  1. more complicated/costly
  2. plethora of topics and messages, not well documented (no standard)
  3. More robust (request persisted until acknowledged)

meeting Agreed to use REST interface.  

2ModuleSetTag based on Hash no (yet) implemented!

This study seems to assume the module set tag is already implemented but it isn't!


[kieran mccarthy]:  the request it to introduce the hash module set tag/identifier of some kind for this new upgrade usecase.  Not assuming it is there already.  Will be costlier but is important for performance to avoid pulling models if they are already known to NCMP.
3Expected Responses

when and what content?

  1. just acknowledge upon receipt
  2. response on completion

202 Accepted if there are no issues with the payload
     - request payload is well formed 
     - all cmhandles are valid

404 Not Found Reject the request if an unknown cmhandle is sent in

4Should CM-Handle state change (e.g. to 'locked')  'during' upgrade?Yes but is important to not be locked for long which makes it important to use the tagmoduleSetTagShould be set to LOCKED until the new moduleSet is associated with the cmhandle.  I think there is a LOCKED_UPGRADING if I remember right.  Lock reason should state "upgrade initiated at time xxx for new moduleSetTag xyz".  When lock is being removed any lockReason message should be cleared. 
5ModuleSetTag is Optional (owned and defined by DMI Plugin)Support for upgrade without continues using delete/add cm handle approach.
If the update includes an ModuleSetTag it would be considered an upgrade

meeting Agreed to use REST interface with "upgradedCmHandles". 

6ModuleSetTag should be able to be used during initial inventory too!Initial Inventory should be sped up too (capability requirements impacts ?!)
7Exact name ModuleSetTag

meeting agreed on ModuleSetTag

8How to store: hardcoded (postgress schema), inventory yang model or as additional property (private or public)? update Inventory Yang Model so it can be queried (without code changes!) like other aspect such as 'state'

meeting agreed to update Yang Model

Is it  ok for cmhandle to send out a cmhandle lcm update event for a change in this property to indicate to client applications that a new moduleSet is available?  

9additional operation for inventory Interface: 'upgradedCmHandles'
The interface currently supports
  1. createdCmHandles
  2. updatedCmHandles
deletedCmHandles
  1. removedCmHandles

it possiblycould be done as part of 'updatedCmHandles' and look for /recognize the moduleSetTag update but this would be messy and confusing, also thentheoretically properties could be updated as the same time as the module set..

 Toine Siebelink , changed updatedCmHandles to removedCmHandles as per openAPI.

 

meeting agreed 



Solution Proposals 

Toine Siebelink Can you alternative proposals be maintained (kafka) so we know they were considered and reviewed and ruled out.  Be good to see what was reviewed/considered.

Update Inventory REST Interface

...