Re: Persistent Volumes on Cloud Foundry
Dr Nic Williams <drnicwilliams@...>
Is a goal of this work to run pure data services like PostgreSQL or Redis inside "application instances"?
toggle quoted message
Show quoted text
On Tue, Apr 5, 2016 at 5:01 PM -0700, "Ted Young" <tyoung(a)pivotal.io> wrote:
This proposal describes the changes necessary to the Service Broker API to utilize the new Volume Management features of the Diego runtime. It contains examples of how services can provide a variety of persistent data access to CF applications, where each service maintains control of the volume lifecycle. This is to allow some services that provide blank storage space to applications, and other services that provide access to complex or externally managed data (such as IBM's Watson).
http://bit.ly/cf-volume-proposal
We are moving fast on delivering a beta of this feature, so please have a look and give feedback now if this is of interest to you. More detail will be added to the proposal as necessary.
Cheers,
Ted YoungSenior Engineer / Product ManagerPivotal Cloud Foundry
This proposal describes the changes necessary to the Service Broker API to utilize the new Volume Management features of the Diego runtime. It contains examples of how services can provide a variety of persistent data access to CF applications, where each service maintains control of the volume lifecycle. This is to allow some services that provide blank storage space to applications, and other services that provide access to complex or externally managed data (such as IBM's Watson).
http://bit.ly/cf-volume-proposal
We are moving fast on delivering a beta of this feature, so please have a look and give feedback now if this is of interest to you. More detail will be added to the proposal as necessary.
Cheers,
Ted YoungSenior Engineer / Product ManagerPivotal Cloud Foundry