Presentations
These slides present an overview of the project, or related concepts. They are listed in reverse chronological order.
| Title | URL | Presentors/Authors | Focus |
|---|---|---|---|
| Aeolus Projects | google doc | Hugh Brock | Comprehensive Aeolus overview |
| Deploying Across Clouds: The Open Source Way | pdf, showoff, commands | Mo Morsi at Ohio LinuxFest 2012 | Minimal slides, heavy on live demo |
| “Clouds in the wild” | showoff | Francesco Vollero and Michal Fojtik | Focusing on Deltacloud and Aeolus |
| “The Aeolus Project: A Breeze to the Cloud” | Francesco Vollero delivered at FOSDEM 2012 | ||
| “Aeolus: Cloud Management System” (in Czech) | Jaromír Coufal delivered at Charles University | ||
| “Aeolus Architecture Diagram” | png | Chris Lalancette at FUDCON 2011 | |
| “Opening Up Cloud Computing With Aeolus” | odp | Upstate NY Engineering Expo Mo Morsi | Beginner cloud computing / Aeolus overview for less-technical audience |
| “Opening Up Cloud Computing With Aeolus” | odp | Mo Morsi - FOSSCon | Updated overview, minimal slide text, focusing more on talk |
| “Deltacloud: Many Clouds, One API, No Problem” | odp | FUDCon - Mo Morsi | Early project overview, when project was known as deltacloud |
These presentations focus on specific components or aspects of Aeolus.
| Title | URL | Presentors/Authors | Focus |
| Designing HTTP RESTful APIs | showoff | Petr Blaho, Jiri Stransky | |
| Apache Deltacloud API v1.0 | showoff | Michal Fojtik | |
| Orchestrating complex deployments on OpenStack using Heat | showoff, screencast | Tomas Sedovic | |
| Image management in a federated cloud environment | odp | Martyn Taylor | |
| Aeolus on Heat (on Deltacloud) | showoff | Tomáš Šedovič | Heat API with regard to Conductor |
| Conductor Walkthrough | zip | Jaromír Coufal | Improving and standardizing Conductor UI |
| converge-ui | zip | Jaromír Coufal | The converge-ui (now ui-alchemy) project |
| Developing the Aeolus Community | odp | Tzu-Mainn Chen, Matt Wagner, Jiří Stránský, Francesco Vollero | Discussing about enhancing and expanding the upstream community |
| Provider Selection | Imre Farkas | Conductor’s provider selection system | |
| Renaming Status | Angus Thomas | Conductor vs. downstream product terminology | |
| Winged Monkey | Angus Thomas | Winged Monkey project | |
| Conductor API & CLI | odp | Richard Su | Status future of the Conductor API and CLI tools |
| dev_tools | odp | Richard Su | Tools for setting up an Aeolus development environment |
| Upstream and the Future | Hugh Brock | The importance of a strong upstream community | |
| Conductor Roles and Permissions UX Evaluation | Jeremy Perry | A look at the user experience of our Roles and Permissions screens | |
| Rails Engines | odp | Martyn Taylor | Rails Engines |
| Introduction to Openstack and the HEAT API project | odp | Steven Hardy | Openstack and Heat |
| Tim | odp | Martyn Taylor | The Tim engine |
| Resource State Tracker | Jan Provaznik | Formerly known as Deltacloud Tracker | |
| Travis | odp | Richard Su | Upstream CI |
| “Git Workflow” | odp | Chris Lalancette | Working with git |
Resources to use to setup and use environments containing Aeolus.
The following is suggested for a robust demonstration of Aeolus capabilities:
- 2 workstations - one to serve as one or more ‘external’ cloud providers and one to serve as the Aeolus server controlling this.
- ‘’’Highly suggested’’’ to not rely on external cloud resources (such as EC2 or other), networks at conferences are almost always unreliable, and many operations (eg uploading images) take time
- One workstation could be used, though it is conceptually nice to show Aeolus in one location controlling external cloud resources
- Cloud provider workstation: (reqs will vary depending on the providers), a minimum of 3GB of memory 250GB of disk space and hardware virtualization is required
- The Aeolus workstation: hardware virtualization is required
- Fresh Fedora 17 install, Aeolus is available to existing systems, of various OS and Distro types, but to ensure you don’t lose any local data and that the config experience goes as smooth as possible an unused F17 system is desirable
- Setting_up_Openstack
- Setting_up_oVirt
- Setting_up_vSphere # coming soon
Aeolus Demo Setup Aeolus Demo Commands
It is good to begin and end the demo by cycling back around to the problem at hand at the solution Aeolus provides. Discussing vendor lockin, proprietary and custom apis, and price hikes, and how Aeolus can be used to mitigate all that (as just demonstrated).
Deploying Fedora to oVirt using Aeolus