From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...")
 
No edit summary
Line 11: Line 11:
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->


= Feature Name <!-- The name of your feature --> =
= Feature Name OpenNebula =


== Summary ==
== Summary ==
Line 18: Line 18:
== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:FASAcountName| Your Name]]
* Name: [[User:Spstar|Shawn Starr]]
* Email: [mailto:shawn.starr@rogers.com]


<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Name: [[User:Jmelis|Jaime Melis]] (upstream project)
* Email: <your email address so we can contact you, invite you to meetings, etc.>
* Email: [mailto:jmelis@opennebula.org]


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/17 | Fedora 17 ]]
* Last updated: (DATE)
* Last updated: (11/18/2011)
* Percentage of completion: XX%
* Percentage of completion: 0%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
[http://opennebula.org]Open Nebula is an Open Source framework for Data Center Virtualization. The project is designed to be scalable and offer compatibility with Amazon EC2 the Open Cloud Computing Interface (OCCI).
 
It includes a core (oned) which orchestrates the deployment and management of Virtual Machines, and is managed via a CLI, a web service (Sunstone), and language specific bindings (Ruby, Java and Python).
 
It also features management of Virtual Data Centers.


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
Allow Fedora to have an integrable and extensible framework for Data Center Virtualization.


== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
Get all dependencies into Fedora, and build a single package that provides OpenNebula. Upstream will test it.


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.  
OpenNebula must be tested in a physical server, not a Virtual Machine, since it requires virtualization extensions to manage Virtual Machines. The physical server must have virtualization capabilites.


Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A typical OpenNebula installation requires external servers to handle virtualization, but for these purposes the same server can be used as:
* OpenNebula frontend: opennebula package + dependencies
* OpenNebula node: a hypervisor of choice. Libvirt + KVM recommended.


A good "how to test" should answer these four questions:
After installing the software, these tests should be run to validate the package:
* Manage a Virtual Machine with the CLI (following [http://opennebula.org/documentation:rel3.0:vmg|these] instructions). This implies creating a network, registering a host, an image, etc.
* Use the graphical user interface (sunstone) to do the same thing.


0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Fedora users will be provided with a CLI and a web-based GUI to manage VMs.


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
TODO: create list (mainly rubygems)


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
Delay the release to F18.


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
* [http://opennebula.org/documentation|OpenNebula Official documentation].


== Release Notes ==
== Release Notes ==

Revision as of 17:36, 18 November 2011

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Feature Name OpenNebula

Summary

Owner

Current status

  • Targeted release: Fedora 17
  • Last updated: (11/18/2011)
  • Percentage of completion: 0%


Detailed Description

[3]Open Nebula is an Open Source framework for Data Center Virtualization. The project is designed to be scalable and offer compatibility with Amazon EC2 the Open Cloud Computing Interface (OCCI).

It includes a core (oned) which orchestrates the deployment and management of Virtual Machines, and is managed via a CLI, a web service (Sunstone), and language specific bindings (Ruby, Java and Python).

It also features management of Virtual Data Centers.

Benefit to Fedora

Allow Fedora to have an integrable and extensible framework for Data Center Virtualization.

Scope

Get all dependencies into Fedora, and build a single package that provides OpenNebula. Upstream will test it.

How To Test

OpenNebula must be tested in a physical server, not a Virtual Machine, since it requires virtualization extensions to manage Virtual Machines. The physical server must have virtualization capabilites.

A typical OpenNebula installation requires external servers to handle virtualization, but for these purposes the same server can be used as:

  • OpenNebula frontend: opennebula package + dependencies
  • OpenNebula node: a hypervisor of choice. Libvirt + KVM recommended.

After installing the software, these tests should be run to validate the package:

  • Manage a Virtual Machine with the CLI (following [4] instructions). This implies creating a network, registering a host, an image, etc.
  • Use the graphical user interface (sunstone) to do the same thing.


User Experience

Fedora users will be provided with a CLI and a web-based GUI to manage VMs.

Dependencies

TODO: create list (mainly rubygems)

Contingency Plan

Delay the release to F18.

Documentation

Release Notes

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/OpenNebula&oldid=261578"