Bug 751787 - [RFE] : add capability to "hook" custom actions at vm creation and destroy
Summary: [RFE] : add capability to "hook" custom actions at vm creation and destroy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: deltacloud-core
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Michal Fojtik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-07 15:04 UTC by Alfredo Moralejo
Modified: 2012-08-29 14:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 00:56:07 UTC


Attachments (Terms of Use)

Description Alfredo Moralejo 2011-11-07 15:04:38 UTC
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:

Comment 1 wes hayutin 2012-01-10 17:10:54 UTC
adding to ce-sprint-next

Comment 2 wes hayutin 2012-01-10 17:13:41 UTC
adding to ce-sprint-next

Comment 3 wes hayutin 2012-01-12 16:32:36 UTC
adding to ce-sprint

Comment 4 wes hayutin 2012-01-12 16:39:25 UTC
removing ce-sprint-next tracker

Comment 5 jrd 2012-01-13 15:24:50 UTC
1.1

Comment 6 David Lutterkort 2012-02-14 00:56:07 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.