|
=== harlowja_ is now known as harlowja_away |
|
=== shardy_z is now known as shardy |
|
=== harlowja_away is now known as harlowja_ |
|
[19:11] <xenol> hi, I am trying to setup cloud-init and I would like to setup root password, which is provided by SmartOS datasource as root_pw metadata. However, I do see anything in the source that sets up the root password |
|
[19:12] <xenol> is there a way how to achieve this? |
|
=== ijw__ is now known as ijw_ |
|
[20:26] <tennis> smoser: Trying to set an id other than ubuntu to be the system default. I notice that cloud-init creates a file called /etc/sudoers.d/90-cloud-init-users. Can cloud-init generate this file with my alternative user id in it, or do I have to manually zap it like what is described here: http://alestic.com/2014/01/ec2-change-username |
|
[21:08] <xenol> can cloud-init set root password? |
|
[21:25] <smoser> if you just define it in the users, it might not know any better. |
|
[21:25] <smoser> tennis, you just provide the user you want in user-data |
|
[21:25] <smoser> yeah, as that blog post says. |
|
[21:26] <smoser> xenol, similar answer. |
|
[21:26] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-user-groups.txt |
|
[21:26] <smoser> you might be able to do: |
|
[21:26] <smoser> users: |
|
[21:26] <smoser> - default |
|
[21:26] <smoser> - name: root |
|
[21:26] <smoser> passwd: foo |
|
[21:27] <xenol> smoser: I have password available by the metadata service and I would like to get it from there if possible |
|
[21:27] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt#L565 |
|
[21:27] <smoser> so cloud-init probably can't direclyt do it like that. |
|
[21:27] <smoser> i'm not *opposed* to a feature ot pull it from the openstack metadata service |
|
[21:27] <smoser> but really thats a regression |
|
[21:27] <smoser> use ssh public keys |
|
[21:37] <xenol> so, I have a default cloud.cfg, which is slightly modified to suit my needs. If I want to add users, shoudl I move cloud.cfg contents with "users" block into metadata service? |
|
[21:39] <smoser> you mean to user-data |
|
[21:40] <xenol> I have defined datasource_list in my cloud.cfg. I suppose that should stay there and the rest moved to user-data? |
|
[21:42] <smoser> yeah,, generally thats more dynamic. although user can override what is in cloud.cfg through user-data |
|
[21:43] <tennis> smoser: Thanks! Yeah, I have tiny script (like the blog post) which I run just before a reboot. |
|
[21:45] <tennis> tennis: testing |
|
[22:31] <xenol> smoser: the passwd needs to be a hash, right? |
|
[22:42] <kwadronaut> xenol: i agree with smoser, use ssh public keys, generate passwords. |
|
[22:45] <xenol> I am generating them creating virtual machines (I'm not giving the user the ability to input his password). I just to this because not every user has a SSH key and expects password |
|
[22:45] <xenol> This way I am able to offer both solutions |
|
[23:07] <tennis> smoser: re the usermod to change the default user. How can that work for the default id if it is being called by the (current) default? |
|
|