See merge request nexedi/slapos.core!473

   Otherwise capacity is closed due lack of access.

   There is no reason to handle capacity in a different way for personal or friend. This comply with the future design, so keep all consistent by only differentiating Open and Close allocation scope whenever update capacity.

See merge request nexedi/slapos.core!472

   This automatic updates arent required anymore, since we do not intend to have public machines anymore.

See merge request nexedi/slapos.core!443

See merge request nexedi/slapos.core!470

See merge request nexedi/slapos.core!471

this bt5 is used to monitoring compute node state

compute node upload file data into data stream of slapos master

then data stream is transformed into data array which can be easily processed

for more infos: https://www.erp5.com/rapidspace-Server.Check.Process

  since accountants use directly the system, it is normal to allow include Invoice Lines.

See merge request nexedi/slapos.core!466

See merge request nexedi/slapos.core!465

   Ignore the render_oss since it always change after the installation due the update of translation data.

    Use another website for handle OSS (administrative) operations rather them overwrite properties on renderjs_runner itself

See merge request nexedi/slapos.core!468

When using slapos console on scripts defining functions, for example

```py
def my_request(*args, **kw):
  ...
  return request(*args, **kw)
```

the global names such as `request` where no longer available in the
namespace of the function, because of a wrong usage of exec regarding
locals/globals.
Co-authored-by: Kirill Smelkov <kirr@nexedi.com>

See merge request nexedi/slapos.core!459

See merge request nexedi/slapos.core!463

See merge request nexedi/slapos.core!464

   This is a workaround for fixup when objects has internal invalid properties, since we do not want to extend the general error display before replace the json form.