Hi Anders,

On Apr 24, 2013 2:01 AM, "Anders Ingemann" <[email protected]> wrote:
>
> > We're currently thinking of an official naming scheme of the form
> > debian-X_Y_Z-vYYYYMMDD for each image. (Unfortunately periods are not
> > allowed in image names, so underscores would work instead.) This is
> > meant to be similar to our other official images but is open to change
> > if Debian has a strong preference.
> Have a look at https://github.com/andsens/build-debian-cloud/tags. I know
my tagnames contain periods, but it would be cool if could arrive at some
common naming scheme across platforms. I'm sure James has some ideas as
well.

I was referring to the name of the image as customers would reference it
within Google Compute Engine after being uploaded and added. The pattern I
listed is based on what Google Compute Engine uses for its non-Debian
images. The name of the corresponding build-debian-cloud tag should
probably specify which cloud now that multiple are supported, but otherwise
I have no immediate thoughts there.

The name of the generated image tarball itself is only relevant to Google
Compute Engine as input to "gcutil addimage", but if we nevertheless want
to stick to a scheme there, a suitable name can be chosen at upload time
until the code is updated to use the scheme. After "gcutil addimage: all
dependencies on the input tarball are dropped.

- Jimmy

Reply via email to