OpenStack Support in Conductor (Revisited)

Hi, I'm going though the most recent testing version Aeolus attempting to get a connection to our OpenStack cloud platform. I've installed aeolus-all from the testing repo, along with the deltacloud packages. I can use irb to connect to the launched daemon and successfully get responses back from our platform. However, once configuring aeolus (ec2,mock) and tring to add a new provider, I get the same error mentioned back in a July thread: Cannot add the provider. 1 error prohibited this Provider from being saved Url translation missing: en.activerecord.errors.models.provider.attributes.url.invalid_framework The deltacloudd logs the standard 401 message (this is before credentials are created): 127.0.0.1 - - [03/Dec/2012 10:52:52] "GET /api HTTP/1.1" 401 - 0.0073 I followed the recommendations to get aeolus updated, but still getting this error. Here's the list of current packages installed: [gadams@cloudmgr nodes]$ rpm -qa | grep 'aeolus\|delta'|sort aeolus-all-0.10.6-1.fc17.noarch aeolus-conductor-0.10.6-1.fc17.noarch aeolus-conductor-daemons-0.10.6-1.fc17.noarch aeolus-conductor-doc-0.10.6-1.fc17.noarch aeolus-configure-2.6.1-1.fc17.noarch deltacloud-core-1.0.5-1.fc17.noarch deltacloud-core-ec2-1.0.5-1.fc17.noarch deltacloud-core-openstack-1.0.5-1.fc17.noarch deltacloud-core-rhevm-1.0.5-1.fc17.noarch deltacloud-core-vsphere-1.0.5-1.fc17.noarch deltarpm-3.6-0.7.20110223git.fc17.x86_64 python-deltarpm-3.6-0.7.20110223git.fc17.x86_64 rubygem-aeolus-cli-0.5.0-1.fc17.noarch rubygem-aeolus-image-0.5.0-1.fc17.noarch rubygem-deltacloud-client-1.0.4-1.fc17.noarch I am completely new to aeolus, so didn't want to open a ticket if there is a configuration issue I'm missing vs. a functionality issue. Regards, Gavin Adams | Sr. Solutions Engineer