GSOC2010OpenFlow - Revision history

Vedranm: Remove manual links and replace them with wiki links

2013-02-10T16:53:37Z

Remove manual links and replace them with wiki links

← Older revision		Revision as of 16:53, 10 February 2013
Line 57:		Line 57:
	*Started work on a more user-friendly interface for manipulating the SwitchNetDevice's flow table.		*Started work on a more user-friendly interface for manipulating the SwitchNetDevice's flow table.

	'''~~Midterm Report~~ [~~http://www.nsnam.org/wiki/index.php/~~GSOC2010OpenFlow/MidTermReport]'''		'''[[GSOC2010OpenFlow/MidTermReport\|Midterm Report]]'''

	'''7/12 -- Week 7 Milestones'''		'''7/12 -- Week 7 Milestones'''

Bhurd: /* Deliverables */

2010-08-10T00:20:45Z

Deliverables

← Older revision		Revision as of 00:20, 10 August 2010
Line 142:		Line 142:
	\|-		\|-
	\| src/devices/switch/wscript \|\| Waf building script for the OpenFlowSwitch module. It has two parts to it: build the OpenFlow C static library from the OFSID, and build the OpenFlowSwitch module itself. The first part adds all files from specific directories within the OFSID and compiles them into the library. The second part is similar to the building process of other modules/devices in ns-3, with create_ns3_module and ns3header for the .cc and .h files within the Switch module.		\| src/devices/switch/wscript \|\| Waf building script for the OpenFlowSwitch module. It has two parts to it: build the OpenFlow C static library from the OFSID, and build the OpenFlowSwitch module itself. The first part adds all files from specific directories within the OFSID and compiles them into the library. The second part is similar to the building process of other modules/devices in ns-3, with create_ns3_module and ns3header for the .cc and .h files within the Switch module.
			\|-
			\| src/devices/switch/README \|\| Documentation on how to set up the OFSID library, link it, and build ns-3 to activate the Switch module.
	\|-		\|-
	\| src/devices/switch/openflow/waf \|\| Once a copy of the OFSID is established somewhere in an "openflow" directory, copy this file to it to establish it as a waf project.		\| src/devices/switch/openflow/waf \|\| Once a copy of the OFSID is established somewhere in an "openflow" directory, copy this file to it to establish it as a waf project.
	\|-		\|-
	\| src/devices/switch/openflow/wscript \|\| Like above, once the "openflow" directory is established, copy this file to it to describe the waf project. Run "./waf configure" then "./waf build". Afterwards, you can configure ns3 with "./waf configure --with-openflow=path/to/openflow~~/build/default~~" and "./waf build" to link the OFSID library with ns-3 and activate the Switch module.		\| src/devices/switch/openflow/wscript \|\| Like above, once the "openflow" directory is established, copy this file to it to describe the waf project. Run "./waf configure" then "./waf build". Afterwards, you can configure ns3 with "./waf configure --with-openflow=path/to/openflow" and "./waf build" to link the OFSID library with ns-3 and activate the Switch module.
	\|}		\|}

Bhurd: /* Progress/Plan */

2010-08-10T00:19:35Z

Progress/Plan

← Older revision		Revision as of 00:19, 10 August 2010
Line 75:		Line 75:
	'''8/2 -- Week 10 Milestones'''		'''8/2 -- Week 10 Milestones'''
	*Released patch for review.		*Released patch for review.
	*Developed a system for downloading and building the OFSID library separate from ns-3 and linking to it. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow~~/build/default~~" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.		*Developed a system for downloading and building the OFSID library separate from ns-3 and linking to it. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.
	*Conclude the project.		*Conclude the project.

Bhurd: /* Progress/Plan */

2010-08-08T23:15:43Z

Progress/Plan

← Older revision		Revision as of 23:15, 8 August 2010
Line 75:		Line 75:
	'''8/2 -- Week 10 Milestones'''		'''8/2 -- Week 10 Milestones'''
	*Released patch for review.		*Released patch for review.
	*Developed a ~~method~~ for downloading and building the OFSID library separate from ns-3. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow/build/default" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.		*Developed a system for downloading and building the OFSID library separate from ns-3 and linking to it. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow/build/default" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.
	*Conclude the project.		*Conclude the project.

Bhurd: /* Progress/Plan */

2010-08-08T23:14:58Z

Progress/Plan

