On 10 Jul 2010, at 02:10, Scott Moser wrote:
Hi Scott,
As Eric said, the 'user' only supports one initial user.
The 'user' is really only to avoid completely hard coding 'ubuntu'.
It
doensn't attempt to create a user or verify they have 'su' credentials
either.
I wouldn't be opposed to supporting multiple users there, but I'm
not sure
I understand why. The key that you put in there would then get
copied to
both accounts, basically making the user the same until some
subsequent
configuration change (which could also pull in some keys).
In my system when building on top of the Ubuntu image, I've created an
additional generic user (with su credentials) that have different
settings that
the ubuntu user, and that we use for generic tasks. I'd rather have
direct ssh
access to this account rather than ssh as ubuntu and then do su.
So probably a startup script as suggested by Eric is still the best
way to go at the
moment.
One fairly nice feature that the Lucid images have is the
'ssh-import-lp-id' tool. Using this, you can add your public ssh
keys to
a launchpad account, and then run a command (via 'runcmd' or other)
like:
sudo -Hu ${local_username} ssh-import-lp-id ${laundpad_user}
That will pull the launchpad ssh keys into the instance for that user.
Indeed nice tool! In our case, at the moment we stick with the public
keys
generated by EC2, on which we apply regular create/destroy rotations.
I'm glad you found cloud-init / cloud.cfg to be useful. Please let me
know any things you think could work better so we can improve it.
Sure. Is cloud-init/cloud.cfg ubuntu-specific or has it been taken up
by other
distribs?
Thanks,
Abel
Scott
__
Abel Ureta-Vidal, PhD MBA
Managing Director, Eagle Genomics Ltd
M: +44 7792 318503 | E: [email protected]
http://www.eaglegenomics.com
--
Ubuntu-cloud mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-cloud
