Hi, We are using bosh-init to creating and updating bosh-director. The problem is that bosh-init will recreate the target vm when upgrading cpi release, it might cause inconvenience to our system. I

This means, one has to use the old type L2 networking: a subnet minus reserved ips. With the dynamic set up, one can have multiple networks (net ids) within the same subnet; this way, one can have

Can you clarify how you're deploying BOSH? Is this micro bosh?

Micro bosh, yeah.

Hi, bosh-init's (currently only) way of applying updates is to re-create the VM. It will however preserve persistent data (detach and re-attach the persistent disk after creating new VM). The way

Hi, for testing purposes (I don't do that in production), where I find myself quickly iterating on different versions and configurations, I first use bosh-init to bootstrap a director and then use

We did a spike <https://www.pivotaltracker.com/story/show/116805009> to figure out the Metron behavior. We have a story <https://www.pivotaltracker.com/story/show/117257489> to fix in our icebox, but

Hi Yitao, Ben, Ben, since you seem to have nailed this issue down to a specific version, can I ask you to open an issue on the bosh repo: https://github.com/cloudfoundry/bosh/issues That way it

Filed the issue: https://github.com/cloudfoundry/bosh/issues/1206

Hi everyone I need help.. I deployed CF-233 release when i push sample app and it's work well but loggregator something wrong... do you know this one? root(a)director:~/sample/spring-music# cf

What are you using as a load balancer in front of *.system.test.cloud.com? It sounds like the LB doesn't support the web socket protocol's Upgrade request. I've seen this on AWS when using ELBs in

Thank for your answer I use ha_proxy in cf release instead of external LB I didn't see this one cf-221 release # cf logs my-app Error dialing loggregator server: websocket: bad handshake. Please

The unknown-route 404 makes it look like either the loggregator-traffic controller nodes are registering a different route than what the cloud controller nodes are telling cf-cli to use, or the

Hi, while updating a docker job we have observed the issue `Error response from daemon: client is newer than server (client API version: 1.23, server API version: 1.22)` while the code triggered by

Unfortunately right now agent doesnt wait for monit stop to finish so there is possbility for it to execute some newer package scripts. We've done some work to remedy that

Hi Jeff, Since we haven't heard back from you in a week, we will consider this issue resolved. Let us know if you have any more problems. Thanks! George and Adrian

We will consider this issue resolved. Let us know if you have any more problems. Thanks, George and Adrian

i tried to follow the readme.md here: https://github.com/cloudfoundry-community/terraform-aws-cf-install however, ended up with getting error 255 when "make provision" step. The worst thing is: after

Thanks for your help, this issued is resolved. 2016-04-19 0:15 GMT+08:00 George Dean <gdean(a)pivotal.io>:

Hi there, I have filed an issue where a VM got deleted in a deployment on OpenStack: https://github.com/cloudfoundry/bosh/issues/1223 Let me know if you have any questions Best, Tomoe