nexedi / slapos.toolbox

With slapos.core!125,
this is not the case anymore by default.

This commit does not nothing when using older slapproxy.

/reviewed-on !62

/reviewed-on !51

This shall be helpful when debugging why the data disappeared from a
webrunner.

…er (as done on slapos master)

@jerome @jm @vpelletier @rafael @Nicolas @guillaume.hervier @alain.takoudjou

I tested in my webrunner

/reviewed-on !48

When the URL /isSRReady is called if the software release link is not present in softwareLink folder, webrunner will launch build of software. The result is slapgrid trying to build sr every minutes, then resiliency fail.

Start slapproxy at runner startup and when instance is removed in webrunner. This fix resiliency problem when proxy.db file does not exist.

/reviewed-on !36

  Follow up erp5@ccbf9007

  Pin version of setuptools as >=34 don't work

  It means there is no extra test to run.

@Tyagov 

Some screenshots:
![Screenshot_from_2017-03-24_11-54-11](/uploads/16f5901303b083dee2c771bcc77dd93b/Screenshot_from_2017-03-24_11-54-11.png)

/reviewed-on !10

…runner" and its fixup!

This reverts commit 26c5ef0b.
This reverts commit edc91312.

…&run feature shouldn't work"

The current behavior should stay until a correct way of restarting processes in the webrunner (ie: watchdog within slapproxy) is implemented

This reverts commit 50948d5b.

It makes tests easiers and lighten the code in view.py

The code in the view is lighter, and the generic part could have been moved to utils

This also makes the function easier to test

It's not needed anymore to create a user at first launch of webrunner. Credential can be created from slapos recipe directly.
Webrunner can also clone default repository at first launch.

/reviewed-on !7

Merge erp5 resilient tests code

This code tests the former ERP5 Cluster (now already in master) into a current resilience tests.

See merge request !3