Hi folks,
I know that there was work afoot to release the F16 Beta AMi on the same day as the rest of F16 Beta.
Is that something that is good to go? And if it's not, what was the thing that blocked or held up the release of the Beta? The last AMI that I can see owned by aws@fedoraproject.org is 125523088429/Fedora-16-Beta-ec2-20110923-x86_64-sda -- I played around with that AMI and while I think there were a few cloud-init issues, it worked well enough to get the authorized_keys in the right place.
I'd also recommend that it become part of the schedule and workflow to update the get.fedoraproject.org page with a link to the AMI IDs, as well as the EC2 Images wiki page itself, with those AMI IDs. Not only for Alpha/Beta, but definitely for GA.
Maybe even add a blurb to the release announcement when it talks about the different ways to consume Fedora.
To me, those are the sorts of actions that begin to put Fedora on EC2 at a similar level to some of the other architectures, etc.
Good think Fedora's PM and RelEng are on this list :)
--Max
On Oct 4, 2011 12:59 PM, "Max Spevack" mspevack@fedoraproject.org wrote:
Hi folks,
I know that there was work afoot to release the F16 Beta AMi on the same day as the rest of F16 Beta.
Is that something that is good to go? And if it's not, what was the thing that blocked or held up the release of the Beta? The last AMI that I can see owned by aws@fedoraproject.org is 125523088429/Fedora-16-Beta-ec2-20110923-x86_64-sda -- I played around with that AMI and while I think there were a few cloud-init issues, it worked well enough to get the authorized_keys in the right place.
I'd also recommend that it become part of the schedule and workflow to update the get.fedoraproject.org page with a link to the AMI IDs, as well as the EC2 Images wiki page itself, with those AMI IDs. Not only for Alpha/Beta, but definitely for GA.
Maybe even add a blurb to the release announcement when it talks about the different ways to consume Fedora.
To me, those are the sorts of actions that begin to put Fedora on EC2 at a similar level to some of the other architectures, etc.
Good think Fedora's PM and RelEng are on this list :)
And the person who writes the release announcements, right? Heh.
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.
--Max _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On 2011-10-04 12:06, Robyn Bergeron wrote:
On Oct 4, 2011 12:59 PM, "Max Spevack" <mspevack@fedoraproject.org mailto:mspevack@fedoraproject.org> wrote:
Hi folks,
I know that there was work afoot to release the F16 Beta AMi on the same day as the rest of F16 Beta.
Is that something that is good to go? And if it's not, what was the thing that blocked or held up the release of the Beta? The last AMI that I can see owned by aws@fedoraproject.org
mailto:aws@fedoraproject.org is
125523088429/Fedora-16-Beta-ec2-20110923-x86_64-sda -- I played around with that AMI and while I think there were a few cloud-init issues, it worked well enough to get the authorized_keys in the right place.
I'd also recommend that it become part of the schedule and workflow to update the get.fedoraproject.org http://get.fedoraproject.org page
with a link to the AMI IDs, as
well as the EC2 Images wiki page itself, with those AMI IDs. Not only for Alpha/Beta, but definitely for GA.
Maybe even add a blurb to the release announcement when it talks about the different ways to consume Fedora.
To me, those are the sorts of actions that begin to put Fedora on EC2 at a similar level to some of the other architectures, etc.
Good think Fedora's PM and RelEng are on this list :)
And the person who writes the release announcements, right? Heh.
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.
But I do. :) cloud-init is currently doing things that make SElinux unhappy in such a way that one cannot log in. Dennis and I are working on the problem.
On Tuesday, October 04, 2011 10:14:18 PM Garrett Holmstrom wrote:
On 2011-10-04 12:06, Robyn Bergeron wrote:
On Oct 4, 2011 12:59 PM, "Max Spevack" <mspevack@fedoraproject.org
mailto:mspevack@fedoraproject.org> wrote:
Hi folks,
I know that there was work afoot to release the F16 Beta AMi on the same day as the rest of F16 Beta.
Is that something that is good to go? And if it's not, what was the thing that blocked or held up the release of the Beta? The last AMI that I can see owned by aws@fedoraproject.org
mailto:aws@fedoraproject.org is
125523088429/Fedora-16-Beta-ec2-20110923-x86_64-sda -- I played around with that AMI and while I think there were a few cloud-init issues, it worked well enough to get the authorized_keys in the right place.
I'd also recommend that it become part of the schedule and workflow to update the get.fedoraproject.org http://get.fedoraproject.org page
with a link to the AMI IDs, as
well as the EC2 Images wiki page itself, with those AMI IDs. Not only for Alpha/Beta, but definitely for GA.
Maybe even add a blurb to the release announcement when it talks about the different ways to consume Fedora.
To me, those are the sorts of actions that begin to put Fedora on EC2 at a similar level to some of the other architectures, etc.
Good think Fedora's PM and RelEng are on this list :)
And the person who writes the release announcements, right? Heh.
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.
But I do. :) cloud-init is currently doing things that make SElinux unhappy in such a way that one cannot log in. Dennis and I are working on the problem.
and we sorted it out, so far i have ami-7f5a063a
On 2011-10-04 20:14, Garrett Holmstrom wrote:
On 2011-10-04 12:06, Robyn Bergeron wrote:
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.
But I do. :) cloud-init is currently doing things that make SElinux unhappy in such a way that one cannot log in. Dennis and I are working on the problem.
[Insert commentary about replying to oneself here] 8^)
I just tested a small fix by hand that appears to resolve the login issue. When I get a chance I will spin a new cloud-init package that contains it in the hopes that we can get a working image out of koji.
An unrelated issue I noticed is that the images that koji generates seem to contain no man pages, and even installing packages that are supposed to contain them does not make them appear on the system. Any ideas?
root@i-8d7dd3ca ~ # find /usr/share/man -type f | wc -l 0 root@i-8d7dd3ca ~ # yum -y install man-pages >/dev/null root@i-8d7dd3ca ~ # find /usr/share/man -type f | wc -l 0