![]() | 1 | initial version |
I am looking for ODL-OVSDB northbound REST interface APIs to create/configure queues (Min/Max rate and burst).
My hardware Switch(Trident-II based) runs OpenvSwitch (2.3.0) and has connection ACTIVE connection to ODL controller (Beryllium SR3) . I am able to configure flows rules, meters via Openflow interface. Like: http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/table/0/flow/5141 http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/meter/41
Now I want to create qos and configure queues and set the action in my flow rules: I am able to do this by executing ovs-vsctl commands locally at switch and also can see the configuration through flollowing APIs http://192.168.103.242:8181/restconf/operational/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2Fuuid%2Fab64fd09-bf4d-48b2-8417-e176385cbc21/ovsdb:queues/queue:%2F%2F0823d6db-2b9a-4674-88ad-45d67fcc8e24
But I would like to do the queue configuration also using REST API available from OVS-OVSDB plugin. I am not intend to use openstack for my purpose.
Could someone please give me pointers for APIs and data(xml body) , where should I look for such details.
![]() | 2 | No.2 Revision |
I am looking for ODL-OVSDB northbound REST interface APIs to create/configure queues (Min/Max rate and burst).
My hardware Switch(Trident-II based) runs OpenvSwitch (2.3.0) and has connection ACTIVE connection to ODL controller (Beryllium SR3) .
I am able to configure flows rules, meters via Openflow interface. Like:
http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/table/0/flow/5141
http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/meter/41
Now I want to create qos and configure queues and set the action in my flow rules: I am able to do this by executing ovs-vsctl commands locally at switch and also can see the configuration through flollowing APIs http://192.168.103.242:8181/restconf/operational/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2Fuuid%2Fab64fd09-bf4d-48b2-8417-e176385cbc21/ovsdb:queues/queue:%2F%2F0823d6db-2b9a-4674-88ad-45d67fcc8e24
But I would like to do the queue configuration also using REST API available from OVS-OVSDB plugin. I am not intend to use openstack for my purpose.
Could someone please give me pointers for APIs and data(xml body) , where should I look for such details.
![]() | 3 | No.3 Revision |
I am looking for ODL-OVSDB northbound REST interface APIs to create/configure queues (Min/Max rate and burst).
My hardware Switch(Trident-II based) runs OpenvSwitch (2.3.0) and has ACTIVE connection to ODL controller (Beryllium SR3) . I am able to configure flows rules, meters via Openflow interface. Like: http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/table/0/flow/5141 http://192.168.103.242:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:12255366180885515072/meter/41
Now I want to create qos and configure queues and set the action in my flow rules: I am able to do this by executing ovs-vsctl commands locally at switch and also can see the configuration through flollowing APIs http://192.168.103.242:8181/restconf/operational/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2Fuuid%2Fab64fd09-bf4d-48b2-8417-e176385cbc21/ovsdb:queues/queue:%2F%2F0823d6db-2b9a-4674-88ad-45d67fcc8e24
But I would like to do the queue configuration also using REST API available from OVS-OVSDB plugin. I am not intend to use openstack for my purpose.
Could someone please give me pointers for APIs and data(xml body) , where should I look for such details.
© 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.
Please see our brand guidelines, trademark guidelines, terms of service and privacy policy.