By default everything in a VPC outbound is restricted, whether you are in a "public subnet" or "private subnet" or not. http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html The

By hanging I supposed eventually timeout? If so...you sure you have the routing table configured for that subnet of your VPC? Create a vm in the same subnet and try if you get the same

Congrats BOSH team! I'll upgrade my little tutorial repos to use new GitHub releases asap. wrote:

Hey all, I'm happy to announce beta release of bosh-init. bosh-init is a tool used to create and update the Director (its VM and persistent disk) in a BOSH environment. It's meant to replace the

There is no error. That VM hangs when I execute apt-get update or do a traceroute to Yahoo. Thanks Sumanth Sent from my iPhone

Does it not work at all or is some error is shown? wrote:

I tried putting 10.0.0.2 as my dns.recursor…I am still having issues with DNS resolution on nodes which use network with DNS entry of micro-bosh (10.0.0.6) for the other nodes provisioned there is

I was experimenting with the warden stemcells and found that I could upload a locally downloaded stemcell, but that neither of the following worked: ``` $ bosh upload

You should be able to use dns.recursor exactly the same way on AWS as you did on OpenStack. Btw AWS provides 10.0.0.2 address in your subnet as a full DNS. wrote:

Correct. Two options of getting stemcells are downloading them locally (curl/wget) or directly uploading them to the Director (e.g.

Aha. I was using bosh.io and I was trying to see if users could still download the stemcells locally using both the BOSH CLI as well as wget/curl. Is the intention moving forward that eventually users

Hi , I am using the features of BOSH DNS resolution. Deployed a microbosh. In my deployment manifest I specify for a default network to use 10.0.0.6 as my DNS. The behavior is: in AWS It is able to

The command isn't deprecated yet, but the `--full` flag is used for `bosh public stemcells`, rather than `bosh download public stemcell`. The idea behind the `--full` was to display a full URL from

It has not been officially deprecated just yet (thanks for the reminder!), but it's definitely better to look at https://bosh.io/stemcells. wrote:

I think "bosh public stemcells" is deprecated in lieu of bosh.io. I think. wrote:

There have been some early discussions (and I believe there might be a closed source prototype out there), but it's a logical step at some point. -chip

I was playing around with the CLI and I noticed that the output of `bosh public stemcells` indicates there should be a `--full` parameter; however, it doesn't seem to work? ``` $ bosh public

Given the recent announcement of BOSH on Azure; is there any news coming about managing Windows VMs using BOSH? I'm wondering if this is a: * Not even on the roadmap; never going to happen *

Hi, I was able to deploy my release a few weeks back, now it fails with strange errors including some manifest schema and default VPC being used. Bosh CLI version: BOSH 1.2950.0 (updated

Hey Quinn. 6.2kb seem like right size for light stem cell. If you want full stemcell it's around 400mb and there is different url for that. Long