© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
This is something that could certainly be discussed. The actions API in Heat is set up in such a way that it should be comparatively easy to add new actions. However, there is a fair amount of implementation involved, since each resource type that needs to do something on stop/start would need to have the correct actions implemented.
However, there are some open issues with suspend/resume:
https:/
https:/
I'd be very reluctant to add any new actions before those are resolved.
The addition of extra states also contributes to disproportionately increased complexity (as illustrated by that second issue above), so it would require a compelling use case. A comprehensive spec where somebody has worked out in advance how each potential state transition should be treated (e.g. what should happen if you stop a suspended stack, &c.) would be the most helpful thing to make it more likely to be accepted.