[OPNFLWPLUG-699] Refactoring Device*Registry Created: 20/May/16  Updated: 27/Sep/21  Resolved: 20/May/16

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jozef Slezák Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5935

 Description   

DeviceFlowRegistry needs to be rebuild after FAILOVER.

Refactor 1/ Recreate DeviceFlowRegistry after failover (it should not be empty)
Refactor 2/ It is not enough to identify flow by FlowRegistryKey(tableId,priority,cookie). The match is mising. Try to lookup by (tableId,priority,cookie,match)
Refactor 3/ retrieveIdForFlow: If entry is missing there should lookup Inventory DS
Refactor 4/ Extract specific code for handling writing to operation DS only when stats are disabled.

  • DeviceContext.processFlowRemovedMessage()
  • org.opendaylight.openflowplugin.impl.device.DeviceContextImpl.processFlowRemovedMessage(FlowRemoved)
  • org.opendaylight.openflowplugin.impl.statistics.StatisticsGatheringUtils
  • SalFlowServiceImpl deviceFlowRegistry.markToBeRemoved()
    Refactor 5/ Nullobject implementaiton for specific code for handling writing to operation DS only when stats are enabled

 Comments   
Comment by Jozef Slezák [ 20/May/16 ]

Check the these refactoring rules also for DeviceGroupRegistry, DevicePortRegistry.

Generated at Wed Feb 07 20:33:09 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.