Impl. Proposal for Merging of Subscriptions ( Positive Scenarios )

References

Assumptions

Issues & Decisions

Overview

This page only contains the details used for starting the development on the Merging of Subscriptions use case. Just the straight forward scenarios will be covered and the overall solution will be build on top of it.

Schema Definitions

1. DME to NCMP Subscription Request
   
   

   DME to NCMP Subscription Request Expand source

   Header values ( all cloud events header )
   
   
   {
     "data": {
       "subscriptionId": "unique subscription id",
       "predicates": [
   	{
           “targets” :  list of cmhandles
           "datastore": “ncmp-datastore:passthrough-operational or ncmp-datastore:passthrough-running",
           "datastore-xpath-filter": list of valid xpaths
     
       }
   	]
   }

2. NCMP to DMI-Plugin Subscription Request
   
   

   NCMP to DMI-Plugin Subscription Request Expand source

   // correlationId for tracking
   {
     "data": {
      
   	"cmhandles" : [
   	{
   		"cmHandleId": "cmhandle1",
   		"private-properties": {...} 
   	},
   	{
   		"cmHandleId": "cmhandle2",
   		"private-properties": {...}
   	},
   	{
   		"cmHandleId": "cmhandle3",
   		"private-properties": {...}
   	}
   	]
       "predicates": [
   	{
           “targets” :  [“cmHandle1”, “cmHandle2”, "cmhandle3"]
           "datastore": “ncmp-datastore:passthrough-operational",
           "datastore-xpath-filter": ["p1/c1", "p2/c2"]
     
       },
   	{
           “targets” :  [“cmHandle1”]
           "datastore": “ncmp-datastore:passthrough-running",
           "datastore-xpath-filter": ["p3/c3", "p4/c4"]
       }
   	]
   }

3. DMI-Plugin to NCMP Subscription Response
   
   

   DMI-Plugin to NCMP Subscription Response Expand source

   Headers will have relevant fields including the subscriptionId
   
   // correlationId for tracking - to link with NCMP. ( get clarity )
   { 
   "data" : {
   
      "dmiName":"<dmiName>", 
      "statusCode": "1", // open issue for the status codes ( whether to use the same for DMI to NCMP  as for NCMP to Clients)
      "statusMessage" : "accepted/rejected"
   }
   }

4. NCMP to DME Subscription Response
   
   

   NCMP to DME Subscription Response Expand source

   Headers will have relevant fields including the subscriptionId
   
   {
     "data": {
   		"subscriptionId": "sample-subscription-id",
   		"accepted-targets" : ["ch-1", ...],
   		"rejected-targets" : ["ch-1", ...],
   		"pending-targets" : ["ch-1", ...],
     }
   }