[14:56] powersj: A couple of small (not at all urgent) PRs of mine that you could take a look at once you're around: https://github.com/canonical/cloud-init/pull/257 https://github.com/canonical/cloud-init/pull/263 [14:57] Odd_Bloke, ok will review post-standup === tds0 is now known as tds [15:47] Odd_Bloke, leave the merging to you [16:01] powersj: Thanks! [19:28] So if `write_files` is used in `/etc/maas/preseeds/*some*userdata` and then let's say a machine is instantiated using cloud_init which calls `write_files` will both `write_files` properly function? I'm thinking that one (user_data) will supercede that of `curtin` it seems. Can someone confirm or deny that observation? [19:33] https://discourse.maas.io/t/write-files-for-curtin-and-write-files-for-cloud-init-using-both-seems-to-conflict/1403 [19:35] cloaked1, hey thanks for the link - I think the best person to answer that isn't around this week unfortunately [19:35] ah man! [19:35] that sucks. [19:35] I kinda need to know... [19:36] ok, I'll figure something out. Thanks @powersj [19:37] powersj: do you happen to know if there's a recommended way to add lines to /etc/fstab? [19:39] cloaked1, if you are using cloud-config there is a mounts key [19:39] https://cloudinit.readthedocs.io/en/latest/topics/examples.html#adjust-mount-points-mounted [19:39] beautiful [19:39] thank you! [19:40] so does that have a curtin equal? [19:40] that's what I'm trying to figure out...sorry, I misspoke in my questin. [19:40] question [19:41] I believe modifying /etc/fstab is what curthooks are for in curtin [19:41] but rharper or smoser know much better than me :) [19:48] powers: thank you [19:48] er powersj:) [19:50] cloaked1: are you snafuxnj ? [19:50] it doesnt sem likely to me that user-data and curtin_userdata_custom would conflict. [19:51] yup [19:51] I am [19:51] one would be applied in install time frame [19:51] and one would be installed during first boot [19:52] hmm. OK. for some reason I seem to be observing that they conflict, but I could be wrong. I'll some code to the discourse question. Maybe someone can validate what we're doing. I may have something wrong in my write_files object. [19:53] for the most part , curtin is done after install [19:53] so , anything it was going to do (write_files) is done [19:54] user-data is like ec2 user data. [19:54] in that it goes to the system on first boot [19:55] the one overlap that i'm aware of in curtin and cloud-init is the networking bit. [19:55] curtin just passes the network config that it is given through to the system rather than rendering it itself. [19:55] then cloud-init will render on first boot [20:07] ok cool. I'm running some testing right now with the mount: option you provided. If that works then I'm not gonna press the write_files issue I'm observing for now. [20:07] otherwise, I'll need to press it because it will likely be the only way to achieve what I'm trying to achieve.