Home
Aeolus is software for running virtual machines both internally on your own equipment, and in Clouds from several leading vendors. All at the same time.
REDUCE YOUR RISK of being caught out whenever your preferred Cloud vendor has issues.
-
Frequently Asked Questions (FAQs)
-
Aeolus vs. OpenStack - A comparison
If you have further questions, please feel free to contact us.
After following the Use It instructions, use these guides to explore other features.
- Launching Instances - A quick guide to building, pushing, and launching images from Conductor
- Building Images for RHEL - How to build images for Red Hat Enterprise Linux
- Building Images for Windows - Building Windows guests is not supported by Aeolus at this time
- Oz_template_description_language
- Deployable XML
- Image Warehouse Admin Guide
- Using Audrey with Conductor for post-boot config
- Upgrading Aeolus - Step-by-step upgrade instructions
- LDAP Support
- Command Line Interface commands
- Known limitations
The Use It guide explains how to configure Aeolus for Amazon EC2. To configure Aeolus for additional providers, follow these instructions:
- Common Error Messages - Common errors and how to fix them
This section is for people who’d like to contribute to the Aeolus project, or who simply want to get a peek behind the scenes.
- Developer Information - Resources for developers to get them up and running quickly.
- Developers communicate through the aeolus-devel mailing list
- Coding Guidelines
- Implementing New Providers - So you want to add support for a new cloud provider?
- Manual Aeolus installation on CentOS, Fedora, and others -- How to manually install latest Aeolus components together on CentOS, Fedora, and more.
Aeolus is composed of many moving parts which communicate through carefully controlled APIs.
- List of log files
- Development Setup - quickly build and install components from source.
- In Development - Learn about planned and future work.
Conductor provides the web-based user interface that allow users to manage Aeolus.
- Conductor_API
- Roles and Permissions - Roles and Permissions system
- Internationalization - How to write code that can be translated into other languages
- Rails3 Upgrade
- Catalogs
- Renaming All the Components
- Upstream and Product Name Cheatsheet
- Instance and provider states
- Image Management Engine
- Cloud State
- Provider Selection Algorithms
- Auto Scaling - Initial thoughts on instrumentation requirements and implementation of automated instance scaling.
- Catalogs
- Deployables - draft
- Deployments - draft
- Instances - draft
- Pool Families - mapping of provider accounts needs to be revised
- Pools
- Provider Types - draft
- Providers
- Provider Accounts
- Realms - Front End - draft
- Realms - Provider
- Detailed architecture of the Conductor UI
- Conductor UI Style Guide (_work-in-progress_)
- Mustache templates
- List of UI Annoyances - We are collecting UI inconsistencies and annoyances here to tackle
- Forms - Basic developer guide
- Image Build/Push - workflows, concepts
- blog.aeolusproject.org playbook
- Etherpad playbook for etherpad-aeolusproject.rhcloud.com
Deltacloud is an independent open-source project that provides an abstraction layer in front of supported cloud APIs. This abstraction is what allows Conductor to easily manage multiple cloud providers.
Deltacloud utilizes a RESTful API for communication.
- aeolus-umbrella:Event_Format
- aeolus-umbrella:Event_Definitions
- aeolus-umbrella:Event_Attributes
- Feature_1_0_Syslog_Event_Documentation
- Syslog_Libraries
- Using the RHEV-M API - How to find RHEV data centers and image templates using the API
- document:“Aeolus/Katello User Stories”
- Condor Removal - The hows and whys of our switch away from Condor for scheduling
- OAuth as used in Aeolus between components
- Image Models - Images, ImageBuilds, TargetImages, and ProviderImages, oh my
- ICICLE
- RPM diff between master and product - rpms currently used in master but not available yet in product
- Debugging Conductor (production)
-
General Development Process - What is the general flow of development to keep things sane (and branches next/master in a reasonable state)
-
Release Checklist - Checklist of tasks done for each release
-
Code Repository and Commits - Ready to contribute? Learn about our access and commit policies.
-
Testing Holy Grail - Pragmatic look at testing in our app (ported from old wiki)
-
Continuous Integration Testing - We are currently using Travis CI. We also evaluated CloudBees and OpenShift.
-
In Development - Learn about planned and future work.
-
- Estimated next release dates for all Aeolus projects
-
Documentation Plan - Planning for user documentation expansion
- Presentations about Aeolus
- Upcoming Topics
- Git Inside (not presented yet)
- Plugins In Use - Info about plugins we currently have set up
- Plugins Of Interest - Plugins we may want to think about using
- Public Redmine - Options for a publicly facing Redmine (COMPLETE)
- Redmine Bugzilla Integration
- Redmine Performance - it’s annoyingly slow
- Publicity Cabal - Notes from the regular Publicity Cabals
- Release Cabal - Notes from the regular Release Cabals
- Website Cabal - I bet you can figure it out
Aeolus developer conference November 5-9, 2012 (over)
- Agenda ======================================================