In 51f89902 (slapos/cli/entry.py, slapos/cli/format.py, slapos/format.py:
Do not double the log output when "slapos node boot" failed., 2017-05-11)
we fixed a problem that every failure during boot causing twice more output
(which filled up the disk very fast), but a side effect was that using
--log-file no longer cause messages to also go to the console.

The "Always send higher-level messages to the console via stderr" comment
in entry.py seems that this was always intentional to output messages on
the console.

Keep the same "don't configure again logging system when it's already
configured", but implemented in a slightly different way, because since
a FileHandler is a StreamHandler, the check of already having a
StreamHandler was true also for the case where --log-file added a
FileHander (a few lines above, also in configure_logging method)

this test checks "slapos node boot" which calls check_root_user after
importing it in slapos.cli.boot, so we should patch in that module.

  This is a safe measure in case the alarm to delete the instance is temporarily disabled.

    This is a initiall prototype (as experiment) to be moved and improved elsewhere later.

Keep source[_section] None on the New template tests

   This feature (with values set) is covered on Dual organisation settings.
   Unify code into mixin for Chinese scenarios
   Update Payzen for the new API
   Remove duplication and fix up assert
   Implement Test for Parallel subscriptions

      Test 2 organisations rather them a single one with parallel Subscriptions
      Move more code into the Mixin, for reuse it.

   Instead relies on Templates for define source[_section] for subscription related simulation use Subscription Condition (Path-Like), and by consequence Subscription Request, settings as source[_section] on Packing Lists.

  This allow us define multi-organisation providers of services, to comply of world-wide deployments.

   As the model is use single Open Order, it isn't possible to use multiple
   organisations (one per region), so we rely on Subscription Request Information
   to describe the providers.

See merge request !274

  Changes on PaymentTransaction_updateStatus were added for debugging purpose it seems.

See also slapos!875

See merge request !271

  It is required due the replacement of the ownership.

   Sometimes the instances where the data is commited, don't have the same user set as the tests.

   Remove useless duplication on the security test (just duplication)
   Remove and include test for Organisation

  Move access into assignment based security

   Open tickets have to be handled by Administrators, and not by the user, only suspended tickets or confirmed upgrade decisions should be displayed on the front page, as it is duty of the user respond them.