Sorry for the slow response. Thanks Dmitriy for the outline of the read-only access. Additional "admin" access probably wasn't a good way to describe what I was referring to. Below is a description

Hi all, I am in the process of bringing up cloud foundry setup using BOSH for the first time. when i execute bosh micro deploy it got stuck at below point. I see a Vm got created in AWS. I am not

Nice find. wrote:

Hi all, I am in the process of bringing up cloud foundry setup using BOSH for the first time. when i execute bosh micro deploy it got stuck at below point. I see a Vm got created in AWS. I am not

Following up on this thread: https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/NokZ5H6b1Xs It intimates that I can preload my stemcells on a shared vCenter datastore. Can I do

That was it. A cautionary tale, I suppose. Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology

Hi Ahmed, This property is coming from the "templates/cf-lamb.yml" within cf-release. You are able to overwrite this property in your stub like so: meta: environment: [name-of-environment] Hope

Welp, I’m an idiot. My bosh.yml had the solution the whole time and I didn’t even see it till reading things for the ten thousandth time. I should have been pointing everything to 192.168.245.2,

Thanks for the clarification of microbosh — sometimes I get a bit confused between bosh, bosh-lite, and microbosh. I did try uploading a different release directly from bosh.io (vs creating the

The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh). wrote:

That’s a good question. I’m not even sure this is a microbosh environment. I followed the steps to use `bosh-init`, which I was under the impression created a full-fledged BOSH environment. Should

Josh, to confirm - is uploading other bosh releases to your microbosh also failing? Eg uploading releases from bosh.io? wrote:

Hi all, I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release

sounds like some sort of firewall or security groups issue, where the VMs that are created are not able to talk to the BOSH Director. did you perform this step:

Can you give us a bit more details about what you are trying to do?

Hi again - I still haven't been able to track down why the monit processes are sometimes not restarted. Does anybody have ideas for other things I can try or do to further debug this issue? Any help

Hi, guys! I'm trying to deploy CF on aws and I'm following strictly this tutorial: http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html I completed succesfully steps 1, 2 and 3, but I'm stuck

Right!I stand corrected. -- Best regards from Kamil Burzynski

Errands run their script on a new VM

There is a chance that errands would do the job here? -- Best regards from Kamil Burzynski