Still many variants which could likely be simplified.

Getting them from the runner backup avoids to get false positive if some
of the instance's backup files were excluded using an exporter.exclude file

slaprunner: export script shouldn't succeed if the backup of the contained instances are running at the same time

/reviewed-on nexedi/slapos!117

Otherwise, slaprunner-supervisord crashes because of unknown paths

Also, the instance-runner-export template becomes a Jinja template

This commit is a fix for 8787716d. It allows to get the random cron string
generated previously through parameters, and not reading manually .installed.cfg.

This message is also available via a promise

If slapgrid fails, print the end of instance/software log in resilient log.
Now an the exit-code-file is always written, even if runner-importer fails.
The promise on this file gives the URL where the resilient log can
be accessed, to simplify the debugging

Then we'll upgrade setuptools for everyone at the same time as we switch to
zc.buildout 2.x

Because slapos.core hardcodes a "supervisord.socket", this file happens to be deleted and cause bugs

Revert "resilient: new paramater to define the time to sleep before running the backup in the cron job."

This reverts commit 30d1a937.

It includes more debugging lines, not deploying a slapproxy (no need anymore thanks
the free-port selection recipe), and not delegating some work to a cron job.

In gunicorn v19.6 and v19.5, a bug was introduced which deletes socket when nginx worker exits.
In our case, it crashes the slaprunner and prevents it from restarting by slapos.
Let's stick to v19.4.5 until this issue is closed : https://github.com/benoitc/gunicorn/issues/1298

Default is a random value between 0 and 6 hours. KVM and Slaprunner test instances set it at 0.

  Version up only goes to buildout2 case, buildout 1 series keep the same.

For sftp to work we need to define sftp "subsystem" on server side in
sshd speak. Sftp support in turn allows for sshfs to work.

NOTE

	Subsystem sftp internal-sftp

won't work because we are doing games with ForceCommand and reexecution
of "$SSH_ORIGINAL_COMMAND" (see previous patch for details).

2a733418 (slaprunner: replaces dropbear by openssh) switched slaprunner
sshd from dropbear to openssh (thanks for it once again) and used
ForceCommand to imitate login shell to be partitions `${bash:location}/bin/bash -l`.

For case when original ssh command is explicitly provided
("$SSH_ORIGINAL_COMMAND" is not empty) the code there tries to just
execute what was provided by caller.

However the reexecution is not completely correct as for cases when
origin command contains some quoting, 1 level of quotes is removed.

The case when I hit this in practice is git access to repositories over
ssh. When git wants to e.g. clone a repository it runs `git-upload-pack
quoted-path-to-repo.git` and fails this way:

```
$ GIT_TRACE=1 git clone ssh://host1/~/B.git
19:28:23.558858 git.c:350               trace: built-in: git 'clone' 'ssh://host1/~/B.git'
Cloning into 'B'...
19:28:23.572994 run-command.c:336       trace: run_command: 'ssh' 'host1' 'git-upload-pack '\''~/B.git'\'''
fatal: ''~/B.git'' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
```

Quoting SSH_ORIGINAL_COMMAND and evaluating it completely via eval fixes this.

/cc @Nicolas, @alain.takoudjou

Slapos.toolbox has a new dependency to pycurl, which fails to compile if libcurl cannot be found. This commit adds the component/pycurl dependency to most of the Software Releases which have a dependency to slapos.toolbox.

I tried to do it globally, so I couldn't check the compilation of all the modified SRs. Is it a way to test that all SRs still compiled ?

Also, did I forget some important SR ?

@rafael @alain.takoudjou @kazuhiko @jm 

/reviewed-on nexedi/slapos!97

Openssh (sshd) doesn't want to start with keys generated by dropbear