Bug 864182 - [RFE] Launching Multi-assembly application with Instances of two different providers fail
[RFE] Launching Multi-assembly application with Instances of two different pr...
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: beta5
: ---
Assigned To: Jan Provaznik
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-10-08 15:32 EDT by Shveta
Modified: 2012-10-10 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-10 12:29:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
multi-instance (107.17 KB, image/png)
2012-10-08 15:32 EDT, Shveta
no flags Details

  None (edit)
Description Shveta 2012-10-08 15:32:11 EDT
Created attachment 623685 [details]

Description of problem: lauch multi-assembly deployments with images of 2 different providers fails

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Added Provider accounts for ec2, rhevm and Vsphere
2. Built and Pushed for all the providers together 
3. Created an Application Blueprint from this image and launched
Actual results: Only one instance is launched according to priority (for me rhevm had 1) 

Expected results: Three instances should be launched under one application for all the proviuders.

Additional info:

rpm -qa|grep aeolus
Comment 2 Shveta 2012-10-08 16:43:17 EDT
Another Scenario :

Created Three Separate images for ec2 , rhevm and vsphere  and copied the image id of these three into a single xml as shown below :

<?xml version="1.0"?>
<deployable version="1.0" name="all_img">
    <assembly hwp="small-x86_64" name="rhev-img">
      <image id="b16a5506-1170-11e2-9f1b-0023aefc3864"/>
<assembly hwp="small-x86_64" name="ec2-img">
      <image id="56a64d20-1178-11e2-9f1b-0023aefc3864"/>
<assembly hwp="small-x86_64" name="vsphere-img">
      <image id="816a5506-1170-11e2-9f1b-0023aefc3864"/>

But even this doesn't work and launch all the three instances
Comment 3 Mike Orazi 2012-10-10 11:05:07 EDT
Will provide an updated error message that this should not be allowed to launch.
Comment 4 Jan Provaznik 2012-10-10 12:29:23 EDT
Conductor doesn't support launching of cross-provider deployments.

Behavior in both comments is as expected.
1) in first case one image was built and pushed to all 3 providers, deployable with this one image was then launched on one provider with highest priority.
2) in second case a deployable contained 3 images and none of the providers contained all 3 images. Error message that deployment can't be launched was displayed on launch overview page.

-> closing as not a bug

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