On 2014-07-14 14:09, Colin Walters wrote:
[ Posting here for increased visibility ] Right now, cloud-init is only installed in the cloud images, so it's OK if it enables itself by default. However, for future Atomic work, we'll likely only have one tree that's also running on bare metal, and that will include cloud-init. This change should be safe because the Fedora Cloud kickstart in spin-kickstarts uses services --enabled=cloud-init. --- cloud-init.spec | 22 ++-------------------- 1 file changed, 2 insertions(+), 20 deletions(-)
This would be a great thing to add to the bug report for this issue [1] as well.
If the kickstart explicitly enables cloud-init then yes, let's drop the self-enabling bits. We should really be using per-product service presets for that instead; I suppose I should work on a policy for that [2] now that it is finally clear which packages those belong in. 8^)
Please remove .atomic from the release tag. The spec file will also need to use %systemd_post and %systemd_postun in addition to %systemd_preun if we're to follow the packaging guidelines [3].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=850058 [2] https://fedorahosted.org/fesco/ticket/945 [3] https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd -- Garrett Holmstrom _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
