=== tds0 is now known as tds
[05:45] <ongy> Hi, quick question (Assuming runcmd: thingy in lxd config uses cloud-init): do the runcmds get executed on each boot/container start, or only once in some init phase during firstboot?
[05:46] <ongy> hm, looking into the FAQ there's some boot-done filemark, so I guess the init-phase
[14:07] <Odd_Bloke> ongy: runcmd runs once per instance (i.e. first boot), yeah.  If you want to run a script every boot, you can put it in /var/lib/cloud/scripts/per-boot/ (and ensure it's executable).
[14:08] <Odd_Bloke> (And you could do that with write_files: https://cloudinit.readthedocs.io/en/latest/topics/modules.html#write-files)
[14:33] <ongy> ok, thanks
[14:33] <ongy> ahh, the per-boot might help as well at some point
[14:33] <ongy> My main issue was the pulse lxd profile not working if I attach afterwards, because the sed that patches the config didn't trigger
=== waxfire8 is now known as waxfire
[20:01] <blackboxsw> Odd_Bloke: one question for you before I can wrap up ec2 multi-nic/ip support https://github.com/canonical/cloud-init/pull/114#discussion_r393921933
[20:02] <blackboxsw> think I'll have the rest of the review comments addressed
[20:02] <blackboxsw> and will push once we resolve the above
[22:21] <blackboxsw> Thanks again for the review Odd_Bloke I've addressed all comments and force pushed https://github.com/canonical/cloud-init/pull/114. Just ran networking tests on upgrade path, dual nic and single nic configs to show route-metric is only presented on multi-nic VMs. It's ready for review tomorrow