This part is handled automatically by the site creation.

slapos_configurator: Create a single script to define the inital list of BT5 between the configurator and the upgrader.

This allow us link Computers and Hosting Subscriptions to Projects using Tracking API

/reviewed-on nexedi/slapos.core!31

See also slapos@04e5d4aa.

Those scripts are part of the new API, added upfront to keep backward compatibility.

  The API uses code which is part of the new VIFIB 2.0 API, and
  uses simpler scripts and JSON for the exchange of information.

  This API may change again in futher future, but backward compatibility will be kept with the current implementaion

- Acquire subordination from parent Computer: Thanks to this Computer Partitions
can be in same category as Computers they are contained in.

- Computer should acquire region from parent.
- Add group acquisition on Computer Partition

Those changes overwrite the configuration from erp5_base, and to avoid fork erp5 code.

The reimplementation make both complaint with ERP5LoginUserManager

  Include custom ERP5Type_asSecurityGroupId (Required for Computer and Software Instance usage of user_id)
  machine_login was renamed to external_login to be complaint with ERP5LoginUserManager

  On SlapOSShadowAuthenticationPlugin, the enumerateUsers contains a huge copied code from
       ERP5LoginUserManager, which could be be factoried in a sense in future.

  Update related tests and code to:

   - Add ERP5 Login in person, Computer and Software Instance
   - Set user id while create or clone objects
   - Update ROLES and logins (for tests) to use User ID instead reference.
   - Login is defined by ERP5 Login and not by object reference.

 Check if the user has a login subobject before set local roles on the user.
 Reference is never None.

The ownership is not exported into business templates anymore.

   Organisation is going to be used as Site to identify the Location of a group of Computers.
   User can add Organisations
   User can add Projects
   Owners are also Assignees on theirs Orgsanisations and Projects

A common problem on this test is when you run in your instance the modules are owned by the user that setup the Instance while the tests expects to be owned by ERP5TestCaseUser.

This change update the ownership of the modules to be on the expected user used by the tests (which is mostly safe even in production).

We only had a global "pidfile" configuration, but it's more conveniant
to be able to configure different pidfile for each command (software,
instance, report)

The supported config file would look like:

```
[slapos]
pidfile_software = /path/to/pid
pidfile_instance = /path/to/pid
pidfile_report = /path/to/pid

```



/reviewed-on nexedi/slapos.core!29

  Include a test for fetch configuration

  Conflicts on namespace can easily break this feature, so pick the
  template directly is safer.