| Summary: | during launch: rename blank realm to "auto select" or something intuitive | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> | ||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, deltacloud-maint, slinaber, ssachdev, sseago | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://qeblade31.rhq.lab.eng.bos.redhat.com/conductor/deployments/launch_time_params?deployable_id=3&deployment[name]=RHEL6-Basic&deployment[pool_id]=1 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-30 17:17:09 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
I'm not sure we want to key this off of priority -- ultimately, there will be additional methods of identifying which provider account to select if there are multiple matches (least used, lowest error rate, etc). Also, the problems associated with not setting account priority aren't unique to whether or not the user picks a realm here. If a realm maps to multiple providers, you're back to tie situation of a seemingly random selection if priority isn't set. I'm thinking we should stick with something like option 1 -- and again, something like 'auto select', 'pick for me', 'no preference', etc. the other problem with tying this to provider account priority is that they are different levels of matching. When we match to provider accounts, there are several filters that eliminate possibilities. We start with the list of provider accounts in the current environment. We drop accounts that don't have images built and pushed. We drop accounts with no matching hardware profile. We drop accounts that have reached quota. If the user picks a realm, we also drop accounts that don't belong to a provider that's either mapped directly to the chosen realm or indirectly via one of the provider's back end realms. Ultimately, I think the question you're trying to address here is "if I hit 'launch', where will my deployment be placed?" -- messing with a small subset of the parameters (realm selection plus account priority) won't get at this. Maybe the real answer is a 'what if' button -- or even adding something to the confirmation screen "most likely candidate provider account for launch" and we show where it will probably be placed -- I say "probably" because in the intervening time before 'launch' is pressed, something may change (quota reached, etc), forcing a different selection. We should rename the blank realm in the launch process with a label, saying "Auto-select" We can also assist the user in understanding the effect of choosing a realm by allowing showing text which the admin has associated with each realm when it is selected. In order to do that, we'll need: - A UI change to allow admins to enter some descriptive text when they edit a realm. - A model change to store that text, associated with the realm - A UI change to show the text when the user is choosing a realm at launch time. For this, a flat text field would suffice, rather than using tooltips etc. Patch on list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-January/007997.html (see thread) adding to ce-sprint removing ce-sprint-next tracker Pushed in this trio of patches:
commit dfce63bb0950a749bd8007b978a25061c1317b8d
Author: Matt Wagner <matt.wagner>
Date: Tue Jan 17 11:08:02 2012 -0500
Fixes failing test revealed by previous patch
commit 9f4dd8d500de2662dff0ac82b002a4e0752416fa
Author: Matt Wagner <matt.wagner>
Date: Tue Jan 10 16:40:02 2012 -0500
Adds description to Realms
Second half of https://bugzilla.redhat.com/show_bug.cgi?id=772357
commit 802d02c1582679797d7f09ef6b908e10867bfb1b
Author: Matt Wagner <matt.wagner>
Date: Tue Jan 10 14:56:40 2012 -0500
Blank default realm at launch now shows 'Auto-select'
Component of fix for https://bugzilla.redhat.com/show_bug.cgi?id=772357
c3fb5c1fc6f6ba6be1778edd0ece07380875e7ff ade4d6925756c9fe39c82ff9bf0d275afd1fdfeb in aeolus-conductor-0.8.0-8.el6.src.rpm Created attachment 556209 [details]
auto_select
auto-select is displayed in realm and when no realm selected it auto picks realm
As per comment 2 In order to do that, we'll need: - A UI change to allow admins to enter some descriptive text when they edit a realm. - A model change to store that text, associated with the realm - A UI change to show the text when the user is choosing a realm at launch time. For this, a flat text field would suffice, rather than using tooltips etc. ================================================= a) description field is added to realm b) "auto-select" by default in realm field while launching instance ================================================= Verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-configure-2.5.0-5.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch |
Created attachment 551299 [details] ss Description of problem: Leaving the realm blank at launch time should allow conductor to launch the instance in a realm based on the priority entered by the admin in the provider account setup. My proposal is this.. 1. If any of the provider accounts have a priority entered.. show the now "blank" option and rename it to "auto select" "pick for me" or what ever magic eight ball phrase you want. 2. If none of the provider accounts have a set priority.. remove the option.. [root@qeblade31 ~]# rpm -qa | grep aeolus aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch rubygem-arel-2.0.10-0.aeolus.el6.noarch aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch