[02:10] <pycurious> I'm trying to optimize my boot time for an aws instance - any suggestions on how to optimize this -> cloud-init-local.service @1.296s +1.506s ?
[19:21] <akutz> falcojr: Does your e-mail re: testing mean that the current cloud-images for Focal and Bionic *also* have the new DataSource baked in? I see that Focal's current cloud image was last updated on 8/25, but Bionic's is from 8/18, and Cloud-Init 21.3 was not released until 8/23. 
[19:25] <akutz> By the way, regarding the "ssh_import_id", the current public CI docs examples section also has "None" - https://cloudinit.readthedocs.io/en/latest/topics/examples.html
[19:26] <falcojr> akutz: it means that it will once we finish testing. Those recent uploads would be unrelated to cloud-init. After every upstream release of cloud-init, we also backport those changes to the supported ubuntu releases through our Stable Release Update (SRU) process. The entire process is laid out here (but you probably don't want to read it all)
[19:26] <falcojr> https://wiki.ubuntu.com/StableReleaseUpdates
[19:27] <akutz> Understood. I ask because blackboxsw said the same thing about Impish, but it turned out that its cloud-image already had cloud-init 21.3 baked into it. I didn't know if that happened to any of the other cloud-images unexpectedly as well.
[19:27] <falcojr> currently 21.3-1 exists in the -proposed pockets which are used for ubuntu testing before they land in -updates. If you update your apt config to use -proposed, you can get the latest cloud-init in existing releases via apt upgrade
[19:27] <falcojr> yeah, impish is treated separately because it's still unreleased
[19:27] <akutz> I'm saying that the current Impish cloud-image works out of the box... Ah, okay, thanks.
[19:28] <akutz> Okay. Well, I'm drafting a doc on how to validate the VMware DS with both the existing images and newer, so I wanted to be clear on what is necessary where. Thanks for your help falcojr!
[19:29] <akutz> If I wanted to include the doc in the CI repo, where would be a good place to locate it? In the RST for the DS itself? In a specific testing doc? I was just going to describe how to validate it with Fusion/Workstation.
[19:29] <falcojr> I'll get that doc example updated at some point too...None is a bad value there
[19:30] <akutz> Ack, thanks falcojr. That's what I used when drafting *my* example as well. If you update that doc, can you please include the vmware.rst too? I know it uses None as well.
[19:30] <falcojr> sure
[19:30] <falcojr> for the other doc, probably the DS itself
[19:31] <falcojr> shouldn't be too hard to move it around if we decide it belongs somewhere else
[19:32] <blackboxsw> akutz: impish (aka; the current development release) has less strict update requirements (though impish is currently in FeatureFreeze meaning that we have a little more launchpad paper work/review needed if we are adding new features) https://discourse.ubuntu.com/t/impish-indri-release-schedule/18540 . We happened to get published  automatically in Impish because the changelog  represented only bug fixes, not new features.
[19:33] <akutz> Ack. I may keep it internal since it's more just a guide for engineers here on how to test it. The public DS doc has enough info to instruct people how to use the DS. The doc I'm creating is if they don't know how to test CI at all.
[19:33] <blackboxsw>  For Stable releases (Bionic, Focal Hirsute)  we still have a strict release policy that would require enabling <release>-proposed apt sources in order to see/test cloud-init 
[19:34] <akutz> Ack. I was not trying to call you out as incorrect or anything. I just did not know if perhaps there was a possibility the existing cloud images (since Focal was updated today) might also have the bits already since Impish did unexpectedly. When you said CI had been approved, I didn't realize it was only for Impish. Thanks for the detailed info. 
[19:34] <blackboxsw> once Impish gets officially released October 14th, it then falls into the same stable/strict release process where we can no longer get cloud-init auto-published into impish-updates without full SRU verification on all clouds
[19:34] <blackboxsw> "Ack. I was not trying to call you out as incorrect or anything." +1 totally here you. Just wanted to clarify for posterity
[19:35] <blackboxsw> *hear*
[19:35] <akutz> "We happened to get published  automatically in Impish because the changelog  represented only bug fixes, not new features." Is that true though? I thought the VMware DS would be considered a new feature?
[19:35] <blackboxsw> akutz: we happened to perform an upload into impish about 1 week before the FeatureFreeze deadline :)
[19:36] <blackboxsw> cloud-init can upload any new features anytime we want (daily if we needed to) into the development release until FeatureFreeze hits, which was August 19th.
[19:37] <falcojr> We uploaded what we thought would be 21.3 a few days before feature freeze, but then had to fix a couple major bugs that took us past feature freeze. So the diff between that original upload and what become 21.3 amounted to just bug fixes
[19:38] <blackboxsw> which we uploaded on  2021-08-13  per here. https://launchpad.net/ubuntu/impish/+queue?queue_state=3&queue_text=cloud-init
[19:38] <akutz> Ahh. 
[19:39] <akutz> I felt dirty for a moment, like y'all were calling all my work a "bug fix." So that's how it is. I see, I see ;) 
[19:40] <falcojr> hah...nope, the bugs were both mine :)
[19:40] <blackboxsw> haha
[20:13] <Guest9190> Hello I want to create LVM partition with encryption in cloud-init file