Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • gh-pages
  • hot-failover
  • master default protected
  • master-green
  • master-prejava8
  • perf-test
  • release.asplus
  • release.asplus.bvs
  • revert-555-master
  • revert-559-revert-555-master
  • revert-594-master
  • v0.8
  • v0.82
  • v0.85
  • v0.90
  • v0.91
  • v1.0
  • v1.1
  • v1.2
  • wallaby
  • v1.2
  • v0.91
  • v1.1
  • v1.0
  • v0.90
  • v0.85
  • v0.82
  • v0.8
  • asplus-rc5
  • asplus-rc2
30 results
Created with Raphaël 2.2.029May262313121110130Apr272019181716138327Mar262019171615141312109327Feb20165420Jan1230Dec2925232221191817161512121Nov2018141310753131Oct3027261024Sep1615141129Aug27211917161514131211108765431Jul302818Jun21Apr20625Mar754228Feb1Mar30Dec205Nov30Oct17Sep756Aug222Jul1728Jun26252423222120191817141312111076543231May3029282726252423222120191817161514131211109876532130Apr2928272625Support masked flow mods inserted into the SFP via an OFFlowAdd. This is different from MatchUtils, since we have to put into the map with the SFP's column keys.Merge pull request #540 from oxisto/upstream/masterMerge pull request #537 from Pengfei-Lu/patch-2Merge pull request #543 from phpHavok/masterAdded a more useful toString() method.minor changes in variable name and description of flag to includesmall change in description for SEND_FLOW_REM flagadded option to add SEND_FLOW_REM flag into new flowmod messagesMerge pull request #536 from rizard/masterDelete FlowPusher.javaChange log level of ACL to debug for all logs except REST API. Info produces too much debug output for some of these, especially when the ACL is not being actively used.Added ability to specify the tables to receive table-miss flows for OF1.3+ switches. What we did before was insert these table-miss flows in all tables, which for OVS is 254 flows and not only is a waste of resources if the tables aren't being used, but also serverly clutters the REST API and Web UI output when listing flows. By default, the first 4 tables will receive the forward-to-controller table-miss flow. The reason for 4 is to account for a small number of software tables present on many hardware switches. If the actual number of tables is less, the lesser value will be used. To modify these settings, there are two options: (1) change the default for all switches or (2) specify the max tables to insert the table-miss flow on a per-DPID basis. These options are exposed in the floodlightdefault.properties file. Toy, no-op examples are given setting the default to 4 and two switches to 4 (the internal default is 4, thus it's a no-op). The list of switches and max tables should be given as a list of JSON key:value objects to the net.floodlightcontroller.core.internal.OFSwitchManager.maxTableToReceiveTableMissFlowPerDpid config variable. The default can be specified as an integer to the net.floodlightcontroller.core.internal.OFSwitchManager.defaultMaxTableToReceiveTableMissFlow variable.Merge pull request #535 from rizard/masterUpdated properties files to include more recent controller features (security, handshake, etc).Merge pull request #532 from rizard/masterSupport for OFTableFeatures messages. OpenFlowJ-Loxi bindings have been updated to support a variable pad (byte-aligned to 8 bytes) for each OFTableFeaturesProp list. Loxi has not been 'officially' updated yet though due to a lack of a C implementation. The handshake handler in Floodlight and the switch representations were also updated in order to support OFTableFeatures. By default, the features are requested for an OF1.3+ switch. They will be updated if they are reconfigured through a writeRequest() call IOFSwitch. To access table features, call getTableFeatures(TableId tableToGetFeaturesFor). They are exposed as a TableFeatures type, which more is more efficient than OFTableFeatures for frequent data accesses (especialy OFTableFeatureProp lists).Merge pull request #534 from FatRabiTree/masterFix Web UI link errorSpecify what to match on for Forwarding. This is a first step towards automatically adapting the match depending on what the switch requires for the flow to be in hardware.Merge pull request #526 from electricjay/patch-1Merge pull request #531 from Pengfei-Lu/patch-1Merge pull request #528 from rizard/masterUpdate floodlightdefault.propertiesFixed action serializer for actions that do not have values e.g. strip_vlan and such. Added in a 'n/a' value for the JSON key's value. Perhaps we should rethink how a list of actions is serialized to avoid the 'n/a' all together.update formatting of README.mdMerge pull request #525 from puneet2singh/patch-4v0.91v0.91Added Comment OFVendorStatistics.javaMerge pull request #523 from rizard/masterv1.1 v1.1v1.1 v1.1Update readmeMerge pull request #522 from rizard/masterFinally got around to fixing LearningSwitch.Merge pull request #519 from rizard/masterFixed issue where multipart flow replies would only show the last part/reply and not print the others. Only a REST API issue. This will also fix the Web UI where people reported not seeing all their flows.Merge pull request #521 from puneet2singh/patch-2Update OFVendorStatistics.javaModified slightly to track the specific initial state. If we were slave first, then we won't clear the flow table if we go to master for the first time.Added ability to customize start/role-transition behavior at the request of an individual a while ago. Using floodlightdefault.properties, you can specify if you want the controller to clear the flow tables of switches (1) upon inital handshake and transition to master or (2) upon every transition to master. Or you can not ever clear the tables if you want.Fix Firewall bug with getting in_port from Match vs from PI.Added ability to switch OF roles per DPID or for all switches at once. This includes a REST interface and integration with the handshake and channel handlers in order to keep the switch in the correct state. An IOFConnectionListener also has the ability to listen for messages that are written now instead of read from the wire. This allows modules to write role requests, have the underlying handshake/channel substrate tap in and listen to the request, and automatically update the role of the switch when the response comes back.fix typo in comment