From Fedora Project Wiki
Line 61: Line 61:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation 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.  
A basic test will involve booting the image in a cloud environment and running some of the featured tools.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A test plan including as much automation as possible will be developed.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== User Experience ==
== User Experience ==

Revision as of 20:09, 8 April 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

  • Targeted release: Fedora 21
  • Last updated: April 8, 2014
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

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

N/A (not a System Wide Change)

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)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Big_Data_Cloud_Image&oldid=375814"