Provide stable names for images #7520

Open
opened 2018-05-26 06:39:22 +00:00 by till · 19 comments
Contributor

The images at
https://kojipkgs.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud/x86_64/images/

contain dynamic information in their name that might change daily, e.g.:

Fedora-Cloud-Base-Rawhide-20180525.n.0.x86_64.qcow2

It would be great if there was also a symlink with a stable name, e.g. Fedora-Cloud-Base-Rawhide-x86_64.qcow2 to make it easier to automatically download the latest image. CentOS does this for example as well:
https://cloud.centos.org/centos/6/images/

The images at https://kojipkgs.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud/x86_64/images/ contain dynamic information in their name that might change daily, e.g.: Fedora-Cloud-Base-Rawhide-20180525.n.0.x86_64.qcow2 It would be great if there was also a symlink with a stable name, e.g. Fedora-Cloud-Base-Rawhide-x86_64.qcow2 to make it easier to automatically download the latest image. CentOS does this for example as well: https://cloud.centos.org/centos/6/images/
Contributor

Metadata Update from @mohanboddu:

  • Issue tagged with: meeting
**Metadata Update from @mohanboddu**: - Issue tagged with: meeting
Owner

So, we avoid symlinks because some mirrors are not able to use/mirror them.

We could hardlink, but then anyone who didn't use hardlinks would get lots of extra space used.

I wonder if we couldn't add something to mirrormanager for this case? @adrian what do you think?

Or, could you just use @adamwill 's fedfind tool?

So, we avoid symlinks because some mirrors are not able to use/mirror them. We could hardlink, but then anyone who didn't use hardlinks would get lots of extra space used. I wonder if we couldn't add something to mirrormanager for this case? @adrian what do you think? Or, could you just use @adamwill 's fedfind tool?
Contributor

@till What is the use case here?

One of the use case we heard is:

mboddu: hey/ping! I'm wondering whether would be possible that we could have a fixed symlink pointing to every new rawhide iso. Currently we have http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/x86_64/iso/ and then the iso names as Fedora-Server-dvd-x86_64-Rawhide-20180530.n.0.iso (for instance). Would be possible to have a symlink like Fedora-Server-dvd-x86_64-Rawhide-latest.iso pointing to the latest built ISO
mboddu: the reasoning behind that is: we've got some reports of people who'd like to give it a try on latest rawhide using Boxes (which can automatically download and express-install the iso for you)

@till What is the use case here? One of the use case we heard is: ><fidencio> mboddu: hey/ping! I'm wondering whether would be possible that we could have a fixed symlink pointing to every new rawhide iso. Currently we have http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/x86_64/iso/ and then the iso names as Fedora-Server-dvd-x86_64-Rawhide-20180530.n.0.iso (for instance). Would be possible to have a symlink like Fedora-Server-dvd-x86_64-Rawhide-latest.iso pointing to the latest built ISO <fidencio> mboddu: the reasoning behind that is: we've got some reports of people who'd like to give it a try on latest rawhide using Boxes (which can automatically download and express-install the iso for you)

Let me complement this comment.

Boxes gets the URL from osinfo-db in the following format:
https://gitlab.com/libosinfo/osinfo-db/blob/master/data/os/fedoraproject.org/fedora-28.xml.in#L37

As the rawhide ISOs have their URL changing on every new ISO, it makes impossible to provide a Rawhide experience of "Download and Install this ISO" as we can do for released ones.

So, that's the main reason we'd benefit from a "latest" link,

Let me complement this comment. Boxes gets the URL from osinfo-db in the following format: https://gitlab.com/libosinfo/osinfo-db/blob/master/data/os/fedoraproject.org/fedora-28.xml.in#L37 As the rawhide ISOs have their URL changing on every new ISO, it makes impossible to provide a Rawhide experience of "Download and Install this ISO" as we can do for released ones. So, that's the main reason we'd benefit from a "latest" link,
Author
Contributor

