I just was offered a slot to present Aeolus at The Ohio LinuxFest .
The OLF is one of the biggest community-run Linux conferences in the
States so it'll be a great opportunity to share / promote the project to
a wide / diverse audience.
The conference is at the end of September, so besides my usual security
and other work up to then, I'm going to be taking some time to throw
together and send around a quality presentation for the event. I would
like to heavily lean on a demo, using the wui and cli tools to deploy to
the cloud using a hosted instance of Aeolus (even if that is non-public
at the time being). I'd like to skip over the configure / setup stuff
and just demonstrate the meat and bones of using the application to
deploy to the cloud.
Any thoughts, comments, presentation material, etc would be appreciated,
I've been following the Aeolus Community Assessment conversation and I though I might start a separate e-mail chain regarding an idea I had instead of railroading the original conversation.
>From what I saw of the original conversation, we're looking to build our community and evangelize Aeolus' strengths.
It's also been questioned as whether we'd recommend using Aeolus in it's current state in a production environment. This got me thinking... there's a difference between what we'd recommend to users, and what they'll actually do. By this, I mean that there might be a boffin or two somewhere who could devise some unique uses for Aeolus that we've never even thought of. And I think that what some might consider Aeolus's biggest weakness (it's still experimental) could end up being its biggest strength (experimental is fun and exciting!).
We develop our own (for lack of a better word) "Apps Store" -- a place when users can share Image and Deployable templates for Aeolus, much along the same lines as addons.mozilla.org or extensions.gnome.org. And following these subdomain conventions, I suggest... templates.aeolusproject.org!
How it works
A user writes an image template and deployable for a particular application. For example, they might want to launch a base Drupal installation in EC2 using Fedora as an OS. So they write an Image Template that includes the relevant Apache and Postgres packages. They also write a Deployable Template that installs and configures Drupal (via Audrey) to an instance with httpd/db.
Then the user thinks, "Hey, I bet there are others out there who want to install Drupal in the cloud. Maybe I should share these templates with the world."
The user uploads the templates to templates.aeolusproject.org, tags them as an Image Template and Deployable Template respectively, and create an associates between the two (basically a way of signifying a relationship between an image/deployable pair that works well together).
So then, I want to create a Drupal site on a standalone instance in my own RHEV environment.
I search templates.aeolusproject.org and find someone has already created the templates I need. Perfect. (Plus I could substitute the Image template for one with a different distro if I prefer).
I use both these template in Aeolus and install Drupal on EC2. It works great!
I go back to templates.aeolusproject.org and give the template author a 5-star rating. Great job, everything went better than expected. Plus, the rating helps his Deployable Template becomes TOTM (Template of the Month).
But I also leave a comment to say, "Hey, great templates, but I think you should include a param in the deployable that allows a user to input a comma-separated list of additional modules for their Drupal installation." This way I'm helping improve the content of templates.aeolusproject.org through feedback.
templates.aeolusproject.org does a couple of cool things:
1. Encourages people to join, contribute and collaborate to the Aeolus community
2. Encourages people to experiment with Aeolus and share their results
3. Helps new users wanting to learn more about TDL/Deployable XML
4. Provides users with a library of applications to launch into their cloud (and only needing two XML files to do so)
5. Gives us a better idea of how people are using Aeolus so that we can enhance the features they like and improve the features they don't like
These are very rough ideas that I've come up with in a day, so please forgive me if they seem a little ill-thought. Regardless, I do think is an idea that can really enhance the Aeolus Community and the project too. If anyone has an ideas, suggestions, drawbacks or general comments, please share them.
Engineering Content Services
Red Hat Asia Pacific Pty Ltd
Make sure if testing this that you are testing against conductor from
master. The versions currently present in f17 updates/updates-testing
are missing some functionality of the providers api; specifically,
creating a new provider will redirect to the provider html view. The
version in master will return a 200, with the xml body containing the
newly created provider. Configure validates this response body, so
the old version will not work.
As I return from PTO and try to catch up, I wanted to propose an idea.
I think it'd be swell if, at the beginning of each sprint, we sent out
an email outlining what we hope to accomplish, with a little blurb on
each story, a quick estimate, and who (if anyone yet) is taking it. It
could also spell out the start and end dates, as well as any other
notable dates (code freeze, etc.) It would help people like me get up to
speed more quickly, but much more importantly, I think it would be
interesting to people monitoring Aeolus development but not necessarily
Picking a random example from the backlog that I'm semi-familiar with,
we have #3499, which reads "As a user, I want a consistent, coherent UI"
with no further explanation. There's been other discussion of this, so I
happen to know what it means, but it's ultra-vague as published in
Redmine. It seems like it would be quite helpful if it got a blurb in a
beginning-of-sprint email like:
#3499 - As a user, I want a consistent, coherent UI
We've been gathering a list of UI annoyances on the wiki:
For this story, we plan to review that list and identify the "quick
fixes" that don't require much discussion/consideration, and then
implement them. This should make the Aeolus user experience much more
Jiri has volunteered to lead this; it is estimated at 13 points.
Admittedly, writing this up for each story is a decent bit of work.
However, it's really nothing but a quick summary of what we discuss on
sprint planning calls. I think this would have two benefits:
1.) It would be very useful as far as making it clear what we are doing,
especially to outsiders. (It would have an incidental benefit for people
like me, that miss a sprint planning call, but that's not the primary
2.) It would force us start to write decent descriptions for our tasks.
If people agree that this is useful, I'd be happy to take a stab at
writing it up next sprint during/after the planning call. What do you
think? And should Conductor/Infra emails be separate, or combined?
This revised patchset adds Rspec tests for the templates (very basic).
The mapping from /api/hardware_profiles to /hardware_profiles is temporary. It is needed to test the cli functionality. It can be removed later