<p><br>
On Oct 4, 2011 12:59 PM, "Max Spevack" <<a href="mailto:mspevack@fedoraproject.org">mspevack@fedoraproject.org</a>> wrote:<br>
><br>
> Hi folks,<br>
><br>
> I know that there was work afoot to release the F16 Beta AMi on the same<br>
> day as the rest of F16 Beta.<br>
><br>
> Is that something that is good to go? And if it's not, what was the<br>
> thing that blocked or held up the release of the Beta? The last AMI<br>
> that I can see owned by <a href="mailto:aws@fedoraproject.org">aws@fedoraproject.org</a> is<br>
> 125523088429/Fedora-16-Beta-ec2-20110923-x86_64-sda -- I played around<br>
> with that AMI and while I think there were a few cloud-init issues, it<br>
> worked well enough to get the authorized_keys in the right place.<br>
><br>
> I'd also recommend that it become part of the schedule and workflow to<br>
> update the <a href="http://get.fedoraproject.org">get.fedoraproject.org</a> page with a link to the AMI IDs, as<br>
> well as the EC2 Images wiki page itself, with those AMI IDs. Not only<br>
> for Alpha/Beta, but definitely for GA.<br>
><br>
> Maybe even add a blurb to the release announcement when it talks about<br>
> the different ways to consume Fedora.<br>
><br>
> To me, those are the sorts of actions that begin to put Fedora on EC2 at<br>
> a similar level to some of the other architectures, etc.<br>
><br>
> Good think Fedora's PM and RelEng are on this list :)</p>
<p>And the person who writes the release announcements, right? Heh.</p>
<p>I have no idea what the status is. Dennis mentioned the other day that the latest thing he had wasn't working (while we were in milan) - beyond that, without a ticket or etc. i have no idea. </p>
<p>><br>
> --Max<br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/cloud">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
</p>