Up to you but nornally you just need to create a package to install openJdk, for example https://github.com/cloudfoundry-community/jenkins-boshrelease/tree/master/packages we install the jre, should

Try to make bosh cck before bosh deploy. wrote:

I was able to fix this by copying from the generated cf-deployment.yml and use it in cf-stub.yml after changing cf release and jobs section. Now "bosh deploy" works but not complete, running into an

The BOSH_INSTALL_TARGET would be /var/vcap/packages/<nameofPackage>. The files under this folder would be saved from the compilation vm onto the target vm with the same path if the job has a

the uaa needs java the java buildpack builds and hosts the openjdk jre's on a repository: https://github.com/cloudfoundry/java-buildpack/blob/master/config/repository.yml you'll just need some help

i'm trying to create a bosh release that needs openjdk 1.8 but i have no clue on how to do this i know that you can do it with bosh-gen --apt option and then it downloads a massive amount of

Hi, I am trying to use manifest that is generated using the to_yaml transformation technique in Ruby. However, this deployment manifest is not recognized by bosh because it has comments that detail

This is a package script sample from https://bosh.io/docs/create-release.html#pkg-scripts set -e -x cp -a ardo_app/* ${BOSH_INSTALL_TARGET} cd

OK it's fixed now, for the record, Oddly enough, apparently it was related to the fact that external ip address was not assigned to project. truly misleading error message :I --- Armin ranjbar

With pleasure, it's quite possible that i didn't understand my setup as well :) since the neutron issue, i have noticed that my floating network had static range stuff, so i have changed the type to

Can you share your manifest? I dont quite understand your setup.

Typically releases are distributed to end users via release tarballs or release git repo: - to generate release tarball use `bosh create release --with-tarball` or for the existing release `bosh

That fixed the error, thank you! And run into another error :) M-20JW:cf-release ali00$ bosh deployment cf-deployment.yml Deployment set to

Hi Ahmed, It looks like you haven't allocated enough IPs in your network. The line for reserved IPs "10.166.166.104 - 10.166.166.115" should be increased to have at least 19 IPs. You'll need to

Hello everyone, I have been playing with CF installation, and i have noticed that during DNS binding stage of deployment, BOSH tries to create an instance (zrouter) that directly connects to External

If you OpenSource your bosh-release you can ask to be added to https://github.com/cloudfoundry-community/ and you will be able to ask for the community s3 bucket to put your final release and maybe be

Hi, I have a process which creates a bosh release -> which has all the artifacts and use a microbosh instance to create my release. It all works great! As I move to the next step to distribute my

Thanks Gwenn, Dmitry I'll try this out.

Thanks for the suggestions. No `depends on` directives though, and canary/update watch times were set to `30000-120000`. I was thinking it was more an issue of monit not getting a chance to

Do you use 'depends on' directives? Are you sure you have configured `update` options for your deployment giving enough time for the monit to spin up processes and have them running?