- What is MD-SAL? main purpose?
- Advantages of MD-SAL over AD-SAL?
- What is yang and how it is related to MD-SAL?
Model-driven Service Adaptation Layer (MD-SAL), is the kernel of the platform where the different layers and modules are interconnected through well-defined API. NB and SB plugins can be service producers or service consumers or even both. The SAL works as a large services’ registry where the producers advertisetheir services through their APIs. When a consumerrequests an advertised service by a generic API, theSAL connects and binds both the producer and the consumer . The developers of ODL started codingthe original SAL with an API-Driven SAL architecture. The API-DrivenSAL or AD-SAL, the developers had to code the SAL APIs (to route service requests between consumers andproviders) and the adaptation functionality (if NB (Ser-vice, abstract) API is not similar to its correspondingSB (protocol) API) . Despite AD-SAL hiding theelement-level complexity, the scalability of ODL can be limited by coding the SAL APIs as well as theadaptation functionality of each new plugin each time. you can refer this links for better understanding.
As for the relationship between YANG and MD-SAL, YANG is used as the Interface Definition Language (IDL) to define data and services. MD-SAL provides the compile-time and run-time support needed to implement and cross-connect those services in Java.
This thread is public, all members of ask.opendaylight.org can read this page.
Asked: 2015-12-15 02:26:47 -0700
Seen: 63 times
Last updated: Apr 08 '16
© 2014 OpenDaylight, A Linux Foundation Collaborative Project. All Rights Reserved.
OpenDaylight is a trademark of The OpenDaylight Project, Inc.
Linux Foundation is a registered trademark of The Linux Foundation.
Linux is a registered trademark of Linus Torvalds.