#396 Provide unversioned cloud images
Opened a year ago by eskultety. Modified a year ago

Other major distros provide an unversioned ("latest") symlink to their cloud images (true, they build those daily). Would it be possible to get such a symlink on fedora images? Even though you're not building them daily these days, that:
a) might change in the future
b) would help automation scripts getting always the latest build rather than scraping the http tree manually

A similar request with an affirmative response was made on CentOS Stream as well here:
https://www.spinics.net/lists/centos-devel/msg21318.html


Unlike CentOS, our image creation process is a bit more ossified. But we are working on retooling things. We can try to accommodate this as part of that.

Metadata Update from @ngompa:
- Issue tagged with: AWS, Azure, GCP, IBM, Kubernetes, OpenStack

a year ago

Metadata Update from @davdunc:
- Issue tagged with: meeting

a year ago

In my opinion, we should continue to maintain the major release, but then I don't have a problem with having the "modified date" or "creation_date" in there.

A "fedora latest" designation doesn't seem consistent with our release process
it seems like that would be like saying CentOS/Latest and getting 9 the next time you want to deploy when you are using 8.
Also, are we making enough images to have a "latest"?
right now, I don't think so.

Metadata Update from @davdunc:
- Issue assigned to davdunc

a year ago

Is this something we can maintain through the current methods that most public clouds provide? Similar to the naming conventions in GCP or AMI Public Parameters for AWS?

In my opinion, we should continue to maintain the major release, but then I don't have a problem with having the "modified date" or "creation_date" in there.

A "fedora latest" designation doesn't seem consistent with our release process
it seems like that would be like saying CentOS/Latest and getting 9 the next time you want to deploy when you are using 8.

This is an incorrect assumption. Why would you consider "latest" pointing to CentOS Stream 9 only? Both images have their respective URI path. Same goes for Fedora, this request is not about getting "fedora-latest", but getting a "latest" symlink for images of all supported Fedoras, IOW versions not EOL'ed, so you'd have fedora-36-latest, fedora-37-latest, etc.

Also, are we making enough images to have a "latest"?
right now, I don't think so.

The point isn't whether you're making enough images or not, but whether getting the latest image build of a given fedora version can be automated, because right now, it can't be without web scraping and comparing numbers or release dates - having a plain symlink named "fedora-<N>-latest while keeping your existing naming scheme will immediately alleviate this problem.

An easy way to fix that would be to have some kind of text or json file that gives you that information for a tool to parse as an API. That would also avoid the problems related to having symlinks on a server that needs to be mirrored.

An easy way to fix that would be to have some kind of text or json file that gives you that information for a tool to parse as an API. That would also avoid the problems related to having symlinks on a server that needs to be mirrored.

Well, technically yes, this would unarguably be a solution to the problem I described. Unfortunately for us, it wouldn't help as in our case we're relying on this information to come from libosinfo's osinfo database where this vendor OS information is stored statically in XML files (https://gitlab.com/libosinfo/osinfo-db/-/tree/main/data/os), so again, while I agree an API would likely help most, ours would not be the case.

Metadata Update from @ngompa:
- Issue tagged with: OCI

a year ago

Login to comment on this ticket.

Metadata
Boards 1
Meeting Topics Board Status: Actionable