Announcing Volume Services for Cloud Foundry


Ted Young
 

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones with
network-based interfaces, such as a SQL database. With Volume Services,
brokers can now attach data services which have a filesystem-based
interface.

Currently, we have platform support for Shared Volumes. Shared Volumes are
distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in the
links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in touch.
You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email me
directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


Amit Kumar Gupta
 

Sweet!!!

On Tue, Sep 20, 2016 at 2:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes are
distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in the
links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in touch.
You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email
me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


Chip Childers <cchilders@...>
 

+1 ... this is awesome to see released!

On Tue, Sep 20, 2016 at 5:33 PM Amit Gupta <agupta(a)pivotal.io> wrote:

Sweet!!!

On Tue, Sep 20, 2016 at 2:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes
are distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in
the links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in touch.
You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email
me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal

--
Chip Childers
VP Technology, Cloud Foundry Foundation
1.267.250.0815


Mike Youngstrom <youngm@...>
 

This is great! Something many of my customers have been wanting for a long
time. Now to figure out how to integrate it with our NetApp NFS.

Mike

On Tue, Sep 20, 2016 at 3:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes are
distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in the
links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in touch.
You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email
me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


Shawn Nielsen
 

Thanks to all who helped contribute and make this happen! This is
fantastic news.

On Tue, Sep 20, 2016 at 3:56 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

This is great! Something many of my customers have been wanting for a
long time. Now to figure out how to integrate it with our NetApp NFS.

Mike

On Tue, Sep 20, 2016 at 3:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes
are distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in
the links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in touch.
You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email
me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


Paul Bakare
 

Thank you very much.

So much awesomeness.

On Wed, Sep 21, 2016 at 12:00 AM, Shawn Nielsen <sknielse(a)gmail.com> wrote:

Thanks to all who helped contribute and make this happen! This is
fantastic news.

On Tue, Sep 20, 2016 at 3:56 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

This is great! Something many of my customers have been wanting for a
long time. Now to figure out how to integrate it with our NetApp NFS.

Mike

On Tue, Sep 20, 2016 at 3:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes
are distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in
the links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in
touch. You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or email
me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal

--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde


Shannon Coen
 

Persistence!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Tue, Sep 20, 2016 at 4:28 PM, Kayode Odeyemi <dreyemi(a)gmail.com> wrote:

Thank you very much.

So much awesomeness.

On Wed, Sep 21, 2016 at 12:00 AM, Shawn Nielsen <sknielse(a)gmail.com>
wrote:

Thanks to all who helped contribute and make this happen! This is
fantastic news.

On Tue, Sep 20, 2016 at 3:56 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

This is great! Something many of my customers have been wanting for a
long time. Now to figure out how to integrate it with our NetApp NFS.

Mike

On Tue, Sep 20, 2016 at 3:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes
are distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in
the links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's talk
detailing the types of Shared Volume Services available, and their usecases.

If you're interested in rolling out a volume service, please be in
touch. You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or
email me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde


Julz Friedman
 

This is ridiculously cool - nice work Persils!

On Wed, 21 Sep 2016 at 02:50, Shannon Coen <scoen(a)pivotal.io> wrote:

Persistence!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Tue, Sep 20, 2016 at 4:28 PM, Kayode Odeyemi <dreyemi(a)gmail.com> wrote:

Thank you very much.

So much awesomeness.

On Wed, Sep 21, 2016 at 12:00 AM, Shawn Nielsen <sknielse(a)gmail.com>
wrote:

Thanks to all who helped contribute and make this happen! This is
fantastic news.

On Tue, Sep 20, 2016 at 3:56 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

This is great! Something many of my customers have been wanting for a
long time. Now to figure out how to integrate it with our NetApp NFS.

Mike

On Tue, Sep 20, 2016 at 3:31 PM, Ted Young <tyoung(a)pivotal.io> wrote:

As of cf-242
<http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=242>
and Service Broker API v2.10, Cloud Foundry now ships with support for *Volume
Services*: filesystem-based data services. The v2.10 API is a release
candidate, and will be considered GA unless a bug in the implementation is
fond. An experimental version of the API was added in v2.9.

Until recently, the only data services that have been allowed are ones
with network-based interfaces, such as a SQL database. With Volume
Services, brokers can now attach data services which have a
filesystem-based interface.

Currently, we have platform support for Shared Volumes. Shared Volumes
are distributed filesystems, such as NFS-based systems, which allow all
instances of an application to share the same mounted volume simultaneously
and access it concurrently.

This feature adds two new concepts to CF: *Volume Mounts* for Service
Brokers and *Volume Drivers* for Diego Cells. Details can be found in
the links below.

*Documentation:* https://bit.ly/cf-volume-services
*CF Summit Talk:* https://www.youtube.com/watch?v=ajNoPi1uMjQ

If you're going to CF Summit Europe, be sure to check out Julian's
talk detailing the types of Shared Volume Services available, and their
usecases.

If you're interested in rolling out a volume service, please be in
touch. You can ask questions here, on the OSS #persi
<https://cloudfoundry.slack.com/archives/persi> slack channel, or
email me directly at tyoung(a)pivotal.io.

Cheers,

Ted Young
Persistence Project Lead, Pivotal


--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde