- Invoice is generated 15 days before next period and a RR is created
   - 15 later a stop warning is sent (or when invoice expires)
   - 7 days later all instances are stopped if RR still open
    - 5 days after the user is informed his instances will be removed if payment is not done
    - 10 days after ALL his instances will be removed (for safety, as instances can be scaled faster if needed)

So, we assume:

   User is informed 22 days in advance before his instances stop to work, and if nothing is done 15 after (or 37 days after the first request to pay), we just remove all.

Person_checkToCreateRegularisationRequest

See merge request nexedi/slapos.core!248

    This email is already part of Subscription System. Regularisation Request is only for later payments.

By following feature of JSON Schema Draft-06 render a structure like:

  "element": {
    "oneOf": [
      {
        "const": "value1",
        "title": "Description1"
      },
      {
        "const": "value2",
        "title": "Description2"
      }
    ]
  }

To:

  <select size="1">
    <option value=""></option>
    <option value="value1">Description1</option>
    <option value="value2">Description2</option>
  </select>

JSON Schema types array and object are stringified to be safely represented
as option keys.

slapos_accounting: In case of Subscription, generate invoice 15 days earlier them begin of the next period.

After 1.6.1 was deployed we have two processes, stop the redundant process.

In 58fbaabf (svcbackend/standalone: use shorter names for supervisor sockets
, 2020-07-17) we changed the socket path from supervisord.sock to a shorter
sv.sock, but this caused issues when updating running slapos node instances,
because this was trying to start a new supervisord process using the new
socket path, while the old one was still running.

To keep services running after upgrade, introduce a compatibility layer in
this socket path - if we still have a supervisord running with a socket at
this previous path, keep using this old socket name.

Output is already captured on SlapPopen instances and the output
is available with output attribute.

    User can view his Cloud Contract and its consumption.

      This is used to Sales website when a Invitation token is provided and it will be used when request button will be available on logged user website.