On 02/08/14 at 09:51 +0800, Paul Wise wrote: > On Fri, Aug 1, 2014 at 10:31 PM, Lucas Nussbaum wrote: > > > FAI and Kickstart rely on an installation process (even if not > > debian-installer's): packages are extracted, installed and configured. > > Kadeploy and CloneZilla rely on cloning: you install and configure one > > system first, then create an image from it, and copy this image to the > > other systems. > > One downside of cloning Debian based images is that debootstrap, dpkg > and package maintainer scripts leave system-specific files (like > openssh private keys, systemd machine ids, dbus machine ids etc) in > the resulting image and you have to workaround that after generating > the image. > > How does Kadeploy currently deal with this sort of issue?
There's a post-installation phase where machine-specific files are copied to the cloned system. > Perhaps we need to merge the Debian cloud/live team's handling of this > issue and put that in a package that Kadeploy can use... Yes, or at least the Kadeploy developers should take a look at what is done there, to make sure that the same things are covered on both sides. Lucas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140802052224.ga29...@xanadu.blop.info
