Durable data

I'm not looking to actually merge this PR, just get some feedback on two possible approaches.

If there is agreement on one approach, then I will code it up, and convert this design document into user documentation.  

I'm inclined to add a new type of REST resource to model Durable local data.  I know new resources are always  controversial, so I've written this doc to compare the alternatives.  Comments welcome from anyone.  I'd particularly like comments from @dchen1107 @bgrant0607 @thockin @brendanburns @jbeda @lavalamp @smarterclayton.

People might build their own pod management flows that involve a pod exiting with success success when it is ready to be upgraded, or multi-stage map-reduce pipelines where the output of one stage is persisted on local storage for the next stage to run.