History

Sprint 4¶

Background:¶

InContext developed stages 1 to 3 of a portal to record experiment runs and results.

The version form the end of sprint 3 has been installed on norbit for internal testing.

Develop a new state tracker class, with custom fields per ticket. --> only one tracker
Add support for multiple testbeds: iREEL and Wireless --> done even not in used currently
Uploading of scripts from MyPage wiki, or by New Experiment --> done and liked to a git repository
Add a calendar to the experiment page, for scheduling runs --> modified ireel script can run experiment
Change from git to a simple filesystem to manage versions: --> No
'experiment version x.y' maps to 'X/Y/experiment_name'
Students will use their redmine wiki page as a lab notebook. Create an easy way to reference experiments from the wiki. --> when creating a account a new subproject is created therefore the student is granted a full administration right on his private sub-project
Implement the scheduling user interface. It will be tested against Guillaume's simple FIFO scheduler as a back-end --> done
Integrate visualisation of the results, which is implemented as a service in the back-end. --> visualisation done through the use of the dygraph javascript
Portal fetches the graph, probably using jquery, and displays it.
Finally, if time permits, an accounting function may be added. --> need to be done
The reservation class will save its data to disk. The accounting function is just a display of historical reservations.

clear the interface of the portal, migrate the documentation and files in mytestbed.net
- done, need to finish the documentation and update the git repo
provide an access control for the saving and versionning system
more choice for the topology
- done
single vs multiple repository for experiments?
Transmission to the repository at the end of the experiment, this will be integrated within the EC
Creation of new experiments with log/script/measurement