Cloud images must be easy to consume as part of a public or private cloud. Because we target these environments, we won't be worrying about physical media at all. The cloud images also won't be "installed" in the same manner that users are accustomed to with desktop or server images. The cloud image will simply boot in its target environment ready to run, or for further customization and configuration via a boostrapping service.

Cloud images must be easy to consume as part of a public or private cloud. Because we target these environments, we won't be worrying about physical media at all. The cloud images also won't be "installed" in the same manner that users are accustomed to with desktop or server images. The cloud image will simply boot in its target environment ready to run, or for further customization and configuration via a boostrapping service.

=== Where to obtain ===

=== Where to obtain ===

−

Users will be able to obtain the images for public clouds via download ''or'' via the usual marketplace for those images. For instance, we publish AMIs to be run on the [https://aws.amazon.com/ Amazon Web Services] (AWS) directly to the [https://aws.amazon.com/marketplace AWS Marketplace]. Users are able to launch new instances with Fedora without having to obtain the images directly from the Fedora Project and then upload to AWS.

+

Users will be able to obtain the images for public clouds via download ''or'' via the usual marketplace for those images. For instance, we publish AMIs directly to the [https://aws.amazon.com/marketplace AWS Marketplace]. Users are able to launch new instances with Fedora without having to obtain the images directly from the Fedora Project and then upload to AWS.

Users will be able to download appropriate images for Apache CloudStack, Eucalyptus, OpenStack, OpenNebula, and other IaaS platforms.

Users will be able to download appropriate images for Apache CloudStack, Eucalyptus, OpenStack, OpenNebula, and other IaaS platforms.

Line 321:

Line 321:

== Document Conventions==

== Document Conventions==

=== Definitions and Acronyms ===

=== Definitions and Acronyms ===

−

* AWS: Amazon Web Services

+

* AWS: [https://aws.amazon.com/ Amazon Web Services]

* Amazon EC2: Amazon Elastic Compute Cloud, a popular public IaaS, part of AWS

* Amazon EC2: Amazon Elastic Compute Cloud, a popular public IaaS, part of AWS

Document Purpose and Overview

Provides a high-level market of the cloud computing market as it pertains to the Fedora Cloud SIG; this includes overviews of things which may not be within our actual scope/ability to accomplish at the current time.

Provides deeper understanding of the types of users who could use Fedora for their cloud computing needs. This includes describing their main day-to-day tasks, common problems, and so on. The perspective here is not necessarily limited to system administrators, or developers, but a combination of many types of users and roles.

Ties common issues and needs of potential users and consumers of the Fedora Cloud product to high-level product needs, from a "functional" standpoint

Provides solutions, in the form of "changes" or "features" which will provide the functionality described as needs for the potential users.

Release/Product Overview

Fedora Cloud provides a customizable base image and tools for developing scale out applications on public and private clouds, as well as two to four images pre-configured for what we expect to be the most popular scenarios/use cases for using Fedora for cloud computing.
Public and private cloud adoption is taking off, and the requirements for an image OS differ significantly from the requirements for a desktop or server OS. In these environments, much or all of the instance lifecycle — from the creation of the image and addition of software or configuration specific to the instance, to the teardown of the image — will be automated. Systems are designed to scale out via many identical nodes rather than scale up with carefully-tended individual servers. Individual uptime (mean time between failure) is not as important as the ability to get a new instance running quickly (mean time to recovery).
With that in mind, we're tailoring a release specifically for cloud environments.

Market Opportunity

Public and private cloud adoption is happening rapidly, but the market is not yet mature and is relatively ripe for disruption even though some favorites have emerged as early leaders.
In the next two to three years, we expect to see a great deal of growth in adoption and still see a number of emerging players where no clear favorites have emerged (for instance, Google Compute Engine). Additionally, some platforms (Amazon Web Services) have matured to a point where a large number of companies are relying upon the technology for their full infrastructure. While this is not a widespread practice, AWS is seeing a great deal of adoption and will likely start eating into "traditional" workloads that currently live behind the firewall.
In short, there's an enormous opportunity for Fedora to become an instance-OS of choice if the project moves quickly, develops or adopts the right technologies, and succeeds in educating the market about its existence. A failure on any of those three points means that the Fedora Cloud product will have little chance in taking a significant portion of the new market or taking any of the existing market.

Major Release Themes

Cloud computing in general is the transition of computing power from individual hand-tended resources to a ubiquitous utility. Fedora fits in at several levels, from the infrastructure service software we include (like OpenStack and Eucalyptus) to end-user tools.
The Fedora Cloud image fits into middle of this, providing a guest OS image to run on Infrastructure as a Service systems, on which platform and application services can be deployed. We targets use cases which fit the "cattle" side of the "pets vs. cattle" metaphor for computing.

Secondary Objectives

Aside from adoption and development of applications on top of the Fedora Cloud images, we have a few secondary goals that will be helped by wider adoption:

More testing of Fedora images with additional bug reports.

Better feedback about how the product should improve. This is separate from "bug reports" in that we hope to engage the audience and receive detailed feedback about use cases, desired features, developing trends in cloud management, etc.

Patches and contributions that will help improve the product, and Fedora in general. As we are increasingly successful, more users will take an interest in helping to develop our product.

Target Market / Audience

Developers and operators creating scale out applications on top of public and private clouds, and organizations and users running those applications. Fedora is particularly interested in organizations that might want to contribute back to Fedora and be involved in helping find/report/fix bugs, and develop new features.

Delivery Mechanisms

Cloud images must be easy to consume as part of a public or private cloud. Because we target these environments, we won't be worrying about physical media at all. The cloud images also won't be "installed" in the same manner that users are accustomed to with desktop or server images. The cloud image will simply boot in its target environment ready to run, or for further customization and configuration via a boostrapping service.

Where to obtain

Users will be able to obtain the images for public clouds via download or via the usual marketplace for those images. For instance, we publish AMIs directly to the AWS Marketplace. Users are able to launch new instances with Fedora without having to obtain the images directly from the Fedora Project and then upload to AWS.
Users will be able to download appropriate images for Apache CloudStack, Eucalyptus, OpenStack, OpenNebula, and other IaaS platforms.

Delivery Format

Images will be delivered as AMIs on Amazon EC2, and as downloadable images in qcow2 and raw.xz formats. We may add other public cloud images and other downloadable formats to meet demand or anticipated need.

Architectures

Initially, we will target 32 and 64-bit x86. As ARM-based cloud systems become available, we will add ARM images. We may consider dropping 32-bit x86 in the future.

Updates

Fedora Cloud images can be updated using yum as normal. We also intend to produce periodic respun images with security updates, once the infrastructure is in place to support that.

Image Creation Toolkit

We will also maintain a set of tools that can be used to generate, modify, and configure Fedora instances for use with public and private clouds. Initial efforts will focus on creating official images in Fedora's build system. This effort is in parallel to that and does not block the main release. The Fedora Cloud SIG is also interested in a curated library of image templates.
Unofficial templates will be made available through a peer-reviewed portal, so that users can use these templates with confidence to bootstrap their own images.

Measuring Success

Currently, Fedora is not a widely used option for instances on public and private clouds. We know there's some usage, but it's not one of the top three or four OSes on Amazon or (likely) for private clouds.
Success looks like:

Increase in adoption.

Third party support / targeting of Fedora Cloud as a platform.

Increased contribution and participation in the Fedora Cloud WG and Fedora Project in general.

User Profiles, Goals, and Primary Use Cases

User Profiles

There are three cloud user roles which describe the tasks of the people who interact with any cloud-based system:

Cloud Service Creator: Develops the technical and business aspects of a (simple or high-level) cloud service

Cloud Service Provider: Provides all types of services to a Service Consumer

Cloud Service Consumer: Consumes all types of services offered by a Service Provider

We will use a set of personas to describe our target users and their respective needs. These users are primarily in the cloud service creator and cloud service provider roles.
This document lists the personas in summary form, with detailed explanations of each one available in a separate document. https://fedoraproject.org/wiki/Cloud_Personas. These roles include aspects of cloud service creators, providers, and consumer.

AWS enthusiast and Early Adopter

Writes and maintains a number of AWS-deployed applications including staging and production.

Works for a small start-up, primarily on his own. Automates as much as possible.

DevOps Team Member

Uses the cloud to do Ruby on Rails development utilizing virtual machines.

Works as part of a DevOps team responsible for all aspects of a set of applications.

Development, QA, and Production environments need to be identical.

Web Developer

Concentrates on app development, not architecture, deployment, or operations.

Unlikely to care deeply about OS internals, cares that they can easily deploy the frameworks they want to use.

Large-Environment Sysadmin

Interested in deploying self-service PaaS to lighten operational load

Will work closely with development team on deployment and development.

Primary Use Cases

Web Application Deployment in a Public Cloud

Modern web applications are deployed as a collection of interconnected services, including parts like web servers, application servers, databases, and caching layers. Fault tolerance is handled at the overall orchestration level rather than by individual instances. Fedora Cloud can be the base of each of these parts, providing recent libraries, server software, and language toolchains. Each system will be managed using the public cloud's own management tools plus a configuration management system like Puppet, Chef, Salt, or Ansible.
Code may be developed against different language stacks; if these are readily available to users, that's a win. In the real world, libraries and other code we don't include may also be required and we should make that as painless as possible.
Fedora Cloud will provide access to the following stacks (not exhaustive):

Ruby: Rails, Sinatra

Python 2 & 3: Django, Pyramid, Flask

PHP 5.x: Symfony2, ZendFramework 2.x

Node.js

Java

Perl 5.x

Go

Web Application Deployment in Private Cloud

As above, but in a locally-deployed and managed private cloud system.

Web Application Deployment in Hybrid Cloud

As above, but rather than a single cloud provider, the application seamlessly takes advantage of resources in both a private and public cloud.

Hybrid Cloud as Staging Area

Application development and testing happens in-house on a private cloud, while production goes to a public cloud.
Possible scenarios: Using an open source IaaS stack internally and externally (e.g. OpenStack internally, Rackspace externally; Eucalyptus internally, AWS externally; CloudStack internally, any of the CloudStack providers or AWS externally; or using a library like jClouds to smooth out the bumps.) This may include identical which run in different clouds, or cloud-specific tailored images onto which an application is deployed, or even very different environments under which the same Docker container is run.

Big Data / Number-Crunching

Deploy scale-out application for data processing to public, private, or hybrid cloud for running batch jobs. This includes short-lived instances that will be used for processing a large amount of data in a scale-out fashion; perhaps using Amazon Web Services spot instances or similar instances on other providers.
Possible scenario: Using Fedora plus Hadoop and other Hadoop ecosystem pieces to do processing in a public/private cloud setting.

PaaS node images

We should be able to provide Fedora Cloud Images for platform-as-a-service (ie: OpenShift Origin) for easy deployment.
Since we have a limited output, Cloud SIG will focus on a limited set of open-source PaaS, and provide support for volunteer-based efforts to port other PaaSes.
Currently supported:

OpenShift Origin (included in Fedora Packages Collections)

Simple Deployment of Code from Development to Production

As a developer, I want to ensure that my code is easily deployable from my development environment to a QA environment and finally a production environment, without encountering compatibility issues or surprises from differences in the environment. A solution where an identical customized image or container is used in all three environments is ideal.

Target IaaS environments

The Fedora Cloud product can be used as a guest/VM/image under many IaaS services and providers. For projects that are not currently packaged within Fedora/EPEL, we may need to locate a kind person to ensure testing. These include:
Open source IaaS systems:

OpenStack

Eucalyptus

Apache Cloudstack

OpenNebula

oVirt

Public clouds:

Amazon EC2

Google Compute Engine

HP Cloud

Rackspace

Digital Ocean

Linode

Features

Feature: Ready to run in Public and Private Clouds

The Fedora cloud image is ready to go out of the box in the public and private cloud environments we target. It includes cloud-init, the defacto standard for boot-time configuration for cloud instances, and heat_cfgtools package, which is used for handling guest initialization with OpenStack Heat.

Feature: Ready Access to Fedora Collection of Packages

Access to the standard Fedora package repositories

Standard language stacks (like Python, Ruby, NodeJS, PHP)

Modernized language and application-specific stacks, perhaps in the form of SCLs, for running userspace applications

Feature: Updated Images

Currently, the Fedora Cloud images are only produced twice-yearly as part of the general Fedora release. Because Fedora updates constantly, this means that after several months, it is often the case that a newly-launched image has pending updates which effectively replace the entire content. This is slow and wastes bandwidth, and in many cases means that users simply never update.
Instead, we will produce images with security updates and critical bugfixes rolled in. Our initial target is monthly releases, with special updates produced for critical security flaws.

Feature: Docker support

Docker is an easy to use interface for running application containers on Linux. Fedora is uniquely positioned to provide the best platform for Docker, since this container technology is not a security solution, but can be made reasonably secure when wrapped with SELinux. This includes adding libvirt support to the image, which is more heavyweight than many users of the image for other purposes will want, so we will produce a dedicated image specfically tailored for Docker.

Feature: Big Data Tools

We will produce a specialized image with various tools for Big Data processing preloaded and preconfigured where possible. The exact composition of this image will be determined in collaboration with the Fedora Big Data SIG [1].

Feature: Quick OpenShift Deployment

We will provide specialized images to deploy quick OpenShift Origin (broker + nodes), with little to no configuration, anyone should be able to deploy a single-node to a simple multi-nodes deployment. The node image should be usable to extend existing OpenShift Origin deployment. The exact composition of this image will be determined in collaboration with OpenShift Origin upstream.

Feature: Cloud -> Server

The Fedora Server product targets more traditional server roles, where systems have a more unique identity. The Fedora Cloud image supports this by providing a path to go from our base to a Fedora Server role, in effect taming one of your cloud computing "cattle" and making it into a "pet" traditional server — but running in a cloud environment.

Future Features

The following areas are unlikely to be completely addressed in the upcoming iteration of Fedora Cloud, but we intend to work on them in the future.

Image Generation Tools

The official Fedora Cloud images will be produced in the Fedora build system (Koji) using kickstart scripts, Anaconda, Oz, and ImageFactory. We also want to provide tools and documentation so users can easily respin their own images. This will likely be using ImageFactory as well. We may provide a web-based service for user-created images.

Image or Image Template Library

In addition to the basic tooling for image creation, we want to enable sharing of user-created images and their recipies. This may apply to Docker or other container images in addition to images targetted at full virtualization.

Higher-Level Cloud Tooling

Initial efforts focus on individual cloud images. In the future, we want to address higher level concerns as well. These areas include:

Orchestration

Performance / Scalability / Failover

Logging / Auditing

Monitoring / Notification

Database requirements

Requirements

Requirement #1: Reducing Image Footprint

Making the Fedora Cloud image fit in a smaller space. Storage is a significant cost element on cloud platforms.

Feature Addressed

Ready to run in Public and Private Clouds.

Priority

Nice to Have. The current cloud image is reasonably sized when compared to our competitors. However, smaller footprint has several advantages. Fewer packages means fewer updates and a smaller target for security problems. It makes it faster to download and deploy images across networks where the image storage and compute nodes run separately. And, reducing things our users don't really need gives more room to include things that they do.

Specific Areas

This requirement has several areas where effort will yield meaningful results. Each has its own level of effort, stakeholders, and dependencies.

Cloud-Focused Base Kernel

The cloud-focused base kernel will be a minimal kernel without many of the drivers traditionally necessary on hardware, like most PCI devices. The goal of having a custom kernel package is ultimately to reduce the size of the images which will reduce storage costs, make the images easier to move across networks between compute and image storage nodes.

Note that the kernel binaries will be shared across all of Fedora; the difference will be that not all modules will be packaged and included by default in the cloud image. This also means that it will be simple to add the other drivers if they are needed for special cases.

Effort is moderate; it includes defining the exact requirements of the smaller kernel, and creation and maintenance of that separation by the Fedora kernel team.

Internationalization / Localization

Fedora Cloud base images should only include a single default locale since it is meant to be used as an deployment target to save space. Other locales should be available through repositories. The idea is to rely on langpacks rather than the current RPM kludges which leave out internationalization, because that approach does not allow one to easily add language support later.
Effort required is fairly high, because the packaging tools do not currently have such support. It will also likely have some impact on all Fedora packagers, depending on the implementation, and may also involve changes to the packaging guidelines.

Included Documentation

Documentation has the same issue as internationalization: it is often not needed on each image but takes significant space, and cannot be easily added back if RPM is configured to exclude it initially.
Effort is similar to that for internationalization, although significant impact could be made by breaking out documentation from key packages included in the base image.

Refactoring Cloud-Init

Cloud Init was initially designed for a different distribution and is only loosely tailored for our needs. As it stands, it pulls in a rather large set of packages not used for other things. It is also written in Python, itself a large subsystem which it would eventually be nice to leave out of the base.
Effort is moderate, with some low-hanging fruit which may be addressed easily.

Requirement #2: Improved Docker Integration

Docker is a popular tool for launching and managing application containers. This runs on bare metal, in virtualization on developers' machines, or in cloud guests.
Right now, Docker can be added to the cloud base image but isn't included by default. Docker itself is small, but infrastructure to support it includes Libvirt, which is not small. In order to make it easier to get started and to speed up use in production, we will produce a Docker-specific image.
Additionally, we want to create a library of Dockerfiles and possibly our own registry of images.

Feature Addressed

Docker support.

Priority

Should. This feature is an important change to support a variety of different teams working on PaaS (like OpenShift) and end-user delivery issues. That being said, since there is very little usage of Docker in those tools right now and the package is available in the repositories already, it won't be terribly detrimental to not have the image complete.

Effort required

High. We can produce the basic image with minor work, but SELinux is a key feature which will make us stand out from other systems on which Docker can be run. Additionally, producing official Docker container images depends on changes to the build system.

Stakeholders / Owners / Major Dependencies

The Cloud SIG and our users are the major stakeholders. The SELinux team is instrumental in delivering the functionality we would like to see. Fedora Infrastructure and Release Engineering are involved in updating the build system. And the official images will be produced through Release Engineering.
Major dependencies include:

ImageFactory support for creating Docker images, and that support integrated into Koji.

Requirement #3: Automatic Production and Upload of Images

We will develop Fedora Cloud images using text-based descriptive files and use an automated toolchain that generates images for our targets and upload them where appropriate. Currently, this is done by hand. Automation is necessary to scale to multiple supported images and a growing set of targets.
Fedora images must pass automated QA before publication to ensure a minimum level of quality. In order to release updated images with confidence, automated testing is required, because we cannot expect the level of human attention which can be brought to a twice-yearly release.

Feature Addressed

Updated Images.

Priority

Must. We simply need this to be useful to our users, and therefore to be competitive.

Effort required

High. Release Engineering does not currently have the tooling in place to support this.

Stakeholders / Owners / Major Dependencies

The Fedora Cloud Working Group will work with Release Engineering in implementing and supporting the needed functionality.

Requirement #4: Needs for Big Data Image

Since large and complex data sets that are difficult to process using RDBMS and traditional data processing tools are now common, and the open source big data ecosystem is now quite mature, we ought to provide a ready-to-go image for these usages.
Hadoop and its ecosystem is clearly a key player and the Big Data SIG is working to bring it on Fedora.
Should. Real-time analysis is also growing, and components like Spark and Storm are also something we'd like to include.

Feature Addressed

Big Data Tools.

Priority

Should. Very useful for our users, but does not block anything else.

Effort required

Medium. Requires packaging the missing bits of the Hadoop ecosystem, most of it being java packages. The effort is being led by the Big Data SIG, as a stakeholder, and the Cloud SIG will support them to improve this.

Stakeholders / Owners / Major Dependencies

The Fedora Cloud SIG will work with the Big Data SIG to package and deliver a rock-solid Big Data Image.

Requirement #5: Software Stacks for Various Languages

People developing and deploying code on top of Fedora need access to the relevant language stacks. Fedora already provides the latest versions of many of these, but often real-world version dependencies do not match the Fedora cycle. We need some way of offering multiple versions of languages and software stacks. Additionally, it is ideal if support for a given version lasts longer than the 13-month Fedora lifecycle, so that moving from one release of the base to the next can be less painful.
The Cloud SIG plan to support the major languages:

Ruby

Python 2 & 3

PHP 5.x

Java

Node.js

Perl 5.x

Go

We will provide infrastructure and support to volunteers who want to complete the supported stacks or bring new ones.

Feature Addressed

Ready Access to Fedora Collection of Packages.

Priority

Must. This addresses a key need of userbase.

Effort required

High. Access to existing Fedora packages is simple (we simply won't break what currently works), but Fedora does not currently have a good infrastructure for multiple versions of stacks or for decoupled lifecycles.

Stakeholders / Owners / Major Dependencies

Software in this area will be the responsibility of the Environments and Stacks working group.

Requirement #6: Integration with Fedora Server Roles

We simply want to make sure that the tools to convert a Fedora Cloud base image to a Fedora Server role are available and function.

Feature Addressed

Cloud -> Server

Priority

Should. This helps tie the Fedora products together and makes the blurry lines between the Cloud and Server product more understandable.

Effort required

Medium. Effort is primarily in coordination and testing.

Stakeholders / Owners / Major Dependencies

This effort will be done in collaboration with the Fedora Server Working Group.

We do not have a standardized process for end-user image creation, although we have several tools which can be used. We plan to develop this process and document it. This may also include an image library or a library of image creation templates, or both.

Features Addressed

Image Generation Tools, Image or Image Template Library

Priority

Nice to have. This is not required for our initial launch.

Effort required

High.

Stakeholders / Owners / Major Dependencies

Requirement #8: Updated Web Site for Obtaining Cloud Images

As we provides images for various use cases (ie: Big Data, PaaS hosting, scale-out apps, etc.) and various target platforms, we need an updated website.
Fedora provides its build toolchain and encourage the community to use it to build new products. The updated website should also reflect that by allowing folks to share and review the work done by their peers.

Feature(s) Addressed

Easy access to Fedora Cloud products and encouraging sharing in the community.

Priority

Must. A simple access to the cloud products is also a key argument to their success.
Should. Providing a sharing platform to the community (as in not supported by the Cloud SIG) and peer-review based system will allow to service better our users and foster innovation.

Effort required

High. We need to define precisely what we want to show, and maintain the website.

Stakeholders / Owners / Major Dependencies

The Cloud SIG will work closely with Fedora Websites/Infrastructure and possibly Fedora Engineering if we need to develop specific apps and/or integrate with the existing Fedora infrastructure (like fedmsg).

Documentation

We aim to provide a comprehensive documentation covering users to developers.
Should. Provide narrative documentation to make it easier to use cloud images and use them as foundations to new products.
NTH. On a volunteer basis, we will maintain a knowledge base.

Fedora Project Documentation

The Cloud SIG will cooperate with the Documentation Project to provide documentation to users, and developers of Fedora Cloud Products.

Open Source Projects documentation

Ensuring that Fedora is well-represented, up-to-date in other open source project documentation...

About this Document

This PRD (Product Requirements Document) is an evolving document, created by the Fedora Cloud SIG Working Group as part of the process for designing the Fedora Cloud product. The framework for the PRD itself is currently in a draft state.
This document will evolve over time as the purpose of the SIG continues to be determined as the working group process gets under way and initial products start to get produced.

Credits

Some of the Cloud User Roles are based on “Description and Application of Core Cloud User Roles” ACM CHIMIT 2011, December 4 2011.
Some aspects of Fedora Cloud personas are based on OpenStack personas (licensed under CC-By 3.0)

Community Information

The Fedora Cloud SIG is one of many teams within the Fedora Project.
The Cloud SIG mailing list is located here.
Minutes and logs from IRC meetings related to the development of this document should be listed here as the document evolves.

Approval History

Over time, it is expected that this document will undergo various rounds of review, approval, and editing; in the future, it may be rewritten for different releases of Fedora.
While one can review the history of a wiki document (by clicking the "history" tab), it is useful to provide explicit indicators of any major format changes, approvals, or indications of it being in a “final” state, in a list that can allow someone to quickly see that all of the prescribed layers of approval have occured.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.