On Fri, Nov 9, 2012 at 3:20 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Nov 09, 2012 at 11:28:49AM -0500, Matthew Miller wrote:
On Fri, Nov 09, 2012 at 11:16:21AM -0500, Matthew Miller wrote:
cloud-init pulls in some, um, not exactly minimal stuff. python-cheetah? (which then brings in, for example, freetype...)
and python-imaging, and python-pygments.
All told, cloud-init and dependencies add 50MB to the on-disk size of the current F18 cloud image I'm working on.
Graphics and templating languages. Plus xfsprogs. And a large amount of selinux stuff. And libcgroup, which despite its name is a collection of (somewhat klunky) utilities for something actually handled better by systemd.
Cloud-init is nifty, but this seems like a kitchen sink of random stuff. Opinions, everyone? Should this go in the EC2 cloud image? Should it go in the downloadable one? Should we offer options? Should we have something more lightweight which just pulls in ssh keys?
I could see an argument for separating some of the cloud-init plugins into subpackages. Of course, then someone is going to request that cloud-init be executed in such a way that it can install packages and then reread its configuration & load newly installed plugins. That'll be fun. :-)