Bug 991117

Summary: Lifecycle BPMN process too coupled with deployment svc endpoints
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: kconner
Component: DT GovernanceAssignee: Eric Wittmann <eric.wittmann>
Status: CLOSED CURRENTRELEASE QA Contact: Stefan Bunciak <sbunciak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: ldimaggi, soa-p-jira
Target Milestone: ER1   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description kconner 2013-08-01 16:49:19 UTC 
The back-end deployment endpoints are split up by type, so there is a deployment copy service and a separate rhq endpoint (for example). There should be a single "deploy" service endpoint that decides how to deploy based on the dtgov configuration of the target. This will fully de-couple the business process from the configuration of the deployment target.
Comment 1 Stefan Bunciak 2013-08-28 11:33:00 UTC 
Verified in S-RAMP 6.0.0.ER1 with community seed data.