← Older revision		Revision as of 23:14, 8 August 2010
Line 75:		Line 75:
	'''8/2 -- Week 10 Milestones'''		'''8/2 -- Week 10 Milestones'''
	*Released patch for review.		*Released patch for review.
	*Developed ~~an effective, easy~~ method for downloading and building the OFSID library separate from ns-3. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow/build/default" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.		*Developed a method for downloading and building the OFSID library separate from ns-3. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow/build/default" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.
	*Conclude the project.		*Conclude the project.

Bhurd: /* Progress/Plan */

2010-08-08T23:14:22Z

Progress/Plan

← Older revision		Revision as of 23:14, 8 August 2010
Line 75:		Line 75:
	'''8/2 -- Week 10 Milestones'''		'''8/2 -- Week 10 Milestones'''
	*Released patch for review.		*Released patch for review.
	*~~Explore~~ the ~~OFSI STP (spanning tree protocol) implementation for possible use~~.		*Developed an effective, easy method for downloading and building the OFSID library separate from ns-3. Download the provided OFSID .tgz and extract it to wherever, naming the directory "openflow". Drop in the openflow/waf and openflow/wscript files from the patch into the "openflow" directory, run "./waf configure", then "./waf build" in the "openflow" folder. That will build the openflow library, and linking it is done with "./waf configure --with-openflow=path/to/openflow/build/default" then "./waf build" in the ns-3-dev (whatever you have named the root of the ns-3 distribution) directory.
	*Finish MPLS integration [it~~'s already started~~ in the ~~SwitchNetDevice; most of~~ the ~~work~~ will ~~be developing or downloading code for an ns3 understanding of MPLS~~, ~~such as an ns3::MplsLabelStack that can be detected on a Packet~~ and ~~utilized in the BufferFromPacket method]~~
	*Once MPLS is ~~integrated, create a second demo~~/~~test [~~in ~~addition to csma~~-~~switch.cc] for showing OpenFlow MPLS functionality~~.
	*Conclude the project.		*Conclude the project.

	'''Incomplete Milestones'''<br>		'''Incomplete Milestones'''<br>
	These are goals that may not make the final project, either due to current lack of feedback necessary to finish them, or not enough time in the scope of the project:		These are goals that may not make the final project, either due to current lack of feedback necessary to finish them, or not enough time in the scope of the project:
			*Adding OFSI's STP (spanning tree protocol) implementation.
			*Finishing MPLS integration and creating a demo/test for it showcasing the OpenFlow MPLS functionality. Note: No matter what, the OFSI's MPLS functionality limits the flow table matching to up to two MPLS labels. Labels deeper in the stack won't be matched.
	*Reestablishing the controller as a remote connection [installing it on another node so that different ns3 Channels/NetDevice connections can simulate the connection between the controller and the switch(es)]		*Reestablishing the controller as a remote connection [installing it on another node so that different ns3 Channels/NetDevice connections can simulate the connection between the controller and the switch(es)]
	*Adding simulated processing overheads other than the flow table lookup overhead.		*Adding simulated processing overheads other than the flow table lookup overhead.

Bhurd: /* Deliverables */

2010-08-08T23:06:30Z

Deliverables

← Older revision		Revision as of 23:06, 8 August 2010
Line 143:		Line 143:
	\| src/devices/switch/wscript \|\| Waf building script for the OpenFlowSwitch module. It has two parts to it: build the OpenFlow C static library from the OFSID, and build the OpenFlowSwitch module itself. The first part adds all files from specific directories within the OFSID and compiles them into the library. The second part is similar to the building process of other modules/devices in ns-3, with create_ns3_module and ns3header for the .cc and .h files within the Switch module.		\| src/devices/switch/wscript \|\| Waf building script for the OpenFlowSwitch module. It has two parts to it: build the OpenFlow C static library from the OFSID, and build the OpenFlowSwitch module itself. The first part adds all files from specific directories within the OFSID and compiles them into the library. The second part is similar to the building process of other modules/devices in ns-3, with create_ns3_module and ns3header for the .cc and .h files within the Switch module.
	\|-		\|-
	\| src/devices/switch/openflow \|\| A copy of an ~~OFSID~~. ~~This one has~~ the ~~MPLS extension built in~~, ~~a distribution that Ericsson researchers developed~~ to ~~propose an OpenFlow standard that includes MPLS capability~~. ~~There are many files within~~, and ~~documenting them would take a long time~~. ~~The grand majority aren't even used; the current abstraction uses wscript~~ to ~~build~~ the ~~necessary files into a C static~~ library~~, and the openflow~~-~~interface .h~~ and ~~.cc contain~~ the ~~code that utilizes this library. Consider this a black box of OpenFlow functionality~~.		\| src/devices/switch/openflow/waf \|\| Once a copy of the OFSID is established somewhere in an "openflow" directory, copy this file to it to establish it as a waf project.
			\|-
			\| src/devices/switch/openflow/wscript \|\| Like above, once the "openflow" directory is established, copy this file to it to describe the waf project. Run "./waf configure" then "./waf build". Afterwards, you can configure ns3 with "./waf configure --with-openflow=path/to/openflow/build/default" and "./waf build" to link the OFSID library with ns-3 and activate the Switch module.
	\|}		\|}

