Aeolus_Components

{{toc}}

Aeolus Components

Aeolus is composed of many moving parts which communicate through carefully controlled APIs. The above diagram gives a good sense of how the various components interact.

• **Get It
  ** **Use It
  ** List of log files
• Development Setup - quickly build and install components from source.
• In Development - Learn about planned and future work.

Conductor

Conductor provides the web-based user interface that allow users to manage 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

Deltacloud

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.

[Image

Factory](https://www.aeolusproject.org/redmine/projects/image-factory)

Image Warehouse

• clearing iwhd

Oz

Aeolus Configure

• Aeolus Configure

Audrey

Spherical

Event Subsystem

• aeolus-umbrella:Event_Format
• aeolus-umbrella:Event_Definitions
• aeolus-umbrella:Event_Attributes
• [[Feature10SyslogEvent_Documentation]]
• Syslog_Libraries

Other

• 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
• Image Models - Images, ImageBuilds, TargetImages, and ProviderImages, oh my
• ICICLE