here [2] I am not sure what you mean by that. If bosh.io picked it up that means everything that was needed was uploaded to correct places. wrote:

I enjoy seeing more innovation in this area. As a bonus, there is also a `curl | bash` solution that I like to use as it requires zero setup at deploy

Hi, The admin-ui boshrelease has created a new version (v6) which can be manual downloaded from here: [1] It would be nice to have this release also available in S3 as documented here [2]. I don't

Awesome idea! Thanks for this.

Thanks for the information. I'm assuming that I can use a "VIP" bosh network definition to solve this, then put the ip address in as the property. It was relatively easy to define this, but I can't

Hi, I am getting the following output and error when attempting a bosh upload release on AWS bosh upload release ~/cf-deployment/cf-release/releases/cf-217.yml Acting as user 'admin' on

Hello , We are open sourcing one of our bosh release : Dotfile bosh release https://github.com/rakutentech/dotfiles-boshrelease Inspired by

We currently have a problem rendering templates with default ruby installed - 1.9.x, because json gem changed some behavior. If you upgrade your ruby issue should go away. Sent from my iPhone

Trying to Bosh-init install and getting the following error rendering the director.yml.erb.erb file. What is the best way to troubleshoot rendering issues? Error filling in

Hi Ronak, Thanks for your reply. I’m not sure what API we’re currently using and if not LBaaS, why not. Either way, it sounds like the collocated job is the easiest solution for

We have fixed an issue with director->nginx communication on Director VM. ( https://github.com/cloudfoundry/bosh/commit/3e82ae48555c0f8c4f01ce339ca864d0cd85894f ) It's available in bosh release 202+

While doing bosh export,I kept on getting 502 after copying packages ..Systemlevel resources looks good..Tried to locate compiled packages under /var/vcap/data and /var/vcap/store..Once it fails,I

Thank you for correct me. Shame on me, I meant bosh-init instead of bosh-lite.

Hi Alex, That's not correct. bosh-init is an executable binary, written in golang, used to deploy single-VM deployments of anything you can colocate onto one VM. Using it to deploy BOSH itself is

@daxiezhi in case you are talking about BOSH-director update you should described the way you deployed BOSH. Did you used `bosh micro` command to deploy MicroBOSH? Or did you used bosh-lite? If you

Sorry, I guess some misunderstanding took place. Approximately the same number you’ll get if you run `gem list bosh_cli` because bosh-director has the same version numbering as a bosh_cli, as far

For me, `bosh -t lite status` shows "Version 1.3056.0 (00000000)". I believe that's the version of the bosh-director gem: https://rubygems.org/gems/bosh-director/versions/

Hi, all. Amit, I guess it is not bosh-lite version, because bosh-lite versions are over 9000 [1]. daxiezhi, if you mean by “local bosh” your version of bosh_cli gem, then everything you need to

Hello, I Agree that it will be helpful for Openstack deployments but having something like this in CPI will only be helpful when native Openstack LBaaS api are used . For custom ELB deployments it

Hi Dies, I agree that the registration at an external ELB would be very helpful to have – just like it is done for AWS. We currently use the HAProxy, so I guess this is a challenge which will hit