FTS3 is the service responsible for globally distributing the majority of the LHC data across the WLCG infrastructure. Is a low level data movement service, responsible for reliable bulk transfer of files from one site to another while allowing participating sites to control the network resource usage.
To ease the development of FTS3, we provide here a Vagrantfile. Using it should be straight forward, provided you have installed Vagrant and a provider (i.e. VirtualBox).
Once you have them installed, just run
vagrant upAnd ready to go. However, if you want to be able to compile the changes you make in your local copy (with your preferred IDE/editor), you may need to run
vagrant rsync-autoafter the instance is up. This will synchronize the files.
Note: Now the image is based on bento/centos, which by default installs Virtual Box Guest Additions, making unnecessary this command.
To enter the vagrant instace, just run on a separate shell
vagrant sshand you will be there. The source code will be under /vagrant. You should do the builds
somewhere else, though, since that folder is going to be synchronized, and you will lose
the artifacts and build configuration.
You can do the build in /home/vagrant/build, for instance.
cd /home/vagrant
mkdir build
cd build
cmake /vagrant/ -DALLBUILD=ON`
makeIf you want to get rid of the image, run vagrant destroy
- Web page: http://fts3-service.web.cern.ch/
- Documentation: http://fts3-docs.web.cern.ch/fts3-docs/docs/cli.html
- Developers guide: http://fts3-docs.web.cern.ch/fts3-docs/docs/developers.html
- Ticket handling in JIRA
- Continuous integration in Jenkins
- Monitored by the Dashboard
- For help, contact fts-support@cern.ch, or fts-devel@cern.ch