On Tue, Jul 15, 2014, at 02:52 AM, Garrett Holmstrom wrote:
> This would be a great thing to add to the bug report for this issue [1]
> as well.
Done, patch attached.
> If the kickstart explicitly enables cloud-init then yes, let's drop the
> self-enabling bits. We should really be using per-
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 th
On Mon, Jul 14, 2014 at 05:09:34PM -0400, Colin Walters wrote:
> This change should be safe because the Fedora Cloud kickstart in
> spin-kickstarts uses services --enabled=cloud-init.
+1 -- and in the future, we should be using systemd presets in the cloud
image.
--
Matthew Miller
Fedora Proje
n Walters
Date: Mon, 14 Jul 2014 16:55:33 -0400
Subject: [PATCH] Don't enable by default
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 r
