On Mon, May 27, 2013 at 12:49:22PM +0200, Vitaly Kuznetsov wrote:
1) There is no NETWORKING_IPV6=no setting in /etc/sysconfig/network
there is still no ipv6 in EC2)
There might be in OpenStack environments. Are there negative consequences
2) There is no 'PasswordAuthentication no' setting in
/etc/ssh/sshd_config (it was there for a long time)
Hmmm; that was dropped from the kickstart from F15 to F16, with the comment
"let cloud-init setup sshd". Can we reverify this after the cloud-init
SELinux bug is fixed?
3) We have slightly different package set:
At least partly intentional. Reordering the list a bit and commenting...
Added to @core comps.
Ditto; also, good to have for configuration. I could see removing this if
people thing it's best.
First of these keeps the image portable (next cut will be to have a
"dracut-cloud" module to replace "nohostonly"). The second prevents
rescue image from being created to save space and because at least in EC2 it
can't really be used anyway.
cloud-init deps. There are more, many of which seem equally unfortunate in a
pulled in by krb5-libs as of 1.11.1-4.
'newt', 'newt-python', 'p11-kit-trust',
Pulled in by authconfig; see above. Altogether, removing authconfig would
save 6.8 mb installed space.
Pulled in by extlinux; https://bugzilla.redhat.com/show_bug.cgi?id=928055
systemd pulls this in via gnutls, which is used _only_ for libmicrohttpd,
which in turn is used only by the journald gateway, which is a) off by
default and b) not ever supposed to be turned on except for developers. I
have an open request to make that a subpackage at the very least, but the
systemd packagers don't seem interested. See
On purpose, so we have a lightweight bootloader for non pv-grub cloud
['dbus-glib', 'dbus-python', 'ebtables', 'file',
'gobject-introspection', 'hwdata', 'libdb4',
'psmisc', 'pygobject3-base', 'python-decorator',
'python-slip', 'python-slip-dbus', 'tmpwatch']
I think this is all intentional. tmpwatch is now handled by systemd. Anyone
feel tha tany of these really should be there?
4) cloud-init is not handling userdata scripts any more. I've
simple scripts (like 'touch /test_file_1'), multipart/mixed, ... -
nothing works for me now. I can't find any error in
/var/log/cloud-init.log, I can see my scripts in
/var/lib/cloud/instance/scripts/ (only if I use multipart/mixed) but
they never were executed. Can anyone shed some light into this?
I _think_ this is probably just the above-mentioned bug. Retest after that's
4+) I can also see cloud-init fails to set hostname:
And this _is_ the above-mentioned bug. :)
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>