Jump to: navigation, search

Messaging4Transport:Main

Messaging4Transport Facts

Project Creation Date: August 6th, 2015
Lifecycle State: Incubation
Type: {{{type}}}
Primary Contact: Pradeeban Kathiravelu <kk.pradeeban@gmail.com>
Project Lead: Pradeeban Kathiravelu <kk.pradeeban@gmail.com>
Committers:

  • Pradeeban Kathiravelu kk.pradeeban@gmail.com ( ODL User Name pradeeban)
  • Tony Tkacik tony.tkacik@gmail.com ( ODL User Name ttkacik)
  • Thanh Ha thanh.ha@linuxfoundation.org ( ODL User Name zxiiro)

IRC: freenode.net #opendaylight-m4t
Mailing List: Messaging4transport-dev@lists.opendaylight.org
    Archives: mailing list archives
Meetings: none
Repository: git clone https://git.opendaylight.org/gerrit/p/messaging4transport
Jenkins: jenkins silo
Gerrit Patches: All Patches
Bugs:

[[Category:{{{type}}} Projects]]


The OpenDaylight controller is based on an MD-SAL allows the modeling of data, RPCs, and notifications. Because of this model basis, adding new northbound bindings to the controller is simple, and everything modeled becomes exposed automatically. Currently the MD-SAL has restconf NB bindings, where more bindings such as AMQP and XMPP can easily be implemented and integrated.

AMQP is an open standard application layer protocol for message-oriented middleware. This project adds AMQP bindings to the MD-SAL, which would automatically make all MD-SAL APIs available via that mechanism. AMQP bindings integration is built as an independent Karaf feature, that would expose the MD-SAL datatree, rpcs, and notifications via AMQP, when installed.

Many implementations of AMQP exists. ActiveMQ is a popular open source messaging and Integration Patterns server, which offers an implementation of AMQP. Initial implementation of AMQP bindings are developed and tested with ActiveMQ-5.9.0. Deploying the bundle as an Apache Camel processor, any broker can be chosen without the bundle being coupled to a specific bundle.


Key Features

  • Messaging Oriented Middleware Northbound Bindings for MD-SAL.

Use Cases

Multiple industry and research use cases of Messaging4Transport have been proposed. Proof of concepts have been built with preliminary results, using the proposed architecture of Messaging4Transport.

Getting Started with Messaging4Transport

We are still in development and highly welcome contributions from developers. Contributions include (but not limited to), code contributions and applications leveraging Messaging4Transport.

Project Information

Project Proposal

Release Release Plan Release Notes Release Review Installation Guide User Guide Developer Guide Integration System Test
Beryllium Release Plan Release Notes Release Review Installation Guide User Guide Developer Guide Integration System Test

List of all subpages

Messaging4Transport:AMQP Bindings for MD-SALMessaging4Transport:Beryllium:Release NotesMessaging4Transport:Beryllium:Release Review
Messaging4Transport:Developer GuideMessaging4Transport:Installation GuideMessaging4Transport:Integration System Test
Messaging4Transport:MainMessaging4Transport:Release Plan BerylliumMessaging4Transport:Use Cases
Messaging4Transport:User Guide