Backing storage/client are dependent on md5 checksum

[Joshua Harlow]

In multiple places there is a lacking of information on what checksum algorithm a image used.

So if someone wanted to use a better hashing algorithm they would not be able to.

Looking at the db it only has (in the images table).

| checksum | varchar(32) | YES | | NULL | |

Note a checksum_type (which could vary) would be needed to allow for other hashing algorithms (besides md5).

Similarly with the glance client, it would need something like.

x-image-meta-checksum-type header to distinguish what to use.

[Brian Waldon (bcwaldon)]

python-glanceclient's image-create now communicates md5 as the required hash algorithm. The backend does not allow this to be configurable, I agree, but I'm not convinced there is a big need for this.

[Erno Kuvaja (jokke)]

Old and inactive, closing for glance.