Hi all, I deleted my "cf" deployment git cloned the latest https://github.com/cloudfoundry/cf-release.git I am using the latest stemcells

Hi all, I deleted my "cf" deployment git cloned the latest https://github.com/cloudfoundry/cf-release.git I am using the latest stemcells

Ah I think the problem with bosh-lite might be it's configured to use admin/admin-password for the resurrector but the Director has

Hi Dmitry, Is there official documentation of the external CPI contract ? I had noticed a draft [1] you mentionned on bosh-dev@ a while ago. An official doc will be quite helpful as a complement to

Hi, I'm trying to deploy bosh on an OpenStack instance. I am following the directions from https://bosh.io/docs/init-openstack.html bosh-init will deploy the instance on Openstack; it will then

Thanks a lot for the respond. Pablo, Lev and Nic also gave me some pointers. I am redeploying with cf-212. thanks all. Sincerely, Dulanjalie wrote: -- Dulanjalie

Thanks a lot Pablo, Lev and Nic. I will give this a try ... Sincerely, Dulanjalie wrote: -- Dulanjalie

It's not necessary to change tag to recreate a final release or upload it. The cf-212.yml is permanent in the repo (unless someone removes it) and can be used from any commit. You will want to

The newest stable release (as well as any other production release) has to be built not from the master branch but from the corresponding tag - for the release 212 it is v212: git checkout v212

Best way delete deployment and redeploy to start from clean env.

this looks like DB migrations may be messed up. -- Thank you, James Bayer

i think the resurrector works on bosh-lite already. let us know if you find that isn't the case. michael.grifalconi(a)studenti.unimi.it> wrote: -- Thank you, James Bayer

looks interesting, would love to hear if people try this approach. thanks for sharing! leandro.21.2008(a)gmail.com> wrote: -- Thank you, James Bayer

I see two possibilities here: A Cloud Controller database corruption (due to previous errors) or a version mismatch. I think more of the latter because staticfiles_buildpack and binary_buildpack have

Don't think so ...

Hi Dmitriy Thanks for your reply. My Google Hangout jimlintw922(a)gmail.com One more questions: 1. My target IaaS is a KVM-based computing platform inside my company. It is not

Dmitri, The spec of the compile VM is amzn-ami-vpc-nat-pv-2014.09.1.x86_64-ebs. Neto, The security group for the Director has the following inbound rules.. The source IP was originally set to my

Hi Holger, You can name a job (in manifest ) anything you want , it is the template name that matters which refers to the actual package or job from cf-release. Regards, Ronak -- View this

The dbg.log file was included in the original message Dmitry. I’d start by checking the BOSH director security group - it sounds like you’re getting a connect timeout error? D, [2015-06-23

Please include a stack trace from `bosh task X --debug` where X is the Director task number that was included in the `bosh deploy` output. wrote: