Make sure to set `region` configuration (See http://bosh.io/docs/init-aws.html for an example manifest with region set). It defaults to us-east-1. Yours should be us-west-2. Also make sure to

We are trying to do a bosh-init deploy bosh.yml onto AWS (using http://bosh.io/docs/init-aws.html) and keep getting this as a result: Command 'deploy' failed: Deploying: Creating instance

awesome! I changed the property and redeployed. It works! Thanks you very much. -Ramesh

Hi Ramesh, Looking at the original logs you provided, we see the following error when the CC tries to talk to HM9000: "SSL_connect returned=1 errno=0 state=SSLv3 read server certificate

Thanks Dmitriy. Would it be possible to put this in an attachment so I can see how you have things spaced out?

What you want is something like this (combination of two): resource_pools: - name: runner_z1 network: cf1 stemcell: name: bosh-vsphere-esxi-ubuntu-trusty-go_agent version: latest

Looks like my YAML format was broken. Here is the YAML configs in Github: https://github.com/coryjett/Cloud-Foundry-DRS/blob/master/README.md

Amit, Below are my cf trace output. guests-MacBook-Pro:apps rsamban$ cf logs gs --recent REQUEST: [2015-09-14T09:39:28-06:00] GET

When you say "local bosh", do you mean BOSH-Lite?

Hello. We are running Cloud Foundry v215 deployed to vSphere and are looking to implement drs_rules to improve fault tolerence per this document https://bosh.io/docs/vm-anti-affinity.html. The

Hi Ramesh, You mention Diego, but I doubt your app is actually trying to run on diego. You are not defaulting to the Diego backend, and I don't see anything about how you're pushing this specific

I deployed diego release and still have issues. 1. Uploaded the app with no-start flag. 2. cf apps works 3. Started the app, got the failed status (app it self is working. I can get int o the app

Hi,all. My local bosh version is 1.2124.0. From cf v208, there is a change in the templates to no longer include resoure pool sizes require s a minimun bosh director of v149. So I guess the solution

Dear Dmitriy, thanks for the quick reply. See my response inline.

Thanks for this simplification! Cyrille wrote: -- Cyrille Le Clerc email & gtalk : cleclerc(a)cloudbees.com / mob: +33-6.61.33.69.86 / skype: cyrille.leclerc CloudBees, Inc www.cloudbees.com

I'm having some difficulty with the new networking configuration. I've defined a 'default' network as follows: networks: - name: default subnets: - range: 10.244.11.0/24 gateway: 10.244.11.1

Everything should still work as is. wrote:

I am glad for future simpler networking for bosh-lite manifests; I just know we have lots of infrastructure-warden.yml spiff templates in lots of bosh releases. Also, will bosh-lite stemcells keep

I know versioning is somewhat a lost cause for bosh-lite.  I guess my actual question is: will old manifests still work for new bosh-lite? I assume so as you said "you will not notice any

Perhaps worthy of a major version bump? wrote: