Bosh-init deploy with little Director downtime

[schmidtsv]

It is possible to use the bosh Director as DNS server for deployments. On our Openstack Environment, the downtime for compilation is about 19-20 minutes. During this time, deployments using the DNS of the Bosh Director are unable to access a DNS server. One way to improve that behavior would be the option to use a Compile VM, instead of compiling on the new director.

As a Cloud Operator

• I want to upgrade the Bosh director with minimal downtime for deployments
• I want to have minimal downtime of the resurrection service and cloud monitoring

[jianqiu]

@cppforlife Any target date or release? We are also looking forward to this feature, thanks!

[cppforlife]

@schmidtsv dont really have a date at this point. we are trying to get to this in the next 2-3 months.

[JamesClonk]

@cppforlife Any update on this? We face a similar issue, as we rely on the BOSH heartbeat metrics to monitor our environment, and everytime we upgrade a BOSH with bosh-init we have a 20-30min. gap with lot's of alerts going off. Drives our Ops guys crazy. :smile:

Otherwise we might have to think about going back to a 2-layer microbosh->bosh style of deployment, with the first BOSH being deployed with bosh-init, and then the actual main BOSH as a bosh deployment itself on the first one. (We already have several other "secondary" BOSHes per environment that are deployed via the main BOSH like this, and there each update only takes about 1-2min., which is what we'd like to aim for for the main BOSH too)