-
Notifications
You must be signed in to change notification settings - Fork 0
Proposed_Wiki_Reorg
{{toc}}
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.
-
**Get It
** **Use It
** Latest News -
Presentations about Aeolus
-
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
- [[Oztemplatedescription_language|Template Description Language (TDL)]]
- Deployable XML
- Image Factory wiki
The Use It guide explains how to configure Aeolus for Amazon EC2. To configure Aeolus for additional providers, follow these instructions:
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.
-
Aeolus Components - Learn about the various components that work together within Aeolus.
-
Developer Information - Resources for developers to get them up and running quickly.
-
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
-
Testing Holy Grail - Pragmatic look at testing in our app (ported from old wiki)
Aeolus uses GitHub for its code repository.
- Git Commit Access Policy
- Git Branching Strategy - Where should I be putting my stuff and how does it affect releases?
- Git Workflow - How to send and apply patches
- Patch Reviews and Commits
- Infrastructure Projects - Email git patch or not email git patch. That’s the question.
- Packaging
Conductor is the web-based user interface that manages Aeolus.
- Conductor_API
- Conductor Image Management API - Initial Design Thoughts for providing Restful Image Management API through Conductor
- 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
- aeolus-umbrella:Event_Format
- aeolus-umbrella:Event_Definitions
- aeolus-umbrella:Event_Attributes
- [[Feature10SyslogEvent_Documentation]]
- Syslog_Libraries
A summary of the Aeolus infrastructure components can be found on the Projects page.
- Aeolus Configure
- Common Error Messages - Common errors and how to fix them
- 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
- clearing iwhd
- Image Models - Images, ImageBuilds, TargetImages, and ProviderImages, oh my
- ICICLE
- Development Setup - How to build and install components from source
This section details planned and future work.
- Hardening the app
- Integration Environment + Automated Tests - High level description of the infrastructure requirements to flush out problems sooner
- Next-generation Testing Brainstorm - Thoughts for enhancing test coverage
- Website Revamp Project
- Feature - Launch Stand-alone Images
- Pacemaker Cloud and Conductor Notification API - under review, not yet implemented
- Feature - Permissions management UI
- [[ConductorDeployableTemplate_Stories]]
- TBD
- 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