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.

I found the reason. I had CF DEV VM running on my machine. When I had quit it showed me progress of downloading being done. Finished (00:02:20) Validating release 'bosh'... Finished (00:00:00)

Below is what I get for past few hours. bosh create-env bosh-deployment/bosh.yml \ Deployment manifest: '/home/wso2/BOSH/bosh-deployment/bosh.yml' Deployment state: 'vbox/state.json' Started

When I tried to install Bosh Lite and executed the below step [2], it does not show any progress except the below [1] for few hours right now. Is it because of a network delay or anything wrong in my

In CredHub documentation there are manifest identifiers defined with dot notation that seem to conform to the JSON objects for certificates (and other types) that can be specified in CredHub API

Hi all, You can now register for the (free!) Unconference <https://www.eventbrite.co.uk/e/cf-summit-europe-2017-unconference-tickets-37837803890> at CF Summit Europe 2017. It'll take place between

hey, we currently have two separate cpi methods for creating vms (create_vm) and setting metadata on the vms (set_vm_metadata). create_vm call does not receive necessary metadata to apply tags to the

Hi, We have deployed BOSH 261.4 with Azure-CPI 260.5 with stemcell bosh-azure-hyperv-ubuntu-trusty-go_agent version 3363.27. I have deployed a BOSH release of our own application that uses two VMs and

Hello Every one, we are currently using bosh version 262.3. The question I have is on how bosh provisions ec2 instances in AWS through bosh-aws-cpi. To give a little context on how provisioning on

if vcloud cpi allows to specify root disk size this might be one way to bypass this problem. wrote: