Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Work-in-progress. Completed page will be linked into the Tutorials page.

Overview

        ONOS Rabbit MQ application will be capture and parse the ONOS events and notifications. There by converting the below listed events into appropriate json schema and publish them on to MQ server. The interested ONOS application can consume the published json messages.

Types of ONOS events supported by RabbitMQ app

    • Device Event
      Describes infrastructure device event.
    • Port Event
      Describes infrastructure port event.
    • Link Event
      Describes infrastructure link event.
    • Topology Event
      Describes network topology event.
    • Packet Event
      Describes inbound packet recieved.

      Configuration

To configure Rabbit MQ event notification from ONOS the following components needs to be configured:

    • ONOS Rabbit MQ App

      The implementation of rabbitmq can be found at $ONOS_ROOT/app/rabbitmq

    • Rabbit MQ Server (External to ONOS)

      The latest release of RabbitMQ can be available at https://www.rabbitmq.com/download.html
      Please refer the server documentation at administrator's guide
      You can access the user-management with rabbitmqctl and use the command:

      rabbitmqctl add_vhost <vhost>
rabbitmqctl add_user <username> <password>
rabbitmqctl set_permissions -p <vhost> <username> ".*" ".*" ".*"
rabbitmqctl set_user_tags <username> management
    • Rabbit MQ Client (External to ONOS)
      Please follow below steps to setup mq consumer application.
      Extract below attached message-consumer-app.tar.gz
      Build and generate the jar using mvn clean install
      Run the consumer application using command java -jar MessageConsumer-jar-with-dependencies.jar

      Json message onos event structures and their attributes

             For example device event message structure as below

{
"switch_id": "of:0000000000000001",
"infra_device_name": "SWITCH",
"event_type": "DEVICE_EVENT",
"sub_event_type": "DEVICE_UPDATED",
"hwVersion": "Open vSwitch",
"mfr": "Nicira, Inc.",
"serial": "None",
"sw_version": "2.5.0",
"chassis_id": 1,
"occurrence_time": "Tue Aug 23 15:40:59 IST 2016"
}

Please refer below attached document for complete set of json message onos event structure, attributes and their definitions,

mq_message_definition_&_structures.docx

 

  • No labels