Hi Alex, I’ll make sure I at least have a second nats for my meta bosh so things can be booted around. Thanks! Allan Sent: Mierkoles, Hulyo 01, 2015 9:22 PM To: Discussions about the Cloud Foundry BOS

So, in the case when nats goes down, how does the ressurector try to recover deployments? So micro bosh will resurrect the nats instances. But my multi-bosh will see all deployments as down because it

Hi Alex, Yup. We have that kind of setup now actually. My problem now is getting the bosh-release manifest to accept multiple machines so that the agents can pick it up. Thanks Allan Sent: Mierkoles,

Well my intention is to have the nats the director and agent is depending on be HA. I can use the nats job in bosh-release and do a binary bosh setup as well. Sent: Mierkoles, Hulyo 01, 2015 3:01 PM T

Hi, I'm thinking of connecting our bosh-agents to the NATS cluster provided in cf-release instead after the initial bootstrap like the following: * deploy director together with the single NATS in bos

Argh sorry. Read the cpi job spec again Apparently I have the hash at the wrong level. s/cpi.env.http_proxy/env.http_proxy/

Hi, We need specify https_proxy to connected to our avcenters. We're able to do this when we deploy Bosh directors using bosh micro and multi-bosh setups. But I cannot get it running under bosh init.

Thanks Gwenn, Dmitry I'll try this out.

Hi, We currently have a binary bosh [1] setup. However we would like to transition to bosh-init to prevent having to manage multiple bosh deployments. I'm looking at how to regenerate the state file d