FlowConfig to only run syntactic validation 63/5463/1
authorAlessandro Boch <aboch@cisco.com>
Tue, 25 Feb 2014 02:03:34 +0000 (18:03 -0800)
committerAlessandro Boch <aboch@cisco.com>
Tue, 25 Feb 2014 19:02:14 +0000 (11:02 -0800)
commit91d7e02667138a10df0dc5666cf177375f2ff4c4
treed9251d02f21f81b4017f9d05a11e960b6dda10eb
parent0aa213fe3642365828fdd4de07bf5673429dc5eb
FlowConfig to only run syntactic validation

- The validate function of FlowConfig class should only run syntactic validation
  The opearational validation like input/output/enqueue port presence, flood
  action on non default container check, etc. should be run only at installation
  time. Also this validation should be run for all the flow installation requests
  either they come from static flow config or from Flow Entry install/modify
  request coming from other bundles.
- With the above change at controller restart, static flow configurations which
  were valid at controller stop but no longer after reboot (for ex. switch sdn
  enabled ports have changed) will still show on the Flow GUI as non installed,
  and their toggling with fail with proper message.

Change-Id: I49d97af49d58102e51a3c8c12db915b60bcb6f4b
Signed-off-by: Alessandro Boch <aboch@cisco.com>
opendaylight/forwardingrulesmanager/api/src/main/java/org/opendaylight/controller/forwardingrulesmanager/FlowConfig.java
opendaylight/forwardingrulesmanager/api/src/test/java/org/opendaylight/controller/forwardingrulesmanager/frmTest.java
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java