[08:53] <gjolly> hi! Is there a way of writing the metadata/userdata/network-config directly in a cloud-image/live-image without using an extra CIDATA partition with NoCloud? I tried placing the files in /var/lib/cloud/seed/nocloud (before first boot) and it seems to work but I don't know if this is a supported  feature or a hack.
[15:55] <blackboxsw> gjolly: sorry for the big delay here. you are correct and adding /var/lib/cloud/seed/nocloud or /var/lib/cloud/seed/nocloud-net/meta-data|user-data|network-config files is supported for image creation and not a hack
[15:57] <gjolly> blackboxsw: no worries, thanks! It's good news. Is that documented somewhere? or is it missing from here: https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[15:59] <blackboxsw> it is supported to allow any image creator to override other datasource detection avenues.  And NoCloud will always be detected first if present. that nocloud content can come from those seed files you suggested, or even a URL that you provide via either kernel cmdline  or smbios serial number in qemu https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html#nocloud
[16:00] <blackboxsw> gjolly: right that link is correct. it's worth a doc update for representing that 
[16:00] <blackboxsw> gjolly: yes I think that is a gap, and the default seed directory should be represented in docs and it isn't
[16:02] <blackboxsw> BTW the /var/lib/cloud/seed/nocloud-net  dir is what LXD uses on anything earlier than Jammy
[16:03] <blackboxsw> so if you are looking to modify test images and using LXD be wary that launching those images may end up overwriting your tests
[16:04] <blackboxsw> some context on seed dirs and lxd https://blackboxsw.github.io/2021-11-08-customize-lxd-metadata-templates/
[16:05] <minimal> blackboxsw: I'd looked into this a while. For url-based seeding it does *not* request the network-config url (as networking is already up via DHCP in order to be able to fetch URLs) - however I did workaround this in the past by putting network config inside the meta-data file fetched
[16:27] <blackboxsw> falcojr: I've provided a manual for ubuntu/bionic for the SRU  since new-upstream-snapshot isn't working yet when refresh patches are involved
[16:28] <blackboxsw> *manual diff*
[16:28] <blackboxsw> +1 thanks for the reminder minimal 
[16:28] <blackboxsw> reminder and workaround
[16:34] <minimal> blackboxsw: yeah I hit that as I was trying to using cloud-init with machines that needed to configure a VLAN (either for the initial DHCP to be able to reach the seed urls or to configure an initial static network config before requesting seed urls)
[16:53] <gjolly> blackboxsw: thanks for all the info
[18:55] <falcojr> blackboxsw: branches updated
[19:15] <faa> hello, now cloud-init may work with jsonschema4?
[19:18] <falcojr> I'm assuming you're referring to jsonschema draft 4? Yes, cloud-init validates cloud-config userdata against a version 4 schema
[19:20] <faa> thank, i'm maintain FreeBSD port, and old version (21.4) require jsonschema-3
[19:20] <faa> now enable jsonschema-4 too
[20:32] <blackboxsw> falcojr: I just put up a devel release PR https://github.com/canonical/cloud-init/pull/1687 so that we can SRU that content into bionic|focal|jammy PRs 
[20:41] <falcojr> blackboxsw: didn't we already upload 22.3 into ubuntu/devel? Is this just for the additional commits going into the SRU?
[20:41] <blackboxsw> falcojr: we did but we now pulled the additional commits into the SRU uploads
[20:42] <blackboxsw> I generated that ubuntu/devel branch with the same commitish sync
[20:42] <blackboxsw> `new-upstream-snapshot 9f0efc474ea430c75cd0abec3e2da719d4934346`
[20:42] <blackboxsw> once we have that PR in, I can dput your bionic|jammy|focal branches up
[20:42] <blackboxsw> changsets look good, I'm just commenting on the PRs now 
[20:43] <falcojr> blackboxsw: sounds good. One comment on the PR
[20:46] <blackboxsw> yes it should, thanks for the fix merge
[21:17] <blackboxsw> kinetic uploaded, and bionic, focal impish uploaded to -proposed pockets
[21:18] <falcojr> s/impish/jammy ?
[21:19] <blackboxsw> force of habit
[21:19] <blackboxsw> jammy
[21:19] <blackboxsw> Unapproved: cloud-init (bionic-proposed/main) [22.2-0ubuntu1~18.04.3 => 22.3-3-g9f0efc47-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[21:19] <blackboxsw> 15:16 Unapproved: cloud-init (focal-proposed/main) [22.2-0ubuntu1~20.04.3 => 22.3-3-g9f0efc47-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)
[21:19] <blackboxsw> 15:16 Unapproved: cloud-init (jammy-proposed/main) [22.2-0ubuntu1~22.04.3 => 22.3-3-g9f0efc47-0ubuntu1~22.04.1] (core, ubuntu-cloud)
[21:19] <blackboxsw> [ubuntu/kinetic-proposed] cloud-init 22.3-3-g9f0efc47-0ubuntu1~22.10.1 (Accepted)
[21:19] <blackboxsw> External
[21:20] <blackboxsw> so those releases will include up until upstream commit 9f0efc474ea430c75cd0abec3e2da719d4934346
[21:20] <blackboxsw> I'm uploading them to our ppa:cloud-init-dev/proposed now too
[21:22] <falcojr> sounds good