From Fedora Project Wiki
(Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
 
Line 25: Line 25:
== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
By design, Docker container internal storage is ephemeral in nature and data is lost when a container is stopped.  Kubernetes uses Persistent Volumes to provide a means for containers to keep data for extended periods of time and between restarts.
Kubernetes provides a mechanism for providing storage to containers called Persistent Volumes. Persistent Volumes support several underlying storage protocols, but clients are needed to support each typeNative GlusterFS and Ceph clients will be added to the Atomic host base to support new Persistent Volume types.
 
A Persistent Volume (PV) in Kubernetes represents a real piece of underlying storage capacity in the infrastructurePersistent volumes are intended for "network volumes" like NFS shares, GlusterFS volumes, or Ceph devices.
 
In order to access the underlying storage, the appropriate drivers must be available to Kubernetes on the Atomic host.  We will add the appropriate packages to support the following Persistent Volume types:
 
* GlusterFS
* Ceph


== Owner ==
== Owner ==
Line 48: Line 41:
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* Product:
* Responsible WG:
* Responsible WG: Cloud SIG
-->
-->


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/24 | Fedora 24 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- 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 67: Line 60:


<!-- 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. -->
By design, Docker container internal storage is ephemeral in nature and data is lost when a container is stopped.  Kubernetes uses Persistent Volumes to provide a means for containers to keep data for extended periods of time and between restarts.
A Persistent Volume (PV) in Kubernetes represents a real piece of underlying storage capacity in the infrastructure.  Persistent volumes are intended for "network volumes" like NFS shares, GlusterFS volumes, or Ceph devices.
In order to access the underlying storage, the appropriate drivers must be available to Kubernetes on the Atomic host.  We will add the appropriate packages to support the following Persistent Volume types:
* GlusterFS
* Ceph


== 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 functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->


Better support for Kubernetes
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:

Revision as of 21:38, 6 January 2016


Atomic Storage Clients

Summary

Kubernetes provides a mechanism for providing storage to containers called Persistent Volumes. Persistent Volumes support several underlying storage protocols, but clients are needed to support each type. Native GlusterFS and Ceph clients will be added to the Atomic host base to support new Persistent Volume types.

Owner

  • Name: mmicene
  • Email: nzwulfin@gmail.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 24
  • Last updated: 2016-01-06
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

By design, Docker container internal storage is ephemeral in nature and data is lost when a container is stopped. Kubernetes uses Persistent Volumes to provide a means for containers to keep data for extended periods of time and between restarts.

A Persistent Volume (PV) in Kubernetes represents a real piece of underlying storage capacity in the infrastructure. Persistent volumes are intended for "network volumes" like NFS shares, GlusterFS volumes, or Ceph devices.

In order to access the underlying storage, the appropriate drivers must be available to Kubernetes on the Atomic host. We will add the appropriate packages to support the following Persistent Volume types:

  • GlusterFS
  • Ceph

Benefit to Fedora

Better support for Kubernetes

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this 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

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes