Page MenuHomeSoftware Heritage

fed4fire setup for winery benchmarks
Closed, MigratedEdits Locked


Event Timeline

dachary changed the task status from Open to Work in Progress.Oct 19 2021, 3:44 AM
dachary triaged this task as Normal priority.
dachary created this task.
dachary created this object in space S1 Public.
dachary added a parent task: T3432: Add winery backend.

/opt/jFed/jFed-Experimenter works but I'll have to wait on the approval of the account before proceeding further.

The Connectivity tester has some red but their meaning eludes me.

But the Grid5000 tests are green:

Test name: [AM] Grid'5000 Geni.AMv3
Message: Successfully opened socket to


Test name: [AM] Grid'5000 development Geni.AMv3
Message: Successfully opened socket to

Followed the tutorial to run a first experiment which failed

There is a monitor that shows all testbeds, among which is grid5000:

And there is a documentation on how to use grid5000 through Fed4Fire. I wonder if I'm in the right direction. and asked for advice to the grid5000 contact.

Subject: Grid5000 via Fed4Fire


En errant[0] pour trouver comment utiliser Grid5000 via Fed4Fire je suis tombé sur une documentation[1]. Avant de continuer plus loin ce serait formidable si tu pourrais me dire si je suis perdu ou bien dans la bonne direction :-) Ca ne me bloque pas mais comme j'ai retenu que l'idée était d'utiliser les outils Fed4Fire et pas seulement les outils Grid5000, je tiens à comprendre un peu comment tout ça fonctionne.


[1] is the better documentation to use Grid5000 via Fed4Fire

The Grid5000 machines are found in the "

The error is because the account is not linked.

I wanted to terminate the experiment but it looks like it must expire (although Grid5000 has the option to terminate a job).

Created another experiment (with 25min lifetime only) and it's going better:

Using Export As ansible, I unzipped the result.

$ ssh -i id_rsa -F ssh-config node0
Warning: Permanently added '' (ECDSA) to the list of known hosts.
Linux 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64
 (Image based on Debian Buster for AMD64/EM64T)
  Maintained by support-staff <>


The CLI may be easier to use than the graphical client when repeatin experiments.

The CLI is actually more complicated because it requires input that are difficult to figure out:

  • a slice is an experiment
  • a sliver is a resource that has been allocated

Mandatory arguments are the PEM file (-p) which I got from the user preferences, clicking on As PEM, although I have no clue if this is the right pem file.

When provided, the password to the PEM file (-P) triggers an error:

$ java -Djdk.gtk.version=2 -jar experimenter-cli.jar status -P foobar  -p /tmp/ilabt.imec.be_dachary.pem -s
FATAL: Not in interactive mode, so password cannot be requested.

And I do not know how the interactive mode can be activated. So I removed the password from the file with:

openssl rsa < /tmp/ilabt.imec.be_dachary.pem > /tmp/ilabt.imec.be_dachary.pem.unprotected

And tried again but got another error message:

$ java -Djdk.gtk.version=2 -jar experimenter-cli.jar status -p /tmp/ilabt.imec.be_dachary.pem.unprotected -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.fasterxml.jackson.module.afterburner.util.MyClassLoader (file:/opt/jFed/jfed_cli/lib/jackson-module-afterburner-2.9.6.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.fasterxml.jackson.module.afterburner.util.MyClassLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
	at be.iminds.ilabt.jfed.ui.commandline.BaseCli.checkUser(
	at be.iminds.ilabt.jfed.ui.commandline.BaseCli.checkUser(
	at be.iminds.ilabt.jfed.ui.cli.ExperimenterCli.main_internal(
	at be.iminds.ilabt.jfed.ui.cli.ExperimenterCli.main_helper(
	at be.iminds.ilabt.jfed.ui.cli.ExperimenterCli.main(
Will now exit due to uncaught exception.

I tried numerous combinations of options (--slice, --rspec, --project-name) without success: the same error comes back. I searched the net for examples or discussions related to the usage of the jFed CLI without much success. The rspec was downloaded from the RSpec viewer page:

However there seem to be more than one rspec file and maybe it's not the right one.

The Fed4Fire page of Grid5000 does not mention the CLI.

It was worth a shot but it is probably not worth obsessing over it.

When trying to extend the duration of an experiment (slice in the Fed4Fire parlance), an error occurs.

The bug report was sent as suggested, with a message saying the problem was not urgent for this experiment. I was able to extend the duration of the experiment using oarwalltime 2049867 +10 therefore it is not a limitation imposed by Grid5000 triggering the error.

But then Fed4Fire killed the experiment prematurely, ignoring the Grid5000 extension. I'll have another go at it.