I would like to use the images easily for a CI tool to test software against it. It uses a format that is desscribed here:
https://github.com/linux-system-roles/test-harness/blob/master/README.md

A solution with some mirror manager magic would be great, too. In general it would be great if mirror manager would only contain redirects for the actual files that are mirrored and not the directories (I believe I filed this, too, somewhere) then it would be easy to also provide a virtual link (download.fedoraproject.org is backed by mirror manager, is it not?)

I would like to use the images easily for a CI tool to test software against it. It uses a format that is desscribed here: https://github.com/linux-system-roles/test-harness/blob/master/README.md A solution with some mirror manager magic would be great, too. In general it would be great if mirror manager would only contain redirects for the actual files that are mirrored and not the directories (I believe I filed this, too, somewhere) then it would be easy to also provide a virtual link (download.fedoraproject.org is backed by mirror manager, is it not?)
Author
Contributor

Btw. since CentOS does it, maybe we can use their solution? Not sure how they actually do it. Also about the lots of extra space used, the images are rather small (at least the cloud images, therefore it would not be that much extra space).

Btw. since CentOS does it, maybe we can use their solution? Not sure how they actually do it. Also about the lots of extra space used, the images are rather small (at least the cloud images, therefore it would not be that much extra space).

Metadata Update from @syeghiay:

  • Issue assigned to mohanboddu
**Metadata Update from @syeghiay**: - Issue assigned to mohanboddu

@mohanboddu needs to find out if CentOS has mirroring or not. If yes, then can find out what their solution is. If not, we need to come up with a solution.

@mohanboddu needs to find out if CentOS has mirroring or not. If yes, then can find out what their solution is. If not, we need to come up with a solution.

@mohanboddu is working on a proposal that requires this feature.

@mohanboddu is working on a proposal that requires this feature.
Member

Metadata Update from @cverna:

  • Assignee reset
**Metadata Update from @cverna**: - Assignee reset
Owner

@bstinson how does centos handle this? Is it a post compose link/mirror setup?

Otherwise I think we may need to implement something in mirrormanager for this? CC @ardian

Or, fedfind I think can find these, perhaps we could just ask people using CI to just call fedfind? CC @adamwill

@bstinson how does centos handle this? Is it a post compose link/mirror setup? Otherwise I think we may need to implement something in mirrormanager for this? CC @ardian Or, fedfind I think can find these, perhaps we could just ask people using CI to just call fedfind? CC @adamwill
Member

Metadata Update from @patrikp:

  • Issue close_status updated to: Can't Fix
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @patrikp**: - Issue close_status updated to: Can't Fix - Issue status updated to: Closed (was: Open)
Member

On second thought let's keep this open for now.

On second thought let's keep this open for now.
Member

Metadata Update from @patrikp:

  • Issue status updated to: Open (was: Closed)
**Metadata Update from @patrikp**: - Issue status updated to: Open (was: Closed)
Member

Metadata Update from @patrikp:

  • Issue untagged with: meeting
  • Issue tagged with: groomed
**Metadata Update from @patrikp**: - Issue **un**tagged with: meeting - Issue tagged with: groomed
Owner

Today, at the releng weekly I decided to take and groom this, and perhaps open a discussion around it!

Today, at the releng weekly I decided to take and groom this, and perhaps open a discussion around it!
Member

There's also a cloud sig ticket with more relevant discussion: https://pagure.io/cloud-sig/issue/396

There's also a cloud sig ticket with more relevant discussion: https://pagure.io/cloud-sig/issue/396
Owner

Metadata Update from @jnsamyak:

  • Assignee reset
**Metadata Update from @jnsamyak**: - Assignee reset
Owner

How does the discussion looks like @jnsamyak?

How does the discussion looks like @jnsamyak?
jnsamyak removed their assignment 2026-04-30 09:25:24 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
10 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
releng/tickets#7520
No description provided.