Very cool! wrote:

Re-posting from CF-Dev --- Hi, The EMC Cloud Platform Team in Cambridge MA has been working very closely with the Bosh and Bosh Infrastructure teams to create a Bare-Metal Cloud Provider

This is off the top of my head, but I believe it will work to stop the VM. However bosh then recreates the VM, so you're back in the same spot with the errand VM still hanging around. I'll try to

Does `bosh stop <errand-name> --hard` work for this?

Hi Rafal, The tool creates a new dhcpOptionSet, and tries to delete the default one. I'm not sure of the historical reasons why it tries to delete the default one. This is a known issue and people

Hi, If I execute `bosh run errand` with the `--keep-alive` flag, it will keep the VM around after the errand completes. This has been helpful in debugging problems with errands. When I'm done with

Is there any reason that bosh runs on a centos basis but not on rhel? Im quite confused about this. pivotal states that: „BOSH does not support a RedHat Enterprise Linux OS stemcell. This is due to

Hello, we make use of specifying multiple datastores by providing a pattern. Our config looks like this: cloud: plugin: vsphere properties: agent: ntp: - ntp1.example.com

I saw some discussion around support for datastore clusters or wildcard datastore names in BOSH deploying to vSphere. Is there currently any support for this? Currently, when targeting a datastore

i do not have a know_host file because i have the following in my config Host * StrictHostKeyChecking no UserKnownHostsFile=/dev/null

Ramon can you check the know_hosts file in .ssh dir of your home dir . -- View this message in context:

make sure your CLI is up to date. bosh vms will show list of machines but note that each machine actually has an id. machines will be sorted alphabetically based on ids and that's the order they

Hi Amit, Sorry, I meant the order of the "instances" of a particular job, for example, we have 100 runners in zone1, what is the order of deployment of these

It's in order that the jobs are in the manifest, however you can control the parallel behaviour with the global "update" section, and the "update" subsections on each job: * global update:

It looks like you might be using some internal BOSH releases, so probably a first step is to verify that those release jobs are able to correctly handle when a peer goes offline. Can try watching the

Hi, I was wondering what is the logic behind the order in which bosh update the instances of a job. If I remember correctly, before it was more like: - job_z1/0 - job_z1/1 - job_z1/2 -

Hi all I am trying to configure my bosh setup to really have a zero downtime deploy. Currently even if I add a second instance to my jobs when I deploy I still get downtime I have two instances

yes bosh_config is in my vcap home_dir and .bosh/ .bosh/cache/ < filled with allot of blobs .bosh/tmp/ < empty

Hi Ramon, Are you able to locate your .bosh directory ?? Usually it is created in same directory where .bosh_config file is created. config path for .bosh_config should be there on output of bosh

bosh status info Director Name microbosh-openstack URL https://172.21.42.148:25555 Version 1.3147.0 (00000000) User test UUID