In the 20091011 batch of AMIs published on Alestic.com I switched to
Amazon's kernel modules instead of building my own from source.
Yep, just be aware that reverting to the previous AMI downgrades the
kernel to one which includes the security hole where users on the system
can gain root.
At the moment we're stuck with two kernel choices from Amazon for
2.6.21, both of which have problems (XFS vs. security).
If your application has any chance of running on Karmic, then I
recommend trying out the Beta AMIs from Canonical which run on 2.6.31.
There has been a little movement on Hardy from Canonical, but I don't
expect a lot to get done there in the short term since Karmic is
launching in a couple weeks.
I have also heard some folks having success running the Alestic.com
Jaunty on the 2.6.27 kernel from Canonical, but that kernel was built a
while back and I don't know how reliable or secure it is.
> Thanks to you both for this thread, and related traffic.
> I'm preparing to try the canonical karmic image -- canonical-testing-
> eu/karmic-i386-20090929.manifest.xml -- for use in EU-west, and I'm
> doing pre-tests on the AWS Management Console.
> When I try to run image ami-404f6434 that requires kernel
> aki-6e4f641a, I get
> "Nonexistent default AKI 'aki-6e4f641a' for AMI 'ami-404f6434'."
> But running in us-east the counterpart ami-145ebe7d that uses
> aki-841efeed there is no problem.
The above is an error, probably on my part. The error is correctly
stating that, while aki-6e4f641a is referenced by ami-404f6434, there is
no such registered kernel. I've removed the AMI in question to remove
any confusion. There will probably be further cleanup that needs to be
done at some point in the near future.
I've been getting automated publishing of our daily builds working over
the last 3 weeks or so.
We're fairly well set now. Automated daily build output is published to
'ubuntu-images-testing-us' and 'ubuntu-images-testing-eu' at the same
time. You can see builds named such as:
There is more information on the publishing policy at
https://wiki.ubuntu.com/UEC/Images/NamingConvention . The above represent
our RC candidate builds. If successful testing, they'll be promoted this
thursday (10/22) to the 'ubuntu-images-milestone-eu' bucket as:
On promotion, their AMI ids and name will change, but their content will
not. The new AMIs will be released as RC, and will not be removed. The
nightly AMI's further above *will* be removed.
> And am I wasting my time trying bleeding-edge tests in the EU region?
I surely hope not. I apologize for the snafu that you've seen and the
lack of ext4 support in the karmic kernel. I can only promise that we're
getting better, and the NamingConvention doc above should be consistent
from here out.
Also, please see https://wiki.ubuntu.com/UEC/Images/RefreshPolicy for
information about post-release refreshing of images.
Regarding the ext4 support in karmic, that bug 428692 is set for 'karmic
updates' , so it is expected that at some point soon after release we will
get ext4 support in AMIs.