* Minor refactoring in the original FlowManager logic when setting
the Flow Entry Switch State (for new Flow Entries):
- The appropriate state is not hardcoded anymore inside class
FlowDatabaseOperation. Instead, it is explicitly set by the caller method.
* Add new method FlowManager::pushModifiedFlowEntries() that is used
by the PathComputation to push the modified flow entries to the switches
controlled by this instance.
Eventually, this method will be one that needs to be
modified/refactored/adjusted to use the forthcoming FlowSynchronizer module.
For now, the method is disabled, so it doesn't conflict with the
existing FlowManager mechanism.
diff --git a/src/main/java/net/onrc/onos/ofcontroller/flowmanager/FlowDatabaseOperation.java b/src/main/java/net/onrc/onos/ofcontroller/flowmanager/FlowDatabaseOperation.java
index 5bc35d2..d06c62c 100644
--- a/src/main/java/net/onrc/onos/ofcontroller/flowmanager/FlowDatabaseOperation.java
+++ b/src/main/java/net/onrc/onos/ofcontroller/flowmanager/FlowDatabaseOperation.java
@@ -309,7 +309,7 @@
flowEntryObj.setUserState("FE_USER_MODIFY");
else
flowEntryObj.setUserState("FE_USER_ADD");
- flowEntryObj.setSwitchState("FE_SWITCH_NOT_UPDATED");
+ flowEntryObj.setSwitchState(flowEntry.flowEntrySwitchState().toString());
//
// TODO: Take care of the FlowEntryErrorState.
//