...
# | Parameter | Expectation | Notes | |
|---|---|---|---|---|
| 1 | Frequency of LCM Events | No high volume of such events is expected For testing purposed 1 LCM event per minute would suffice | ||
| 2 | How many subscriptions | Max and the average | ||
| 3 | How many cmhandles will be there per subscription | Max and the average | ||
| 4 | How many datastore-xpaths-filter for the subscriptionMax and the average |
Out-of-scope
- Working with the wildcards, only list of specific CM Handle IDs are supported
- Subscription Update scenarios for an ongoing subscription.
Assumptions
# | Assumption | Notes |
|---|---|---|
| 1 |
Issues & Decisions
# | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Maximum number of cm data subscriptions for create and delete use case | ||
| 2 | Maximum, Average CM Handles/subscription | ||
| 3 | Maximum, Average XPaths/CmHandles | ||
| 4 | What all datastores are supported ? | ncmp-datastore:passthrough-running or ncmp-datastore:passthrough-operational ?? or both? |
Overview
- Page to keep track of the underlying use case for Subscription Create and Subscription Delete.
- The events used will adhere to CNCF Cloud Events.
- NCMP wil not be responsible for keeping the 'state' of any subscription and thus decide which CM Events should be forwarded
...