The consistent target from an Engineering perspective should always be the contract or interface, but should never degrade to the point of being a particular implementation. This has been damaging in

I think this confusion (or misrepresentation) is best solved by the Cloud Foundry Expert Certification that Stormy Peters has coordinated. I objected initially to the mandatory inclusion of BOSH in

Regarding a consistent operator experience, I believe it will differ with or without BOSH being a requirement for certification. Some vendors will choose to add layers on top of BOSH, to improve UX,

It's important that this community understands that the *inclusion* of BOSH in the 2017 certification would *exclude* the Stackato and ContainerCF distributions which were certified in 2016, possibly

Great feedback Cornelius. Inline comments and questions for everyone below: wrote: Your points are really good. I can also see a clear argument for eventually having multiple stemcells based on

I think it's good to keep some flexibility and openness, especially at such integration points as the stemcell where there are defined interfaces and tests. This can help to accommodate customers

See inline... Noted. It is an interesting point that this is isolated to just those circumstances. I don't think that this is a build pack error because you're not getting to the point where the

Hi Daniel, I tried starting the application with CF_TRACE enabled and/or checked the cc logs but did not find any thing useful yet in CF Trace only seeing generic error msg eg: 'Stager error:

What do you (or others) think would be the right approach? -- Chip Childers VP Technology, Cloud Foundry Foundation 1.267.250.0815

Great news! -- Chip Childers VP Technology, Cloud Foundry Foundation 1.267.250.0815

What does that mean for the stemcells? Is it required to use the stemcells being officially released by the BOSH team, or is this one of the "explicitly defined plugin points" where it's ok to use

Hello All, HPE would like to propose incubating the https://github.com/hpcloud/garden-hcs repo with the Greenhouse team. This repo contains source code developed by HPE to demonstrate the

Hi all, We want "Stacks" for limited number of users. Stacks are Cloud Foundry structure, which provides base runtime environment of applications. In the current implementation of Cloud Foundry, all

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.