OFELIA Control Framework was originally born to manage OFELIA FP7 facility. Today the main directions and decisions over the development of the software are still very OFELIA driven, since it is the creator and major contributor. Nevertheless, the design of the OCF allows it to be used to manage different facilities, doing the proper extensions, which are basically developing the required Resource Managers for the equipment in the testbed.
In order to foster the use and development of the control framework we have moved the OCF’s public repository to Github and been working on some more improvements. Check them out at next lines…
Soon after the public opening of the OFELIA facility to the research community, a first attempt to provide the source code of its control software was carried out, although not that successfully. A new public respository, forked from the private internal one was created and made available at codebasin. Nevertheless, the site did not count with the required visibility or development tools, making it only a site from where downloading the code.
Having learned from the experience, the DANA team in charge of the OCF’s development decided a better strategy needed to be planed to put in place the necessary tools that help to create a development community around the OCF.
Following these directions several steps were done:
- The internal repository was forked and totally cleaned up. This supposed making the size of the repository VERY MUCH lighter by cleaning the log history, deleting old experimental branches and refactoring part of the code.
- From this new internat repository, a public one was forked and hosted in Github. Everyone can download this repository in an only-readable mode in order to deploy the OCF in its facility or work with it. In addition, the source code tarball is also available for download in the dedicated site.
- In addition, the official channels of documentation, manuals, wiki and issue tracker were migrated to Github, making them all available to the community.
This is still work in progess, but it looks quite well. You can check it at the OCF Github’s page.
For already existing installations of the OCF the migration to these new repositories will be automatically performed by tools provided. For both cases of an internall OFELIA installation or external installation using the old codebasin repository or tarball, the upgrade process will be done by the ofver tool which will update the code at the time the new repositories are set up, doing it completely transparent to the user.
We hope that centralizing the development tools and the documentation in a unique place, although maintaining the separation and privileges of the two repositories (internal/public), the community, already composed by people from OFELIA-FP7, FIBRE-FP7 and GEANT’s task JRA2T5, can benefit from a much more clear information at the time they can report bugs, new features and provide with enhancements of the source code.