From Fedora Project Wiki
< Changes
(Moving to Fedora 22) |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 22: | Line 22: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Fedora | * Targeted release: [[Fedora 22 ]] | ||
* Last updated: April 8, 2014 | * Last updated: April 8, 2014 | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 32: | Line 32: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1090879 #1090879] | ||
== 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. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones, produced in collaboration with the Big Data SIG. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 44: | Line 45: | ||
<!-- What work do the developers have to accomplish to complete the change 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 change 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?--> | ||
* Proposal owners: The developers must get a kickstart ready for a big data image that has the Hadoop ecosystem installed and configured for changes that distributed big data servers typically need. The developers may also if time is permitting work on a second big data image centering around the Apache Mesos ecosystem. The change does not affect large part of the distribution and does not block or affect other parts of the distribution. | * Proposal owners: The developers must get a kickstart ready for a big data image that has the Hadoop ecosystem installed and configured for changes that distributed big data servers typically need. The developers may also if time is permitting work on a second big data image centering around the Apache Mesos ecosystem. The change does not affect large part of the distribution and does not block or affect other parts of the distribution. | ||
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 55: | Line 55: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
No previous image exists; no upgrade imapact or compatibility changes. | |||
== How To Test == | == How To Test == | ||
| Line 95: | Line 92: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 103: | Line 98: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:ChangePageIncomplete]] | |||
[[Category:SelfContainedChange]] | [[Category:SelfContainedChange]] | ||
Latest revision as of 15:07, 13 October 2014
Big Data Cloud Image
Summary
Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones, produced in collaboration with the Big Data SIG.
Owner
- Name: Julien Eid
- Name: Haïkel Guémar
- Email: jeid64@gmail.com
- Email: karlthered_gmail_com
- Release notes owner:
- Product: Fedora Big Data Cloud image
- Responsible WG: Cloud
Current status
Detailed Description
Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones, produced in collaboration with the Big Data SIG.
Benefit to Fedora
The benefit to the platform is for people interested in large distributed "big data" applications that want to use Fedora while being able to spin up VM's or containers on a number of "cloud" platforms. It merges the ability to have distributed applications be easily spun up on a large number of virtualized machines.
Scope
- Proposal owners: The developers must get a kickstart ready for a big data image that has the Hadoop ecosystem installed and configured for changes that distributed big data servers typically need. The developers may also if time is permitting work on a second big data image centering around the Apache Mesos ecosystem. The change does not affect large part of the distribution and does not block or affect other parts of the distribution.
- Other developers: N/A (not a System Wide Change)
- Release engineering: not a System Wide Change, but there will be a new image for release engineering to produce and handle.
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
No previous image exists; no upgrade imapact or compatibility changes.
How To Test
A basic test will involve booting the image in a cloud environment and running some of the featured tools.
A test plan including as much automation as possible will be developed.
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: No Big Data image until F22.
- Contingency deadline: Since this is largely based on the Cloud Base Image plus additions, beta freeze is the deadline.
- Blocks release? No
- Blocks product? No
Documentation
N/A (not a System Wide Change)