Odd_Bloke | smoser: We have a CloudStack partner who would like passwords to be checked and possibly reset on each boot. | 12:02 |
---|---|---|
Odd_Bloke | smoser: The CloudStack data source does the password fetching etc.; will it be called on each boot? | 12:02 |
smatzek | Odd_Bloke: doesn't datasource search happen on every boot? I think it does and get_data is called on each. Cloud-init needs to do the datasource search to get the data to get the instance-id before it can check that vs the id on disk an no-op. | 12:19 |
Odd_Bloke | True. | 12:21 |
Odd_Bloke | And we also do filesystem checking at each boot for Azure. | 12:21 |
Odd_Bloke | smatzek: Thanks. :) | 12:27 |
Odd_Bloke | smoser: So I think we'd need to modify the CloudStack DS to enable cc_set_passwords when it detected a new password. Does that sounds right? | 12:44 |
smoser | Odd_Bloke, the cloudstatck datasource is probably read each boot, but probably setting of passwords does not happen. | 13:16 |
smoser | but cc_set_passwords sets for all accounts. | 13:16 |
smoser | so, yeah, you coudl do that. i guess. | 13:17 |
smoser | but it'd be a seemingly likely failure path if they re-set the root password and kept their old known values for other users | 13:17 |
smoser | and then cloud-init re-set those users passwords. | 13:17 |
Odd_Bloke | smoser: Blargh, this sounds painful. | 13:27 |
smoser | Odd_Bloke, we want to fix this in 2.0 with "agent" like thing that can set password for the expected user in an api like way. | 13:35 |
Odd_Bloke | Yeah. | 13:38 |
=== shardy is now known as shardy_afk | ||
openstackgerrit | Merged stackforge/cloud-init: Configure basic logging, and make it possible to log to console. https://review.openstack.org/220536 | 18:36 |
openstackgerrit | Merged stackforge/cloud-init: Use a single source for version information. https://review.openstack.org/220543 | 18:37 |
=== shardy_afk is now known as shardy | ||
=== cpaelzer_ is now known as cpaelzer |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!