No edit summary |
No edit summary |
||
Line 67: | Line 67: | ||
== How To Test == | == How To Test == | ||
Install all dependencies. Once installed, run "aeolus-configure" as root to configure the system. Once aeolus-configure has completed, login to the host at http://some.host.org/conductor and test the UI end-to-end, including building images, uploading images to specific clouds, and launching instances in the clouds. More information is available at [http://www.aeolusproject.org/use_it.html]. | Install all dependencies. Once installed, run "aeolus-configure" as root to configure the system. Once aeolus-configure has completed, login to the host at http://some.host.org/conductor and test the UI end-to-end, including building images, uploading images to specific clouds, and launching instances in the clouds. More information is available at [http://www.aeolusproject.org/use_it.html]. | ||
== User Experience == | |||
== Dependencies == | |||
Many. See the list | |||
== Contingency Plan == | |||
== Documentation == | |||
== Release Notes == | |||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | |||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | |||
== Comments and Discussion == | |||
== Help == | |||
If you need help, please [http://www.aeolusproject.org/contact.html contact us]. | |||
[[Category:FeaturePageIncomplete]] | |||
<!-- When your feature page is completed and ready for review --> | |||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | |||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | |||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> |
Revision as of 19:08, 25 May 2011
Feature Name Aeolus Conductor
Summary
Aeolus Conductor (http://aeolusproject.org) is a cross-cloud IaaS platform.
Owner
- Name: Chris Lalancette
- Email: clalance@redhat.com
Current status
- Targeted release: Fedora 16
- Last updated: 2011-05-25
- Percentage of completion: 0%
- Packages submitted for review:
- Packages necessary, but not yet submitted:
- compass-960-plugin >= 0.9.13
- rspec-rails >=1.3.2
- aeolus-image-builder-agent
- aeolus-image-builder-console
- sunspot_rails
- cucumber-rails
- factory_girl
- sunspot
- waz-blobs
- fog
- excon
- iwhd
- aeolus-conductor
- condor >= 7.5.5
- solr
- oz
- imagefactory
- python-cloudservers
Updates:
- 2011-05-25 - Initial Feature submission
Detailed Description
Aeolus is an umbrella for a number of cloud related projects. The projects all come together to create the Conductor, a Web UI and tools for managing cloud instances across heterogeneous clouds. For instance, a user can build and launch instances into EC2, RHEV-M, and Rackspace all from the same UI.
Benefit to Fedora
Allow Fedora to have a hybrid cloud-management stack.
Scope
Get all dependencies into Fedora, and test the project end-to-end.
How To Test
Install all dependencies. Once installed, run "aeolus-configure" as root to configure the system. Once aeolus-configure has completed, login to the host at http://some.host.org/conductor and test the UI end-to-end, including building images, uploading images to specific clouds, and launching instances in the clouds. More information is available at [1].
User Experience
Dependencies
Many. See the list
Contingency Plan
Documentation
Release Notes
Comments and Discussion
Help
If you need help, please contact us.