- Jul 28, 2014
-
-
Ryan Izard authored
-
- Jun 18, 2014
-
-
Ryan Izard authored
Refactored structure of core components to work with openflowj-loxi. Presently refactoring Routing, Firewall, Forwarding, DeviceManager, LinkDiscovery, Topology, and LearningSwitch. Hub has been refactored.
-
- Apr 21, 2014
-
-
Jason Parraga authored
Issue#447
-
hwchiu authored
-
- Apr 20, 2014
- Apr 06, 2014
-
-
Jason Parraga authored
Update Cluster.java
-
Jason Parraga authored
added override for port value in FallbackCCProvider
-
- Mar 25, 2014
-
-
Rakurai authored
Removed redundant code that added new link set mappings to the instance hashmap.
-
- Mar 07, 2014
-
-
Ayaka Koshibe authored
amend to PR #443
-
- Mar 06, 2014
-
-
Jason Parraga authored
added exception handling for the device curl call in the circuitpusher app.
-
- Mar 04, 2014
-
-
subh authored
-
- Mar 02, 2014
-
-
hwchiu authored
-
Jason Parraga authored
List ports on virtual network
-
- Mar 01, 2014
-
-
Jason Parraga authored
Make Firewall POST method return the ruleid
-
hwchiu authored
-
- Feb 28, 2014
- Dec 30, 2013
-
-
Jason Parraga authored
Redundant_type_cast
-
- Dec 20, 2013
-
-
Rémy Léone authored
-
- Nov 05, 2013
-
-
Jason Parraga authored
Restore computeEntryCookie() functionality
-
- Nov 04, 2013
-
-
tamihiro authored
-
- Oct 30, 2013
-
-
Jason Parraga authored
Fix packet tracer API
-
Sovietaced authored
-
- Sep 17, 2013
-
-
Jason Parraga authored
add match method in OFMatch
-
- Sep 07, 2013
-
-
Jason Parraga authored
Makes Floodlight's Static Flow Pusher compliant with RFC 2616
-
- Sep 05, 2013
-
-
Henrique Rodrigues authored
This commit removes the StaticFlowEntryStoreResource as discussed in the pull messages at: https://github.com/floodlight/floodlight/pull/420
-
Henrique Rodrigues authored
Floodlight's Static Flow Pusher REST interface expects "posted data" for DELETE requests. It uses this posted data to identify which entry should be deleted. However, the RFC 2616 states that resources to be deleted using the DELETE method should be identified by a URI (not by posted data): http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7 This is a problem when you try to use a spec-compliant framework to communicate with the REST interface provided by StaticFlowEntryPusher module. The Restlet framework, that is being used in the implementation of the module itself, is an example. It prevents you from posting data with a DELETE method, according to what is specified in the HTTP1.1 RFC.
-
- Aug 06, 2013
-
-
CodingCat authored
-
Jason Parraga authored
-
- Aug 02, 2013
-
-
Rob Adams authored
Add a logback-test.xml default logging config for good measure to hide the SyncManager log spam at debug level
-
- Jul 22, 2013
-
-
Jason Parraga authored
Fixed floodlight default properties file
-
- Jul 17, 2013
-
-
Jason Parraga authored
-
- Jun 28, 2013
-
-
Jason Parraga authored
Floodlight subtree merge
-
Sovietaced authored
-
- Jun 26, 2013
-
-
Vishnu Emmadi authored
-
Jason Parraga authored
Issue #406 continued
-
Saurav Das authored
1) Ability to ask for last N events 2) Events now show up with most-recent-first 3) Including ThreadName as one of the columns 4) Ensuring moduleName and eventNames in URL do not include '/' 5) Removing dead code in Event.java 6) Updating unit tests
-
Saurav Das authored
accomodating the CLI)
-
Sovietaced authored
-