bosh-init? Not in my opinion regardless if you are using bosh-init or micro CLI plugin. Regarding error from bosh-init, you can try turning on verbose logging: export

Hi all, I configured the email notification for health monitor. and I checked the configure file “jobs/health_monitor/config/health_monitor.yml" in bosh director. plugins: - name: logger

I was able to resolve issue by changing dns host to 10.0.0.2..Please ignore my first question.

I am getting confused here...Is there any reason to deploy bosh after deploying micro-bosh using bosh-init? Doesn't it serve same purpose as bosh ? Really appreciate if someone can educate me..

Hi , We've been using microbosh -> bosh -> CF model in AWS.. I tried to use bosh-init and able to deploy microbosh successfully..When I am trying to upload stemcell (As part of deploying bosh) ,I

Sweety ! wrote:

Hi, We have a number of BOSH deployed applications that use persistent disks. My understanding is that these are what VMware terms "independent disks". I'm looking for ideas on how to efficiently back

Congrats on shipping this! wrote:

Hey all, Starting with version bosh-release v209+ colocated with uaa v1+ you can use the UAA for authentication and authorization of the Director users. This means that you can have read-only users

Currently an email to Dmitriy works a treat. Nic

Hi all I'd like to get the next release of the logsearch-for-cloudfoundry boshrelease added to bosh.io/releases Could someone give me some pointers as to what I need to do? Thanks! David

Hi Jim, You are right, Garden is platform neutral API and in one CF/Diego DEPLOYMENT it is possible to have both backends. You may have many cell INSTANCES, but one cell INSTANCE may contain only one

Correct, you can have linux and windows cells managed by the same CF deployment. (Btw for more detailed CF answers you can try cf-dev mailing list)

Hi all With Diego, Garden-Linux , and Garden-Windows, does it mean that I can deploy one Cloud Foundry instance which is backed by both Linux and Windows containers at the same time?

bosh.pem should contain private key. machines will be provisioned with associated public key. did you use aws generated key from the console? also make sure you are using correct key pair name.

Can you try with ubuntu instead of vcap ? wrote:

I have the same issue. I can get through to the VM but it seems like the certificate based login fails, not comms to the machine. I get this response when I try to connect manually: ssh

Hi, I have the exact same issue but have not heard back from anyone. Glad to see Im not the only one stuck on this issue.

Hi, I am trying to deploy to AWS and everything goes fine until the " Waiting for the agent on VM.." step has to happen. I have tried to login to the VM with my pvt key (ssh -i

Hi All, When am uploading the Cloud Foundry Release v202 to the Director, its throwing the following error. bosh upload release /root/tmp/cf-release-202.tgz Acting as user 'admin' on