From Fedora Project Wiki
No edit summary
No edit summary
Line 36: Line 36:
== Benefit to Fedora ==
== Benefit to Fedora ==
Containers are a powerful and flexible way to deploy and manage server applications, with numerous benefits such as density, ease of deployment, and orchestration.  In concert with [[Changes/Docker_Container_Image]], this will allow running Fedora content in containers and on the host system.  The same RPM content will go into both.
Containers are a powerful and flexible way to deploy and manage server applications, with numerous benefits such as density, ease of deployment, and orchestration.  In concert with [[Changes/Docker_Container_Image]], this will allow running Fedora content in containers and on the host system.  The same RPM content will go into both.


== Scope ==
== Scope ==
* Proposal owners: Regarding the core objective, it's just about creating a new kickstart file (probably even %include-ing the base one) add some minor stuff and make sure it gets built into a new image. Also, for added security, we'd like to see Docker and SELinux integrate better. There's already work going on about this.
* Proposal owners: Currently generating trees on a compose server and syncing them.
** The bonus objectives (i.e. leading edge approaches) further require:
*** ostree to work with SELinux
*** Creating a filesystem tree for ostree that equals the filesystem of the image as created by traditional means
*** min-metadata-service to gain the ability to execute scripts just like cloud-init does
*** CoreOS' cloud-init or other alternatives to be packages (and possibly tailored) for Fedora


* 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 -->
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: Will need to generate trees during the general Fedora compose process, and generate install media and cloud image based on trees.
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


Revision as of 15:56, 2 July 2014

Atomic Cloud Image

Summary

New Fedora product: Fedora Atomic Cloud Image - Docker host ready to go.

Owner

  • Name: Cloud SIG / Sandro Mathys Colin Walters
  • Email: red@fedoraproject.org walters@verbum.org
  • Release notes owner:
  • Product: Atomic Cloud Image (duh!)
  • Responsible WG: Cloud

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-04-05
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

This could be though of as a Fedora instance of the Project Atomic pattern, oriented for cloud usage. The technology will support bare metal installation, making this a cross Server/Cloud product, but for F21 cloud targets will be primary.

A major difference with traditional Fedora projects is this will use rpm-ostree technology to do atomic updates of the host system.

Another major feature is using Cockpit for server management.

Benefit to Fedora

Containers are a powerful and flexible way to deploy and manage server applications, with numerous benefits such as density, ease of deployment, and orchestration. In concert with Changes/Docker_Container_Image, this will allow running Fedora content in containers and on the host system. The same RPM content will go into both.

Scope

  • Proposal owners: Currently generating trees on a compose server and syncing them.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Will need to generate trees during the general Fedora compose process, and generate install media and cloud image based on trees.
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

If any of the bonus objectives fail to make it in time, we simply go on without them and use the established mechanisms (i.e. what F20 did or what the F21 Fedora Base Cloud Image does) instead.

If all fails, there simply won't be a Fedora Atomic Cloud Image product for F21.

  • Blocks product? Yes, Atomic Cloud Image (duh!)

Documentation

N/A (not a System Wide Change)

Release Notes

New Fedora product: Fedora Atomic Cloud Image, featuring Docker and tools from Project Atomic.

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.

TODO: include notes if any of the bonus objectives are included. TODO: add something about the Project Atomic tools

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