On Tue, Jan 31, 2017 at 1:55 AM, <pub@xxxxxxxxxxxxxx> wrote: > Greetings! Can someone please explain the process for publishing Fedora AMI's to AWS? > > I see the "official" Fedora Cloud page has 'Click to launch' base images for AWS here: https://alt.fedoraproject.org/cloud/ > > However, if I click to launch the GP2 HVM AMIs, I see the us-west-2 (Oregon) AMI listed is ami-3dea475d, which was published 2016-11-15. > > Do new AMI's get published on a particular cadence? If so, how/when does that happen? > > If I search for AMI's from the Fedora account ID (125523088429), I can see AMI's as recent as January 29th. > https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#Images:visibility=public-images;ownerAlias=125523088429;search=Fedora-Cloud-Base-25;creationDate=%3E2017-01-01T00:00-07:00;sort=name > > Are all images published by the Fedora account suitable/recommended for use? > > I'm assuming that the newest AMI's would have all updates and patches up to date as of the publish date, is this correct? > > What is the retention policy on AMI's? Can we count on a particular AMI (eg; ami-d27bc3b2 ) being available and not disappearing for a specific amount of time? Regarding the deletion of the AMIs, a policy is in place[1] - Delete the pre-release AMI(s) after the final release. - Delete the nightly build AMI(s) after 5 days of the build. The script will be deployed in next few days. For now the nightly AMIs are deleted manually periodically. So, the AMIs to consider should be the released AMIs till EOL. We are yet to decide on the policy for the deletion of the released AMIs but for now the it can be considered that they will be available till EOL. [1] https://pagure.io/atomic-wg/issue/99 -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization! _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
