Redmine #3288, #3404, #3405
This is the lastest revision to the latest round of security updates,
incorporating all feedback so far. The spec and feature suites still work
after these patches are applied and everything should be good to go for
Would you be ok to recompile the latest 0.4.x series
Audrey Agent rpm, to F16, and push it out to the official
repos? (ie through Bodhi)
The existing Audrey Agent rpm is busted, missing the
systemd startup bits:
As a rough suggestion, the "aeolus-audrey-agent-0.4.10-1"
from RHEL6 seems happy when recompiled for F16.
Haven't been able to test it fully yet, as my VMware setup
is still having issues with passing userdata... but at least
the above rpm is starting ok, and trying to grab user data
(several times according to the log file).
Regards and best wishes,
Aeolus Community Manager
RM3392, RM3394 This patchset updates the converge-ui used by Conductor
it. Patchset also makes Conductor to use converge-ui Login layout.
git-send-email won't allow me to send the patchset so I added the
patches as attachment.
On 06/22/2012 09:04 PM, Matt Wagner wrote:
> As discussed on the call today, I put together a wiki page outlining my
> "annoyances" with our UI -- places we are inconsistent or do weird
> I seeded it with my own list, but the intention is to gather data from
> Please feel free to contribute your own, or share the link as you deem
> appropriate. (This should probably go out to aeolus-devel, but I wasn't
> certain if that's a good idea or not, so I'm holding off for the moment.
> Please feel free to send there if you think we should.)
> -- Matt
I have added my findings to the wiki and sending it here too. I
especially agree on Monitor/Administer distinction issue.
I will try to go deeper in the app and update list with another issues.
I think we should share this on aeolus-devel so I add it to the
recipients. Hope nobody is against it.
Here is the list (also available at
* Logs UI needs polishing and figure out proper Logs link placement
(original designs puts the link (icon) between pretty/filter togle
buttons ), resolve places where logs sections should be also present
(eg. related only to pool, deployment, instance, user, provider...) see
logs section design: 
* Launch from Catalog (dropdown) is not clear what it does (should be
something like Launch NEW DEPLOYMENT from CHOOSE CATALOG)
* Settings tab is kind of empty (is needed?) the first page just points
to another with link
* As Matt pointed out let's make the administer tabs first level and add
Overview tab at the beginning.
* Based on changed top tabs, let's make a dropdown shortcuts for the
folowing tabs if the page under the tab is tabbed (Users, Environments,
Content, providers (make a new provider link) , this also brings some
space to utilize changes for better workflows which Brian works on.
Display tabs and subtabs based on permissions of user.
* Breadcrumbs - enable them everywhere, original point - maintain
applied filters (viewstate), use it to help with the navigation (plays
nice with dropdown tabs), we need to figure out proper placement and design
* Notifications, the current placement of notifications is wrong and
doesn't fit the current Header style. UXD Wiki says nothing about
notifications look and placement either 
* The Overpass font does not align vertically to it's line height.
Should Audrey's (config) server run ok on i386 hosts?
Thinking that unlike other parts of the Aeolus stack - which we "advertise"
as 64-bit only - Audrey probably doesn't have to be.
Being able to run on i386 vs just x64 *might* help keep deployment costs
Even though EC2 Micro instances can be either 32 or 64 bit, other cloud
providers may be different. (no idea personally :>)
Aeolus Community Manager
From: Imre Farkas <ifarkas(a)redhat.com>
The String#each method does not exist in Ruby 1.9
src/app/controllers/application_controller.rb | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/app/controllers/application_controller.rb b/src/app/controllers/application_controller.rb
index aed6b7e..a090a17 100644
@@ -117,10 +117,11 @@ class ApplicationController < ActionController::Base
# Returns an array of ids from params[:id], params[:ids].
- other_attrs.each do |attr_key|
- return Array(params[attr_key]) if params.include?(attr_key)
- if params[:id].present?
+ if other_attrs.is_a?(Enumerable)
+ other_attrs.each do |attr_key|
+ return Array(params[attr_key]) if params.include?(attr_key)
+ elsif params[:id].present?
These patches move creation of the default admin user from configure
into conductor via db seeds. The problem with doing it in configure
is ensuring that the admin user doesn't get recreated on multiple
invocations. If the user modifies the user (say, change username from
'admin' to 'root') then configure will note that admin does not exist
and recreate it, but this is not what the user wants. Alternatively,
it was discussed to have configure only create the user configured in
the admin profile only if no other admin user already exists. This
however would be confusing to a user who believes they can use the
admin profile to create arbitrary admin users (a not-unreasonable
belief). By doing the creation with db seeds, we ensure that the
admin user is always present (no more "oh i forgot -p admin") but is
only created once - during initial setup.
BZ#806001 - aeolus-configure will always create an admin user, need to key of a uuid not name