Bug 743682

Summary:	[RFE] Realm mapping us-east-1a listed but not available
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Joe Vlcek <jvlcek>
Component:	aeolus-conductor	Assignee:	Angus Thomas <athomas>
Status:	CLOSED NOTABUG	QA Contact:	Rehana <aeolus-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0.0	CC:	akarol, dajohnso, deltacloud-maint, dgao, morazi, ssachdev
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-30 13:17:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joe Vlcek 2011-10-05 17:56:40 UTC

Description of problem:

When creating an EC2 Realm mapping us-east-1a was listed in the drop down but was not available.

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


How reproducible:



Steps to Reproduce:

From Conductor UI
1. Attempt to create a "New Realm" under provider ec2-us-east-1
2. Select "Add mapping to realm", ec2-us-east-1:us-east-1a is among the available to choose from even though it is unavailable.
  
Actual results:

The result is what is reported in bug:

743676 - Invalid EC2 zone error message not indicative of the problem.

This bug is not reporting the eventual failure but how the user was erroneously lead down that road.

Expected results:

I think two things would be nice to have happen:

1- If a zone is not available when a deployment is launched and the Realm being used contains multiple mappings the deployment should automatically be tried on another selected mapping.

2- The list of mappings (zones) should indicate if they are currently available or not.




Additional info:

Comment 2 wes hayutin 2012-01-10 17:10:33 UTC

adding to ce-sprint-next

Comment 3 wes hayutin 2012-01-10 17:13:17 UTC

adding to ce-sprint-next

Comment 4 wes hayutin 2012-01-12 16:34:59 UTC

adding to ce-sprint

Comment 5 wes hayutin 2012-01-12 16:41:19 UTC

removing ce-sprint-next tracker

Comment 6 Angus Thomas 2012-01-12 17:39:54 UTC

The mapping of a back-end realm to a user-defined realm is a persistent configuration. The fact that ec2-us-east-1:us-east-1a is listed as an available realm is because it is provided by ec2, irrespective of the fact that it might be temporarily unavailable at any given moment.

To address the issue of avoiding attempting to launch in a a realm which is suffering a temporary outage, we need to add QoS metrics to Conductor, which would influence the selection of a provider account/realm at launch time.

That isn't in scope for the 1.0 release.

Comment 7 wes hayutin 2012-01-16 19:25:06 UTC

moving to 1.1

Comment 8 wes hayutin 2012-02-22 23:46:27 UTC

moving version to 1.0.0 .  version = found in version