Bhurd at 21:37, 2 August 2010

2010-08-02T21:37:44Z

← Older revision		Revision as of 21:37, 2 August 2010
Line 1:		Line 1:
	This project will enable ns-3 simulations to use OpenFlow switches (McKeown et al.), widely used in research. OpenFlow switches are configurable via the OpenFlow API, and also have an MPLS extension for quality-of-service and service-level-agreement support. By extending these capabilities to ns-3 for a simulated OpenFlow switch that is both configurable and can use the MPLS extension, ns-3 simulations can accurately simulate many different switches.		This project will enable ns-3 simulations to use OpenFlow switches (McKeown et al. [http://doi.acm.org/10.1145/1355734.1355746]), widely used in research. OpenFlow switches are configurable via the OpenFlow API, and also have an MPLS extension for quality-of-service and service-level-agreement support. By extending these capabilities to ns-3 for a simulated OpenFlow switch that is both configurable and can use the MPLS extension, ns-3 simulations can accurately simulate many different switches.

	'''The Code Review is available here [http://codereview.appspot.com/1872049/show]'''		'''The Code Review is available here [http://codereview.appspot.com/1872049/show]'''
Line 145:		Line 145:
	\| src/devices/switch/openflow \|\| A copy of an OFSID. This one has the MPLS extension built in, a distribution that Ericsson researchers developed to propose an OpenFlow standard that includes MPLS capability. There are many files within, and documenting them would take a long time. The grand majority aren't even used; the current abstraction uses wscript to build the necessary files into a C static library, and the openflow-interface .h and .cc contain the code that utilizes this library. Consider this a black box of OpenFlow functionality.		\| src/devices/switch/openflow \|\| A copy of an OFSID. This one has the MPLS extension built in, a distribution that Ericsson researchers developed to propose an OpenFlow standard that includes MPLS capability. There are many files within, and documenting them would take a long time. The grand majority aren't even used; the current abstraction uses wscript to build the necessary files into a C static library, and the openflow-interface .h and .cc contain the code that utilizes this library. Consider this a black box of OpenFlow functionality.
	\|}		\|}

	~~== References ==~~

	Kurkowski, S., Camp, T., and Colagrosso, M. 2005. MANET simulation studies: the incredibles. SIGMOBILE Mob. Comput. Commun. Rev. 9, 4 (Oct. 2005), 50-61. DOI= http://doi.acm.org/10.1145/1096166.1096174

	McKeown, N., Anderson, T., Balakrishnan, H., Parulkar, G., Peterson, L., Rexford, J., Shenker, S., and Turner, J. 2008. OpenFlow: enabling innovation in campus networks. SIGCOMM Comput. Commun. Rev. 38, 2 (Mar. 2008), 69-74. DOI= http://doi.acm.org/10.1145/1355734.1355746

	== About Me ==		== About Me ==

Bhurd: /* References */

2010-08-02T21:36:29Z

References

