Bug 751798 - Deployment to 4+ providers fails
Summary: Deployment to 4+ providers fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: wes hayutin
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-07 15:45 UTC by Jason Ganovsky
Modified: 2013-04-30 22:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-01 14:00:50 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jason Ganovsky 2011-11-07 15:45:04 UTC 
Description of problem: Intermittent failures when deploying instances to more than 3 cloud providers


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


How reproducible: Deploy to RHEV, VMW, EC2 and Rackspace in a single deployable
Comment 1 wes hayutin 2012-01-10 17:11:20 UTC 
adding to ce-sprint-next
Comment 2 wes hayutin 2012-01-10 17:14:40 UTC 
adding to ce-sprint-next
Comment 3 wes hayutin 2012-01-12 16:36:15 UTC 
adding to ce-sprint
Comment 4 wes hayutin 2012-01-12 16:42:26 UTC 
removing ce-sprint-next tracker
Comment 5 wes hayutin 2012-01-12 16:44:23 UTC 
taking off ce-sprint-next..
Comment 6 Angus Thomas 2012-01-12 17:59:17 UTC 
As part of the preparation for CF 1.0, scalability constraints are being tested as a discrete task.

This bz should either be substantiated with the results of that scalability testing, or moved outside the scope of CF 1.0
Comment 7 wes hayutin 2012-01-16 19:18:02 UTC 
Rackspace is not supported in 1.0
Comment 8 wes hayutin 2012-02-22 23:47:11 UTC 
moving version to 1.0.0 .  version = found in version
Comment 9 wes hayutin 2012-05-01 14:00:50 UTC 
deploying to rackspace is not supported.

build/push/deploy to ec2,rhevm,vsphere works and is supported
Note You need to log in before you can comment on or make changes to this bug.