In the previous post, I discussed what is fedimg and how it works currently. In this post, I plan to explain the issue in the current uploading process of the AMIs and how we plan to fix it. What’s the problem? fedimg boots an utility instance using the RHEL AMI configured for that region. The problem with this design is that while adding a new region we need to look for the appropriate RHEL AMI in the newer region first....
What is fedimg? Fedimg is a Python-powered service that uploads the Fedora Cloud images on various Cloud providers. such as Amazon Web Services (AWS) . How does it currently work? Fedimg listens to fedmsg for nightly as well as the production compose builds messages. On receiving a new message, the FedimgConsumer triggers the upload process. fedimg uses fedfind to extract the metadata for the compose from where it get’s the URL for the compressed raw image files....
Fedimg is a Python-powered service which is built to make Fedora-Cloud images available on popular cloud providers, such as Amazon Web Services (AWS). The plans are to support more cloud providers such as Rackspace, Google Compute Engine. Fedimg listens for the messages from Fedmsg for the Koji image builds. Plan of work Add scripts to remove old AMIs we have uploaded (https://github.com/fedora-infra/fedimg/issues/37) Storing the AMIs are costing us lot....
Fedimg is a Python-powered service which is built to make Fedora-Cloud images available on popular cloud providers, such as Amazon Web Services (AWS). The plans are to support more cloud providers such as Rackspace, Google Compute Engine. Fedimg listens for the messages from Fedmsg for the Koji image builds. Plan of work Add scripts to remove old AMIs we have uploaded (https://github.com/fedora-infra/fedimg/issues/37) Storing the AMIs are costing us lot....