[Container-tools] Persistent storage in Docker (Flocker plugin)

[Charlie Drage]

Also:

The current consensus in order to implement persistent storage is
adding a function to each provider (for example. def
persistent_storage)

The code within the folder /nulecule (`base.py` and `lib.py`) detects
that the Nulecule file contains persistent storage parameters, it will
then check the respective provider it's deploying on.

If that provider has the persistent_storage function created, it will
pass in all graph parameters related to persitent storage (see:
http://www.projectatomic.io/nulecule/spec/0.0.2/index.html#storageRequirementsObject)

On 11/24, Charlie Drage wrote:
> So I'm working on getting persitent storage implemented for Atomic App
> GA.
> 
> Kubernetes seems straight forward: 
> http://kubernetes.io/v1.0/docs/user-guide/persistent-volumes/README.html
> 
> The same as OpenShift:
> https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html
> 
> Docker is a bit cumbersome at the moment. They have "data volumes",
> but  it's not very intuitive:
> http://docs.docker.com/engine/userguide/dockervolumes/
> 
> The best possible way of implementing this (imo) would be the Flocker plugin
> recommended by Docker itself here:
> http://docs.docker.com/engine/extend/plugins_volume/
> (See 1.9 announcement:
> https://blog.docker.com/2015/11/docker-1-9-production-ready-swarm-multi-host-networking/)
> 
> Anyone else have any ideas/alternatives for the best possible
> implementation for the Docker provider?
> 
> 
> -- 
> 
> Charlie Drage
> Red Hat - OSAS Team / Project Atomic
> 4096R / 0x9B3B446C
> http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C
> 
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools

-- 

Charlie Drage
Red Hat - OSAS Team / Project Atomic
4096R / 0x9B3B446C
http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C