Ok, now I've read it. Brava, Usha! Anything that evolves us away from ASG's is a win in my book. wrote: -- -- Marco Nicosia Product Manager Pivotal Software, Inc. mnicosia(a)pivotal.io

Hello everyone, A few months ago we shared a vision <https://www.cloudfoundry.org/vision-future-container-networking-cloud-foundry/> for container networking. The container networking team has been

I agree with Vedran that extending the SB API + CC to further help reduce state mgt in brokers could be useful (related thread and discussion at [1] beyond improvements brought in [2]). Shannon, do

Hi, Sorry for the late response. Indeed the /dev/std{out,err} thing is implemented by the OS. I'm not a windows user by myself, but I read somewhere that bash emulates that. Can you try on

Hi Amulya, Could you try running "cf env <app-name>" at each step during reproduction? If the environment variables go away when you unbind then come back the same when you make a new binding, this

Thanks Chip. I've added suggested associated edits to the Requirements document in google docs. It would be great if the CF community could be informed and ideally asked for feedback when the formal

Yes, we too use org and space guids for the dynamically created security groups (to enable consumption of the services from the apps), but we also follow the CF CC here and associate backups with

Hi all, The PMC Council has formally voted to approve the updated (removing BOSH) requirements document for the 2017 program. Those organizations that have offerings already certified will be

These are excellent ideas Guillaume, which we'll use when creating the formal audit process in the coming year. Thanks so much for taking the time to document your thoughts! Chip Childers CTO, Cloud

Interesting. I assumed that you would be able to create multiple process types with the multiple buildpacks. I understand you can only have one named "web" but I thought that if each buildpack

I believe the idea is that the last build pack in the list will have the final say. It can either return the command it wants to use or it can take the command from a previous build pack and use (or

All, The PMC Council voted yesterday, forming the Extensions PMC with Dr. Max as the PMC Lead. All of the projects within the Buildpacks, Services and Utilities PMCs are now under the new structure.

Even with that limitation, which buildpack is supposed to create the start command? I could see instances where the "normal" buildpack start command is fine but also cases where the add on would want

We also use the org and space guids in some brokers: 1- In autosleep [1], as to opt in for space level features (as an alternative to the usual app or route level opt-in provided through

Thanks Shannon. Public pipelines displaying risk of vulnerability for online services could be feasible by asserting the version of mandatory Cf core components, including rootfs and buildpacks. I

That is indeed true. All the use cases still assume a single main application process, and therefore a single start command, and owner of $PORT. Any additional processes are meant as helpers inside

We also use these fields in a credentials broker that hands out separate credentials in test vs. production spaces. It Is a somewhat specialized use case, where credentials must not be written to disk

We used them in a bunch of insignificant places and in one significant place. Our significant use case is that we have a billing system that associates internal billing codes with organizations and

Hi, all, Quick reminder of the CAB call next Wednesday, November 9th @ 8a PDT. In addition to open QAs with CF PMs, we are also looking for suggestions of two or three cloudfoundry-community

I don't see any consideration in the document for having multiple start commands and picking who gets the default PORT.