/reviewed-on nexedi/slapos.toolbox!51

/reviewed-on nexedi/slapos.toolbox!59

promise-timeout provides global timeout for the promise, so use it as
base for calculating default timeout.

/reviewed-on nexedi/slapos.toolbox!58

Enhancements:

 * implement ignore-code
 * cover http_code
 * cover timeout
 * implement verify
 * correctly cover ca-cert-file
 * use SLAPOS_TEST_IPV4

Improvements:

 * flake8ize test_check_url_available and check_url_available
 * cover more of check_url_available

It will be easier to improve it soon.

Additionally print exact exception message.

/reviewed-on nexedi/slapos.toolbox!56

support broken symlink and don't care about modified files that wouldn't be transferred anyway.

/cc @jm for python review :)
/cc @luke @Nicolas to be sure it's what we want

/reviewed-on nexedi/slapos.toolbox!55

/reviewed-on nexedi/slapos.toolbox!34

source and exclude can be in artbitrary order, so sort them in order to have
stable calls.

This simplifies assertions in tests and is no-op for the code.

It is important for DevOps to understand which files were modified during
synchronisation procedure in order to track issues fast.

and not in the backuped files.
If we look in the backup files, then of course we find modified files, which are
the ones that have just been copied from the instance folders

/reviewed-on nexedi/slapos.toolbox!53

As these slapparts are unstable and are updated every couples of months.
Do so by using the API-ification of inspectInstance which can now
return a JSON (thus output can be easily processed)

As in webrunner slappart0 is always the root instance and
all needed parameters are bubbled up to it

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

/cc @cedric.leninivin  @jerome @Nicolas @alain.takoudjou @rafael

/reviewed-on nexedi/slapos.toolbox!52

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

This promises are used in caddy-frontend to check slave frontend status. We don't want to run them everytime buildout will deploy frontend because:
- there is too many slaves, check all slave frontend promises while deploying frontend will slow down slave frontend deployment.
- we don't want to reprocess frontend if one of slave frontend promise is failing