Ns-3.23: Difference between revisions

From Nsnam
Jump to navigation Jump to search
(start ns-3.23 page)
 
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{TOC}}
{{TOC}}


This page summarizes the release planning for ns-3.23 (tentatively May 2015).  The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].
This page summarizes the release planning for ns-3.23 (tentatively May 6 2015).  The ns-3 release process is listed [http://www.nsnam.org/developers/release-process/ here] and [[Release Process | here]].
 
= How you can help =


The release manager is [mailto:tomh@tomh.org Tom Henderson].  Please contact him if you would like to participate in any way in preparing the ns-3.23 release.
The release manager is [mailto:tomh@tomh.org Tom Henderson].  Please contact him if you would like to participate in any way in preparing the ns-3.23 release.
 
* If you are interested in testing a particular feature that is planned for ns-3.23, see the section on this page for [[Ns-3.23#Testing_repos | testing repos]].
If you are interested in testing a particular feature that is planned for ns-3.23, see the section on this page for [[Ns-3.23#Testing_repos | testing repos]].
* If you are interested in helping with a code review of a specific feature that you'd like to see in ns-3.23, please leave your comments on the code review pertaining to the [[Ns-3.23#New_features | feature of interest]].
 
* If you are interested to see that a specific bug be fixed, please email ns-developers mailing list, or the release manager.  You will probably be asked to help with creating a patch or testing an existing patch for that bug, if so.
If you are interested in helping with a code review of a specific feature that you'd like to see in ns-3.23, please leave your comments on the code review pertaining to the [[Ns-3.23#New_features | feature of interest]].
 
If you are interested to see that a specific bug be fixed, please email ns-developers mailing list, or the release manager.  You will probably be asked to help with creating a patch or testing an existing patch for that bug, if so.
 
= Release goals =
 
1) make a major dent in the [http://www.nsnam.org/bugzilla bug tracker].  Can we clean out most issues on our actively maintained modules, including closing out feature requests for which we do not have anyone working on them?
 
2) continue the transition to a [[BakeIntegration | more modular build system]].  While a major change to the build system is not planned for ns-3.22, one goal is to start to allow modules outside the core of ns-3 to be maintained in separate places, and integrated using the 'bake' tool (rather than merge everything into ns-3-dev).
* A proposal can be found at [[ns-3.22-build]]
 
3) finally try to implement [http://www.nsnam.org/docs/meetings/ns-3-developer-meeting-notes-May14.pdf Object Start/Stop]


= Release and development schedule =
= Release and development schedule =


ns-3.23 is planned for May 2015.  ns-3 makes roughly three releases per year (Dec/Jan, Apr/May, and Aug/Sept timeframes).
ns-3.23 was planned for Wednesday May 6 2015 but is likely to be released in the May 13 timeframe.   
* '''Release candidate''' (posted May 7):  http://www.nsnam.org/release/ns-allinone-3.23.rc1.tar.bz2


This means that we ought to get most new features and major changes into the simulator by April.
ns-3 makes roughly three releases per year (Dec/Jan, Apr/May, and Aug/Sept timeframes).


= Packaging =  
= Packaging =  
Line 41: Line 28:


A patch from ns-3.22 to ns-3.23 will also be posted.
A patch from ns-3.22 to ns-3.23 will also be posted.
Whether ns-3.23 is prepared in other packaging (e.g. Debian) would require a volunteer to prepare this.
Whether ns-3.23 will be distributed also as a [http://www.docker.com Docker container] would require a volunteer to prepare this.


= Release platforms =
= Release platforms =
Line 50: Line 33:
We usually try to keep pace with the latest popular versions of Linux, OS X, and FreeBSD.  For the ns-3.23 release, we plan to support the following systems and compilers:
We usually try to keep pace with the latest popular versions of Linux, OS X, and FreeBSD.  For the ns-3.23 release, we plan to support the following systems and compilers:


* OS X 10.10 Yosemite with latest Xcode
* OS X 10.10 Yosemite with latest Xcode (6.3)
* Ubuntu 14.04 and 15.04
* Ubuntu 14.04, 14.10, and 15.04
* Fedora 21
* Fedora 21
* Debian 7 (gcc-4.9)
* Debian 7 (gcc-4.9)
* FreeBSD 10 (clang 3)
* FreeBSD 10 (clang 3)
* CentOS 6.6 (gcc-4.4.7)
* CentOS 6.6 (gcc-4.4.7)
* others TBD


= Testing repos =
= Testing repos =
Some repositories, based on a recent copy of ns-3-dev, are available for testing specific features.
Some repositories, based on a recent copy of ns-3-dev, are available for testing specific features.


== Mobility Service Interface ==
== Mobility Service Interface ==
'''Note:''' inclusion of this code will slip to ns-3.24


Tiago Cerqueria has posted some code that uses Google Maps and Directions API to fetch waypoints for the ns-3 waypoint mobility model, corresponding to real-world routes provided by the service.  There is a testing repository available for this code (the patchset in https://codereview.appspot.com/176430044/ is too large to download from Rietveld).  To test, one must obtain an API key from Google, as described in the code review issue.  One must also have installed GeographicLib, xerces-cpp, libcurl, and libdl.
== Python 3 support ==
<pre>
Modifications to support [[Python3 Project | Python 3]] are available as part of a 2014 summer project, were planned for inclusion in this release cycle.
hg clone http://code.nsnam.org/ns-3-dev
cd ns-3-dev/src
hg clone http://code.nsnam.org/tomh/mobility-service-interface
cd mobility-service-interface
mkdir conf
# copy your API key to this conf directory as described here https://codereview.appspot.com/176430044/
cd ../../
./waf configure ...
</pre>
 
= New features =
 
Developers are working or planning to work on the following new features for ns-3.23.  '''Note:''' there is no guarantee that the features will be finished by the end of the year, so check back for progress/status.
 
=== Changes to the simulation core ===
 
* Shared RngStream (Peter Barnes)
** '''Synopsis:'''  Add API to allow multiple random variables to share an underlying RNG stream
** https://codereview.appspot.com/114060043/
** '''Status:'''  No change recently.
* Changes due to Object Start/Stop discussion held at [http://www.nsnam.org/docs/meetings/ns-3-developer-meeting-notes-May14.pdf May developers meeting].
* Changes to better support [[Ns-3_on_Visual_Studio_2012 | ns-3 on Windows Visual Studio]]
** https://codereview.appspot.com/8932044/
 
''' Others to be determined'''


=== Statistics ===
'''Note:''' This support will slip to ns-3.24 release cycle.


* Add a basic statistics collector, and convert some existing stats helpers in LTE and WiFi to use the statistics framework (Tom Henderson and Li Li)
= Pending repository changes =
** A staging repository (containing the BasicStatsCollector and other collector types) is being kept at http://code.nsnam.org/safe/ns-3.21-collector
** '''Status:''' Still under development.


=== Internet module ===
Developers are working or planning to work on the following new features for ns-3.23.  '''Note:''' there is no guarantee that the features will be finished by the end of the release cycle, so check back for progress/status.
 
* An implementation of MLDv2 for IPv6 (Krishna Teja Yadavalli and Tommaso Pecorella)
** http://www.nsnam.org/wiki/GSOC2014MulticastIPv6
** https://codereview.appspot.com/121680043/
 
A number of changes relate to supporting AQM and ECN.  This code may end up in the internet module or a new 'internet-queues' module.
* Move RED queue from network module to internet module
* pfifo_fast queue module
** Some code (lacking IPv6 support, and Sphinx documentation) is staged here:  http://code.nsnam.org/tomh/ns-3-dev-aqm/rev/4e1543dc9d68
* Explicit Congestion Notification
** Brian Swenson started to implement it here: http://code.nsnam.org/brian/ns-3-dev/diff/a9858c40b539/src/internet/model/red-queue.cc
* FQ-Codel and SFQ-Codel models (Anh Nguyen and Dave Taht)
** http://www.nsnam.org/wiki/GSOC2014Bufferbloat
** This will require some refactoring to allow AQM queues that need access to the IP and transport headers to get access at the layer at which ns3::Queue operates
 
'''Status:''' Tom Henderson is working on progressing the idea to add a TC sublayer, socialized by Natale Patriciello on the ns-developers list here:  http://mailman.isi.edu/pipermail/ns-developers/2014-November/012398.html
 
=== TCP ===
 
* TCP variants for satellite networks (Natale Patriciello)
** https://codereview.appspot.com/122010043/
 
The following were mentioned in the past but don't seem to be actively worked at the moment:
* RttEstimator improvements (Natale Patriciello)
* Multipath TCP ([mailto:M.Kheirkhah@sussex.ac.uk Morteza Kheirkhah Sabetghadam])


=== WiFi ===
=== WiFi ===
 
* Sebastien Deronne and Ghada Badawy are working on these bugs:
* MPDU aggregation for 802.11n ([mailto:sebastien.deronne@gmail.com Sebastien Deronne] and [mailto:gbadawy@gmail.com Ghada Badawy], and others)
** [https://www.nsnam.org/bugzilla/show_bug.cgi?id=2097  ACKs should be sent using legacy rates and preambles in 802.11n]
** https://codereview.appspot.com/164020043 (replacing previous review at https://codereview.appspot.com/14549044/)
** '''Status:''' Sebastien Deronne will soon post a testing repository for this feature.
* New power and rate control algorithms
** https://codereview.appspot.com/119130043
** '''Status:''' No change since code review.
 
=== Vehicular networks ===
 
'''status:''' There is a 'testing repository' available to test Scott's example and Junling's WAVE code; see [[Ns-3.22#Testing_repos]].
 
* WAVE for 802.11 vehicular networks (Scott Carpenter and Junling Bu)
** Finish off the 2013 GSoC code merging
* VANET example (Scott Carpenter)
** https://codereview.appspot.com/103470050/
* [[RoutesMobilityModel | Routes Mobility Model]] (Tiago Cerqueira)
 
=== Delay-tolerant networking ===
 
* Self-Delimiting Numeric Values (Dizhi Zhou and Ruben Martinez)
** https://codereview.appspot.com/97540043/
* Licklider Transport Protocol (Ruben Martinez)
* Bundle Protocol from SOCIS 2013 (Dizhi Zhou)
 
'''Status:''' Currently interoperability testing of ns-3 LTP with ltplib.
 
=== DSR ===
 
* LEAR extensions https://codereview.appspot.com/96130043/
'''Status:''' Tomasz is working on addressing the review comments
 
=== Epidemic Routing ===
* https://codereview.appspot.com/13831049/
 
'''Status:''' Still undergoing code review revisions.
 
=== UAN WOSS ===
* https://codereview.appspot.com/14677043/
 
=== Satellite models ===
* http://mailman.isi.edu/pipermail/ns-developers/2014-June/012071.html
 
'''Status:''' There hasn't been any recent activity so this will likely slip another release
 
== Software maintenance issues ==
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1900 Time arithmetic consistency]
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1868 Wstrict-overflow and gcc-4.9] (Tom Henderson and Peter Barnes)
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1941 Remove unnecessary dependency on Application module in other modules (1941)] Tommaso Pecorella
** Cleanup of remaining modules unnecessarily dependent on applications (aodv, mesh, olsr, lte)
 
== Documentation improvements ==
* [https://www.nsnam.org/bugzilla/show_bug.cgi?id=1490 improve documentation on linking ns-3 with other libraries] (Tom Henderson)
 
''others to be determined''

Latest revision as of 04:43, 8 May 2015

Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects

HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers

This page summarizes the release planning for ns-3.23 (tentatively May 6 2015). The ns-3 release process is listed here and here.

The release manager is Tom Henderson. Please contact him if you would like to participate in any way in preparing the ns-3.23 release.

  • If you are interested in testing a particular feature that is planned for ns-3.23, see the section on this page for testing repos.
  • If you are interested in helping with a code review of a specific feature that you'd like to see in ns-3.23, please leave your comments on the code review pertaining to the feature of interest.
  • If you are interested to see that a specific bug be fixed, please email ns-developers mailing list, or the release manager. You will probably be asked to help with creating a patch or testing an existing patch for that bug, if so.

Release and development schedule

ns-3.23 was planned for Wednesday May 6 2015 but is likely to be released in the May 13 timeframe.

ns-3 makes roughly three releases per year (Dec/Jan, Apr/May, and Aug/Sept timeframes).

Packaging

ns-3.23 will be packaged as a source tarball as before: ns-allinone-3.23.tar.bz2.

The tarball will contain:

  • Latest version of pybindgen
  • Latest version of netanim
  • ns-3.23
  • bake

where bake is used to fetch optional ns-3 components, including DCE.

A patch from ns-3.22 to ns-3.23 will also be posted.

Release platforms

We usually try to keep pace with the latest popular versions of Linux, OS X, and FreeBSD. For the ns-3.23 release, we plan to support the following systems and compilers:

  • OS X 10.10 Yosemite with latest Xcode (6.3)
  • Ubuntu 14.04, 14.10, and 15.04
  • Fedora 21
  • Debian 7 (gcc-4.9)
  • FreeBSD 10 (clang 3)
  • CentOS 6.6 (gcc-4.4.7)

Testing repos

Some repositories, based on a recent copy of ns-3-dev, are available for testing specific features.

Mobility Service Interface

Note: inclusion of this code will slip to ns-3.24

Python 3 support

Modifications to support Python 3 are available as part of a 2014 summer project, were planned for inclusion in this release cycle.

Note: This support will slip to ns-3.24 release cycle.

Pending repository changes

Developers are working or planning to work on the following new features for ns-3.23. Note: there is no guarantee that the features will be finished by the end of the release cycle, so check back for progress/status.

WiFi