Page History

...

Jira

server	ONAP Jira
columnIds	issuekey,summary,issuetype,created,updated,assignee,reporter,priority,status,resolution,subtasks
columns	key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks
maximumIssues	20
jqlQuery	key = CPS-828
serverId	425b2b0a-557c-3c0c-b515-579789cceedb

Issues/Decisions

...

Color	Meaning
	New/Open
	Reopened
	Agreed/Closed

To facilitate asynchronous requests to DMI we will need to either create a new endpoint or modify existing endpoint to include /async flag. The second solution may not be backwards compatible. However creating a new endpoint solely for a flag is also not ideal. We could add async to list of options (but this might interfere with the purpose of /options.

Additionally, considered adding a new endpoint for async which simply re-routes the response to the original endpoint while adding the logic for OK response to the client. However, would this lead to a change in the schema? If so, would this be backwards compatible?

#

Issue

Notes/Jira

Decision

1

What topic to use for client?

Topic provided by client as a parameter which will be injected into our environment and used for asynchronous requests sent back to client.

To be supplied by cient

2

What topic to use for private DMI-NCMP?

e.g. ncmp-async-private but decision needs to be made with current best practices.

Contact Fiachra Corcoran regarding ONAP conventions.

Response was that there aren't any conventions to speak of but we would use dashes (i.e. my-new-topic) instead of dot notation (i.e. my.new.topic) for topic name

Proposed:

ncmp-async-m2m

3

Are adding a new REST endpoint for async or modifying an existing endpoint?

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-830

/ncmp/v1/data/ch/123ee5/ds/ncmp-datastore:*?topic=<topic-name> 4Agree URL for async once #2 is clarifiedCPS R10 Release Planning#NCMPRequirements #11. Based on this additional path parameter we no longer require additional /async flag in url.

/ncmp/v1/data/ch/123ee5/ds/ncmp-datastore:*?topic=<topic-name>

5Passthrough request need to be able to handle different response types (using accept header) but the async option would have a fixed and possibly different response type.CPS R10 Release Planning#NCMPRequirements #11.We should, by default, be able to accept multiple contnet-types.6Should we create a standalone app to demo or are tests sufficient?

CSIT tests may require more involved effort - perhaps we could add standalone app to nexus and use it as part of CSIT test?

See #137

Do we need to persist the generated requestID?

We should be be statelessNo8Error Reporting - Topic Correctness/AvailabilityAt a minimum we should report to the client if a topic was not found or if the topic name was incorrectIn Scope9Error Reporting - Kafka IssuesIssues such full buffer/queue, drop messages, failure not in scopeOut of scope10

Async Request Option using Messaging

See: https://wiki.onap.org/display/DW/CPS-821+Spike%3A+Support+Async+read-write+operations+on+CPS-NCMP+interface#CPS821Spike:SupportAsyncreadwriteoperationsonCPSNCMPinterface-AsyncRequestOptionusingMessaging(OutofScope)Out of scope11Do we actually require futures in this implementation proposal?

It could be argued that the need for futures is made redundant by the fact we call dmi from ncmp through rest and the response will be consumed via Kafka.

What benefit would future give us in this case?

Not needed12ID GenerationWhich mechanism to use? Look at CPS-Temporal and follow to keep consistency13Can robot framework verify if Kafka events have been sent/received

This would be less work and overhead (rather than creating/.maintaining client app)

Will need to verify if 3PP libraries are safe to introduce into codebase. If so, what is the process? Do they need to be FOSSed?

UNDER INVESTIGATION14Can Webflux do this work with less code/impl?Sourabh Sourabh suggested using this to compliment our existing approach. By adding webflux we add an event loop to synchronize and access I/O connections to the database.No, It will compliment the design by adding an event loop for I/O synchronization and access15ONAP may be deprecating PLAINTEXT for Kafka. Strimzi Kafka might need to be usedUNDER INVESTIGATION

Proposed Design

...

High-level Steps/Possible Tickets:

...

17 Feb 2022 Update: Toine Siebelink had a conversation with Tony Finnerty it has been agreed CPS is to configure a (temporary) dedicated client-topic as final destination for the async replies: we now want to propose to use a common ‘cps-broadcast’ topic which also will used for broadcasting messages like cm handles being added o removed etc.

Still it is only a temporary solution until the client have a better way of declaring their own topics. It does not affect our proposed interfaces, just the name of the topic that will be accepted by NCMP (for now)

---------------------------------------------------------------------------------------

16 Feb 2022 Update: After discussion with Fiachra Corcoran regarding Kafka-strimzi it has been agreed that we will define a topic for client responses in advance (defined upfront). After release K it is envisioned that auto creation of topics will be disbaled by default thus the client will have to use our predefined topic.

Agreement on topic name outstanding

---------------------------------------------------------------------------------------

~~To be supplied by cient~~

2

What topic to use for private DMI-NCMP?

Contact Fiachra Corcoran regarding ONAP conventions.

Response was that there aren't any conventions to speak of but we would use dashes (i.e. my-new-topic) instead of dot notation (i.e. my.new.topic) for topic name

ncmp-async-m2m

3

Are adding a new REST endpoint for async or modifying an existing endpoint?

To facilitate asynchronous requests to DMI we will need to either create a new endpoint or modify existing endpoint to include /async flag. The second solution may not be backwards compatible. However creating a new endpoint solely for a flag is also not ideal. We could add async to list of options (but this might interfere with the purpose of /options.

Additionally, considered adding a new endpoint for async which simply re-routes the response to the original endpoint while adding the logic for OK response to the client. However, would this lead to a change in the schema? If so, would this be backwards compatible?

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-830

/ncmp/v1/data/ch/123ee5/ds/ncmp-datastore:*?topic=<topic-name>

4

Agree URL for async once #2 is clarified

CPS R10 Release Planning#NCMPRequirements #11.

/ncmp/v1/data/ch/123ee5/ds/ncmp-datastore:*?topic=<topic-name>

5

Passthrough request need to be able to handle different response types (using accept header) but the async option would have a fixed and possibly different response type.

CPS R10 Release Planning#NCMPRequirements #11.

The async response can 'wrap' the native response inside a json object identical to the synchronous response

6

Should we create a standalone app to demo or are tests sufficient?

CSIT tests may require more involved effort - perhaps we could add standalone app to nexus and use it as part of CSIT test?

See #13

7

Do we need to persist the generated requestID?

We should be be stateless

No - Further disc

8

Error Reporting - Topic Correctness/Availability

At a minimum we should report to the client if a topic was not found or if the topic name was incorrect

In Scope

9

Error Reporting - Kafka Issues

Issues such full buffer/queue, drop messages, failure not in scope

Out of scope

10

Async Request Option using Messaging

See: https://wiki.onap.org/display/DW/CPS-821+Spike%3A+Support+Async+read-write+operations+on+CPS-NCMP+interface#CPS821Spike:SupportAsyncreadwriteoperationsonCPSNCMPinterface-AsyncRequestOptionusingMessaging(OutofScope)

Out of scope

11

Do we actually require futures in this implementation proposal?

It could be argued that the need for futures is made redundant by the fact we call dmi from ncmp through rest and the response will be consumed via Kafka.

What benefit would future give us in this case?

Not needed

12

ID Generation

Which mechanism to use? Look at CPS-Temporal and follow to keep consistency

See: https://wiki.onap.org/display/DW/CPS-821+Spike%3A+Support+Async+read-write+operations+on+CPS-NCMP+interface#CPS821Spike:SupportAsyncreadwriteoperationsonCPSNCMPinterface-CanRobotFrameworkverifyKafkaEvents

13

Can robot framework verify if Kafka events have been sent/received

This would be less work and overhead (rather than creating/.maintaining client app)

Will need to verify if 3PP libraries are safe to introduce into codebase. If so, what is the process? Do they need to be FOSSed?

Integration testing should be carried out by a client of NCMP. Demo can be performed up the point NCMP produces message for the client.

14

Can Webflux do this work with less code/impl?

Sourabh Sourabh suggested using this to compliment our existing approach. By adding webflux we add an event loop to synchronize and access I/O connections to the database.

No, It will compliment the design by adding an event loop for I/O synchronization and access. See: CPS-850

15

ONAP may be deprecating PLAINTEXT for Kafka. Strimzi Kafka might need to be used

No relevant information could be found relating to this. See: https://wiki.onap.org/display/DW/CPS-821+Spike%3A+Support+Async+read-write+operations+on+CPS-NCMP+interface#CPS821Spike:SupportAsyncreadwriteoperationsonCPSNCMPinterface-KafkaStrimziInvestigation

The underlying implementation won't be affected. The config will contain relevant configuration for protocol (e.g. PLAINTEXT, SASL) and connections.

This information needs to be made configurable when implementing.

16

Should we have something like the message count in the response or an indication of the last message at least.?

On the topic=Xyz async analysis, One item I forgot to mention was when a client might know when they have received the last response message for a request.

If async there may be many responses (otherwise there's no need for async)

Therefore should it not have something like the message count in it or an indication of the last message at least.

This is another step in an evolution of the product. Multiple response messages might become a necessity for asycnc bulk operations and maybe that is when we can discuss it in more detail. I don’t think it has to affect our current implementation additional field to handle that can always be added in a backward compatible way.

17

Do we need Kafka messaging between DMI and NCMP?

This was discussed as it was argued that the client and CPS ecosystem is decoupled and async using only bus between ncmp and client. However, this would not rectify blocking calls between ncmp and dmi.

It was decided to have two separate kafka topics for client → ncmp & ncmp → dmi

18

Can NCMP list all existing topics

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-828

AC Point 3 : Topic does not exists (not allowed to create new topics, assuming NCMP can 'list' existing topics)

Gareth Roper Need your suggestion.

19

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-828

Async: NCMP Rest impl. including Request ID generation

AC Points :

2. cm handle does not exists

3. No DMI registration for CM Handle

AC point 2 : We agreed to check only if cm handle exists. If cm does not exists will get Http status 404 as below.

{
"status": "404 NOT_FOUND",
"message": "DataNode not found",
"details": "DataNode with xpath /dmi-registry/cm-handles[@id='my-cm-handle1'] was not found for anchor ncmp-dmi-registry and dataspace NCMP-Admin."
}

AC point 3 . Is not valid.

20

Client Kafka User & Privileges

16 Feb 2022 After discussion with Fiachra Corcoran regarding Kafka-strimzi we will need to ensure client can access Kafka user and be allocated sufficient privileges (principle of least privilege)

21

agree client response format

Message gets forwarded to original Client Topic

See https://wiki.onap.org/display/DW/CPS-821+Spike%3A+Support+Async+read-write+operations+on+CPS-NCMP+interface#CPS821Spike:SupportAsyncreadwriteoperationsonCPSNCMPinterface-ProposedMessageFormat

22

Async Ack

{
    "headers": {},
    "body": {
        "requestId": "f1aa75c6-e9ad-4072-bf19-659a66b3e0ff"
    },
    "statusCode": "OK",
    "statusCodeValue": 200
}

Agreed & implemented

Proposed Design

...

draw.io Diagram

border	true

diagramName	CPS-821
simpleViewer	false
width	1000
links	auto
tbstyle	top
diagramDisplayName	Proposed Design
lbox	true
diagramWidth	1256
revision	25

High-level Steps/Possible Tickets:

Modify REST endpoint to include param topic (1)
Add logic to send response and request (2a)
Send request if async is implemented or NotSupportedException if not (2b)
Add producer to DMI (implementation and config) (31 & 3b)
Add consumer to NCMP (implementation and config) (4a)
Add Producer to NCMP (implementation and config) (4b)
Demo & Test (5)

Alternative Approaches

#

Person

Approach

1

Renu Kumari

[Relates to point 3 from high-level steps]

It would be good to have async implementation only dependent on NCMP. So that it does not break or work with only few DMI plugins.
I think a DMI plugin independent async flow would be like
1. Once request is received, check if dmi plugin exist. If exists, generate request uuid, send the message to the Kafka topic (or store it in DB), and send an accepted response back to client.
2. NCMP will listen to the same topic or read from the DB. Process it by calling appropriate DMI Plugins synchronously. After it receives the response back, it sends to to Kafka topic provided in the input by user.

In this implementation, we are not dependent on the DMI implementation.
We do need persistence for storing async request. It can be a stored in DB or Kafka, it does not matter as long as we can read it in the same order.

The main points are
1. No dependency on the DMI for async behavior

2. No async request get lost because of pod restart or JVM crash.

Proposed Message Format

...

Info

icon	false

Legend

Color	Meaning
	NCMP standard event schema
	Event payload schema as per org.onap.ncmp:async-request-response-event:v1
	Response payload schema. The payload schema is an onap one if non-passthrough but may be either an onap published or other (oran, proprietary, etc) schema if the original call received by the dmi plugin is a ncmp:passthrough-*.

SCOPE OF THE WORK : the black highlighted parts of the above events.
The blue highlight is not in current scope. The blue bits will be up to the dmi plugins.
In the future these blue bits may become part of the standard onap base release.

Success Scenario

Info

icon	false
title	DMI Event sent to NCMP

{

"eventId" : "9999", # some generic event uuid generated by DMI Plugin
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2021-11-16T16:42:25-04:00", (kieran mccarthy is this format agreed?)
"eventSource" : "org.onap.ncmp", # ??? Is this needed? Joseph Keenan will use dmiAsyncRequestResponseEvent.setEventSource(Application.class.getPackageName());

"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events (kieran mccarthy Who owns this schema? How do the schemas relate?)
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events (who owns this? table with owner, repo, color coded)
“eventTarget” : “topic:client-application-topic”, # indicates where to route the event - ‘topic’ is default target type (kieran mccarthy will it be in format of topic:<topic> always or could it be extended e.g. ip:<ip-address>?)

"event": {
     “response-data-schema” : “org.onap.cps.yang-patch-json:v1”,
   “response-status” : “SUCCESS”,
     “response-code”   : “201”,
     “response-data” : {
…
<response-data-payload>
…
     }
}
}

Info

icon	false
title	NCMP Event forwarded to Client topic (in eventTarget)

{

  "eventId" : "33001", # some generic event uuid generated by NCMP
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2015-11-16T16:42:26-05:06", ( kieran mccarthy Is this a timezone?)
  "eventSource" : "org.onap.ncmp", # The source of the event
  "eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
  ”eventSchema”        : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events

  "eventOrigin" : {

"eventId" : "00001", # some generic event uuid generated by DMI Plugin
"eventTime" : "2021-11-16T16:42:25-04:00", (kieran mccarthy is this agreed upon?)
“eventCorrelationId” : “request-009995”,
"eventSource" : "org.onap.dmi", # ??? Is this needed?
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
“eventTarget” : “topic:client-application-topic”
},

"event": {
     “response-data-schema” : “org.onap.cps.yang-patch-json:v1”,
   “response-status” : “SUCCESS”,
     “response-code”   : “201”,
     “response-data” : {
…
<response-data-payload>
…
     }
}
}

Failure Scenario

Info

icon	false
title	DMI Event sent to NCMP

{

  "eventId" : "9999", # some generic event uuid generated by DMI Plugin
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2021-11-16T16:42:25-04:00",
  "eventSource" : "org.onap.ncmp", # ??? Is this needed?
  "eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
  ”eventSchema”        : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
  “eventTarget” : “topic:client-application-topic” , # indicates where to route the event
# - ‘topic’ is default target type
"event": {
     “response-data-schema” : “org.onap.cps.generic-error:v1”,
   “response-status” : “FAILURE”,
     “response-code”   : “404”,
     “response-data” : {
…
<response-data-payload-as-org.onap.ncmp.generic-error:v1>
…
     }
}
}

Info

icon	false
title	NCMP Event forwarded to Client topic (defined in eventTarget)

{

  "eventId" : "33001", # some generic event uuid generated by NCMP
“eventCorrelationId” : “request-009995”, # for event correlation - acts as the request Id when
# eventType=org.onap.ncmp.async-request-response-event
"eventTime" : "2015-11-16T16:42:26-05:06",
  "eventSource" : "org.onap.ncmp", # The source of the event
  "eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
  ”eventSchema”        : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events

  "eventOrigin" : {

"eventId" : "00001", # some generic event uuid generated by DMI Plugin
"eventTime" : "2021-11-16T16:42:25-04:00",
“eventCorrelationId” : “request-009995”,
"eventSource" : "org.onap.dmi", # ??? Is this needed?
"eventType" : "org.onap.ncmp.async-request-response-event", # event type for async request response events
”eventSchema” : “org.onap.ncmp:async-request-response-event:v1", # event schema for async request response events
“eventTarget” : “topic:client-application-topic”
},

"event": {
     “response-data-schema” : “org.onap.cps.generic-error:v1”,
   “response-status” : “FAILURE”,
     “response-code”   : “404”,
     “response-data” : {
…
<response-data-payload-as-org.onap.ncmp.generic-error:v1>
…
     }
}
}

Sample Output

Code Block

language	yml
title	Response Event 1: DMI -> NCMP
collapse	true

{
  "eventId": "c5c7c885-2e31-4951-aba5-3062889b8a7c",
  "eventCorrelationId": "2539f8ac-b2c3-422d-bb75-b3f10d3d6216",
  "eventTime": "2022-05-05T13:48:51.157+0000",
  "eventSource": "org.onap.ncmp",
  "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
  "eventTarget": "my-topic-999",
  "event": {
    "response-data-schema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "response-status": "200",
    "response-code": "SUCCESS",
    "response-data": {
      "ietf-netconf-monitoring:netconf-state": {
        "schemas": {
          "schema": [
            {
              "identifier": "ietf-tls-server",
              "version": "2016-11-02",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-tls-server",
              "location": [
                "NETCONF"
              ]
            },
            ...,
            {
              "identifier": "ietf-system",
              "version": "2014-08-06",
              "format": "ietf-netconf-monitoring:yin",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-system",
              "location": [
                "NETCONF"
              ]
            }
          ]
        }
      }
    }
  }
}

Code Block

language	yml
title	Response Event 2: NCMP -> Client
collapse	true

{
  "eventId": "bfb86f3e-641b-4750-b3a0-d8d31f01a708",
  "eventCorrelationId": "2539f8ac-b2c3-422d-bb75-b3f10d3d6216",
  "eventTime": "2022-05-05T13:48:53.375+0000",
  "eventSource": "org.onap.ncmp",
  "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
  "eventTarget": "my-topic-999",
  "eventOrigin": {
    "eventId": "c5c7c885-2e31-4951-aba5-3062889b8a7c",
    "eventCorrelationId": "2539f8ac-b2c3-422d-bb75-b3f10d3d6216",
    "eventTime": "2022-05-05T13:48:51.157+0000",
    "eventSource": "org.onap.ncmp",
    "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "eventTarget": "my-topic-999"
  },
  "event": {
    "response-data-schema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "response-status": "200",
    "response-code": "SUCCESS",
    "response-data": {
      "ietf-netconf-monitoring:netconf-state": {
        "schemas": {
          "schema": [
            {
              "identifier": "ietf-tls-server",
              "version": "2016-11-02",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-tls-server",
              "location": [
                "NETCONF"
              ]
            },
            ...,
            {
              "identifier": "ietf-system",
              "version": "2014-08-06",
              "format": "ietf-netconf-monitoring:yin",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-system",
              "location": [
                "NETCONF"
              ]
            }
          ]
        }
      }
    }
  }
}

Manual Testing

...

Code Block

language	yml
title	Client -> NCMP Response
linenumbers	true
collapse	true

{
    "headers": {},
    "body": {
        "requestId": "0f574dfa-9c05-4899-9ae1-e6741f53c6d9"
    },
    "statusCode": "OK",
    "statusCodeValue": 200
}

Code Block

language	yml
title	NCMP Sync Done
linenumbers	true
collapse	true

{
	"logTimeStamp": "2022-05-10T11:16:27.123Z",
	"logLevel": "INFO",
	"principalId": "cpsuser",
	"serviceName": "cps-application",
	"message": "Async task completed successfully.",
	"processId": "1",
	"threadName": "ForkJoinPool.commonPool-worker-5",
	"class": "o.o.c.n.r.executor.CpsNcmpTaskExecutor"
}

Code Block

language	yml
title	DMI -> NCMP (DmiAsyncRequestResponseEvent)
linenumbers	true
collapse	true

{
  "eventId": "b2f629ae-ee90-44d9-97f9-500c8a595b6a",
  "eventCorrelationId": "2243bbcd-b0b3-4aa5-9d53-41dc88a525a5",
  "eventTime": "2022-05-10T08:39:37.597+0000",
  "eventSource": "org.onap.ncmp",
  "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
  "eventTarget": "my-topic-999",
  "eventContent": {
    "response-data-schema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "response-status": "SUCCESS",
    "response-code": "200",
    "response-data": {
      "ietf-netconf-monitoring:netconf-state": {
        "schemas": {
          "schema": [
            {
              "identifier": "ietf-tls-server",
              "version": "2016-11-02",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-tls-server",
              "location": [
                "NETCONF"
              ]
            },
            {
              "identifier": "nc-notifications",
              "version": "2008-07-14",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:netmod:notification",
              "location": [
                "NETCONF"
              ]
            }
        }
      }
    }
  }
}

Code Block

language	yml
title	NCMP -> Client (NcmpAsyncRequestResponseEvent)
linenumbers	true
collapse	true

{
  "eventId": "699da452-4131-4e55-b49a-50e0c5f0d641",
  "eventCorrelationId": "efc17123-902a-4f50-8294-178a782b9102",
  "eventTarget": "test-env-1",
  "eventTime": "2022-05-10T11:16:27.427+0000",
  "forwardedEvent": {
    "eventId": "0f574dfa-9c05-4899-9ae1-e6741f53c6d9",
    "eventCorrelationId": "efc17123-902a-4f50-8294-178a782b9102",
    "eventTime": "2022-05-10T11:16:27.374+0000",
    "eventSource": "org.onap.ncmp",
    "eventSchema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "eventTarget": "test-env-1",
    "response-data-schema": "urn:cps:org.onap.cps:async-request-response-event-schema:v1",
    "response-status": "SUCCESS",
    "response-code": "200",
    "response-data": {
      "ietf-netconf-monitoring:netconf-state": {
        "schemas": {
          "schema": [
            {
              "identifier": "ietf-tls-server",
              "version": "2016-11-02",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:yang:ietf-tls-server",
              "location": [
                "NETCONF"
              ]
            },
            {
              "identifier": "nc-notifications",
              "version": "2008-07-14",
              "format": "ietf-netconf-monitoring:yang",
              "namespace": "urn:ietf:params:xml:ns:netmod:notification",
              "location": [
                "NETCONF"
              ]
            }
          ]
        }
      }
    }
  }
}

...

Kafka config & Implementation

...

Source: https://docs.spring.io/spring-framework/docs/current/reference/html/web-reactive.html

Pros & cons

Pros

Cons

Better scalability due to non blocking threads
Use less threads (1 per core)
Better CPU Efficiency

Reactive web programming is great for applications that have streaming data, and clients that consume it and stream it to their users. It ain’t great for developing CRUD apps. If you want to develop a CRUD API, stick with Spring MVC.
- Source: https://developer.okta.com/blog/2018/09/24/reactive-apis-with-spring-webflux
Steep learning curve in the shift to non-blocking, functional, and declarative programming

Links to materials:

https://www.baeldung.com/spring-webflux

https:///www.baeldung.com/spring-webflux

https://www.youtube.com/watch?v=1F10gr2pbvQ

Kafka Strimzi Investigation

www.youtube.com/watch?v=1F10gr2pbvQ

Kafka Strimzi Investigation

...

Could not find relevant information for ONAP strimzi but there is a PoC to move CPS to Strimzi:

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	DMAAP-1681

https://strimzi.io/

Can Robot Framework verify Kafka Events?

...

Jira

server	ONAP Jira
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	CPS-834

To facilitate demo and testing of this functionality a new standalone app will be required to act as client.

...

For a demo it will be sufficient to show that the response is being produced on the client topic.

The client should conduct integration testing.

References

...

CPS-391Spike: Define and Agree NCMP REST Interface#Sync&ModelAPI

Space shortcuts

Page tree

Versions Compared

Old Version 87

New Version Current

Key

Issues/Decisions

Proposed Design

Proposed Design

Proposed Message Format

Success Scenario

Failure Scenario

Sample Output

Manual Testing

Kafka config & Implementation

Pros & cons

Kafka Strimzi Investigation

Kafka Strimzi Investigation

Can Robot Framework verify Kafka Events?

References