Hide Forgot
Description of problem: Sometimes customers need to perform some tasks not directly supported in deltacloud and platform-specific according to their particular requirements. Adding the capability to execute custom actions stored in a folder may provide a great flexibility without modifying the deltacloud-core code. Some examples may be (for rhevm which is the platform I'm testing): - Modifing vm just after creating it ( adding custom properties, changing network, etc...) - Managing permissions in VMs. - Interacting with third-party tools. Note that vm data should be provided when calling the custom tasks (vm id, opts, etc...) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
1.1
This is not really something that should go into deltacloud-core; running 'after creation' hooks would force deltacloud to monitor (poll) the state of instances in most clouds. In addition, to make this even moderately useful, we'd have to reimplement Audrey within deltacloud. This is very much an application-specific feature and should be put into the respective applications.