[15:50] <Odd_Bloke> blackboxsw: https://github.com/canonical/cloud-init/pull/364 <-- I think this is ready for review, while I file the annotation bug and prepare the corresponding change for snap.assertions.
[17:11] <Odd_Bloke> blackboxsw: FYI, https://github.com/canonical/cloud-init/pull/358 is potentially a candidate for an SRU blocker; we have an SLA for it that falls before we would expect to do another SRU.
[17:15] <blackboxsw> Odd_Bloke: sorry, are you suggesting we wait trying to start an SRU until this branch lands (and try to work out the patches to Xenial/bionic/focal to enable/disable changes in behavior)
[17:25] <mock> Hello
[17:26] <mock> I am drafting a cloud-config file and looking for functionality to load a rpm package downloaded locally to the server at provision time. Can that be done with packages module...or do I need to use runcmd?
[17:27] <mock> Or is there another channel where this question should be asked?
[17:27] <Odd_Bloke> blackboxsw: I'm saying that, AIUI, per SLAs we need to SRU this change by June 14th; we can either proceed with the SRU today as planned (and so do two SRUs between now and then), or we can hold that SRU until this change lands.
[17:27] <Odd_Bloke> blackboxsw: There may be flexibility on that SLA, we should follow-up on that.
[17:31] <blackboxsw> Odd_Bloke: thanks for clarity. let's SRU today and next SRU will be short
[17:31] <blackboxsw> we've held off on the SRU process for a while anyway and so it's getting to be a larger bit of verification work
[17:31] <blackboxsw> the more times we do it the faster it gets
[17:32] <blackboxsw>  https://github.com/canonical/cloud-init/pull/364 < merged
[17:32] <Odd_Bloke> I think there's a lot of constant cost to the process (we still manually verify on every cloud, for example), so I'm not sure I entirely agree with that.
[17:32] <Odd_Bloke> Specifically with "the more times we do it the faster it gets", that is.
[17:33] <Odd_Bloke> But I do agree that it's been a while, so we probably shouldn't hold off.
[17:34] <Odd_Bloke> Particularly because I am going to have some review comments here, so we don't have a definite timeline on landing the PR.
[17:35] <Odd_Bloke> mock: This is the right channel.  Let me make sure I understand: you want to download an RPM file at boot time and install it in the system, is that correct?
[17:39] <mock> Odd_Bloke: Yes. I'm pulling an rpm from Artifactory to be installed locally on the server where the cloud-config is running.
[17:40] <mock> I can pull the file--and kinda need to--using runcmd + wget to fetch it. I was looking to see if there was a way to install it once it is downloaded.
[17:41] <Odd_Bloke> mock: OK, cool.  I think you're probably best off writing a runcmd entry that does this for you.  (You could potentially perform the download in runcmd and then specify a path in packages, but (a) that might not work at all, and (b) if it does, it's not a common or documented configuration so you'd open yourself up to regressions in future.)
[17:42] <mock> Gotcha. Ok, I'll plan the runcmd route for download and install. I was just looking for functionality if it existed.
[17:42] <mock> Thanks!
[17:43] <Odd_Bloke> No problem!
[18:13] <meena> rharper: thank you for your comment, i left one myself: https://github.com/canonical/cloud-init/pull/363#issuecomment-630351265
[19:07] <rharper> meena: cool!  it'll be a group effort =)
[19:08] <meena> rharper: thank you 💜
[21:33] <dgerich> good afternoon, i am trying to inject a cloud-init (cloud-config) into Ubuntu 18 provisioning via Cobbler, and can't seem to get even a simple example to work, where do i need to save the #cloud-config yaml file for it to be executed by cloud-init on boot?
[21:35] <Odd_Bloke> dgerich: o/ I'm not familiar with Cobbler, unfortunately.  Could you point me at the example you're using?
[21:36] <dgerich> using examples from: https://cloudinit.readthedocs.io/en/latest/topics/examples.html#
[21:36] <dgerich> using cobbler to provision Ubuntu 18 via seed (Automatic Installation Template)
[21:37] <dgerich> i can use wget to download a file with #cloud-config but what confuses me is where that file should be placed in order for cloud-init to pick it up and execute that config
[21:38] <dgerich> i tried placing it in /etc/cloud/cloud.cfg.d/99_test.cfg but that does not seem to work
[21:39] <Odd_Bloke> dgerich: cloud-init expects to fetch its user-data (i.e. cloud-config) from the cloud on which its running, not from somewhere on the instance (though there are ways of doing that).  Does Cobbler master the image for you, or is it running at instance boot time?
[21:40] <dgerich> I am using it to provision VMs in a Datacenter (not on the cloud) I've read that I can use Datasource NoCloud, sorry i am still a bit confused on how its all setup
[21:41] <Odd_Bloke> dgerich: Not a problem!  https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html#datasource-nocloud is the documentation for the NoCloud datasource.
[21:41] <dgerich> also did try to place it here for no effect: /var/lib/cloud/seed/nocloud/user-data
[21:41] <rharper> dgerich: I think you likely want to use NoCloud-net datasource, and you can pass this via kernel parameters, including a url to where the config can be fetched;     ds=nocloud-net;seedfrom=http://10.245.168.20:34347/     ;  you can replace the http= in the seedfrom to point to a web server you can control; from there, you'd need to provide a directory with the required NoCloud files 'user-data' 'meta-data',
[21:42] <rharper> dgerich: if you can use the filesystem itself, you put the user-data in the correct location, but you also need a meta-data file, which contains at least, instance-id: <some string>  and local-hostname: <some value here>   ; in addition to your user-data
[21:43] <dgerich> ah I was only placing the user-data file, so I need to add a meta-data as well to same place?
[21:43] <dgerich> was /var/lib/cloud/seed/nocloud/ correct location to place both files?
[21:44] <rharper> yes
[21:44] <dgerich> ok ill give it a try, thank you
[21:46] <Odd_Bloke> blackboxsw: I see that you moved us away from flake8 in https://github.com/canonical/cloud-init/commit/80dfb3b02.  I have a spurious pyflakes warning in a branch I'm working on that I'd like to be able to ignore (rather than writing extra code to effectively do the same).  Do you have any objections to me moving us back to flake8?