← Older revision		Revision as of 21:36, 2 August 2010
Line 147:		Line 147:

	== References ==		== References ==

	~~Kohler, E., Morris, R., Chen, B., Jannotti, J., and Kaashoek, M. F. 2000. The click modular router. ACM Trans. Comput. Syst. 18, 3 (Aug. 2000), 263-297. DOI= http://doi.acm.org/10.1145/354871.354874~~

	Kurkowski, S., Camp, T., and Colagrosso, M. 2005. MANET simulation studies: the incredibles. SIGMOBILE Mob. Comput. Commun. Rev. 9, 4 (Oct. 2005), 50-61. DOI= http://doi.acm.org/10.1145/1096166.1096174		Kurkowski, S., Camp, T., and Colagrosso, M. 2005. MANET simulation studies: the incredibles. SIGMOBILE Mob. Comput. Commun. Rev. 9, 4 (Oct. 2005), 50-61. DOI= http://doi.acm.org/10.1145/1096166.1096174

	McKeown, N., Anderson, T., Balakrishnan, H., Parulkar, G., Peterson, L., Rexford, J., Shenker, S., and Turner, J. 2008. OpenFlow: enabling innovation in campus networks. SIGCOMM Comput. Commun. Rev. 38, 2 (Mar. 2008), 69-74. DOI= http://doi.acm.org/10.1145/1355734.1355746		McKeown, N., Anderson, T., Balakrishnan, H., Parulkar, G., Peterson, L., Rexford, J., Shenker, S., and Turner, J. 2008. OpenFlow: enabling innovation in campus networks. SIGCOMM Comput. Commun. Rev. 38, 2 (Mar. 2008), 69-74. DOI= http://doi.acm.org/10.1145/1355734.1355746

	Neufeld, M., Jain, A., and Grunwald, D. 2002. Nsclick:: bridging network simulation and deployment. In Proceedings of the 5th ACM international Workshop on Modeling Analysis and Simulation of Wireless and Mobile Systems (Atlanta, Georgia, USA, September 28 - 28, 2002). MSWiM '02. ACM, New York, NY, 74-81. DOI= http://doi.acm.org/10.1145/570758.570772

	== About Me ==		== About Me ==

Bhurd at 21:35, 2 August 2010

2010-08-02T21:35:07Z

← Older revision		Revision as of 21:35, 2 August 2010
Line 1:		Line 1:
	This project will enable ns-3 simulations to use OpenFlow switches (McKeown et al.), widely used in research. OpenFlow switches are configurable via the OpenFlow API, and also have an MPLS extension for quality-of-service and service-level-agreement support. By extending these capabilities to ns-3 for a simulated OpenFlow switch that is both configurable and can use the MPLS extension, ns-3 simulations can accurately simulate many different switches.		This project will enable ns-3 simulations to use OpenFlow switches (McKeown et al.), widely used in research. OpenFlow switches are configurable via the OpenFlow API, and also have an MPLS extension for quality-of-service and service-level-agreement support. By extending these capabilities to ns-3 for a simulated OpenFlow switch that is both configurable and can use the MPLS extension, ns-3 simulations can accurately simulate many different switches.

			'''The Code Review is available here [http://codereview.appspot.com/1872049/show]'''

	'''The OpenFlow software implementation distribution is hereby referred to as the OFSID.''' This is a demonstration of running OpenFlow in software that the OpenFlow research group has made available. There is also an OFSID that Ericsson researchers created to add MPLS capabilities; this is the OFSID currently included with the patch. The design of the patch will allow the users to, with minimal effort, switch in a different OFSID that may include more efficient code than a previous OFSID.		'''The OpenFlow software implementation distribution is hereby referred to as the OFSID.''' This is a demonstration of running OpenFlow in software that the OpenFlow research group has made available. There is also an OFSID that Ericsson researchers created to add MPLS capabilities; this is the OFSID currently included with the patch. The design of the patch will allow the users to, with minimal effort, switch in a different OFSID that may include more efficient code than a previous OFSID.

	'''The OFSID requires OpenSSL (for an SSL virtual connection), libxml2 (for MPLS FIB xml file parsing), libdl (for address fault checking), and boost (for assert) libraries to be installed. The Switch module does not use the code in the OFSID that uses OpenSSL, libxml2 and libdl. The code that uses OpenSSL is guaranteed to not be used in the Switch module, so you can delete the vconn-ssl.h{.c} from the OFSID to remove the dependency. When the project is finalized, libxml2 and libdl may no longer be required as well.~~'''~~		'''The OFSID requires OpenSSL (for an SSL virtual connection), libxml2 (for MPLS FIB xml file parsing), libdl (for address fault checking), and boost (for assert) libraries to be installed.''' The Switch module does not use the code in the OFSID that uses OpenSSL, libxml2 and libdl. The code that uses OpenSSL is guaranteed to not be used in the Switch module, so you can delete the vconn-ssl.h{.c} from the OFSID to remove the dependency. When the project is finalized, libxml2 and libdl may no longer be required as well.

	~~The Code Review is available here [http://codereview.appspot.com/1872049/show]~~

	== Current Issues/Questions ==		== Current Issues/Questions ==