I'm unable to run 'cucumber' or 'rake spec' against conductor using f15.
1) Running 'cucumber' in the src directory gives me this:
no such file to load -- cucumber/rails (LoadError)
Before you send me to lmgtfy.com, I'm wanting to know if any other aeolus developers have hit this same error, and if so what was the workaround specific to our codebase. Is this an error in conductor code itself or a problem with my environment?
2) Running 'rake spec' in the src directory results in no output to stdout from the command, which exits immediately and with a clean exit status. Same if I run it as 'rake --verbose spec'...no output whatsoever.
Thank you, I now return to slowly hitting my head against my desk.
After discussing the "What Is Aeolus?" document / mission statement, and
after reading an article about Aeolus that got a few technical details
wrong, it occurred to me that, in addition to "What Is Aeolus?", we
might want a "What Aeolus Is NOT" page.
Here's a quick stab at that. Obviously, I didn't set out to make a
complete list of things Aeolus is not (a trombone, pecan pie, etc.), but
I tried to focus on possible/common misconceptions. Could you let me
know if (a) the below is accurate and reasonably complete, and (b) if
you think it makes sense to have such a list or not?
* Aeolus is not a part of Linux. Although our packaging efforts
currently focus on Linux, Aeolus is not explicitly tied into Linux. It
is a suite of applications that run on Linux and related operated
(I struggled with how to word this one. I read an article that seemed to
imply Aeolus was a kernel module for the cloud or something of the sort,
which is the idea I'm trying to dispel.)
* Aeolus is not owned by Red Hat. Although the majority of Aeolus
developers are currently sponsored by Red Hat, the project is an
independent community effort.
* Aeolus is not a cloud. Aeolus is a project for managing existing
clouds (public and private), not an attempt at creating yet another
I have started designing katello interface that will return katello
templates in CDL format and would like to ask for more information about
I am particularly interested in all the tags that can appear in the XML
document. Also all possible values that are currently accepted is a must
for me - e.g. os tag (which operating system and version combinations
are supported atm).
I already found few exampled which gave me pretty nice overview how it
<os name="fedora" version="13"/>
Let me describe current template in Katello. We associate template with
environment first, then users are able to add content to it (only using
CLI atm - no support in the UI):
- products (= 1 or more repositories)
- package (no package group support yet)
- foreman host group (not done yet - puppet classes definitions)
- parameters (for puppet classes)
Looking on the example above I have a nice match here:
CDL vs Katello
name = template name
description = description
os = product info
repos = products
packages = packages
package group = n/a
I guess we have all required information to build image template from
Katello, skipping package groups (we can add them later).
Lukas "lzap" Zapletal
I checked all the controllers everything looks good except this list of
controller have no permission checking at all
Next step should be to create subtasks for 2134 and implement the
permissions. Since I am leaving for PTO today afternoon it would be good
if someone can retake this task, or if it can wait till 12.9 i will
After messing things up locally and then provisioning a fresh box for testing, I realized that if I clone the conductor repo, install aeolus-conductor-devel, uncomment the 'development' section in Gemfile, and run "bundle install", it still fails with some errors.
This adds the three packages I needed to install in order to avoid fatal errors. It would be good if someone with a good handle on RPM packaging could sanity-check this, though.