1. Supporting federation with the jFed framework Wim Vandenberghe, Brecht Vermeulen - iMinds Pre-FIA Workshop – Testbed Interoperability Athens, March 17th 2014

2. jFed http://jfed.iminds.be Written in Java(FX) MIT license Test and monitor federation aspects Current focus SFA, additional APIs can be added in the future jFed low level library jFed probejFed probe CLI jFed automated tester jFed automated tester CLI jFed UI High level library

3. 3 jFed parts Probe ◦ Probe individual functions of APIs ◦ Also CLI version (allows integration of Probe in other federation services, e.g. F4F FLS) Automated testing ◦ Scenarios of API calls (which can use information of previous calls) ◦ Also CLI version: (allows integration of Automated testing in other federation services, e.g. F4F daily full login test) UI ◦ Experimenter tool ◦ Abstracts as much of the SFA details as possible from the experimenter

4. 4 Compiling Uses maven: mvn package Or use pre-compiled jars or java webstart on http://jfed.iminds.be http://jfed.iminds.be ◦ Recent Java 7 install required ◦ Mac OS X users: check settings on the website!

5. jFed probe: manual testing + API learning

6. 6 jFed probe CLI java -jar /work/monitoring/jfed/jfed-probe-cli.jar usage: jfed-probe-cli [options... ] [command arguments...] Possible options: -a,--authority fill in server url based on hrn. Only works for … --accept-self-signed accept unknown self signed certificates (DANGER … --api The API to call (MANDATORY) --authorities-file The xml file containing the list of known autho… --clearinghouse fetch certificates etc from clearinghouse first --context-file replaces all previous parameters by those in the… -d,--debug extra debugging output -i,--interactive interactively request some missing options and … -k,--key-file file containing user certificate and key in PEM … --output-file file to write output to -q,--quiet less output -u,--server-url URL of server --use-tested-SA do not use the SA of the user, use the SA of the … Required options: --api either --context-file or both -k and -u (-u can be replaced by -a)

7. 7 Integrating Probe in F4F First Level Support

8. Fed4FIRE First Level Support http://monitor.ilabt.iminds.be

9. 9 jFed automated testing Each call can use information of previous calls Full scenario/compliance testing, e.g. ◦ GetVersion ◦ Create Slice ◦ Create sliver ◦ Ssh login ◦ Delete sliver Creates automatically HTML reports Used to drive http://monitor.ilabt.iminds.behttp://monitor.ilabt.iminds.be

10. 10 jFed automated testing

11. 11 Properties file for test username = ftester passwordFilename = /work/monitoring/logins/ftester.pass pemKeyAndCertFilename = /work/monitoring/logins/ftester_wall2.pem userAuthorityUrn = urn:publicid:IDN+wall2.ilabt.iminds.be+authority+cm testedAggregateManagerUrn = urn:publicid:IDN+wall2.ilabt.iminds.be+authority+cm amversion = 2 testbedid = 1 pinghost = www.wall2.ilabt.iminds.be testclass = be.iminds.ilabt.jfed.lowlevel.api.test.TestAggregateManager2 testgroup = nodelogin testname = Nodelogin Virtual Wall testdescription = Create a sliver with a single node, and login on that node. testcategory = login testforpartialsuccess = testCreatedSliverBecomesReady testforfullsuccess = testNodeLogin Very flexible  also testing 25 GENI testbeds See http://monitor.ilabt.iminds.behttp://monitor.ilabt.iminds.be

12. 12 jFed UI 1. Login using single account 2. Select desired resources

13. jFed UI 3. Design the experiment with a GUI 4. Setup SSH session to any resource with a single mouse click

14. 14 jFed UI 5. Control your experiment

15. 15 jFed summary http://jfed.iminds.be Current state (what do we use in production): ◦ Probe GUI: mature ◦ Automated tester CLI: mature ◦ Experimenter UI: beta ◦ Stitching support: couple of bugs to fix (retries) Mailing list: http://lists.fed4fire.eu/listinfo/jfedhttp://lists.fed4fire.eu/listinfo/jfed

16. 16 Questions www.fed4fire.eu contact@fed4fire.eu Demo booth at FIRE area

17. 17 Acknowledgement This work was carried out with the support of the Fed4FIRE-project (“Federation for FIRE"), an Integrated project funded by the European Commission through the 7th ICT- Framework Programme. (318389). It does not necessarily reflect the views of the European Commission. The European Commission is not liable for any use that may be made of the information contained herein.