i have installed the bosh cli on a new/clean vm and still the same issue. i'm really out of idea's

this will be a weird question and let me explain why: i am using openstack to deploy bosh by using bosh-init. Everything went fine until the bosh VM is spawned and bosh-init is using ssh to contact

Hi Dmitriy, Thanks for your reply. I found where my problem is. Eventually my bosh-state.json file was somehow messed up so bosh doesn’t “remember” the last deployment state for bosh itself.

Hi Dmitriy, Thanks for your reply. I found where my problem is. Eventually my bosh-state.json file was somehow messed up so bosh doesn't "remember" the last deployment state for bosh itself. After I

Hi I was trying to bootstrap an environment on AWS following instructions at [1]. I'm getting an error - Started installing CPI Compiling package

The only thought I have is that for some of us that are doing network level encryption until you guys do have everything secure by default, this would just enforce double encrypting some things. Not

Thanks Zach, I agree it'll be nice to move all the things to secure-by-default as a general rule. I realized I left the link out of my original email when I said "The BOSH release of consul

I love the idea of secure by default, with simple tooling provided to enable development workflows. If things work well on this release it's probably a good idea to start using a similar pattern

Make sure you can ssh vcap(a)ip -i bosh.pem to check that your private key is correct.

layer (i am using openstack), then run bosh-init? to be explicit, no, you should not have to do this when migration happens.

Make sure to follow directions from: http://bosh.io/docs/migrate-to-bosh-init.html. You should see bosh-init find bosh-deployments.yml file and migrate it. If migration has

did you resolve this issue? i have the same problem. i am using openstack and using bosh-init to deploy bosh. in openstack i generated key pair, and save the private key as bosh.pem. In bosh.yml file

Hi all, i was trying to use bosh-init to upgrade my current running bosh director to a newer stemcell, at the very last step when it's creating the VM, it threw error and said: "...fixed ip address

Hey all! The BOSH release of consul maintained by the core CF team [1] currently supports both encrypted and unencrypted modes of operation. "encrypted" means that all server-to-server and

+ cf-bosh Looking for community feedback on bumping consul to 0.6.0 in the consul-release maintained by the core CF team: https://github.com/cloudfoundry-incubator/consul-release. Please see

konstantin, only red hat can distribute RHEL. CF is OSS, therefore centos is what we build and distribute as part of the cloud foundry foundation projects as a bosh stemcell. i'm not sure what

not to say that you cant deploy all cf components colocated on a few machines if you really wanted. Sent from my iPhone

Hi Dr. Williams, For the machine types, it's whatever machine that RackHD supports. We have experimented with IPMI and AMT. They both work very well. For the time being, RackHD CPI is really

Thanks Felix, we'll give it a shot.

Awesome! "Can CF deploy to bare metal?" has been a question for years. From a demo/training/experimenting perspective what will be the smallest footprint of machines/disks etc that will be