ani | Any feedback on this PR? https://github.com/canonical/cloud-init/pull/4395 | 11:03 |
---|---|---|
-ubottu:#cloud-init- Pull 4395 in canonical/cloud-init "net: fix ipv6_dhcpv6_stateful/stateless/slaac configuration for rhel" [Open] | 11:03 | |
Schrostfutz | Hi, I'm trying to figure out how to have a cloud-config that simply defines an authorized ssh key for the root user, and does not create additional users. Is there a way to do this? I have trouble finding the proper documentation | 11:43 |
meena | ani: i reckon most committers are currently held up in SRU. | 12:15 |
meena | Schrostfutz: you could change the default_user in /etc/cloud/cloud.cfg — or possibly in user-data, too, and then just use ssh_authorized_key: in user-data | 12:22 |
toabctl | how does cloud-init netplan config passthrough work? I have a cloud-init config (see https://paste.ubuntu.com/p/zj2CSchSTv/) which I use to generate a config-drive seed (cloud-localds cloud-init-config-node1.img cloud-init-config-node1.yaml) but after booting the node with that, the network config is not in /etc/netplan/50-cloud-init.yaml (but setting the password worked so the config in general worked) | 12:25 |
toabctl | that's on Ubuntu 22.04 ^^ | 12:25 |
meena | toabctl: what do the logs say? | 12:26 |
meena | (i ask, instead of explaining how cloud-init netplan config pass-through works, because i have no idea.) | 12:27 |
meena | (i mostly work on BSDs) | 12:27 |
Schrostfutz | meena: Thanks! I'll look into that. | 12:27 |
toabctl | looks like userdata can not override network config?! | 12:35 |
toabctl | meena, the logs are here: https://paste.ubuntu.com/p/dp9yfzjggb/ | 12:37 |
meena | toabctl: yes, you have to provide network config seperately | 12:37 |
toabctl | can I do that with a nocloud datasource? | 12:38 |
meena | toabctl: yes. | 12:38 |
toabctl | ah. "cloud-localds -N". I'll try that. | 12:39 |
meena | cool | 12:40 |
toabctl | meena, works. thanks! | 12:46 |
meena | toabctl: yay! \o/ | 12:46 |
blackboxsw | toabctl: netplan passthough just means cloud-init sees network "version: 2" from the datasource and knows if it is on a system with netplan installed. In that case, it does not attempt to convert that dictionary into cloud-init's internal NetworkState first for processing. It just writes the version: 2 config directly to /etc/netplan/50-cloud-init.yaml | 14:12 |
blackboxsw | and glad you found the cloudlocalds --network-config option. NoCloud datasource just looks for a yaml file network-config in the same directory as user-data and meta-data files | 14:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!