BRITE integration with ns-3 - Revision history

Vedranm: Vedranm moved page Ns3 BRITE Integration to BRITE integration with ns-3: Wiki page name cleanup

2013-02-10T16:01:26Z

Vedranm moved page Ns3 BRITE Integration to BRITE integration with ns-3: Wiki page name cleanup

← Older revision	Revision as of 16:01, 10 February 2013
(No difference)

Jpelkey at 14:57, 4 March 2011

2011-03-04T14:57:25Z

@@ Line 1: / Line 1: @@
 {{TOC}}
 The Boston university Representative Internet Topology gEnerator ([http://www.cs.bu.edu/brite/ BRITE]) is a topology generation framework built with flexibility and extensibility in mind. By integrating this topology framework with ns-3, users will have the power to quickly and efficiently create large Internet topologies, while taking advantage of ns-3's simulation capabilities.
 = Project Goals =
 # The user will be able to easily leverage the power of BRITE within ns-3, in order to create and simulate large-scale Internet topologies.
 # Example ns-3 scripts will be provided to show use.
-# Several BRITE configuration examples will be run through ns-3's test-runner to ensure continued operation
+# Several BRITE configuration examples will be run through ns-3's test-runner to ensure continued operation.
 # Code documentation, including doxygen will be provided.
 # Manual section will be created to provide information on use and operation.
@@ Line 22: / Line 25: @@
 # http://code.nsnam.org/jpelkey3/ns-3-brite-modular/summary
-The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.
+The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Complete modularization to align with the new ns-3 modularization model remains, including integration with ./download.py to automatically download and build BRITE if enabled.
 == A note on BRITE seed files ==
 BRITE accepts a seed file to seed its psuedo-random number generator. It also spits out a new seed file after every run -- overwriting your old seed file -- in case you wish to randomize subsequent runs. Finally, it saves the most recently used seed file in a file called "last_seed_file." I didn't like the way this was done, specifically the overwriting bit, so I changed it in the ns-3 interface. You still pass in a seed file, but you also pass in another file for BRITE to write the new seed file. This keeps BRITE from overwriting your seed file. I believe this makes it easier to run the exact same simulation over and over. I think this is important. Finally, if you wish to overwrite the seed file each run, randomizing each subsequent run as before, you can simply pass in the same file name for the seed file and new seed file in ns-3.

Jpelkey at 21:40, 3 March 2011

2011-03-03T21:40:32Z

← Older revision		Revision as of 21:40, 3 March 2011
Line 24:		Line 24:
	The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.		The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.

	= A note on BRITE seed files =		== A note on BRITE seed files ==

	BRITE accepts a seed file to seed its psuedo-random number generator. It also spits out a new seed file after every run -- overwriting your old seed file -- in case you wish to randomize subsequent runs. Finally, it saves the most recently used seed file in a file called "last_seed_file." I didn't like the way this was done, specifically the overwriting bit, so I changed it in the ns-3 interface. You still pass in a seed file, but you also pass in another file for BRITE to write the new seed file. This keeps BRITE from overwriting your seed file. I believe this makes it easier to run the exact same simulation over and over. I think this is important. Finally, if you wish to overwrite the seed file each run, randomizing each subsequent run as before, you can simply pass in the same file name for the seed file and new seed file in ns-3.		BRITE accepts a seed file to seed its psuedo-random number generator. It also spits out a new seed file after every run -- overwriting your old seed file -- in case you wish to randomize subsequent runs. Finally, it saves the most recently used seed file in a file called "last_seed_file." I didn't like the way this was done, specifically the overwriting bit, so I changed it in the ns-3 interface. You still pass in a seed file, but you also pass in another file for BRITE to write the new seed file. This keeps BRITE from overwriting your seed file. I believe this makes it easier to run the exact same simulation over and over. I think this is important. Finally, if you wish to overwrite the seed file each run, randomizing each subsequent run as before, you can simply pass in the same file name for the seed file and new seed file in ns-3.

Jpelkey at 21:39, 3 March 2011

2011-03-03T21:39:32Z

← Older revision		Revision as of 21:39, 3 March 2011
Line 23:		Line 23:

	The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.		The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.

			= A note on BRITE seed files =
			BRITE accepts a seed file to seed its psuedo-random number generator. It also spits out a new seed file after every run -- overwriting your old seed file -- in case you wish to randomize subsequent runs. Finally, it saves the most recently used seed file in a file called "last_seed_file." I didn't like the way this was done, specifically the overwriting bit, so I changed it in the ns-3 interface. You still pass in a seed file, but you also pass in another file for BRITE to write the new seed file. This keeps BRITE from overwriting your seed file. I believe this makes it easier to run the exact same simulation over and over. I think this is important. Finally, if you wish to overwrite the seed file each run, randomizing each subsequent run as before, you can simply pass in the same file name for the seed file and new seed file in ns-3.

Jpelkey: /* Project Goals */

2011-03-03T21:32:50Z

Project Goals

← Older revision		Revision as of 21:32, 3 March 2011
Line 7:		Line 7:
	# The user will be able to easily leverage the power of BRITE within ns-3, in order to create and simulate large-scale Internet topologies.		# The user will be able to easily leverage the power of BRITE within ns-3, in order to create and simulate large-scale Internet topologies.
	# Example ns-3 scripts will be provided to show use.		# Example ns-3 scripts will be provided to show use.
	# ~~Test cases~~ will be ~~created~~ to ensure ~~proper~~ operation.		# Several BRITE configuration examples will be run through ns-3's test-runner to ensure continued operation
			# Code documentation, including doxygen will be provided.
	# Manual section will be created to provide information on use and operation.		# Manual section will be created to provide information on use and operation.

Jpelkey: /* Development Plan */

2011-03-02T21:37:11Z

Development Plan

← Older revision		Revision as of 21:37, 2 March 2011
Line 11:		Line 11:

	= Development Plan =		= Development Plan =
	For modularity, the BRITE source code will be separate from the ns-3 code. Within the ns-3-allinone directory, the download.py script will take care of downloading and building the BRITE source code should the user choose to use BRITE. During the ns-3 build process, if BRITE is enabled, the BRITE code will be linked with the ns-3 code. Within the src/~~contrib~~ directory, the ~~"brite" directory will exist which holds the topology~~ helper ~~(brite-topology-helper.cc/h)~~, examples, ~~and~~ test cases.		For modularity, the BRITE source code will be separate from the ns-3 code. Within the ns-3-allinone directory, the download.py script will take care of downloading and building the BRITE source code should the user choose to use BRITE. During the ns-3 build process, if BRITE is enabled, the BRITE code will be linked with the ns-3 code. Within the src/brite directory, the helper code, examples, test cases, and documentation will be provided.

	The heart of the ns-3/BRITE integration is contained within the topology helper. By passing in a BRITE configuration file to this helper, the topology is created with BRITE. This topology is initially incompatible with ns-3; however, the helper will use this initial topology generation to create the ns-3 topology. Once topology generation is completed, the user can install applications on the nodes within this topology and run the simulation.		The heart of the ns-3/BRITE integration is contained within the topology helper. By passing in a BRITE configuration file to this helper, the topology is created with BRITE. This topology is initially incompatible with ns-3; however, the helper will use this initial topology generation to create the ns-3 topology. Once topology generation is completed, the user can install applications on the nodes within this topology and run the simulation.

Jpelkey: /* Current Status */

2011-03-02T21:35:00Z

Current Status

← Older revision		Revision as of 21:35, 2 March 2011
Line 19:		Line 19:

	# http://code.nsnam.org/jpelkey3/BRITE/summary		# http://code.nsnam.org/jpelkey3/BRITE/summary
	# http://code.nsnam.org/jpelkey3/ns-3-brite/summary		# http://code.nsnam.org/jpelkey3/ns-3-brite-modular/summary

			The integration is nearly complete. Users can use the ns-3 BRITE interface to generate ns-3 topologies using BRITE configuration files. An ns-3 example has been provided in src/brite/examples to show its usage. Test cases and complete modularization to align with the new ns-3 modularization model remain.

Jpelkey: Created page with '{{TOC}} = Overview = The Boston university Representative Internet Topology gEnerator ([http://www.cs.bu.edu/brite/ BRITE]) is a topology generation framework built with flexibi…'

2010-11-04T17:12:07Z

Created page with '{{TOC}} = Overview = The Boston university Representative Internet Topology gEnerator ([http://www.cs.bu.edu/brite/ BRITE]) is a topology generation framework built with flexibi…'

New page

{{TOC}}

= Overview =
The Boston university Representative Internet Topology gEnerator ([http://www.cs.bu.edu/brite/ BRITE]) is a topology generation framework built with flexibility and extensibility in mind. By integrating this topology framework with ns-3, users will have the power to quickly and efficiently create large Internet topologies, while taking advantage of ns-3's simulation capabilities.

= Project Goals =
# The user will be able to easily leverage the power of BRITE within ns-3, in order to create and simulate large-scale Internet topologies.
# Example ns-3 scripts will be provided to show use.
# Test cases will be created to ensure proper operation.
# Manual section will be created to provide information on use and operation.

= Development Plan =
For modularity, the BRITE source code will be separate from the ns-3 code. Within the ns-3-allinone directory, the download.py script will take care of downloading and building the BRITE source code should the user choose to use BRITE. During the ns-3 build process, if BRITE is enabled, the BRITE code will be linked with the ns-3 code. Within the src/contrib directory, the "brite" directory will exist which holds the topology helper (brite-topology-helper.cc/h), examples, and test cases.

The heart of the ns-3/BRITE integration is contained within the topology helper. By passing in a BRITE configuration file to this helper, the topology is created with BRITE. This topology is initially incompatible with ns-3; however, the helper will use this initial topology generation to create the ns-3 topology. Once topology generation is completed, the user can install applications on the nodes within this topology and run the simulation.

= Current Status =
Two repositories exist for BRITE integration with ns-3. First is the BRITE code itself, slightly modified to work with ns-3. Second is the ns-3-brite repository where the BRITE toplogy helper, examples, and test cases will exist.

# http://code.nsnam.org/jpelkey3/BRITE/summary
# http://code.nsnam.org/jpelkey3/ns-3-brite/summary