18:19 <blackboxsw> #startmeeting Cloud-init bi-weekly status 18:19 <meetingology> Meeting started Tue Nov 12 18:19:53 2019 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 18:19 <meetingology> 18:19 <meetingology> Available commands: action commands idea info link nick 18:20 <blackboxsw> Thanks for tuning in folks to another quick cloud-init status meeting. 18:20 <blackboxsw> cloud-init upstream uses this meeting as a platform for community updates, feature/bug discussions, and an opportunity to get some extra input on current development. 18:21 <blackboxsw> we have a number of upstream members at a remote conference this week so I'll be the only upstream chairing the meeting for today 18:22 <blackboxsw> right off the bat let's update the topic for next status meeting: .... Thanksgiving week in the US. So, I expect that'll be light/absent attendance as well 18:23 <blackboxsw> I know at least two of us will be around that week, so let's continue to host the status meeting to get into a rhythm 18:23 <blackboxsw> ok Nov 26th it is. a couple hours earlier than this meeting 18:24 <blackboxsw> 16:15 UTC 18:24 <blackboxsw> Our typical format is the following: Previous Actions, Recent Changes, In-progress Development, Community Charter, Upcoming Meetings, Office Hours (~30 mins). 18:24 <blackboxsw> Interruptions/interjections and other topics always welcome 18:27 <blackboxsw> #topic Previous Actions 18:27 <blackboxsw> Our previous meeting minutes are here: 18:27 <blackboxsw> #link https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29 18:27 <blackboxsw> I had two actions listed: 18:27 <blackboxsw> "action: cloud-init upstream discuss where/how/if to host documentation supported cloud-init versions for debian/suse/redhat/ubuntu/freebsd etc." 18:29 <blackboxsw> I did attempt to propose a branch to document the specific versions of cloud-init supported in each distro that cloud-init runs on in the project README.md for github.com/canonical/cloud-init. On further discussion with the team, the thought was that maintaining a version table of cloud-init for all distributions was going to to fairly tedious and costly. 18:29 <blackboxsw> so we didn't commit that changeset to the docs. 18:30 <blackboxsw> I think we are still open to discussion about ways that cloud-init version support could be documented somehow in the project, but at the moment I think we're passing on this idea until someone can suggest of a simple/maintainable solution. 18:31 <blackboxsw> 2nd action: https://cloud-init.github.io/status-2019-10-29.html#status-2019-10-29 18:31 <blackboxsw> 2nd action: action mailing list update to cloud-init community about procedure/timeline for migration to github 18:32 <blackboxsw> woot! initial migration from Launchpad -> github went swimmingly. We are still updating some internal tools to better enable us to land/lint andmerge branches from either Launchpad or github so folks don't *have* to migrate existing launchpad branches to github PRs. 18:33 <blackboxsw> Here's a mail sent out by rharper on the migration to github and what's required for existing Launchpad cloud-init developers: 18:33 <blackboxsw> #link https://lists.launchpad.net/cloud-init/msg00231.html 18:35 <blackboxsw> basically, to have CLA (contributor license agreement) accountability we want to ensure a github user is mapped to the Launchpad user who has already signed the CLA. to tie your Launchpad username to github, one needs to run ./tools/migrate-lp-user-to-gitub LAUNCHPAD_USERNAME GITHUB_USERNAME and upstream will review mirrored merge proposals in Launchpad and Github to ensure the accounts are the same 18:35 <blackboxsw> contributor 18:35 <blackboxsw> Think that wraps it up for "Previous Actions" 18:37 <blackboxsw> #topic Recent Changes 18:38 <blackboxsw> As mentioned above, we've moved to github as our upstream code repository and we are extending our tooling, linting and CI to make this project even easier to contribute to. As we adopt new developer processes in github, keep your eyes on the hacking doc to stay updated on the development process to speed up the inclusion of your patches into upstream 18:38 <blackboxsw> #link https://cloudinit.readthedocs.io/en/latest/topics/hacking.html 18:39 <blackboxsw> The following are the commits landed on tip of master since last status meeting: 18:39 <blackboxsw> $ git log --since 2019-10-29 | log2dch 18:39 <blackboxsw> - reporting: Using a uuid to enforce uniqueness on the KVP keys. [momousta] 18:39 <blackboxsw> - lp-to-git-users: adding paride [Paride Legovini] 18:39 <blackboxsw> - lp-to-git-users: adding powersj [Joshua Powers] 18:39 <blackboxsw> - lp-to-git-users: adding blackboxsw 18:39 <blackboxsw> heh, spam throttled 18:39 <blackboxsw> - github: new basic project readme 18:39 <blackboxsw> 11:39 - Release 19.3 (LP: #1851428) 18:39 <blackboxsw> 11:39 - azure: support matching dhcp route-metrics for dual-stack ipv4 ipv6 18:39 <blackboxsw> 11:39 (LP: #1850308) 18:39 <blackboxsw> 11:39 - configdrive: fix subplatform config-drive for /config-drive source 18:39 <blackboxsw> 11:39 [David Kindred] (LP: #1849731) 18:39 <blackboxsw> 11:39 - DataSourceSmartOS: reconfigure network on each boot 18:39 <blackboxsw> 11:39 [Mike Gerdts] (LP: #1765801) 18:39 <blackboxsw> 11:39 - Add config for ssh-key import and consuming user-data [Pavel Zakharov] 18:39 <ubot5> Launchpad bug 1851428 in cloud-init "Release 19.3" [Medium,In progress] https://launchpad.net/bugs/1851428 18:39 <blackboxsw> 11:39 - net: fix subnet_is_ipv6() for stateless|stateful 18:39 <blackboxsw> 11:39 [Harald Jensås] (LP: #1848690) 18:39 <ubot5> Launchpad bug 1850308 in cloud-init "cloud-init on azure with dual stack needs to add route-metric for dhcp6 also" [High,Fix committed] https://launchpad.net/bugs/1850308 18:40 <ubot5> Launchpad bug 1849731 in cloud-init "Introduction of subplatform around 18.5 broke ConfigDrive" [Undecided,Fix committed] https://launchpad.net/bugs/1849731 18:40 <ubot5> Launchpad bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Fix committed] https://launchpad.net/bugs/1765801 18:40 <ubot5> Launchpad bug 1848690 in cloud-init "subnet_is_ipv6() function does not work for types ipv6_dhcpv6-stateless|stateful" [Undecided,Fix committed] https://launchpad.net/bugs/1848690 18:40 <blackboxsw> - OVF: disable custom script execution by default [Xiaofeng Wang] 18:40 <blackboxsw> - cc_puppet: Implement csr_attributes.yaml support [Matthias Baur] 18:40 <blackboxsw> - cloud-init.service: on centos/fedora/redhat wait on 18:40 <blackboxsw> NetworkManager.service (LP: #1843334) 18:40 <blackboxsw> - azure: Do not lock user on instance id change 18:40 <blackboxsw> [Sam Eiderman] (LP: #1849677) 18:40 <ubot5> Launchpad bug 1843334 in cloud-init "Change location of DHCP leases in CloudStack provider as it doesn't work for RHEL8" [Medium,Fix committed] https://launchpad.net/bugs/1843334 18:40 <ubot5> Launchpad bug 1849677 in cloud-init "azure locks existing user if instance id changes" [Medium,Fix committed] https://launchpad.net/bugs/1849677 18:41 <blackboxsw> As you can hopefully see (if I didn't get kicked again): A lot of tooling for github, upstream fixes for network, SmartOS, Openstack, ConfigDrive and Azure IPv6 support. 18:41 <blackboxsw> We also were able to cut and release cloud-init upstream 19.3! 18:41 <blackboxsw> Thank you all for the excellent contributions there 18:42 <blackboxsw> #topic In-progress Development 18:42 <blackboxsw> We generally track these items on trello 18:42 <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin 18:47 <blackboxsw> But, in flight we have some Azure IPv6 support up for review, just landed a couple of cleanup branches for tox and we should have a couple of FreeBSD branches from the launchpad review queue that we can get merged shortly. 18:49 <blackboxsw> I know that rharper is also continuing to grind away a cloud instance boot speed, as well as network hotplug support so expect those configurable (optional) features to show up in the weeks to come 18:50 <blackboxsw> ok last two topics 18:50 <blackboxsw> #topic Community Charter 18:51 <blackboxsw> We've got a trello board lane for anyone with some time to kill looking to contribute to bite-sized and low-hanging-fruit community efforts 18:52 <blackboxsw> Just look for "Community: Low hanging fruit" on our trello board 18:53 <blackboxsw> The current themes of work items there are scrub and correct existing datasource docs for ReadTheDocs. and around 40 items of adding jsonschema definitions for each cloud-config module so that we can better annotate #cloud-config failures for users providing invalid #cloud-config syntax 18:53 <blackboxsw> #topic Upcoming meetings 18:53 <blackboxsw> As mentioned in the topic Next status meeting will be held Nov 26 16:15 UTC 18:54 <blackboxsw> we should have a couple of folks in attendance if there are any questions 18:54 <blackboxsw> #topic Office Hours (next ~30 mins) 18:54 <blackboxsw> bring your bugs, discussions, features, concerns here about cloud-init life the universe and everything. upstream will spend this time actively grooming the review queue to see if we can't unblock developers 18:55 <blackboxsw> since we have two review queues (Launchpad and github) we'll try to clean out the launchpad queue and get those branches merged into github tip so that we can eventually be looking only at the github review queue: 18:55 <blackboxsw> #link https://github.com/canonical/cloud-init/pulls 18:56 <blackboxsw> Anyone looking to propose new branches to cloud-init, please clone from https://github.com/canonical/cloud-init and propose PRs over in github. 18:57 <blackboxsw> If your github user has not yet been associated with a Launchpad username who has signed the CLA please follow the steps on the hacking guide to tie launchpad user to GitHub user so we can accept commits in github. 18:58 <blackboxsw> Running: ./tools/migrate-lp-user-to-github <your_launchpad_user> <your_github_user> will proposed mirrored branches in both launchpad and github and we can verify the account as 'active' in github 18:59 <blackboxsw> Thanks again for tuning in. Any questions/discussions welcome 19:12 <larsks> blackboxsw: that migrate script seems a bit fragile. I set user.email per-repository rather than globally, so it failed running "git commit --all -F /tmp/commit.msg$ git commit --all -F /tmp/commit.msg" because user.email was unset. So I set it globally, but then it fails because it didn't clean up after itself and now "git pull" fails with "cannot pull with rebase: Your index contains uncommitted 19:12 <larsks> changes.". I can workaround all of this; just pointing it out... 19:13 <blackboxsw> larsks: excellent feedback, yeah that script is a quick tool to try to help, I'll see if I can reproduce given your environment suggestion 19:14 <larsks> blackboxsw: I think if it would just clean up the temporary directory on failure that would be a good change. 19:14 <blackboxsw> and I'll fix the tool as we'll need to use it for a while until we figure out a better "plan" for managing the CLA from github proper 19:14 <blackboxsw> larsks: will add that immediately thx 19:14 <blackboxsw> actually and I'll set you are reviewer to validate 19:14 <larsks> Curses. 19:14 <larsks> :) 19:14 <blackboxsw> hah! 19:14 <blackboxsw> busted 19:15 <blackboxsw> hi ahosmanMSFT 19:15 <ahosmanMSFT> Hi blackboxsw 19:15 <blackboxsw> larsks: yeah I'll add a big old try/except block around those subps and cleanup on the migrate 19:15 <larsks> blackboxsw: ...oh, look, it should also cleanup after itself on successful completion, too :) 19:16 <blackboxsw> will do both. working that now larsks, should have something in 5 pushed to github 19:16 <larsks> blackboxsw: also! (sorry) it looks like --dryrun actually is not a dryrun. 19:16 <ahosmanMSFT> blackboxsw I just pushed an update on cloud tests, sorry for the delay, was sick all last week 19:16 <larsks> Because I ran with --dryrun but it did the thing. 19:17 <blackboxsw> ahh larsks the dryrun is limited to not publishing remotely basically (so it does the local-only work so one could review it). But maybe it should just do nothing and emit the git commands 19:18 <blackboxsw> ahosmanMSFT: sorry about sickness. I hope you are feeling better. Good on your CI update for Azure. I'll peek at that today 19:22 <ahosmanMSFT> blackboxsw ok, let me know if the server auth works when grabbing console log that's been a bit wonky. Other than that it seems like Azure CI is completing. 19:24 <blackboxsw> will do ahosmanMSFT 19:25 <tribaal> hi folks :) 19:26 <tribaal> blackboxsw: quick question for you: what is the status for 19.3 as an SRU? 19:27 <blackboxsw> larsks: https://github.com/canonical/cloud-init/pull/35 19:28 <blackboxsw> hi tribaal, 19.3 will likely stsart SRU shortly (I'm guessing start the SRU process this week) I have a branch in flight that we'll need to land in tip that is gating our next SRU. 19:28 <blackboxsw> *start SRU shortly* 19:29 <blackboxsw> once I have this branch landed in tip, we'll start the SRU. 19:29 <tribaal> blackboxsw: ack, I see. Thanks for the update! 19:30 <blackboxsw> tribaal: if you get a chance this week can you try https://github.com/canonical/cloud-init/pull/35 19:30 <blackboxsw> I want to get your github user added to cloud-init 19:30 <blackboxsw> and I want to test that quick fix on someone else's env 19:30 <tribaal> oh, sure 19:31 <blackboxsw> thanks 19:31 <blackboxsw> same ahosmanMSFT if you get a chance https://github.com/canonical/cloud-init/pull/35 19:31 <tribaal> blackboxsw: so I should run that script, correct? 19:31 <blackboxsw> tribaal: yep it'll proposed two identialy branches (one in Launchpad and one in github) 19:32 <blackboxsw> then I can correlate the two user account together and merge username map into cloud-init proper 19:32 <tribaal> oh I see 19:32 <tribaal> let me give it a shot then 19:32 <blackboxsw> it's our 'accounting' for you gents already signing the CLA (contributor license agreement) for cloud-init 19:32 <tribaal> ah, gotcha 19:35 * tribaal is running the script 19:38 <tribaal> blackboxsw: https://github.com/canonical/cloud-init/pull/36 19:38 <tribaal> :) 19:38 <blackboxsw> thx larsks and tribaal I'll approve both now 19:38 <tribaal> ack thanks blackboxsw 20:13 <blackboxsw> ok I think that about wraps the status meeting for this week. Thanks for joining all! See you next time 20:13 <blackboxsw> #endmeeting