|
|
| (60 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| | {{TOC}} | | {{TOC}} |
| | | | |
| − | This page is a brief summary of current development activities for ns-3. If you want to participate in any stages of the below development activities, please email the contacts listed below, or the ns-developers list.
| + | see the [[Current_Development]] page |
| − | | + | |
| − | __FORCETOC__
| + | |
| − | | + | |
| − | == Release process ==
| + | |
| − | | + | |
| − | ns-3 releases are based on date-driven schedules: rather than target a set of features for a specific version number, we aim instead for a release date and ship whatever is ready by that date. If a cool new feature misses that date, it is not a big deal because the next release is never too far away. Because the project is currently still under some heavy flux where a lot of APIs still change, the current interval between releases is expected to be roughly one month. We expect that interval to increase to 3 or 4 months once the core of the simulator has stabilized sufficiently.
| + | |
| − | | + | |
| − | The roadmap below is tentative. That is, the goal is to document what we would like to see in a number of releases, but, of course, since this is an Open Source project, contributors are free to work on anything they are interested in and try to merge it in earlier than stated. If we feel a specific feature targeted to a specific release just won't make it in time, we will move that feature to the next release.
| + | |
| − | | + | |
| − | Some of the items in this roadmap do not have anyone signed up to get work done on them. So, there is something you are interested in, ask on ns-developers.
| + | |
| − | | + | |
| − | Detailed steps for doing the source code release are found in the [http://code.nsnam.org/ns-3-dev/file/1e8249c58fda/doc/release_steps.txt doc/release_steps.txt] file in the ns-3-dev repository.
| + | |
| − | | + | |
| − | === Deadlines ===
| + | |
| − | | + | |
| − | There are a few deadlines and steps for incorporating code into a scheduled ns-3 release:
| + | |
| − | | + | |
| − | * '''(15 days prior)''' deadline for posting any patches or private repos that are solicited for review/comment, for possible check in to the upcoming release. These are for patches or repos that can be considered as extensions to the simulator. Post a summary to the list, allow 7 days (minimum) for comments, and if all comments and issues can be resolved in that time window, it can go into the next release; otherwise it slides until when things are resolved.
| + | |
| − | * '''(7 days prior)''' deadline for being in a "ready-to-merge" state, which means that there is agreement that comments from the previous stage have been resolved and that the change can go in. Perhaps a "last-call" announcement by the release manager on the list will help.
| + | |
| − | * '''(3 days prior)''' deadline for merging any extensions or new modules that change the API, or any miscellaneous changes by maintainers. Exceptions: critical bug fixes, doxygen and documentation, and coding style alignment nits.
| + | |
| − | | + | |
| − | Finally, it is good practice to announce among the active committers when you are doing a major merge, to avoid bad merge collisions.
| + | |
| − | | + | |
| − | == Release schedule ==
| + | |
| − | | + | |
| − | ns-3 is still in a pre-alpha state, with monthly development releases. We are aiming for an ns-3.1 release in mid-June 2008.
| + | |
| − | | + | |
| − | === May 1, 2008 (ns-3.1-beta) ===
| + | |
| − | | + | |
| − | The following items are candidates for merge into the next release, although merge is dependent on resolving outstanding comments during the release process.
| + | |
| − | | + | |
| − | # '''Python bindings'''
| + | |
| − | #* ''summary'': Python bindings for the ns-3 API, to enable Python scripting
| + | |
| − | #* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-January/003608.html
| + | |
| − | #* ''code location'': http://code.nsnam.org/gjc/pybindgen-notracing
| + | |
| − | #* ''status'': Awaiting stabilization of the APIs before finalizing; probably a May or June merge.
| + | |
| − | #* Here are more details from [http://gjcarneiro.blogspot.com/2007/05/python-bindings-generator.html Gustavo's blog]
| + | |
| − | #* [[NS-3 Python Bindings|Instructions]]
| + | |
| − | #:
| + | |
| − | # '''logging enhancements'''
| + | |
| − | #* ''summary'': refine NS_LOG functionality
| + | |
| − | #* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003974.html
| + | |
| − | #* ''code location'': http://code.nsnam.org/mathieu/ns-3-log
| + | |
| − | #* ''status'': Will merge after discussion concludes
| + | |
| − | #:
| + | |
| − | # '''attribute documentation and configuration generator'''
| + | |
| − | #* ''summary'': cause attributes and trace sources to be automatically documented in Doxygen
| + | |
| − | #* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003950.html
| + | |
| − | #* ''code location'': http://code.nsnam.org/mathieu/ns-3-doc
| + | |
| − | #* ''status'': Will merge after discussion concludes
| + | |
| − | #:
| + | |
| − | | + | |
| − | === June 15, 2008 (ns-3.1) ===
| + | |
| − | | + | |
| − | In general, ns-3 is trying to finalize the API including final revisions to the object model, to the default value system, and to higher-level topology/scenario code.
| + | |
| − | | + | |
| − | An initial strawman for the ns-3.1 release is discussed in [http://mailman.isi.edu/pipermail/ns-developers/2008-April/003993.html this thread].
| + | |
| − | | + | |
| − | == Code proposals under review or development ==
| + | |
| − | | + | |
| − | This section is intended to summarize code proposals under active discussion on the mailing list.
| + | |
| − | | + | |
| − | The following repositories are being actively worked on, but not scheduled for merge anytime soon:
| + | |
| − | | + | |
| − | # '''ns-3 real time scheduler'''
| + | |
| − | #* ''summary'': Add support for various forms of emulation
| + | |
| − | #* ''ns-developers post'': none yet
| + | |
| − | #* ''code location'': http://code.nsnam.org/craigdo/ns-3-emu
| + | |
| − | #* ''status'': Working on emulation code (libnet and pcap integration) and user-space threads
| + | |
| − | #:
| + | |
| − | # '''ns-3 synchronous posix/socket API'''
| + | |
| − | #* ''summary'': Add support for various forms of emulation
| + | |
| − | #* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2008-April/003912.html
| + | |
| − | #* ''code location'': http://code.nsnam.org/mathieu/ns-3-simu
| + | |
| − | #* ''status'': Under list discussion
| + | |
| − | #:
| + | |
| − | | + | |
| − | == Future releases ==
| + | |
| − | | + | |
| − | The following are additional things that various developers are working on, plan to work on, or have brought to a prototype state. (Please keep this brief and add pointers to other pages if there is a lengthy description).
| + | |
| − | | + | |
| − | === Statistics ===
| + | |
| − | | + | |
| − | George Riley(riley@ece.gatech.edu) and Mathieu Lacage (mathieu.lacage@sophia.inria.fr) are the contacts for this development.
| + | |
| − | | + | |
| − | One of the important design goals of the ns-3 tracing framework was to allow users to hook their own online statistic analysis code into trace hooks to avoid having to spew gigabytes of trace files only to post-process them later.
| + | |
| − | | + | |
| − | We thus need a framework to make it easy and safe for users to calculate basic network-specific values in the system such as:
| + | |
| − | * RTT
| + | |
| − | * Throughput
| + | |
| − | * inter-arrival time
| + | |
| − | * ...
| + | |
| − | | + | |
| − | Furthermore, it should be trivial to efficiently calculate basic statistical properties on these collected measurements:
| + | |
| − | * Average with standard deviation. Arbitrary confidence interval ?
| + | |
| − | * Cumulative distribution of a variable. i.e., the EDCF.
| + | |
| − | * ...
| + | |
| − | | + | |
| − | A serious Statistics project should thus first refine the list of variables we want to measure. It should also attempt to define as precisely as possible the type of statistical tools which should be made available for these variable measurements or other types of measurements.
| + | |
| − | | + | |
| − | Once this initial discussion has take place, we should be able to design an API for these features and implement it for a specific ns-3 release. If you believe that you can contribute useful input to this discussion, do not hesitate to join ns-developers to talk about it.
| + | |
| − | | + | |
| − | === Traffic generation applications ===
| + | |
| − | | + | |
| − | George Riley (riley@ece.gatech.edu) is overseeing the porting of application models from [http://www.ece.gatech.edu/research/labs/MANIACS/GTNetS/ GTNetS] to ns-3.
| + | |
| − |
| + | |
| − | === 802.11 PHY cleanup ===
| + | |
| − | | + | |
| − | Mathieu Lacage (mathieu.lacage@sophia.inria.fr) is working on 802.11 PHY cleanup to simplify addition of other 802.11 PHY models.
| + | |
| − | | + | |
| − | === Wireless routing protocol infrastructure ===
| + | |
| − | | + | |
| − | Wireless routing protocol infrastructure for mobile wireless networks. Contact: Mathieu Lacage (mathieu.lacage@sophia.inria.fr)
| + | |
| − | | + | |
| − | === Removing traffic generation from applications class ===
| + | |
| − | | + | |
| − | #* ''summary'': Proposed decoupling to generalize applications
| + | |
| − | #* ''ns-developers post'': http://mailman.isi.edu/pipermail/ns-developers/2007-July/003136.html
| + | |
| − | #* ''code location'': http://code.nsnam.org/laprisee/ns-3-mp/
| + | |
| − | #* ''status'': Was under discussion in the summer.
| + | |
| − | #:
| + | |
