Durable local storage proposal

This is a proposal for #598


I knew an IRL was called for.

On Tue, Sep 16, 2014 at 10:32 PM, Daniel Smith <notifications@github.com>
wrote:

> In docs/volumes.md:
>
> > +In one common case, this would be a single unique label value used by one or more fungible CachedData objects, and an exact match
> > +selector used by one or more fungible Pod objects
> > +The use of selectors:
> > +  - allows Pod creation and CachedData creation to happen independently, in any order.
> > +  - allows any of several fungible Pods to use any of several fungible CachedData objects.  (Object Names have to be
> > +    unique, so cannot fill this role.)
> > +
> > +A CachedData is analagous to a Pod object in that they both:
> > + - are expected to have a resource request in a future version of Kubernetes.
> > + - represent specific resources requested, and which are allocated on a specific node (once bound).
> > + - have own lifetime
> > + - can be created manually or created by a controller
> > + - have labels.
> > + - get bound to a machine by the scheduler.
> > +
> > +The scheduler creates a BoundCachedData in response to creation of a CachedData object.
>
> I do not like at all making the scheduler have to schedule multiple top
> level objects.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1311/files#r17646514>
> .
>