The CF CLI team just cut 6.22.2. Binaries and link to release notes are available at: https://github.com/cloudfoundry/cli#downloads CF Trace file permissions When CF_TRACE or cf config --trace are

My tuppence/two cents: I have met folks who used non-BOSH Cloud Foundry solutions, and were surprised when they hired people with "Cloud Foundry" on their resumes who then had to start from scratch

RE: Question #2 below - One of the things that we've been thinking about regarding operator experiences with Cloud Foundry, and why standardizing on BOSH may be very attractive, is figuring out how

To follow up... it was pointed out to me that the document didn't state DRAFT well enough (it does now). My answers below were from the perspective of having thought this proposal through, and the

Hey y'all, The Buildpacks team has recently made changes[1] to cf-release to rename the java buildpack packages from buildpack_java to java-buildpack and buildpack_java_offline to

Hi everyone, The container networking incubation project netman-release <https://github.com/cloudfoundry-incubator/netman-release> enables direct, policy-driven connectivity between containers on

Thanks Daniel for quick response - will check.

The 500 error is coming from Cloud Controller, which indicates a problem there. Check out the CC logs and look for a stack trace to get more details on what is failing. It doesn't mean that CC is

It is a requirement for all certified offerings of all types. Regarding why: see my comments about consistent operational experience (think about a service provider's ops team as part of the market of

Is the BOSH requirement something that affects everyone, or just non-managed offerings? If the only BOSH isn't required to be provided to users from a managed-offering, why require it to have been

I think the evolution from cf-release to cf-deployment is naturally causing this to happen, although you make a very good point that perhaps that could be accelerated and / or more explicit. The DEA

Bundling up Dr. Nic's questions for a single reply... Great questions! I did a bunch of the pre-work on behalf of the PMC Council on this topic, so I have a bunch of the context loaded. *Question

Hi, I am facing issue while trying to deploy application with diego enabled - I need to provide the build pack information to make app run with diego cell - seems if want to run the application

Am 26.10.2016 um 02:10 schrieb Koper, Dies: I can't remember having a pseudo file for stderr in Windows. The OS provides default handles that can be used to write to stderr - no files. That's why you

Also, why is "using BOSH" a requirement? As awesome as it is for many things, it isn't perfect. If companies innovate/experiment with alternate deployment systems why do they lose certification

"For managed offerings, BOSH does not need to be exposed to customers" - what is the origin & reason this is explicitly stated? Does it infer that there is any scenario at all where BOSH must be

To confirm - if a CF platform patches any CF components outside of the biweekly or so release cycle that the components might have, then they lose their certification status? I know some on-prem

Thanks for that Dieu! Is there work scheduled to get OS cf-release and associated documentation into a state where Diego is the default, rather than deploying the DEA architecture? Regards, Daniel

Hello all, The 2017 PaaS Certification Requirements is available here [1] and we would appreciate questions/comments on the doc or in this thread. I've also attached a PDF version for those of you

Hello, Currently I am working on a Proof of Concept on Docker, Life-ray and Cloud Foundry integration and would like to contribute to Cloud foundry. The idea is to: 1. Create a custom Buildpack