Individual variation can define pricing and capacity consumption per software type.

Prioritize computer_guid for now while parent_reference is used.

slapos_erp5: Since capacity scope is updated after allocation, the computer should have access on mememcached

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.