In fact, installing and using Ruby-2.2.3, instead, got me through

May I go further and ask that snapshots be kept after bosh delete deployment, but be also garbage collected after retention period? Also asking for a friend, I never accidentally deleted data

Great idea. Can I request that disks are kept in the same garbage collection pool after "bosh delete deployment"? Asking for a friend. I definitely never accidentally deleted production

Summary: We want to avoid accidental data loss so we are thinking to keep persistent disks around after deployment is modified. Persistent disks will be regularly garbage collected and you can

This is apparently the same issue as in "Warning: don't use bosh-init with Ruby 1.9.3. " (https://github.com/cloudfoundry/bosh-init/pull/46)

Hi, I'm a total newbie. I've been following the instructions on http://bosh.io/docs/init-aws.html for deploying CF on AWS. I've used the same settings expect for the time-zone which "us-east-1b" and

The short answer is “yes”. Yes, BOSH blocks the whole deployment while you run errand [1]. As far as I see, the main reason hear is consideration that BOSH errand job can perform operations on

Gwenn, is the any list of bosh tasks that require a lock available? Why do we need to lock running different errands? They are independent. Aleksey Zalesov | CloudFoundry Engineer | Altoros Tel:

Yes except this kind of task .. bosh deploy lock for example... aleksey.zalesov(a)altoros.com> wrote:

Bosh doesn’t lock on any task - while running tests I can list vms using `bosh vms` and ssh to vm using `bosh ssh`. Aleksey Zalesov | CloudFoundry Engineer | Altoros Tel: (617) 841-2121 ext. 5707 |

I will say no, bosh lock for any task and running errand is a task. aleksey.zalesov(a)altoros.com> wrote:

Hi all, I'd like to propose tuning a couple kernel parameters related to tcp performance: # TCP_FIN_TIMEOUT # This setting determines the time that must elapse before TCP/IP can release a closed

Hello! Can I run two bosh errands simultaneously? Currently I get `Error 100: Bosh::Director::Lock::TimeoutError` when trying to run the second errand while the first errand is running.

I have changed resource pool size for small_errand from 1 to 2 and run `bosh deploy`. Before change I have run `bosh deploy` and verified that no pending changes are available (actually, then I

Hi Marco, Thank you Marco! Yes indeed, the problem in the Github issue is the exact same Problem I have. The provided solution in the issue works. Thanks for referencing me to the Github issue and

We have made IAM instance profile support available in latest bosh-aws-cpi-release. See https://bosh.io/docs/aws-iam-instance-profiles.html on how to use it.

Dear Fabian, your problem might be the same as seen in this github issue: https://github.com/cloudfoundry/bosh/issues/964<https://github.com/cloudfoundry/bosh/issues/964#event-420594944> `bosh ssh`

I have a 2 job (vm) deployment, client and server. In the client, I'm referencing the server host via <index>.<job>.<network>.<deployment>.microbosh, ex.

Hi bosh-freaks, I do have a technical bosh question regarding bosh ssh . I am curious if you do have any solutions to the problem below or ideas for alternative. Please let me know in case this is

Still very interested in getting this working. I hope the hiccups pass soon! Tom wrote: