OpenStack Support in Conductor (Revisited)
by Gavin Adams
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
11 years, 4 months
Factory_Girl version
by Jason Guiditta
Hello list, Tim currently uses Factory Girl version 4.1.0, and fedora
is going to be updated to use that, likely in f19 (possibly f18,
though it may be too late for that, unsure). I am wondering how to
slot that upgrade in for conductor timewise. It seems to me it would
be safe to do it anytime now, as the next downstream release for
redhat will need these updates and dependencies anyway, and upstream
can get there first. Does anyone have questions or concerns, or
should we just get this on a todo list $somewhere?
-j
11 years, 4 months
Fwd: Get your work done from GCI students
by Mo Morsi
Hey all just a reminder, this is still going on and tasks can be added
anytime.
This is a contest for high school students so tasks have to be quite a
bit smaller in scope than what your used to and mentoring students takes
some time, but is definitely a worthwhile experience IMO.
As before, if you're interested in this just shout out here or on IRC
and we can figure something out.
-Mo
-------- Original Message --------
Subject: Get your work done from GCI students
Date: Mon, 3 Dec 2012 10:30:20 +0530
From: Buddhike Kurera <bckurera(a)fedoraproject.org>
To: ambassadors <ambassadors(a)lists.fedoraproject.org>
CC: Mo Morsi <mo(a)morsi.org>
Hi FAms,
If you are thinking of getting a work done this would be a good news.
Fedora is participating GCI 2012 where students work on defined tasks.
Therefore if you have any task we can add it to the list and get it
done. Tasks that are feasible for students to complete such as design,
documentation, QA, testing and simple coding can be added to this
list. Therefore if you have any requirement like posters for your
release parties and kind of, please let me know, so that I can add
them.
Thanks
--
Regards,
Buddhike Chandradeepa Kurera (bckurera)
11 years, 4 months
RFC: The case for a default username/password
by Aaron Weitekamp
I understand this is ultimately a sysadmin responsibility, but is there
any scenario where a user would use the default username and password?
If defaults are for developer and testing convenience it seems we can
take the extra step to put our own values in. Given the serious security
concerns of leaving defaults in place, I'm wondering why would we
provide the option to use a default username/password?
-Aaron
--
Aaron Weitekamp | Red Hat CloudForms Integration QE | IRC: aweiteka
11 years, 4 months
dev-tools as non-root
by Giulio Fidente
hi there,
as per subject, I made some changes to dev-tools to make it work
successfully as non-root.
I tested these changes on CentOS6 and F17, my pull request:
https://github.com/aeolus-incubator/dev-tools/pull/7
it also includes some changes to README.md as it now provides a list of
packages to be installed system-wide before launching the script.
I thought launching as non-root was useful to both end users and devs
cause it helps with the testing, isolation from the other system
components, deploying of more versions in parallel and also provides
some abstraction from the hosting distro.
Feedback is very much appreciated.
--
Giulio Fidente
11 years, 4 months
Aeolus Tech Cabal - 04/12/12
by Martyn Taylor
Gentlemen,
Next weeks agenda can be found here:
http://beta.etherpad.org/p/AeolusTechCabal
Notice we have no new points for discussion.
I have removed many of the items that were on last weeks agenda, since
we agreed many of the points should be first solved on the list/irc. If
you feel you need to readd any of these points, please drop them in.
Unfortunately, the old link to the Agenda is down (since
openetherpad.org is down) if you added agenda items to the old etherpad
page this week, please add them to the new page at the link above.
The normal deadline for Agenda items is end of play today (to give
people time to prepare), but since we've had problems with etherpad feel
free to add items tomorrow (be aware though that people will not be
prepared for items added last minute).
Regards
Martyn
11 years, 4 months
[aeolus-incubator/tim] 041c3e: Added Validation to Models
by Martyn Taylor
Branch: refs/heads/model_validations
Home: https://github.com/aeolus-incubator/tim
Commit: 041c3e0fd6cd6c3e250c8848f19ce7ed95296be5
https://github.com/aeolus-incubator/tim/commit/041c3e0fd6cd6c3e250c8848f1...
Author: Martyn Taylor <mtaylor(a)redhat.com>
Date: 2012-12-03 (Mon, 03 Dec 2012)
Changed paths:
M app/models/tim/base_image.rb
M app/models/tim/image_version.rb
M app/models/tim/provider_image.rb
M app/models/tim/target_image.rb
M spec/controllers/base_images_controller_spec.rb
M spec/controllers/image_versions_controller_spec.rb
M spec/controllers/provider_images_controller_spec.rb
M spec/controllers/target_images_controller_spec.rb
M spec/factories/tim/provider_image.rb
M spec/factories/tim/target_image.rb
M spec/models/base_image_spec.rb
M spec/models/dummy/pool_family_spec.rb
M spec/models/dummy/provider_account_spec.rb
M spec/models/dummy/provider_type_spec.rb
M spec/models/dummy/user_spec.rb
M spec/models/image_version_spec.rb
M spec/models/provider_image_spec.rb
M spec/models/target_image_spec.rb
M spec/models/template_spec.rb
M spec/views/base_images_spec.rb
Log Message:
-----------
Added Validation to Models
Commit: d1b491568b33ed7db05047e0cd6c0ccb62c58265
https://github.com/aeolus-incubator/tim/commit/d1b491568b33ed7db05047e0cd...
Author: Martyn Taylor <mtaylor(a)redhat.com>
Date: 2012-12-03 (Mon, 03 Dec 2012)
Changed paths:
A app/patches/rails/active_record/autosave_association.rb
Log Message:
-----------
Fixed Rails Bug in Monkey Patch
Compare: https://github.com/aeolus-incubator/tim/compare/dcdb9382fe63...d1b491568b33
11 years, 4 months
