[00:50] What is the upstream team's planned cutoff date for the 20.3 release of cloud-init? I looked at the bi-weekly meetings, the cloud-init docs, and ubuntu wiki, but I couldn't find a projected release timeline. [00:50] I'm assuming the following historical precedent, the cutoff date for 20.3 will be sometime soon (next 2-3 weeks)? === paride|off is now known as paride [12:11] "when it's ready" ? [15:49] smoser, hey, I'm reviewing https://github.com/canonical/uss-tableflip/pull/57 and wonder where get-orig-tarball comes from [15:52] https://gist.github.com/smoser/fa77f61a2b650d115b5fc2a8ab028ede [15:52] i'm fine if you want to pull that in somewhere else. [15:58] paride: and if you know of an easier way to do that, i'm all for it. [15:58] its suprisingly difficult in my experience to find an orig tarball. [16:06] paride: do you know what the correct behavior is if upstream has a debian/ in the tarball ? [16:07] does build-package extract the debian.tar.gz over the top? or remove the existing and then extract [16:10] as we should make build-package do the right thing. [17:08] hello, all! could i get a review for merge on this pr? thanks in advance! smoser reviewed some time ago but not sure if another maintainer needs to check it out as well [17:08] https://github.com/canonical/cloud-init/pull/509 forgot the pr link [18:00] Ooops I got logged off so I would not have been able to see whether there was a response regarding the SRU cutoff date. :) [18:01] When is the projected SRU/release cut off date for cloud-init by the way? [18:14] (for 20.3). [18:33] johnsonshi: soon, we're going to write up the announcement to prepare it tomorrow I think [18:33] johnsonshi: so we're looking this week at WIP that needs to land and try to get a sha that's ready before EOW [18:34] rick_h: Thanks! So the likely timeline for the cutoff date is very soon? [18:34] johnsonshi: this week for sure [18:34] johnsonshi: what are you wanting to get in? [18:35] rick_h: Thanks! Just asking because I've got a couple of internal teammates asking about the cutoff date to align priorities. [18:35] johnsonshi: ah ok. Let me know if there's anything we want to make sure and we'll try to help review/etc to get it in. [18:40] rick_h: when will the next SRU be after this one? [18:43] AnhVoMSFT: so after that we've got a project to dev the hotplug support through and the SRU will be after that. Maybe by end of cycle Oct? [18:44] thanks rick_h [18:45] If it's at all feasible it would be nice to land this one for this SRU https://github.com/canonical/cloud-init/pull/529 [18:48] AnhVoMSFT: ty, will do. Dan was trying to get to it before his holiday but we spoke today about getting it picked up by others. We'll get eyes on it. [20:08] Would the upstream team be open to allowing the Azure apply_network_config option to be set through Azure instance metadata? Referring to https://bugs.launchpad.net/cloud-init/+bug/1889112 [20:08] Ubuntu bug 1889112 in cloud-init "cloud-init should support setting apply_network_config through Azure instance metadata" [Undecided,Triaged] [20:28] The Azure datasource's apply_network_config flag determines whether cloud-init is supposed to set up the instance's networking stack by querying IMDS. [20:28] As of now, this flag is only read by cloud-init from the disk configs at /etc/cloud/cloud.cfg.d/*.cfg. [20:29] By default, Azure apply_network_config flag is set to true for the Ubuntu 18.04 LTS images published on Azure. [20:43] A customer that wants to "opt out" of this flag cannot do it during deployment time, as this config cannot be set using the Azure datasource.