Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

Starting point of creating a new plugin / service

I am new to ODL (1 week ) and currently investigating a solution to create a service , which will expose REST API's to north bound , to southbound CLI via MD-SAL.

An example to execute the "show ip " cli command . I am assuming the process is like this ( reading the MD-SAL documents ).

1) Define the yang model wirh rpc defined show-ip 2) Create a CLIConsumer (South bound) 3) Create a CLIProducer
3) Register consumer and Producer with the Binding Broker ( Aware or independent ) 4) Create a CLIService . 5) Add the notification listeners

The LearningSwitch example used the pattern similar to this. But the DeviceManagerImpl which uses receivePacket(..) and transmitPackage (..) doesnt have any producer, consumer pattern.

Can any one please share a example / document related to this.

Starting point of creating a new plugin / service

I am new to ODL (1 week ) and currently investigating a solution to create a service , which will expose REST API's to north bound , to southbound CLI via MD-SAL.

An example to execute the "show ip " cli command . I am assuming the process is like this ( reading the MD-SAL documents ).

1) Define the yang model wirh rpc defined show-ip 2) Create a CLIConsumer (South bound) 3) Create a CLIProducer
3) Register consumer and Producer with the Binding Broker ( Aware or independent ) 4) Create a CLIService . 5) Add the notification listeners

The LearningSwitch example used the pattern similar to this. But the DeviceManagerImpl which uses receivePacket(..) and transmitPackage (..) doesnt have any producer, consumer pattern.

Can any one please share a example / document related to this.