bosh.io stemcell hashes are shown in md5 while bosh-init requires sha1

[voelzmo]

When you include a new stemcell in your manifest, e.g. from http://bosh.io/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent you have to put the sha1 into your bosh-init manifest. However, the page only lists an md5 hash whereas for bosh releases sha1 hashes are listed.

I didn't find a way to specify manifest hashes as md5, so either this option should be added to bosh-init or the shown hashes on bosh.io should be in sha1.

[ghost]

We are planning to make our CI send sha1s to the bosh.io. Stay tuned.

Sent from my iPhone

On Aug 8, 2015, at 1:02 AM, Marco Voelz notifications@github.com wrote:

When you include a new stemcell in your manifest, e.g. from http://bosh.io/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent you have to put the sha1 into your bosh-init manifest. However, the page only lists an md5 hash whereas for bosh releases sha1 hashes are listed.

I didn't find a way to specify manifest hashes as md5, so either this option should be added to bosh-init or the shown hashes on bosh.io should be in sha1.

— Reply to this email directly or view it on GitHub.

[axelaris]

+1

[RiaanLab]

+1

[penrod]

+1

[geofffranks]

+15

Any ETA on when we can expect this?

[drnic]

Dmitriy, which repo is generating the wrong sha? Perhaps one of the +15 people can then PR a fix.

On Mon, Nov 2, 2015 at 10:52 PM, Geoff Franks notifications@github.com wrote:

+15

Reply to this email directly or view it on GitHub: https://github.com/cloudfoundry/bosh-init/issues/41#issuecomment-153168860

[weberstephanhd]

+16

I need that, too.

[cppforlife]

It's not a repo per se but our jenkins pipelines dont produce and send sha1s to bosh.io. I'll bump this in priority.

[nctiggy]

I hate to pile on, but this would nice ;)

[sst1xx]

+1

[sklevenz]

+1

[jhunt]

Just lost about 30 minutes to this.

+30

[lnguyen]

+1

[thegullion]

+1

[geofffranks]

Pretty please can we have this in 2016?

[drnic]

@cppforlife can there be a tracker URL for this please so we can see if/where its in the backlog?

[bosh-cpi-robot]

Yup. Here it is: https://www.pivotaltracker.com/story/show/112466887 as part of the epic to move over to using concourse for stemcell generation.

On Tue, Jan 26, 2016 at 2:13 PM, Dr Nic Williams notifications@github.com wrote:

@cppforlife https://github.com/cppforlife can there be a tracker URL for this please so we can see if/where its in the backlog?

— Reply to this email directly or view it on GitHub https://github.com/cloudfoundry/bosh-init/issues/41#issuecomment-175258063 .

[schabiyo]

+1

[bs-sdev]

Still not available?

[mtekel]

7 months and still no fix?

[SimyungYang]

+1. Please fix this issue. :)

[emalm]

+1: I'd like this to simplify the bosh-init instructions in https://github.com/cloudfoundry-incubator/diego-release/tree/develop/examples/aws#stubsbosh-initstemcellyml. I'd prefer for bosh.io to display the SHA checksums, so https://github.com/cppforlife/bosh-hub/issues/7 is also relevant.

[crawsible]

+1. Come on, dawgs.

[cwlbraa]

+1 please?

[virtmerlin]

+1 Cough Cough ... Still Only See md5 on bosh.io

[geofffranks]

Dmitriy et al are working on this, but it's going to be a gradual migration of stem cells. To help ease the transition, http://stemcell-sha1s.starkandwayne.com/<stem cell name>/<version> will spit back the sha1 of the stemcell.

It only goes back to about 3215, but it is auto-updated as new stemcells come out.

For example:

curl -k http://stemcell-sha1s.starkandwayne.com//bosh-aws-xen-centos-7-go_agent/3232

[combor]

No sha for stemcells makes me sad...

[cppforlife]

bosh.io will now show sha1s for 3262.2+ stemcells.