Ns-3.24

From Nsnam
Jump to navigation Jump to search

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.24 (August 2015). The ns-3 release process is listed here and here.

The release manager is Tom Henderson. Please contact if you would like to participate in any way in preparing the ns-3.24 release, or helping to manage a future release.

  • If you are interested in testing a particular feature that is planned for ns-3.24, 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.24, 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 goals

1) Python 3 support for at least the basic waf and test.py operations; see the Python3 page.

2) continue the transition to a more modular build system. While a change away from the Waf build system is not planned for ns-3.24, 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).

3) finally try to implement Object Start/Stop; Vedran is working on a patch

4) Add new features as they become ready. In particular, finish inclusion of previous summer project code, including SOCIS 2013 and 2014 code (Bundle Protocol, TCP satellite extensions), Google Summer of Code (MLDv2, AQM queues FqCoDel and SfqCoDel), and 2014 mentored projects (Mobility Service Interface, and Python 3 support).

Release and development schedule

ns-3.24 is planned for August 2015; exact date TBD. ns-3 makes roughly three releases per year (Dec/Jan, Apr/May, and Aug/Sept timeframes).

This means that we ought to get most new features and major changes into the simulator by late July.

More detailed scheduling is TBD once the release date is set. In general:

  • one or more release candidates will be posted in the week prior to the actual release
  • new features should be merged several weeks in advance of the release date

Feature and patch review status

This table is meant to put review items for merge to ns-3-dev on a schedule. Maintainers of a module can commit changes as they see fit (i.e. without going through review for everything), but for proposals that seek or need a review, we should try to allow a default of 1 week review time before the release manager or a maintainer commits the change.

Features or patches under review
Contribution Module Review deadline Status Link
TCP L4 Protocol internet June 22 pending resolution of final review comments https://codereview.appspot.com/244350043/
Collectors for data collection stats June 25 pending review comments http://codereview.appspot.com/245260043
WiFi run-time fragmentation wifi June 26 pending tracker comments https://www.nsnam.org/bugzilla/show_bug.cgi?id=730
WiFi propagation frequency wifi June 26 pending tracker comments https://www.nsnam.org/bugzilla/show_bug.cgi?id=2122
UDP ShutdownRecv bug internet July 1 pending tracker comments https://www.nsnam.org/bugzilla/show_bug.cgi?id=2124

Packaging

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

Other details (other formats, etc.) are for further study.

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

Whether ns-3.24 is prepared in other packaging (e.g. Debian) would require a volunteer to prepare this.

Whether ns-3.24 will be distributed also as a Docker container would require a volunteer to prepare this.

Release platforms

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

TBD

Testing repos

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

Mobility Service Interface

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.

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 ...

New features

Developers are working or planning to work on the following new features for ns-3.24.

Note: there is no guarantee that the features will be finished by the end of the release cycle, so check back for progress/status.

Energy Enhancements (Cristiano Tapparello)

Cristiano plans several additions:

  • New models for energy sources, converters, predictors, and sensor models (code to be posted soon)
  • LithiumIonEnergySource helper
  • RVBatteryModel bug fixes

DSR

Status: Tomasz is working on addressing the review comments (no update recently)

Epidemic Routing

Status: Still undergoing code review revisions.

UAN WOSS

Satellite models

Statistics

Enhancements to data collection framework are planned to enable more flexible configuration of time series, time avearge, and asynchronous event plotting (Li Li, Felipe Perrone, Tom Henderson).

TCP

  • Some of the TCP variants for satellite networks (Natale Patriciello) will be merged soon
  • RttEstimator improvements (Natale Patriciello)
    • Resolve bug 1412 RttEstimator to network module

Software maintenance issues

Status: No change on the above lately.