On Fri, Dec 5, 2014, at 08:39 PM, Brian C. Lane wrote: > On Fri, Dec 05, 2014 at 04:36:08PM -0500, Colin Walters wrote: > > The simplest way to implement this would be to simply dump the file into /var/tmp on the target system, and then have the cloud-init program execute it on boot. > > Can cloud-init be run from %post? It is chrooted into the target > filesystem. I looked at the code, and it doesn't today. It looks like this would be a lot of work. I'm not sure there are many advantages to that either versus having it just run on boot. And actually doing so would break features like the "phone-home" where the entire point is that they happen on boot. > I've been meaning to add some way for ssh keys to be included in the > kickstart. Yes, that's just one part of your point, but it will probably > show up in F22. Ok, that would make sense, and it would help lay the groundwork for solving bugs like the "must have password" issue. I scanned the cloud-config examples again and I guess there isn't a lot more that's really compelling. A more minor one is cloud-config has explicit and flexible sudo support, whereas with kickstart you only have user --name=foo --groups=wheel. (Though of course it's not hard to write into /etc/sudoers.d from %post). That said, even skipping the ssh key example, there'd be a lot of value in making it convenient to use from kickstart regardless - admins could take their existing cloud-init configurations and migrate to bare metal more easily. And it's fundamentally necessary for PXE-to-Live, because Anaconda/kickstart isn't involved on the user side there. (We're planning to use LMC on the server side of course). _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
