How did ~/workspace/bosh/boshawsbootstrap/templates/awsconfigurationtemplate.yml.erb come to existence?

[drnic]

In the tutorial on deploying CF on VPC it mentions editing ~/workspace/bosh/bosh_aws_bootstrap/templates/aws_configuration_template.yml.erb; but we aren't told where that file comes from.

Perhaps should bosh_aws_bootstrap be added into the Gemfile (from git source) and then run bundle package --all? Testing that now.

[drnic]

I added the following to my Gemfile:

git "git://github.com/cloudfoundry/bosh" do
  gem "bosh_aws_bootstrap"
end

And ran:

bundle install
bundle package --all

And the config file can now be edited via textmate with:

mate vendor/cache/bosh-*/bosh_aws_bootstrap/templates/aws_configuration_template.yml.erb

[drnic]

Having said that, https://github.com/cloudfoundry/bosh/blob/master/bosh_aws_bootstrap/templates/aws_configuration_template.yml.erb#L8 does not look like it is mentioned in the docs. Do I still need to change anything?

[drnic]

cloudfoundry/bosh@78d6415

Looks like it might load $BOSH_VPC_DOMAIN now

[drnic]

So I guess we can now added export BOSH_VPC_DOMAIN=my-cloud.com to bosh_environment?

[drnic]

With bosh_aws_bootstrap added into the Gemfile, I can now just run:

bundle exec bosh aws create

[drnic]

Hit an error. Raised a ticket. Bed time.

[drnic]

Since I'm using HEAD for the aws plugin, I'll try HEAD for the CLI too:

git "git://github.com/cloudfoundry/bosh" do
  gem "bosh_aws_bootstrap"
  gem "bosh_cli"
end

[drnic]

Nope, still failed.

[mreider]

Ok, this was stupid. The instructions would have never worked, so sorry for banging your head. Now we clone bosh into workspace in the instructions. we also changed the environment variables to my-cloud since we support second level domains with the latest bosh.

We will be pushing a new gem when our CI passes, but in the interim we can still use the bundle exec that is in the instructions. WIll remove when the gem is out.