Have you tried running `bosh run errand X --keep-alive`? wrote:

Hi! I want to run errand with smoke tests as fast as possible. I have resource pool with size=1 so VM for smoke tests is already provisioned when I run `bosh run errand smoke_tests` command. Then

Thanks Dmitriy. We had our persistent disk intact and were able to restore from it. Thanks, Guru. wrote:

Is it intended when updating microbosh that currently running deploys are just killed? Will it resume after microbosh is updated?

Great, thanks a lot Dmitriy, this sounds great. Looking forward to seeing bosh.io leveraging these meta data to help filter/sort/search releases. Guillaume.

I am thinking we can add metadata to config/final.yml (and eventually include it in the release tarballs in release.MF). Once config/final.yml includes metadata, bosh.io can pull it in down and

HI Dmitriy, 3.0.4 Yes. I can see the 2 failures travis reported. Fixed. Thanks! It seems it was only pointing at my updated source code, it didn’t copy the gem file to the vendor cache, so the

If you had deployments managed by the Director, without a backup of a DB there is currently no easy way to recover your Director DB contents. Was the Director VM's persistent disk also

inline wrote: what does 'bundle exec rspec -v' show? if that does not succeed does 'bundle exec rake spec:unit:ruby_gems' run successfully from ~/workspace/bosh? bundler is telling here that it's

Hi Gwen, I did run the add-route utility hence the 'route get' was succeeding as mentioned in my email below, but as I was working from home today, I disconnected from my office network and then re

Would you be ok with specifying this additional options in the deployment manifest per subnet? wrote:

correct. v213 is fine for new deployments. it is not possible to upgrade to v213 with zero-downtime to the cloud controllers from a previous release, which is the reason for the

@Alex Lomov, AFAIK it v213 is OK for fresh deployments. Alex Prysmakou / Altoros Tel: (617) 841-2121 ext. 5161 | Toll free: 855-ALTOROS Skype:

I don’t think that v213 is suitable cf-release for you. It was a notice about its fails [1]. My colleagues are playing around v212, and I have rather stable deployment of v207. [1]

Hi Dmitriy, This is what I get when I try to run the unit tests with that: diesk(a)cloud-cf:~/workspace/bosh/bosh_openstack_cpi$ be rspec spec/unit/ Unknown command 'rspec' (No module named

i'm not sure that CF would fit within the free tier which only allows t2.micros, but you could try it and let us know how it goes. you would have a hard time fitting app containers on a VM with only

do you have a persistent disk backup? if so this can help. https://blog.starkandwayne.com/2014/10/10/restore-micro-bosh-from-just-its-persistent-disk/ guruprakashsrinivasamurthy(a)gmail.com>

Maybe silly question but did you run the "bin/add-route" script in the bosh-lite directory ? wrote:

Hi Eric, Agree, It has stumped me too, hence asking the list if anyone has seen this behavior. Logging into the bosh-lite VM I can run the cf commands fine but not from my MAC. Also tried curl &

Hi, Daya, Hmm, that sounds like something strange with the local networking on your machine. The 'can't assign requested address' error is coming from the Golang standard networking libraries, and