Thanks Dmitriy, so if I “version control” a manifest, I’d have to keep a different version for “prod” and another one for “staging”? Is there a way to override it in the command

It's a safety feature so that people do not accidentally deploy deployment with a same name to a wrong environment. For example if you have staging and prod environments and both have cf deployment.

Team, After reviewing the bosh.io site and other email list, I can't find a good reason on why does the manifest YAML file needs to have the director_uuid in the manifest. According to the docs found

Thank you, Dmitriy.

bosh-init was not properly assigning which network should be used for DNS and gateway settings: https://www.pivotaltracker.com/story/show/94624368 alexander.lomov(a)altoros.com> wrote:

Daya, Thanks for confirming that you're using the `ruby-buildpack`, intended for us in a container rootfs, on the stemcell. As I mentioned earlier in this thread, that's not supported with the

Hi guys, Is there a rough way to calculate how much physical servers a certain deployment will need? Let's say I have an application with 50 instances, RAM = 500Mo and Disk = 100 Mo. My servers are

Hi Mike, May be the following will help you reproduce the problem without having to setup Jenkins But to give you little more context. We have a Jenkins build slave which is container instantiated

The issue is that there appear to not be any light stemcells in your region, there is another recent question on the list to this effect. In order to make progress you might want to build your own

Hi Dmitriy, Thanks and sorry again for the slow response. Nabble stripped out my bosh vms output unfortunately - I’ve created a gist at https://gist.github.com/spikymonkey/9938dcdcc7a9a6097183

Hello, I tried to deploy micro bosh in AWS region cn-north-1 in several ways, but all failed. Any suggestions on how to deploy micro bosh in AWS region cn-north-1? Thanks! I created a EC2 instance

I want to run two cloud foundry instances on my notebook to try something out. I have a problem setting the IP addresses to a range in one of them, so that they can be resolved from the host machine

i you pull down a "light" stemcell, you can see in the stemcell.MF file what regions are supported. ami: eu-west-1: ami-7f443108 ap-northeast-1: ami-5ca76c5c us-west-1: ami-d143ad95

If you use a normal (non-light) stemcell then `bosh micro deploy` will create a private AMI for you. You will need to be in an AWS China VM, a jumpbox/bastion/work VM. Use one of these stemcells

Dmitry, could you please tell what's the problem with bosh-init? Because currently I see a similar problem and I thought that it happens in CPI or IaaS. Is there any description / ticket / issue

Hey all, vSphere stemcell version 2972 is now using hardware version 8 [1]. Dmitriy [1] https://github.com/cloudfoundry/bosh/commit/ac26c2e793c4108ab867d0e6b7f08ff801fddcbb

We have confirmed that bosh-init does not properly set things up; however, when using the Director it _does_ correctly configure DNS when multiple networks are specified for a job. Is this what you

Hi, there I am trying to deploy cloudfoundry environment in AWS China ( http://www.amazonaws.cn/), which is a bit different from golbal AWS ( http://aws.amazon.com/cn/). The most difficult part for

if you have specified your elastic IP in the manifest associated with a deployment job, BOSH will make sure it's connected and will not do any additional work on the subsequent deploys. Btw I cannot

DNS should properly be configured. You are about the gateway though. I'll try to repro the case today. Sent from my iPhone