MD-SAL APPLICATION AWARE DATA STORE (AADS)

Transcription

1 MD-SAL APPLICATION AWARE DATA STORE (AADS) Chandramouli Venkataraman

2 MD-SAL - Today Controller Platform APP MD-SAL Request Routing Notification Routing DOM tree Data store: /config /operational Clustering Service OF Plugin 2

3 MD-SAL Data Store Scaling concerns 1. Centralized DOM Tree based data store Yang model to DOM tree mapping Not suitable for a lot of applications OF objects can be stored in hash-map for better performance Too many tree nodes Single OF object maps to a sub-tree with match/action nodes tree traversal costs 3

4 MD-SAL Data Store Scaling concerns 1. Applications don t have flexibility to choose their data structures based on their performance and scale requirements Scaling becomes directly proportional to centralized datastore s perfromance 4

5 BA BI Infrastructure - complicated BA applications need to go through a set of broker interfaces before reaching DOM data store JAVA objects to DOM mapping overheads 5

6 AADS Introduction AADS let s applications Create/delete their own data stores Choose the type of data structures like hash-table according to their needs Efficiently realize storage objects in alignment with Yang models and manipulate them Decide on structuring data for efficient partition Handle transactions in a flexible manner as per their needs Not intended to replace existing MD-SAL Centralized Data Store 6

7 AADS Introduction (cont.) What applications are we talking about? NSF applications like topology manager Network technologies like OF MD-SAL Services that applications must be able to leverage Data store services Request Routing Clustering Services Notification services 7

8 AADS Conceptual View Controller Platform OF FRMv2 APP (AADS) Request Routing Notification Routing OF Hash Table : /config /operational MD-SAL Clustering Service OF Plugin 8

9 MD-SAL - AADS & DOM DS Controller Platform APP1 (Uses DOM) APP2 (Uses AADS) AADS Data store: DOM tree Data store: /config /operational Request Routing Notification Routing /config /operational MD-SAL Clustering Service OF Plugin 9

10 AADS - Requirements 1. Provide a data store framework to applications that allows them to create/delete data stores dynamically 2. Should be able to support different data stores in parallel 3. Yang related functionalities like augmentation should be supported 4. Existing ODL interfaces like RESTCONF should be supported 5. Provide a transaction library for applications 10

11 AADS - Requirements 1. Provide data change events to be registered at data nodes in the data stores (provide appropriate hooks for applications to register the same) 2. Capable of supporting a flexible clustering service like AKKA based clustering service or data-store clustering service 3. Hide clustering interface from applications as much as possible 4. Provide appropriate hooks for futures/callbacks that applications can register to handle replication, distribution across controller nodes 11

12 AADS - Requirements 1. Provide mechanisms to register dependencies by other applications 2. Re-use the existing MD-SAL RPC, Remote RPC, notification framework 3. Should co-exist with the existing MD-SAL centralized data store framework 4. Applications that use DOM store and those that use AADS should be able to inter-work with each other 12

13 MD-SAL - DOM & AADS API View Controller Platform APP1 (Uses DOM) APP2 (Uses AADS) MD-SAL API MD-SAL API EXT (AADS) MD-SAL DOM Layer AADS Layer Clustering Service OF Plugin 13

14 AADS 20K FEET Component View MD-SAL API MD-SAL AADS API Extn. Notification Broker Data Broker RPC Broker MD-SAL Core Data replication Data sharding State Trasfer Notifications DOM Store Distribution Layer In-Memory Datastore AADS Store AADS Backend (??) OSGi Container Clustering Services Akka Framework Transport (Def Netty) Intrusional changes in Helium MD-SAL and sub-components Code base class-level, module-level, new abstractions and implementation New codebase for AADS proposal 14

15 Q&A 15