Bug 824479 - [RFE] Allow for hooks within workflow
Summary: [RFE] Allow for hooks within workflow
Keywords:
Status: CLOSED DUPLICATE of bug 823581
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 14:54 UTC by james labocki
Modified: 2012-07-13 13:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-13 13:40:53 UTC
Embargoed:


Attachments (Terms of Use)

Description james labocki 2012-05-23 14:54:36 UTC
Description of problem:
This is a request for a framework which allows hooks to be executed within all parts of workflows. This framework would allow for third party tools to be easily integrated with CloudForms.

Example Story: When the launch button is selected a hook is called (start_launch) which executes a script (created by customer, consultant, or third party software vendor). This script would insert a record into a third party tool (such as remedy or BMC). Cloud Engine would not launch the instance, instead it would set the status to "waiting for response from $hook_name". Upon completion of workflow in third party tool the third party tool would call Cloud Engine API and change the status from "waiting for response from $hook_name" to "approved". At this point, Cloud Engine would launch the instance.

Comment 1 Dave Johnson 2012-07-13 13:40:53 UTC

*** This bug has been marked as a duplicate of bug 823581 ***


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