Re: non-standard TCP tunings in EC2 images
>>>>> "Lucas" == Lucas Nussbaum <email@example.com> writes:
Lucas> by this. One could argue that those test suites are a bit
Lucas> fragile, but on the other hand, I would expect an image
Lucas> labelled as "Official Debian" on
Lucas> https://wiki.debian.org/Cloud/AmazonEC2Image to not differ
Lucas> from default Debian configuration in subtle ways like this.
I'm not sure that's true.
We had some interesting discussion of this in the cloud BOF, at debconf.
we had strong agreement there (at least as I read it) that the official
images must include software only from Debian main.
There were people pushing for the idea that it have the entirely
standard config as well, although I and some others pointed out that
isn't going to work.
The most obvious issue is that you need to establish the appropriate
cloud-init data sources for the platform in question unless you want to
introduce significant boot delays.
Also, some folks who've worked with the cloud providers pointed out that
unless people can produce images that work well with their cloud,
they're not going to use the official images.
Tuning things like networking and disk performance to be right for a
given cloud seems like a discussion worth having, and at least in my
mind "debian official," doesn't obviously say no.