bosh cf deploy assumes us-east-1 #100
Comments
Same issue for me; but using |
Firstly, congrats on creating issue #100 :) |
Can either of you paste in your |
|
Ok thanks. This looks good to me; but perhaps it doesn't look good to Next, if you have time, look in bosh source (say deployer/ project) for Else I'll try to look later. Dr Nic Williams |
I've been grepping around looking for us-east-1, but I'm not having any On 12 February 2013 16:32, Dr Nic Williams notifications@github.com wrote:
David Laing |
In my deployment, which was in us-east-1, so it didn't fail, also put the |
i ended up changing DEFAULT_AVAILABILITY_ZONE in /usr/local/lib/ruby/gems/1.9.1/gems/bosh_aws_cpi-0.7.0/lib/cloud/aws/cloud.rb and got a bit further (then ran into another bug). perhaps this helps? i'll join the grep search in a moment. |
Could this be related to a similar default_availability_zone bug in bosh-bootstrap ? Perhaps we should be adding
|
I'm interested in starting to do that because some AWS users have AZs that Also, if we start managing the AZ allocation manually, then we can start |
Does it makes sense to split a single CF cluster over multiple AZs? Wouldn't you run the risk of having a specific app allocated to a router in I'd assumed you would want them all as close together in network hop terms On Tuesday, February 12, 2013, Dr Nic Williams wrote:
David Laing |
Aha! It looks like
You might also want to specify the Manually correcting your |
i have no section compilation_workers. adding region: us-west-2 to the cloud properties section under compilation doesn't get me past the error. |
He's now talking about the deployment manifest at Dr Nic Williams |
This file?
|
That's the one. compilation.cloud_properties is what Dave was referring to Dr Nic Williams |
The region will need to be discovered via the micro_bosh.yml; like we currently discover the AWS API keys (to offer to provide automatic IP address provisioning). |
Specifically, via microbosh_config.rb #fog_connection_properties |
A fix for this (compilation VMs needing a region) is in branch https://github.com/StarkAndWayne/bosh-cloudfoundry/tree/compilation_region The branch is also working on adding region to all cloud_properties (core, dea, & service jobs). |
@pmenglund @frodenas do know if it recently became necessary for |
It is for all VMs, as you neet to pass it in the CPI options. |
Does this mean that BOSH is going to become multi-region? Else why are we |
It might become multi region - I'm not making any promises on when... You might want to have your micro bosh in one region and your bosh in another - my job is to make bosh configurable, yours is to pick good defaults ;) |
Sorry, I was under the impression from last year that BOSH can live in and |
once I'm done with the fake stemcell I'm working on, you can - we are restricted to the current region when we upload create a stemcell, as it we need to attach an ebs volume to the current instance, but that will go away when I'm done (and we can just reference existing AMIs) |
Ok, so if a user creates a custom stemcell or uses a normal stemcell (for which there is not a fleet of AWS AMI backing it), then we need to set the region to the region of the BOSH. If its AWS, and the chosen stemcell has a set of AMIs mapped to it, then we could prompt for which region to deploy to (based on whats available in the fake stemcell) |
I think you're aware of this but running |
There are actually 4 instances of cloud_properties in The following grep shows how the "corrected" sections of your
|
I confirm the bug; and I confirm the fix in the comment above (eu-west-1 zone). |
Hi, I had same "invalid availability zone" issue and followed above comments and modified 4 instances of
|
It first failed, then you corrected and ran again? I have never really understood how to recover from failures like this. You could try running |
Yes, it failed first, and I modified the configuration file and run it again. And it failed with above error. With no other options, I have to start it over from very beginning (boot-bootstrap). I will try the "bosh cloudcheck" next time... Thanks! |
BTW, in case of a failure, such as |
bosh cloudcheck - and say yes fix any problems Then bosh delete deployment production-core --force This should leave you with just your inception vm and your micro bosh. You On Tuesday, March 19, 2013, Steven wrote:
David Laing |
i set my microbosh up on aws us west 2 (oregon). bosh cf prepare system installed bosh on us-west-2 as well.
upon running bosh cf deploy, i receive this error:
The text was updated successfully, but these errors were encountered: