Cloud instance init scripts
da2ae0160a
The most major problem is that it no longer seems possible to define a user via the user-defined cloud-config data and have that user get an SSH authorized_keys correctly installed, when the SSH key comes from the Ec2 datasource. This is a regression from the version shipped in F17 AFAICS, and it's fixed upstream[1]. There are a number of other F18 related fixes upstream which would be valuable, including: - Improved hostname handling (doesn't truncate hostnames containing ".")[2] - Fedora locale, hostname and tz related fixes[3] - Fedora systemd, blkid and sysconfig fixes (rev 809)[3] [1] https://bugs.launchpad.net/cloud-init/+bug/1100920 [2] https://bugs.launchpad.net/heat/+bug/1164400 [3] http://bazaar.launchpad.net/~gpadgett/cloud-init/ovirt/revision/802 |
||
|---|---|---|
| .gitignore | ||
| cloud-init-0.7.1-noblock.patch | ||
| cloud-init-0.7.1-sudo-iterstr.patch | ||
| cloud-init-0.7.2-fedora.patch | ||
| cloud-init-fedora.cfg | ||
| cloud-init-README.fedora | ||
| cloud-init.spec | ||
| sources | ||