Hi Glenn,
I'm all for the simple approach. I think the power of the DC is
for a user to twiddle the bits on and off and extend only if necessary and
skilled enough.
If you have a finalizer which does the checksums then someone
wanting to extend this functionality can always easily slurp-up and modify
that finalizer script. Easier is certainly better!
Though I agree with the simplicity of Karen's desire to have the
create_iso and create_usb steps include the hash generation, having it all
in one place (a single finalizer script) makes a modification by skilled
users easier without really any added complexity for a novice.
Lastly, so the hashes will be in files, how about the DC log?
Thank you,
Clay
On Thu, 12 Mar 2009, Glenn Lagasse wrote:
> Hey Dave,
>
> * Dave Miner (Dave.Miner at Sun.COM) wrote:
>> Glenn Lagasse wrote:
>>> * Eric J. Ray (Eric.Ray at Sun.COM) wrote:
>>>> On Mar 12, 2009, at 10:10 AM, Glenn Lagasse wrote:
>>>>>> What's the use case around generating several kinds of images, but
>>>>>> only requiring checksums for some of them, or generating different
>>>>>> checksums for different kinds of images? Common?
>>>>> I don't know that there is enough data to determine what's common. If
>>>>> we use the OpenSolaris releases as a guide, I'm pretty sure that we
>>>>> want
>>>>> to generate the same checksums for all the images we create. And so
>>>>> requiring checksums for some of them or different checksums for
>>>>> different kinds of images is probably not common (at least in the
>>>>> OpenSolaris release case).
>>>> So, what does that do for your design?
>>>
>>> It makes it simpler. We create a new 'toggle' in the DC manifest to
>>> enable checksumming of images (all images) and then the finalizer
>>> scripts that generate images compute image hashes using the list of
>>> hash types that I deemed appropriate/most useful (md5, sha1, sha256).
>>>
>>
>> Will you be placing the hashes into a single file, a file per hash type,
>> or what?
>
> Ah yes. My thought is to create a file per hash type. The file will
> contain the hash and a reference to the file the hash is for.
>
> So, (just for completeness) if we have OpenSolaris.iso we'll then have:
>
> OpenSolaris.iso.md5
> OpenSolaris.iso.sha1
> OpenSolaris.iso.sha256
>
> And these files will contain text such as:
>
> md5 (OpenSolaris.iso) = e73b3c89c96172030666226313298ba9
>
> The hash files will be stored in the same location as the image media.
>
> --
> Glenn
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
