Hi, On Donnerstag, 6. Dezember 2012, Charles Plessy wrote: > the list can be quite extensive (like resizing the file system when the > image is booted on an larger volume, etc.),
right, thats a nice (optional) feature. > but at the very minimum, I > think that an image needs a system to make sure that one can log in with a > keypair where the private part is available to the machine via a > predetermined URL (that the cloud system makes private to the running > instance). where do you want to provide the private keys? (I dont get it, from a general perspective...) Can you please explain? > In Ubuntu's cloud-init package, there is also a small infrastructure to > update PV-GRUB when installing a new kernel. That would be also quite > useful, see http://bugs.debian.org/672104. I'm not affected by this at all. Grub2 works just fine here. > The following is in my opinion more the job of the image preparation script > or > > preseed configuration: > > b.) create "admin" user with sudo > > c.) disable root login I thought cloud-init is such an image preparation script, or at least it includes it. Does it? > Note that it is strongly discouraged to enable password login for the > default account. this leaves the problem how to distribute the generated private keys... cheers, Holger -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
