Hello, Danny. As I'm doing nested virtualization, both virtualbox need to be the same version? I'm think i'll try to install direct in the my own machine to test, but as i've read, the nested

Hi Devs, I generated a sample tile using the Tile Generator [1] and trying to deploy it on BOSH using bosh-lite. However, I couldn't find information on that in the documentation [2]. Appreciate

Hi, One of my Bosh deployment displays directors version as: 260.0.0 However another one as: 1.3232.7.0 How to interpret them, and how can I map them with github bosh releases? Thanks! in

Hi - welcome to Cloud Foundry! That error probably means you have an incorrect version of Vagrant/VirtualBox installed (e.g. a version for 14.04 vs 14.10), or you're missing the correct kernel modules

Hello! I'm new in this and i need deploy the Cloud Foundry using BOSH-Lite. During the vagrant up --provider=virtualbox, i had the error below: There was an error while executing `VBoxManage`, a CLI

Partha, Like Michal suggested, you can use cf-deployment and you'll likely have an easier time working with the BOSH v2 CLI. In the meantime, the Release Integration team is going to look into the

Hi! It might be the case that VirtualBox shutdown the VM, so it's no longer running. If so, it's probably easiest to rerun the `bosh create-env` or `vagrant recreate` to get it back. If your

Hi :) I need more help than request thread. I just finish http://mariash.github.io/learn-bosh/#introduction tutorial. I closed my Linux and when I back I have error : Fetching info: Performing

Hi, all. I tried to add runtime config and misconfigured something. Can I delete or update the malfunctioning runtime addon config/script? Already deployed addon job script is not updated

Hi, I think you'd be better off with cf-deployment - it's a new way of deploying CF, still under development but mature enough for test environments. It's built to be used with

Folks, Is there any way to build cf-release using bosh cli v2 . Currently I am stuck up while running *./scripts/generate-bosh-lite-dev-manifest* *Unknown command `status'.* This is obvious as

Hi Subin, it appears, that the network ID given in your BOSH OpenStack CPI config does not exist in the (also configured) OpenStack project the CPI is running against. Like the error message states,

I installed spiff using gvm in AWS Ubuntu VM. When I try with spiff -v, it shows me the version of spiff. ubuntu(a)agent-id-bosh-0:~/cf-release$ spiff -v spiff version 1.0.8 Spiff CLI is working

I wonder how many people have gone to look for the original email now :-)

There is no facility to do that, although it would be largely ineffective anyway. Your message went out to all subscribers on this mailing list already. wrote: -- Chip Childers CTO, Cloud Foundry

Hi guys, I just recently made a post however I included a URL which I would like to be deleted, can this please be done? Do I have access to do this? Thanks

This should probably be in cf-dev, but I will say that the first error looks like your user/client does not have the `doppler.firehose` scope in its credentials. As for the second error, looks like

Hey Guys, We have been having an issue when trying to deploy logsearch, all VM’s are running within CF and all instances running for log search except `logsearch-for-cloudfoundry` which is failing.

That new error message is an excellent idea, as it addresses the specific confusion I have witnessed and it leads the user to a resolution in fewer steps than my proposal outlines.

Hello Gwenn, Thanks for info. Yes for contribution , i see the opportunity Thanks