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

Nuno, if the flow has the correct format and you are giving it to the "config" store of the controller you will get a 200. AFAIK there is no way of known in that transaction if the flow was installed correctly on the switch or not. If you wait for some time (up to 15 seconds, I believe) the controller should be polling the connected switches for stats. If the flow exists on the switch, then you can query the "operational" store to verify if the switch has the flow or not.

Nuno, if the flow has the correct format and you are giving it to the "config" store of the controller you will get a 200. AFAIK there is no way of known in that transaction if the flow was installed correctly on the switch or not. If you wait for some time (up to 15 seconds, I believe) the controller should be polling the connected switches for stats. If the flow exists on the switch, then you can query the "operational" store to verify if the switch has the flow or not.

So, the work flow would be like this:

  1. push flow to controller via REST, and on success it will exist in the config store
  2. under the hood, the controller will then push the flow to the switch. on success it will exist in the switch.
  3. stats are collected in some polling cycle by the controller. Once the flow is on the switch, the polling cycle will see that flow and update the operational store.

If you want to know how long it takes for the flow to be seen in the operational store you will be limited by that polling cycle since it could be present on the switch for some period before the operational store is updated.

Nuno, if the flow has the correct format and you are giving it to the "config" store of the controller you will get a 200. AFAIK there is no way of known in that transaction if the flow was installed correctly on the switch or not. If you wait for some time (up to 15 seconds, I believe) 3 seconds by default) the controller should be polling the connected switches for stats. If the flow exists on the switch, then you can query the "operational" store to verify if the switch has the flow or not.

So, the work flow would be like this:

  1. push flow to controller via REST, and on success it will exist in the config store
  2. under the hood, the controller will then push the flow to the switch. on success it will exist in the switch.
  3. stats are collected in some polling cycle by the controller. Once the flow is on the switch, the polling cycle will see that flow and update the operational store.

If you want to know how long it takes for the flow to be seen in the operational store you will be limited by that polling cycle since it could be present on the switch for some period before the operational store is updated.

Once you have installed the controller and deployed the features that enable the openflow services you will find a config file in the distribution subfolder "etc/opendaylight/karaf/30-statistics-manager.xml" In that file you change the default from 3000ms (3s) to something smaller or larger as needed. I believe a restart of the controller is needed after changing that file, and that file will not be created until the feature(s) that use it are enabled.