Built-in blue-green deployment support


John Wong
 

Hi

Is there already a built-in, out of the box solution for blue-green
deployment in CF now without having the need of deploying an app with a
different name and then working with map-route manually? If not, I find
having blue-green out of the box would be great. Right now, CF would switch
automatically at the end of the deployment (with a small downtime tradeoff)
by replacing the existing containers with the new one's.

Thanks.

John


Eitan Suez <esuez@...>
 

i know that the cf autopilot plugin does this (
https://github.com/concourse/autopilot ).

this other plugin:
https://github.com/bluemixgaragelondon/cf-blue-green-deploy
may also be worth checking out.

i haven't used either enough to really vet them out, but i like this idea
of plugging in a suite of smoke tests to control proceeding with vs
aborting a deployment.

/ eitan

On Fri, Jul 1, 2016 at 12:15 PM, John Wong <gokoproject(a)gmail.com> wrote:

Hi

Is there already a built-in, out of the box solution for blue-green
deployment in CF now without having the need of deploying an app with a
different name and then working with map-route manually? If not, I find
having blue-green out of the box would be great. Right now, CF would switch
automatically at the end of the deployment (with a small downtime tradeoff)
by replacing the existing containers with the new one's.

Thanks.

John


Nicholas Calugar
 

Hi John / Eitan,

We have a couple tracks of work planned for the new V3 Cloud Foundry API:

Zero-downtime deployment - Diego to support changing an application
specification of a running LRP in a zero-downtime manner:
https://www.pivotaltracker.com/story/show/111166678

Native support for advanced deployment strategies like blue-green
deployment: https://www.pivotaltracker.com/story/show/124264941


The V3 API is still experimental, but we are working diligently to get to
general availability. Feel free to follow along in our Tracker, read the
docs, and visit us in Slack!

https://www.pivotaltracker.com/n/projects/966314
http://v3-apidocs.cloudfoundry.org/version/release-candidate/index.html
https://cloudfoundry.slack.com/messages/capi/


Thanks,

Nick

On Fri, Jul 1, 2016 at 10:22 AM, Eitan Suez <esuez(a)pivotal.io> wrote:

i know that the cf autopilot plugin does this (
https://github.com/concourse/autopilot ).

this other plugin:
https://github.com/bluemixgaragelondon/cf-blue-green-deploy
may also be worth checking out.

i haven't used either enough to really vet them out, but i like this idea
of plugging in a suite of smoke tests to control proceeding with vs
aborting a deployment.

/ eitan




On Fri, Jul 1, 2016 at 12:15 PM, John Wong <gokoproject(a)gmail.com> wrote:

Hi

Is there already a built-in, out of the box solution for blue-green
deployment in CF now without having the need of deploying an app with a
different name and then working with map-route manually? If not, I find
having blue-green out of the box would be great. Right now, CF would switch
automatically at the end of the deployment (with a small downtime tradeoff)
by replacing the existing containers with the new one's.

Thanks.

John
--
Nicholas Calugar
Product Manager - Cloud Foundry API
Pivotal Software, Inc.


James Leavers
 

On 1 July 2016 at 18:22:41, Eitan Suez (esuez(a)pivotal.io) wrote:

i know that the cf autopilot plugin does this (
https://github.com/concourse/autopilot ).

this other plugin:
https://github.com/bluemixgaragelondon/cf-blue-green-deploy
may also be worth checking out.

i haven't used either enough to really vet them out, but i like this idea
of plugging in a suite of smoke tests to control proceeding with vs
aborting a deployment.

/ eitan




On Fri, Jul 1, 2016 at 12:15 PM, John Wong <gokoproject(a)gmail.com> wrote:

Hi

Is there already a built-in, out of the box solution for blue-green
deployment in CF now without having the need of deploying an app with a
different name and then working with map-route manually? If not, I find
having blue-green out of the box would be great. Right now, CF would switch
automatically at the end of the deployment (with a small downtime tradeoff)
by replacing the existing containers with the new one's.

Thanks.

John