For prevent over allocation, we have to update the state of the Computer just after the allocation. This don't replace alarms to control the global state (when capacity is updated etc etc)

It was set to output on stderr, which is not natural and inconvenient

  Those files are created when eggs are generated, so ignore them.

slapos_erp5: Computers with subscription allocation scope has same security as the ones with open allocation

Use sticky-computer to make the requester use same COMP reference when request himself. It allow us to maintain the requested instance on the same computer as the requester.

Based on allocation scope computers can be segmented for subscribers type, and project_guid can
be used to limit the targeting case.

This category, when set on a computer, defines is as Open for Allocation, but only Subscribers can allocate. Normally, only instances that are linked to a Subscription Request.

slapos_cloud: Allocation is unauthorized for the instance that don't have Subscription Request confirmed or started.

Restore the previous behaviour to set 0.0

Contributed by Sven Franck

This is mostly a simplification to follow range(int)

The price is defined on the subscription request and copied into the Open Order later, for periodical payments.

The person can be a Member and a Subscriber

slapos_accounting: If Hosting Subscription comes from Subscription Request apply Quantity and Pricing

New users should have appropriated email.

This is usefull when send emails

slapos_subscription_request: Subscription Request uses simulation state rather them validation state

This value will be used to request among other things.

The Subscription Item is Hosting Subscription, so it only acts as a "requester".