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.

From: cf-bosh-bounces(a)lists.cloudfoundry.org [mailto:cf-bosh-bounces(a)lists.cloudfoundry.org] On Behalf Of Prysmakou Aliaksandr
Sent: Mierkoles, Hulyo 01, 2015 3:01 PM
To: Discussions about the Cloud Foundry BOSH project.
Subject: Re: [cf-bosh] Configuring bosh-agent to connect to a multi-machine nats cluster

Hi Allan,
I suppose it is better to consider your design again.
It is not good idea to make management system (bosh) dependent on managed system (cf).

Alex Prysmakou / Altoros
Tel: (617) 841-2121 ext. 5161 | Toll free: 855-ALTOROS
Skype: aliaksandr.prysmakou
www.altoros.com<http://www.altoros.com/> | blog.altoros.com<http://blog.altoros.com/> | twitter.com/altoros<http://twitter.com/altoros>

On Jul 1, 2015, at 2:30 AM, Espinosa, Allan | Allan | OPS <allan.espinosa(a)rakuten.com<mailto:allan.espinosa(a)rakuten.com>> wrote:

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 bosh-release
* deploy cf-release' nats cluster
* re-deploy director with the nats job removed and point the manifest to the nats cluster instead.

However, I see in the bosh-release manifest that you can only specify a single machine. How can we specify in the bosh-release manifest a multi-machine cluster like the ones in cf-release?

Thanks
Allan
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh