Apologies for the top post. I am stuck in Outlook:
I love the idea of having our own DB for managing this. Is this something similar to what
Scott Moser did for the Ubuntu Finder with a JSON stream? Do we need to gather it or
should we report it back in deploying the images?
On 2/9/23, 3:31 PM, "Colin Walters" <walters(a)verbum.org
<mailto:walters@verbum.org>> wrote:
On Tue, Jan 31, 2023, at 9:10 PM, Major Hayden wrote:
My team at Red Hat came up with the idea of a locator service that
would gather data from upstream locations (AWS, Azure, GCP, and
others), compile the image data into a common schema, and make it
available for API calls and a web frontend.
I hope we could also share a common model with CentOS Stream, which doesn't seem to
have any answer at all today?
CoreOS already does something like this and offers a JSON[1] file with
a standardized schema that makes it easier to find the current released
in various locations.
Yep, would love to think about how we can share code/approaches here with other Fedora
images!
_______________________________________________
cloud mailing list -- cloud(a)lists.fedoraproject.org
<mailto:cloud@lists.fedoraproject.org>
To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
<mailto:cloud-leave@lists.fedoraproject.org>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<
https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
<
https://fedoraproject.org/wiki/Mailing_list_guidelines>
List Archives:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
<mailto:cloud@lists.fedoraproject.org>
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
<
https://pagure.io/fedora-infrastructure/new_issue>