[12:09] <JRodDynamite> Hey, I'm pretty new to this. I have a server with an existing cloud-init cfg in it and was trying to understand it. There are some modules that are configured and I wanted to understand where the underlying source code for it resides. Eg: in `cloud_init_modules` I have `update_hostname`. I wish to understand how that updates the machines hostname.
[12:10] <minimal> JRodDynamite: look in cloudinit/config/cc_update_hostname.py
[12:13] <JRodDynamite> minimal: How can I find it's absolute path?
[12:14] <JRodDynamite> minimal: Never mind I found it. Thanks!
[13:55] <paride> Slightly OT: I'm preparing a new upstream snapshot of simplestreams
[13:55] <paride> the main reason is releasing a fix for: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1908452
[13:56] <paride> (which will likely need a SRU at least to Focal)
[13:57] <paride> Here is the MP against ubuntu/devel https://code.launchpad.net/~paride/simplestreams/+git/simplestreams/+merge/402896
[14:00] <paride> blackboxsw ^^
[14:05] <paride> As always I'm a bit confused by how we maintain the packaging :-) But hopefully I got used to it
[14:56] <otubo> Hey guys, I have a quick question about python-jsonschema on cloud-init.
[14:56] <otubo> I'm reading through cloudinit/config/schema.py and there's a try-except on line 88 for when the package is not installed.
[14:58] <otubo> How much harm it is to remove python-jsonschema from the dependency list? On RHEL (CentOS 9, Fedora) we're removing some unwanted packages, and python-jsonschema needs pyrsistent that needs a whole chain of stuff.
[14:58] <otubo> Is it ok to remove it? Or we're gonna loose too much functionality in there?
[15:00] <otubo> perhaps smoser or Odd_Bloke can have an idea on this
[15:09] <smoser> i'll leave it to Odd_Bloke to comment. xenial (16.04) does not have it. i think that the fallout would be only present on bad-input .
[15:10] <smoser> jsonschema is going to give better errors telling what is wrong with data.
[15:11] <smoser> blackboxsw did a lot of the jsonschema work.
[15:13] <otubo> smoser: well if someone files a bug for those distros, who's gonna read the logs would be me, so... I'm ok with that :D
[15:24] <smoser> well... yeah, but wouldn't it be nice if instead of having an incomprehensible log message , the user saw something like:
[15:24] <smoser> cloudinit.config.schema.SchemaValidationError: Cloud config schema errors: write_files.0: 'path' is a required property, write_files.0.append: 'false' is not of type 'boolean'
[15:24] <smoser> https://paste.ubuntu.com/p/hHCn8y7PmG/ <-- from that.
[15:26] <smoser> but i fully understand the pain of dependencies.
[15:40] <otubo> smoser: the problem with the dependencies at the moment is: If your package needs it, you own it.
[15:41] <otubo> smoser: so there's a bunch os cloud-init dependencies that no one else needs, so I have to maintain it as well.
[15:42] <otubo> smoser: right now I have 6 python packages on my list. One less would be wonderful :-D
[15:43] <paride> smoser, any change you can review/sponsor https://code.launchpad.net/~paride/simplestreams/+git/simplestreams/+merge/402896 ?
[15:43] <paride> *chance
[15:43] <otubo> smoser: and it's not gonna be one less, if I can't remove pyrsistent from jsonschema, that's gonna be mine too.
[15:43] <otubo> Anyway. I'm leavcing for today. My bot will listen for the input of others on this matter. Thanks again!
[16:02] <blackboxsw> hi otubo: jsonschema is an optional dependency in cloud-init because it still only has coverage for a fraction of the cloudint.config modules and we didn't get a chance last cycle to spend any time getting  that jsonschema coverage complete.
[16:03] <blackboxsw> otubo: We probably won't make it a strict mandatory dependency because of other distros that may not have it available. If we plan on making that dependency strict, we'll email cloud-init mailinglist before hand. I expect that won't happen for a year.
[16:05]  * blackboxsw otubo: without JSONSchema cloud-init the only "loss" from a distro perspective would be that /var/log/cloud-init.log would be unable to provide a specific error messages about invalid lines/keys/values in userdata. 
[16:05] <blackboxsw> so, not critical feature, but nice to have to aid in triage
[16:14] <smoser> paride: it looks like you need jamespage or powersj to ACK that. i'll comment that it LGTM.
[16:16] <powersj> done
[16:24] <smoser> blackboxsw: unable to provide specific error message, and subsequent seemingly arbitrary failures as a result.
[16:24] <smoser> like tracebacks with KeyError or TypeError or some such due to attempted use and assumption that data is valid.
[16:25] <smoser> jsonschema allows you to check once and then assume valid.
[16:30] <blackboxsw> smoser: correct, and more clear. otubo: the lack of jsonschema errors means that your distro will get hard-to-triage failures in config modules as well as potentially silent successes on userdata keys/values with typos or invalid types that may get silently ignored by various config modules.
[16:30] <blackboxsw> ... and here we are again at a stale community status meeting. Let's get this back on track and kick one off for today
[16:32] <blackboxsw> #startmeeting cloud-init bi-weekly office-hours
[16:32] <meetingology> Meeting started at 16:32:21 UTC.  The chair is blackboxsw.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[16:32] <meetingology> Available commands: action, commands, idea, info, link, nick
[16:32] <paride> smoser, thanks, merged!
[16:33] <paride> but as it's not in the server packageset I'll need sponsorship for the upload...
[16:33] <blackboxsw> community-notice: Let's get back to a more regularly scheduled cloud-init office hours. Every two weeks, feel free to watch the channel topic for the next scheduled time. We'll ensure to have a couple of sets of eyes on this IRC  channel.
[16:35] <blackboxsw> Next office-hours meeting is set for June 1, 17:15 UTC. It is worth us having this recurring meeting to give anyone a chance to drive-by #cloud-init if they have questions, discussions, bugs or PRs that need attention.
[16:36] <blackboxsw> Prior to the office hours, we will continue to generate a post with the latest commits to land in cloud-init:master as well as any notable features in progress https://discourse.ubuntu.com/t/cloud-init-status-05-18-2021/22349
[16:41] <blackboxsw> From upstream standpoint,  we were able to cut the time-based release 21.2 on May 6th. And for Ubuntu, we have queued the StableReleaseUpdate (SRU) for 21.2 into Bionic, Focal and Hirsute for which falcojr and Odd_Bloke have been going through verification.
[16:41] <blackboxsw> Think we need to update the topic for the 21.2 upstream release too.
[16:42] <smoser> paride: https://paste.ubuntu.com/p/y3N7wjCG3n/
[16:44] <smoser> fudge.
[16:44] <smoser> but i just noticed your changelog didn't have LP: #1908452
[16:45] <smoser> because the commit message said 'Fixes LP:1908452' rather than just 'LP: #1908452'
[16:46] <blackboxsw> 'Fixes LP:1908452'  almost github; almost LP :/
[16:48] <paride> smoser, argh :/ will update the bug status manually
[16:48] <paride> thanks for the upload
[16:50]  * blackboxsw falcojr: do we have a trello board for the SRU 21.2 created?
[16:50] <falcojr> yep, https://trello.com/b/tBP3Jrwp/sru-cloud-init-212 (just made it public)
[16:51] <blackboxsw> Thanks a lot
[16:55] <blackboxsw> Great, I was originally looking at the older trello board for the 21.1. Ok, so I'll grab Softlayer testing as you mentioned at standup today. If you want me to run through other clouds just let me know or hit me up for reviews.
[17:26] <blackboxsw> Alright, I think that about wraps today's office hours. Next round in two weeks. Thanks for tuning in.
[17:26] <blackboxsw> #endmeeting
[17:26] <meetingology> Meeting ended at 17:26:17 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-05-18-16.32.moin.txt