Versions Compared

Old Version 12

changes.mady.by.user Luke Gleeson

Saved on

compared with

New Version 13

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1415


Issues and Decisions

#IssueNotes Decision
1how fast should CPS (and DB) be able to process max heart beat failuresis 60K really realistic if ENM goes down we should get a notification for each node do we ?!

Description

  1. Define scenarios which cause a CM Handle to go stale
  2. Implement changes to support tracking of CM Handle Freshness/Staleness

...

  1. re-registration, once a day, same requirement as first time registration
  2. single node heart beat failures 30,000 / minute per instance
    1. Kafka should be able handle 2 instances i.e. 60K notifications in one minute
    2. What is expected/realistic here from CPS-NCMP see open issue #1

Scope

  1. Currently only supporting NONE and COMPLETE. PARTIAL and POOR may be added later as below.

...