slapos_subscription_request: Refactor Subscription Request workflow
Modifies the Workflows meaning for Support Request Workflow Draft: Reservation isn't Payed, Person is created Planned: Reservation is Payed, User is going to be Notified Ordered: First month isn't payed, Hosting Subscription is created (started), user is notified about the payment to be done. Confirmed: Hosting Subscription is stopped until the payment is done. Once it done, instance is started and user is Notified. Started: User is available for this user. Stopped/Delivered aren't implemented. Nothing is implemented inside the workflow itself, alarms calls the scripts which changes the transitions once everything is ready to move foward. Allocation aoccur when if subscription request is in ordered state. We allocate earlier to reserve the space until the payment is done.
Showing
This diff is collapsed.
Please register or sign in to comment