[16:08] hey folks, I think it's about time for our bi-weekly cloud-init status meeting. [16:08] #startmeeting [16:08] Meeting started Mon Aug 20 16:08:48 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:08] Available commands: action commands idea info link nick [16:08] #endmeeting [16:08] Meeting ended Mon Aug 20 16:08:52 2018 UTC. [16:08] Minutes: http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.08.moin.txt [16:09] #startmeeting Cloud-init bi-weekly status meeting [16:09] Meeting started Mon Aug 20 16:09:08 2018 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:09] Available commands: action commands idea info link nick [16:09] For those around, let's kickoff another cloud-init status meeting. Feel free to interrupt as we go through the agenda for today. [16:10] agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes) [16:13] #topic Previous Actions [16:13] nothing to speak of here as far as I recall. [16:13] #topic Recent Changes [16:14] We have recently landed the following content in tip of cloud-init over the last 2 weeks [16:14] - Add datasource Oracle Compute Infrastructure (OCI). [16:14] - azure: allow azure to generate network configuration from IMDS per boot. [16:14] - Scaleway: Add network configuration to the DataSource [Louis Bouchard] [16:14] - docs: Fix example cloud-init analyze command to match output. [16:14] [Wesley Gao] [16:14] - netplan: Correctly render macaddress on a bonds and bridges when [16:14] provided. (LP: #1784699) [16:14] - tools: Add 'net-convert' subcommand command to 'cloud-init devel'. [16:14] - redhat: remove ssh keys on new instance. (LP: #1781094) [16:14] Launchpad bug 1784699 in cloud-init "cloud-init not setting mac address for bond or bridge in bionic" [Medium,Fix committed] https://launchpad.net/bugs/1784699 [16:15] - Use typeset or local in profile.d scripts. (LP: #1784713) [16:15] - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547) [16:15] Launchpad bug 1781094 in cloud-init "cloud.cfg.tmpl should not include "ssh_deletekeys: 0"" [Medium,Fix committed] https://launchpad.net/bugs/1781094 [16:15] Launchpad bug 1784713 in cloud-init (Ubuntu) "cloud-init profile.d files use bash-specific builtin "local"" [Low,Confirmed] https://launchpad.net/bugs/1784713 [16:15] Launchpad bug 1768547 in cloud-init (Ubuntu) "OpenNebula DataSource adds null gateway6 to netplan config" [Medium,Confirmed] https://launchpad.net/bugs/1768547 [16:15] most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot. [16:21] new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches [16:21] #topic In-progress Development [16:23] The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there. [16:23] *preparing* rather [16:24] Our trello board is a good representation of any existing work we are "Doing" [16:24] #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin [16:26] recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc. [16:26] thanks for the heavy lift powersj [16:27] I think that wraps up all things cloud-init.... [16:27] #topic Office Hource (next ~30 mins) [16:28] We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour [16:28] Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\ [16:28] Hi all, I'd like to request a review for this MP: https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 (attached to LP: #1722959) [16:28] Launchpad bug 1722959 in cloud-init "Implement Key-Value Pair Telemetry for Azure" [Undecided,In progress] https://launchpad.net/bugs/1722959 [16:29] Hoping we can get this merged sometime soon. :-) [16:29] Hi paulmey thanks for the ping on this. [16:29] #link https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 [16:30] #action rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 [16:30] ACTION: rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 [16:30] that has gotten dusty, thank you [16:31] I'll start a review in earnest now [16:31] Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it... [16:31] 😉 [16:32] paulmey: I'll try spinning up an azure vm to test this out [16:34] let me know if you need anything [17:04] ok thanks folks for tuning in. See you next time [17:04] #endmeeting [17:04] Meeting ended Mon Aug 20 17:04:48 2018 UTC. [17:04] Minutes: http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.moin.txt [17:08] just published minutes to https://cloud-init.github.io/ [17:56] smoser: rharper do you guys recall what platforms we expect don't have jinja2 support? [17:56] blackboxsw: hrm, I feel we discussed but I don't recall the details [17:56] it's an optional dependency from the looks of things in cloudinit/templater.py [17:56] there was a reason we had the simple renderer [17:59] * blackboxsw was thinkings centos 6... but python-jinja2-2.2.1-3.el6.x86_64 exists... hrm [17:59] many non-epel customer or something [17:59] it was probably just added as optional because we didn't want to break existng installations (or supported/sttable OS... like trusty or something) [18:00] related to cheetah being dropped too [18:00] which was pre jinja IIRC [18:00] blackboxsw: why do you care ? [18:00] in jinja template parthandler, I'm trying to decide if I can rely on jinja2 module to exist or do the try/except ImportError dance [18:02] in this scenario, when rendering the thing, the user has declared the template to be jinja [18:02] right? [18:02] yeah, they have [18:03] so that shouldn't run unless ##template: jinja is in user-data [18:03] well, its going to fail either way. [18:03] user is not going to get what they wanted. [18:05] we could chooes to hold off because vmtest seems failing. as a result of the journal colleciton change that rharper memtioned today [18:06] smoser: I've a fix for that now [18:06] I'll put up an MP === r-daneel_ is now known as r-daneel === meetingology` is now known as meetingology === r-daneel_ is now known as r-daneel [20:45] let's assume I have set some data wrong in cloud-init userdata (namely the hostname). Can I edit that somehow after the instance booted? modifying set-hostname didn't seem to work [20:46] the metadata service (cloud-init) did update [20:48] apollo13: the default is for metadata (and userdata) to be only applied once per instance (first boot on a platform); If you do make manual modifications (and don;t mind re-running things, which will for example, change the instance host ssh keys) then you could do something like 'cloud-init clean --logs --reboot' which will remove the current instance information and boot like it was a new instance [20:49] lets see what that does :D [20:49] apollo13: if you wanted to do a more targetted run of a specific module you can make use of cloud-init single, something like [20:49] to late [20:50] worst case I nuke the machine and redo it [20:50] hehe [20:52] https://paste.ubuntu.com/p/dRfsfX8gzt/ [20:52] apollo13: there's a forced update of hostname via a local cloud-config file [20:53] but that will still keep the old data around? [20:54] anyways /etc/hosts etc is correct now [20:54] all that did change seems to be ssh key [20:54] ansible is now refixing the rest [20:58] cool [20:59] yes, it would leave the old data around in the metadata/user-data but the hostname files would have the values you wanted [21:00] ok just pushed up the cloud-init devel render CLI subcommand to https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290 think I'll just await ci builds on that. [21:00] rharper: ok thanks, cloud-init is still magic; not exactly sure what it all touches and when :D [21:05] rharper: shouldn't the reinit process recreate the default user? (I mean I am happy it did not, but…) [21:06] apollo13: well, I didn't think users got nuked with a clean; but if it did, then yes the default user should have gotten recreated via a clean --logs --reboot [21:08] ah no, digitalocean overrids it to root via vendor-data [21:08] yes, that makes sense after looking at source [21:08] clean nukes stuff down /var/lib/cloud and logs [21:09] anyways, thanks for the help. all is well now :) [21:28] apollo13: sure thing; glad you're good to go [22:52] paulmey: I did a pass on https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 I still need a bit more time to think a bit about how we want to handle threading/queues in cloud-init for this feature. but initial comments are up [23:39] blackboxsw: Thanks, I'll take a look (and ask Andy to take a look)