I realize a big part of this thread is about BOSH, but I thought I could
provide a little more context about cf-deployment
<https://github.com/cloudfoundry/cf-deployment>, in case anyone is curious.

cf-deployment will replace cf-release as the source of truth for how to
deploy Cloud Foundry. Instead of a repo with submodules of the various
components (cloud_controller_ng, gorouter, etc.), it's simply a BOSH
deployment manifest that references final release versions of the component
releases (capi-release, routing-release, etc.). Most importantly, it
includes diego-release and, by default, deploys Diego as the backend, in
the same deployment as CF.

The Release Integration team is already testing cf-deployment on a regular
basis and it passes acceptance-tests. We're currently working on fleshing
out the migration path from a spiff-template-generated manifest, which uses
the "v1 schema" for BOSH manifests, to cf-deployment, which uses the "v2
schema". (Note that "v1" and "v2" are not official versioning schemes for
BOSH, they're just a colloquial term that we sometimes use to describe a
collection of features which you read more about here
<https://github.com/cloudfoundry/bosh-notes>.) We're also planning to add
various forms of polish and configuration to cf-deployment.

As far as timelines go, our goal is to have cf-deployment generally
available for a few months before the EOL for the DEAs, to give everyone
time to do the migration. We're hoping to have it GA sometime in February.
We're already starting to dog-food it among the CF engineering teams to get
initial feedback. I'd encourage anybody who's interested in giving it a
shot to try and deploy with cf-deployment and to send feedback our way.

Feel free to reach out to me if you have any questions about cf-deployment.

Best,
David Sabeti
Product Manager, CF Release Integration


On Thu, Oct 27, 2016 at 7:12 AM Chip Childers <cchilders(a)cloudfoundry.org>
wrote:

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 EOL notice that Dieu shared back in mid September talked about the
removal of the DEA's from cf-release after the 6 months of overlap between
Diego "1.0" and the DEA's being fully retired.

Lots of moving parts here, including needing to support the transition of
everyone from one to the other.


On Thu, Oct 27, 2016 at 4:47 AM Daniel Jones <
daniel.jones(a)engineerbetter.com> wrote:

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 Jones - CTO
+44 (0)79 8000 9153 <+44%207980%20009153>
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

On Thu, Oct 27, 2016 at 9:10 AM, Dieu Cao <dcao(a)pivotal.io> wrote:

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 that have difficulty
accessing google docs.

2 major changes from the 2016 certification requirements include requiring
Diego/Garden and also requiring the use of BOSH.

-Dieu Cao
Runtime PMC Lead

[1]
https://docs.google.com/document/d/1S9o4u65uG_YrVQAdg7nxw7BrXAiL64hFSWBNVKZCMNI/edit


--
Chip Childers
VP Technology, Cloud Foundry Foundation
1.267.250.0815 <(267)%20250-0815>