Hi, Ushani, The zookeeper release gets exactly those IPs via the "address" property on each of the instances in its "peers"

Performance is an issue, but just understanding the logic on why Director would make two calls during a deployment to obtain the same secret is important. Thanks.

Hi All, I am getting below exception while uploading stemcell using bosh v version 2.0.40-9fc1ea4-2017-09-18T23:00:15Z ~/bosh-cli-ex$ bosh -e bosh-1 upload-stemcell

we havent spent any time optimizing it since it shuold be pretty cheap to make these calls. are you concerned about the perf aspect of it or something else? wrote:

It appears Director calls CredHub for a single secret twice during a deployment. Here are the Director calls: 1) Calls CredHub with a GET by name. In this case the query name parameter value is the

Hi Dan, I checked the doc and thanks for the info. But what I really need is a way to capture the ips of instances dynamically created when we define a number in deploy. manifest. E.g., -

Thanks Dan will check

Take a look at the example referenced from the docs. You can see the links exposed in the spec file and how they're consumed in the various

Hi Daniel, I'm trying create a cluster setup which is configurable for n number of instances. So, How can I access the IP set for a particular IP dynamically? Or is there a way where I can access

I think you want Bosh links, but more specifically a self link -> https://bosh.io/docs/links.html#self Dan wrote:

Hi there, Im going to deploy my application in BOSH and cluster it with n number of nodes. E.g., 2 So in my app, when I deploy the app in my manifest.yml I have defined below. So it starts at

Could not figure out any solution. Created the same project from scratch with same configs and it started working

bosh -e vbox -d wso2is deploy wso2is-manifest.yml. This is what I get, Task 29 | 13:24:38 | Deprecation: Ignoring cloud config. Manifest contains 'networks' section. Task 29 | 13:24:38 | Preparing

Executing bosh init-release command created it for me.

It seems the config/blolbs.yml is not available. How can I resolve this? bosh -e vbox add-blob /home/wso2/Downloads/jdk-8u144-linux-x64.tar.gz oraclejdk/jdk-8u144-linux-x64.tar.gz Tracking blob:

you might have to update your cloud config with one that cf-deployment wants: bosh -e 192.168.50.6 ucc <(wget

I've been trying to deploy Cloud Foundry on a local machine using Bosh Lite on a VM via cf-deployment. According to the documentation, the following command should build Cloud Foundry bosh -e

Pls ignoe prvious comment Issue was a space before the ( bracer. Correct command is as below. bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) Using

Issue was I had extra ) at the end of the command. bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) should be bosh -e 192.168.50.6 alias-env vbox

bosh -e 192.168.50.6 alias-env vbox --ca-cert vbox/creds.yml Validating Director connection config: Parsing certificate 1: Missing PEM block Exit code 1 Please explain me the below command.