Closed mgarciap closed 10 years ago
mgarciap: can you clarify how you fixed this? it seems like uploading a modified stemcell would require overriding the url it is getting the original from
the hardcoded url for DEFAULT_LIGHT_STEMCELL_URL can be overridden with environment variable BOSH_OVERRIDE_LIGHT_STEMCELL_URL
after downloading latest-light-bosh-stemcell-aws.tgz, replacing all instances of bosh-stemcell with bosh-aws-xen-ubuntu, uploading to a new location and overriding the stemcell url, I still have the same problem. There is no cf-aws.yml in the stemcell though so I may be doing something wrong.
@jblancett I just had a look at the unpacked latest-light-bosh-stemcell-aws.tgz file
~/dev/cf/bosh/stemcells/aws/latest-light-bosh-stemcell-aws
03:35 PM $ ll
total 152
drwx------ 8 manu staff 272B Nov 18 15:35 .
drwxr-xr-x 5 manu staff 170B Nov 7 00:34 ..
-rw-r--r-- 1 manu staff 8.2K Sep 12 22:52 ami.log
-rw-r--r-- 1 manu staff 5.7K Sep 12 22:43 apply_spec.yml
-rw-r--r-- 1 manu staff 0B Sep 12 22:47 image
-rw-r--r-- 1 manu staff 14K Nov 7 00:36 latest-light-bosh-stemcell-aws.tgz
-rw-r--r--@ 1 manu staff 276B Nov 7 00:35 stemcell.MF
-rw-r--r-- 1 manu staff 35K Sep 12 22:44 stemcell_dpkg_l.txt
What I did is modifying the following file changing the name property and it worked such as I posted in the vcap-dev group
03:37 PM $ cat stemcell.MF
---
name: bosh-aws-xen-ubuntu
version: '992'
bosh_protocol: 1
sha1: 64b06787e8e6008d2b66f51f1480a01c5fd6287b
cloud_properties:
name: bosh-stemcell
version: '992'
infrastructure: aws
architecture: x86_64
root_device_name: /dev/sda1
ami:
us-east-1: ami-fdeca594
~/dev/cf/bosh/stemcells/aws/latest-light-bosh-stemcell-aws
@mgarciap thanks! changing only the first occurence of bosh-stemcell did the trick
@mgarciap, @jblancett Is this issue resolved? I'm doing some issue house-keeping and would love to close this if the problem is solved :)
@dajulia3 I tried it out around a month ago and it still wasn't fixed.
@mgarciap, alright thanks for the info, I'll try to follow up with the appropriate people.
@mgarciap I looked into it, and we have decided that we are no longer supporting or maintaining cf bootstrap aws. We will be moving the repo into the cloudfoundry-attic.
Sorry no one got back to you on this sooner!
What will you suggest in exchange? Is this still the way official doc tells you to do it? http://docs.cloudfoundry.com/docs/running/deploying-cf/ec2/index.html
Link to the thread: https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/TPdWxT8LH8w