Hide Forgot
Description of problem: Provider selection is non-deterministic when there are more than one match. The Conductor needs a way for administrators to set a global priority value for provider accounts. The admin should be allowed to prioritize versus allowing the conductor to pick the first from a list that is returned from a query. Because if there is no priority then we might find that there is an implicit favouritism because one provider always seems to top the list. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Patches here: https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007633.html https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007631.html https://fedorahosted.org/pipermail/aeolus-devel/2011-December/007632.html Fixed pushed to master
mapped a realm to two providers mock and ec2 . mock - priority 1 ec2 - priority 2 launched instance , instance was launched for mock Then i interchanged priorities of accounts. ec2 -- priority 1 mock -- priority 2 instance was launched for ec2. verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch