[09:17] <kevko> Hello folks, please could someone advice me how to fix my cloudinit setup ? Point is that I have several interfaces and I want to have control in networking ..so I have own python script which generate netplan and set udev rules (names of interface) ...but cloudinit somehow set ip addresses of interfaces and moreover set default gateways several times for several interfaces and some interfaces don't have connectivity outside ..so cloudinit will fail 
[09:17] <kevko> because of resolve problems and apt problems...
[09:19] <kevko> now I am using heat + heat software deployment in openstack ... first I am waiting for cloudinit is done and then I run networkconfigurator to setup network and apply netplan ... it worked by accident almost always ..because order of interfaces was resolved in corrrect way ..but now the order was different ..so i am tryig to find a way how to configure network before cloudinit will do things which neeed to be connected to internet ...apt ..etc 
[10:23] <aciba> kevko: Hello. I think the following might work. Disabling cloud-init network configuration: https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/network-config.html#cloud-config
[10:23] <aciba> and running your net config script in https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#bootcmd
[10:26] <aciba> kevko: could you try something in the lines of: https://pastebin.ubuntu.com/p/KD95yscZ5G/ ?
[10:33] <kevko> aciba: yeah, this is scenario i was thinking about that should work .... googled 5 minutes ago :P 
[15:10] <holmanb> SuperLag: getting back to this now
[15:29] <holmanb> SuperLag: it looks like you have invalid yaml
[15:29] <holmanb> SuperLag: see https://dpaste.org/FkSKX
[16:08] <SuperLag> I just now got the chance to try, and that did the trick. 🙌🏻
[16:08] <SuperLag> and here I thought that yaml syntax was correct.
[16:12] <SuperLag> holmanb: is there a way with using cloud images to set it up for resizing? 10GB usually isn't enough. :D
[16:23] <meena> SuperLag: https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#growpart & https://canonical-cloud-init.readthedocs-hosted.com/en/latest/reference/modules.html#resizefs
[16:25] <meena> what is cloud-initramfs-tools?
[16:26] <meena> https://launchpad.net/cloud-initramfs-tools
[17:21] <minimal> meena: Ubuntu-specific tool for adding stuff to the initramfs for things like growing partition - nothing to do with cloud-init AFAIK
[17:35] <meena> minimal: funnily enough, OpenBSD and NetBSD would need that too, cuz their growfs doesn't work online
[17:37] <minimal> meena: it is doing *partition* growing, don't think it also does fs growing
[17:40] <minimal> from a quick glance its "growroot" is basically just calling "growpart"
[17:48] <meena> minimal: i do wonder what the point of that is
[18:01] <minimal> to grow partition in an initramfs? ;-) Anyway it is unconnected to cloud-init beyond the fact that they both use growpart from cloud-utils
[21:47] <noahm> Hi folks. I'm not sure when it happened, but the migration of the docs from cloudinit.readthedocs.io to canonical-cloud-init.readthedocs-hosted.com has dropped all documentation for older releases.  With many distros continuing to ship older releases, losing the version specific documentation is problematic.
[21:47] <noahm> I didn't see a bug report for this on launchpad, but figured I'd check here first before opening one.
[22:43] <SuperLag> holmanb: thank you, thank you, thank you!!
[22:44] <SuperLag> holmanb: in that paste, line 19... does that already come with the cloud-init bits?  
[22:45] <SuperLag> holmanb: if not, can you tell me what I need to get the tools to do that test on my own?