-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can latest 1.5.0.pre2 micrbosh work with public gems? #56
Comments
Director.yml.erb has been changed to use the new style properties (08cccdd). I guess there's now some new mandatory property, so if it's not filled then it doesn't detect that cpi plugin should be aws. The only thing it has been changed it's the region. Can you please confirm that you've a region property on the micro_bosh.yml aws credentials. |
There is a cloud.properties.aws.region field in my micro_cloud.yml: cloud:
plugin: aws
properties:
aws:
access_key_id: XXX
secret_access_key: YYY
region: us-east-1
ec2_endpoint: ec2.us-east-1.amazonaws.com
default_security_groups:
- microbosh-aws-us-east-1
default_key_name: microbosh-aws-us-east-1
ec2_private_key: /home/vcap/.ssh/microbosh-aws-us-east-1.pem |
The latest stemcells should be used with the pre-released gems. The public gems are not tested with the 1.5.0.pre2 stemcells so your mileage may vary. |
Use m4 instance types, not m3
Raised at cloudfoundry-community-attic/bosh-bootstrap#115.
I am using the latest public gems and when I try to deploy microbosh I get:
What does
failed to process configuration template 'director/director.yml.erb': line 172, error: Could not find cloud plugin
mean? Did the micro_bosh.yml schema change? Does this stemcell only work with bosh_deployer built from master/HEAD?The text was updated successfully, but these errors were encountered: