[11:47] <haroon> hello everyone is there something like a cloud-init repository, where people shared they cloud-init config. so I can see some examples and maybe modify and use them for myself?
[11:49] <aciba> haroon: hi! There are examples under: https://docs.cloud-init.io/en/latest/reference/examples.html
[11:49] <aciba> which is baked by https://github.com/canonical/cloud-init/tree/main/doc/examples
[11:50] <aciba> Each modules as its documentation and more examples in: https://docs.cloud-init.io/en/latest/reference/modules.html
[11:50] <aciba> * Each module has its documentation and more examples in: https://docs.cloud-init.io/en/latest/reference/modules.html
[11:54] <haroon> thanks links and for the information! I know about the docs, but I was looking for something more like ansible-galaxy. I.e I want to setup a glusterfs and someone shared their cloud-init and I just need to modify it a bit for my usecase.
[11:55] <haroon> I've found seen a few exampled on some random github here and there where people shared their could-init files, but nothing like a propper collectioin, which you can browse.
[12:52] <minimal> haroon: different people would likely use different methods to set up stuff like that
[12:52] <minimal> i.e. cloud-init does have an ansible module to run playbooks
[12:53] <minimal> others might use shell scripts with either cloud-init write_files or runcmd using curl to put the scripts onto the machine before cloud-init runs it etc
[13:42] <Odd_Bloke> I suggested something like this a few years back (perhaps only to Canonical folks at a sprint) as a platform-agnostic alternative to "marketplace images": instead of a pre-baked image, you would use off-the-shelf cloud-config with a compatible base image to get approximately the same outcome.
[13:46] <Odd_Bloke> Then the vendor-specific "magic" is all contained in cloud-config so it's easy to understand what's being done to your instance, it's easier to modify how it's being done without having to fight against the vendor's built-in config, and possible to attempt porting the config to, e.g., a newer Ubuntu release (instead of relying on the vendor to update that bionic-based image any day now we
[13:46] <Odd_Bloke> promise :p).
[13:48] <Odd_Bloke> (And the platform-agnostic aspect makes it easier to test locally, move your workload between platforms, or host it on multiple platforms for redundancy, etc.)
[15:37] <minimal> Odd_Bloke: there's the problem/issue of user-data for distro-specific package repos though - would such an off-the-shelf cloud-config have "apt:" and "apk:" and "zypper:" etc sections?
[15:37] <minimal> also there's the matter of other cloud-init modules that are distro-limited, e.g. "lxd" is only for Ubuntu presently...
[17:12] <Odd_Bloke> minimal: I think the main problem to solve there would be how to help users identify "a compatible base image" and/or how to make it very obvious if they attempted to use off-the-shelf cloud-config on an unsupported image: with that in place, the cloud-config (and/or cloud-init itself) could be iterated to expand compatibility.
[17:15] <Odd_Bloke> (In the context of marketplace images, a cloud-config which only works on Ubuntu 22.04 is still more useful for non-Ubuntu users than a pre-baked-on-private-infra 22.04 image.)
[18:22] <blackboxsw> hiya Odd_Bloke :)
[18:23] <blackboxsw> per haroon's:  earlier query about a library of examples there is also a work in progress by our docs team person s-makin to surface a doc url that will represent common categorized set of examples which are vetted and easier to browse.   This doesn't get all the way to a direct searchable pool of images, but it gets a step closer to canned examples that could be used/adapted in various capacities.  
[18:24] <blackboxsw> I think it'd be neat to provide a process to easily allow others to supplement that library of examples to aid new admins in creating complex cloud-config for certain use-cases.
[18:26] <blackboxsw> also to make it easier to cut-n-paste examples for local modification I know Sally has put up multiple PRs to make sure any of docs containing cloud-config examples surface  a copy button action and contain the leading #cloud-config declaration to make sure those examples can be easily modified by others. I realize it's only a small step toward enabling reuse and adaptation by others, but the trend is to make it easier.
[18:27] <blackboxsw> https://github.com/canonical/cloud-init/pull/5427 is one of those PRs
[18:27] -ubottu:#cloud-init- Pull 5427 in canonical/cloud-init "Doc: Module docs pt3" [Open]
[19:10] <Odd_Bloke> blackboxsw: Hey! :)
[19:13] <blackboxsw> ok, enough is enough on milestone 24.2. We've sorted any integration-test platform issues we are seeing and are comfortable with the signal we are getting on clouds. we have a couple of PRs left to land (integration test fixes & ability to define  a downstream version above which new deprecation warnings will only generate info-level message). The plan is to publish tip of main to Ubuntu Oracular today.
[19:15] <blackboxsw> commuinty-notice:  24.2 milestone should be cut tomorrow once we scrub integration test validation. Any open PRs will be targeted to 24.3 milestone, which is really only ~6 weeks away
[19:16] <blackboxsw> community-notice:  24.2 milestone should be cut tomorrow once we scrub integration test validation. Any open PRs will be targeted to 24.3 milestone, which is really only ~6 weeks away
[19:18] <blackboxsw> before we SRU 24.2, there are a couple of downstream fixes/quilt patches we'll be applying to Ubuntu  which are reprsented as the open issues/PRS here https://github.com/canonical/cloud-init/milestone/1
[19:49] <errcsool> I am having some issues with using cloud-init to setup a multipass instance. can i post my info here for debug assistance?
[22:45] <holmanb> errcsool: sure, but no need to ask to ask on irc