Skip to content

Multiple stream originators

ericvoit edited this page Sep 20, 2017 · 1 revision

Problem statement for multiple stream originators

YANG-Push defines a transport-independent subscription mechanism for datastore updates, in which a subscriber can subscribe to a stream of datastore updates from a server, or update provider. This conceptually centralized model encounters efficiency limitations in cases where the data sources are themselves distributed, such as line cards in a piece of network equipment. In such cases, it will be a lot more efficient to have each data source (e.g. each line card) originate its own stream of updates, rather than requiring updates to be tunneled through a central server where they are combined. What is needed is a distributed data collection model that allows multiple data streams to be managed using a single subscription.

For this purpose, an extension to YANG-Push is defined that allows a single subscription to manage streams of datastore updates from multiple message originators. This includes (but may not be limited to) the following items:

  • A generic architecture abstraction for targeted use cases.
  • Disassemble subscription to corresponding agent nodes
  • Streaming data from originator directly to the receivers, i.e. API 5. The collector should not need to understand the decomposition of a subscription into multiple sub-agents.
  • Assemble subscripted data at collector node, and deduce the missing parts.
  • Multiple subscriptions and multiple receivers

Assumptions

  • Agent nodes connected to the master node and servicing part of information are known.
  • Connectivity and capability of agent nodes do not frequently change.

Out of scope

  • Agent node/master node discovery
  • Detailed specification of API 1 and 4
Clone this wiki locally