Provide stable names for images #7520
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
10 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#7520
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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/
Metadata Update from @mohanboddu:
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?
@till What is the use case here?
One of the use case we heard is:
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,
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?)
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:
@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.
Metadata Update from @cverna:
@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
Metadata Update from @patrikp:
On second thought let's keep this open for now.
Metadata Update from @patrikp:
Metadata Update from @patrikp:
Today, at the releng weekly I decided to take and groom this, and perhaps open a discussion around it!
There's also a cloud sig ticket with more relevant discussion: https://pagure.io/cloud-sig/issue/396
Metadata Update from @jnsamyak:
How does the discussion looks like @jnsamyak?