On 10.12.2015, at 16:53, Matthias Ender <Matthias.Ender(a)sas.com> wrote:

Danke, Johannes.

We actually have an implementation that uses S3, but want to also be able to also support openstack, on-premise. Rather than re-implementing in swift, nfs would be an easier path from the app development side.

But if there is no path on the cf side, we’ll have to rethink.

From: Johannes Hiemer [mailto:jvhiemer(a)gmail.com]
Sent: Thursday, December 10, 2015 10:21 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: [cf-dev] Re: persistence for apps?

Hi Mathias,
the assumption you have is wrong. There are two issues regarding your suggestion:

1) you don't have any control on the cf side (client) over nfs in warden containers. As far as I know this won't be the case for Diego as well
2) you should stick with solutions like swift or s3 for sharing data, which is the propagated way for cloud native applications

What kind of data are you going to share between the apps?

Mit freundlichen Grüßen

Johannes Hiemer



On 10.12.2015, at 16:15, Matthias Ender <Matthias.Ender(a)sas.com> wrote:

We are looking at solutions to persist and share directory-type information among a couple of apps within our application stack.
NFS comes to mind.
How would one go about that? A manifest modification to mount the nfs share on the runners, I assume. How would the apps then get access? A volume mount on the Warden container? But where to specify that?

Or am I thinking about this the wrong way?

thanks for any suggestions,
Matthias