Getting the source¶
Perhaps the easier way to obtain the sources is to download them from here.
The code is publicly available in a git reopository. It is the one shown here. It should be reasonably stable (no rebase). You can clone it as follows.
$ git clone git://git.mytestbed.net/oml.git
The master branch is the development branch, and might include features that are not as well tested as the release branches.
We also have a staging branch, which contains additional patches to be tested before inclusion into the master branch of the public repository. This branch might be broken or otherwise defective, but it gives an insight into what's coming. Also, it allows for early code to be put out and tested. If you are running staging versions of OML, with and/or without success, let us know!
Any commit to the staging branch of this repository will trigger a build on our internal Jenkins instance to make sure nothing (build or test) is broken. You might receive emails if your changes broke the build; otherwise they will start their way towards the master branch.
If you want to get the source of the OML Applications, you can clone our separate applications repository in the same way.
$ git clone git://git.mytestbed.net/oml-apps.git
Our instrumented Iperf has its own project and repository. The source can be fetched as
$ git clone git://git.mytestbed.net/iperf.git
Make sure to work off branch
oml/master, which is the instrumented tip.
masteris a mirror of the upstream iperf SVN.
Have a look at the OML Applications sub-project page for more information.
Note: if you just want to create your own applications that use OML, you don't need the source code. See Client Programming to learn how.