This is an acceptable speed up as the amount of processing is small, and pontual, as states are updated quickly.

This is helpfull to configure configure computers to simulate connection parameters and allocation.

This is a change from Thomas Gambier.

This is a change from Thomas Gambier, I'm just commiting

Don't clear and allow us to pass parameters for the ansible commant which allow us pass extra variables.

  slapos_erp5: Add erp5_authentication_policy as project dependency
  slapos_cloud: Define standard configuration for authentication policy
  Update tests on various bt5.

  Modifies the Workflows meaning for Support Request Workflow

    Draft: Reservation isn't Payed, Person is created
    Planned: Reservation is Payed, User is going to be Notified
    Ordered: First month isn't payed, Hosting Subscription is created
             (started), user is notified about the payment to be done.

    Confirmed: Hosting Subscription is stopped until the payment
               is done. Once it done, instance is started and
               user is Notified.

    Started: User is available for this user.

    Stopped/Delivered aren't implemented.

  Nothing is implemented inside the workflow itself, alarms calls the
  scripts which changes the transitions once everything is ready to move
  foward.

  Allocation aoccur when if subscription request is in ordered state. We
  allocate earlier to reserve the space until the payment is done.

Call the API rather them wait for the alarm hourly alarm. This might update simulation as soon as possible once the Hosting Subscription is created.

See merge request !221

 * Remove duplication of unmodified scripts from Chinese translation
 * Use slapos_jio_ui_test as dependency of slapos_jio_zh_ui_test as we can reuse scripts
 * slapos_ui_zh_tests: Massively Remove unecessary duplication
 * Fixup! default_address_region was replaced by a selection
 * Correctly ident the entire html from the tests and templates (using
monaco autoformat)

revert accidentally pushed commit and fix test failures introduced by nexedi/slapos.core!192

See merge request !216

fixup 31864c5c to make test pass

This reverts commit 3160c589.

pushed by mistake. This is unfinished but it was wrong because we copy
this log file to snapshot directory before we are done writing to it.

When we recurse in instance to find nested slapos that might be using
parts from ourselves, we check all files named slapos.cfg but we may
encounter some slapos.cfg that are not actual slapos config files, for
example in testnodes we have a working copy of slapos repository which
contains a stack/slapos.cfg which is completly different.

This was breaking prune with an error like this:

    2020-04-29 20:07:28 slapos[2097] DEBUG Reading config at /srv/slapgrid/slappart9/srv/testnode/czp/slapos-repository/stack/slapos.cfg
    2020-04-29 20:07:28 slapos[2097] ERROR No section: 'slapos'

See merge request !211

`FolderSizeSnapshot` is too slow and cause some "Database is locked" errors when running software instance tests.

See merge request !206

buildout profiles and .installed.cfg, shared parts signatures

  Extend getBusinessTemplateList to install the dependencies
  slapos_configurator: slapos_jio_zh_ui_test also goes on keep bt5 list

This change allow us to use slapos node boot/bang under a slaprunner (or any non-root environment).

It should be usefull to not create ad-hoc implementation for those procedures.

/cc @jerome @tomo @Nicolas

See merge request !214

  This allow the user uses slapos node boot inside webrunner or any other non-root environment

  This change allow bang been called on slaprunner or on any unprivileged deployment

This reverts commit 8a3c8aa3 because we
still have complaints for binaries that are linked, directly or not, to
libgfortan (e.g. openblas). Adding zlib to the rpath of these binaries
would be annoying.

See nexedi/slapos@6db91afc

See merge request !213

See merge request !192

See merge request !210

When we recurse in instance to find nested slapos that might be using
parts from ourselves, we check all files named slapos.cfg but we may
encounter some slapos.cfg that are not actual slapos config files, for
example in testnodes we have a working copy of slapos repository which
contains a stack/slapos.cfg which is completly different.

This was breaking prune with an error like this:

    2020-04-29 20:07:28 slapos[2097] DEBUG Reading config at /srv/slapgrid/slappart9/srv/testnode/czp/slapos-repository/stack/slapos.cfg
    2020-04-29 20:07:28 slapos[2097] ERROR No section: 'slapos'

Translation of additional forms (already merged) in Chinese.

Please @lu.xu review the translation (and merge if it is appropriated)

See merge request !209