* reduce some alarms frequency
  Interaction workflow are needed to speed up everything
* add Base_reindexAndSenseAlarm
* add interactions to speed up allocation
  Use Base_reindexAndSenseAlarm, to ensure object is reindexed, in order to be handled by the alarm
* test: no need to manually call alarms
  Interaction workflow will trigger them
* and fix wrong usage of Base_reindexAndSenseAlarm

slapos_accounting:

* stop using fixConsistency to set hosting subscription periodicity
  Set it directly from the script which create it

slapos_subscription_request:

* do not set the stop_date on the open order
* generate a discount on the first invoice
  If the open order does not start the same day, do not ask user to pay for those missing days
* no need to call OpenSaleOrder_updatePeriod when creating the open order

* test: create deposit payment to validate the subscription
* test: update related document count

* test: define currency on the organisation
* test: scenario for money deposit
* test: typo
* test: apply tax amount only if the resource is taxable
* allow shadow user to view Organisation
* test: reduce number of alarm calls

* cleanup request when instance is not subscribed yet
* stop instance tree propagation on instance_slap_interface_workflow
  Some alarm call request directly on the Instance Tree (this is expected)
* rename Service_getSubscriptionStatus to Item_getSubscriptionStatus

* test that Subscription Request is created from Compute Node
* drop SubscriptionRequest_processStopped
* drop SubscriptionRequest_processStarted
* drop SubscriptionRequest_processOrdered
* drop SubscriptionRequest_processConfirmed
* drop SubscriptionRequest_processRequest
* drop SubscriptionCondition_renderKVMClusterParameter
* drop Base_instanceXmlToDict
* drop SubscriptionCondition_renderParameter
* drop testSlapOSERP5VirtualMasterSubscriptionRequestScenario
* ensure Subscription Request is consistent
* allow to choose the currency when creating a Subscription Request
* try to close the Subscription Request as soon as user paid an invoice
* block subscription process if there is no deposit
* do not accept new services if the virtual master subscription state is not expected
* use Base_reindexAndSenseAlarm

* update one more test
* test_virtual_master_slave_on_same_tree_without_accounting_scenario
* test_virtual_master_on_remote_tree_without_accounting_scenario
* test_virtual_master_slave_instance_on_remote_tree_without_accounting_scenario
* test: really disable accounting

* test: use Person_addVirtualMaster to create project
* test: login as user to request the instance

* init preferences in test
* test: wip accounting scenario
* test:  slapos_subscription_request is installed again

* test: new parameter
* test: keep compatibility with previous addProject

* test Compute Node subscription creation
* logout test

* Subscription Request are invalidated after Open Order is created
* test: create project by doing a subscription request

* create trade condition which could be applied to subscribe to a virtual master
* local roles of Subscription Request
* subscription request interaction workflow
* do not allow Sale function to modify Subscription Request
  Let's automate everything for now

* ensure that alarm propagate parameters of orphaned Instance Tree
* drop usage of Subscription Request
* check the Subscription Request instead of the Cloud Contract
* drop checkCloudContract method

slapos_cloud: only propagate Instance Tree parameters to the Software/Slave Instance only if an Open Sale Order exists

* add Open Sale Order local roles interaction workflow
* update Sale Trade Condition local roles
* allow user to see his Open Sale Order
* only sale people can create Sale Supply

 allow users to create Compute Node / Instance Tree

* update Sale Trade Condition local roles with interaction
* show Sale Trade Condition to its destination

* add slapos_virtual_master_subscription local roles
* only sort some properties
* Sale agent can access currencies
* restore Subscription Request local roles
* Sale agent can create Subscription Request

* Subscription Request is a ticket like Credential Request
* restore subscription_request_workflow as ticket_workflow
* Subscription Request is not linked to a project
* add Subscription Request Constraint
* new constraint on Subscription Request
* add testSlapOSERP5VirtualMasterSubscriptionRequestScenario
* drop outdated subscription scenarios
* WIP selling project subscription
* forbid Subscription Request which could generate Invoice with a 0 price
* do not allow empty quantity on Subscription Request
* WIP selling virtual master to customer
* improve test Trade Condition
* disable existing Subscription Request alarm
* create Subscription Request from orphaned Instance Tree
* create Open Sale Order from Subscription Request
* drop slapos_subscription_request_process_planned
* drop slapos_subscription_request_process_draft
* drop slapos_subscription_request_process_ordered
* drop slapos_subscription_request_process_confirmed
* drop slapos_subscription_request_process_started
* drop slapos_subscription_request_process_stopped
* drop Alarm_processStoppedSubscriptionRequest
* test slapos_subscription_request_create_from_orphaned_item
* add assert when creating Open Order
* alarm to validate submitted Subscription Request
* create Subscription Requuest manually from a resource
* create Subscription Request for Compute Node
* trigger validation as soon as a Subscription Request is submitted
* decrease slapos_subscription_request_validate_submitted alarm periodicity
* create Subscription Request as soon as a Compute Node is validated
* create Subscription Request as soon as Instance Tree is validated
* use different trade condition for instance and node
* do not generate Subscription for Organisation
  This work must be done later
* constraint: no Organisation as source_section
* constraint: fixup empty price check
* constraint: destination_section is not required
  for accounting less subscription
* stop creating project from subscription request
  It is too complex (as it requires to create Trade Condition, Assignment, Project, etc...), and I don't know for now how to make something generic from it.
  Use a custom action for now.

* Sale person can access Service
* only provide read/write access on Organisation to Sale/Accountant
* Sale aent create Trade Condition