[12:26] <nikconwell> Hi falcojr thanks for your help yesterday.
[12:28] <nikconwell> I got things working on a RHEL cloud image. Needed a couple of fixes, adding #cloud-init to the top of my yaml files, and also my network-config had a route of - to: default which for some reason I thought was OK, but it needed to be - to: 0.0.0.0/0
[12:28] <nikconwell> But apart from that, seems to be good now. I may bring this back to ubuntu to see if it's OK there now.
[12:29] <nikconwell> And also, you were also right on the call about rerunning the cloud-init vs. just starting again fresh. I think in my debugging it wasn't getting as far as I wanted it to do the network again so my settings were not being honored.
[12:29] <nikconwell> Challenge catching things the first time vs. trying to redo.
[12:30] <nikconwell> Anyhoo, many thanks for your help getting me on the right path.
[17:37] <beantaxi> Hello all. I have a specific use case that seems to be popping up -- I want to run a startup script per-instance, only the VM is from a provider that doesn't seem to support creating a VM from the cmdline and specifying user data.
[17:38] <beantaxi> In order to reliably get 'per-instance' for an unknown arbitrary provider, I might have to settle for ...
[17:39] <beantaxi> 1. Create VM 2. Upload a script to /var/lib/cloud/scripts/per-boot 3. Reboot the server 4. Delete the script
[17:40] <beantaxi> How much of this is supported through cloud-init itself? I'd prefer to run cloud-init commands, than destructively poke around folders. Thanks!
[17:49] <minimal> beantaxi: side question: which provider is this?
[18:08] <beantaxi> minimal: I'm currently working with OVHCloud and IONOS. 
[18:08] <beantaxi> I found some article using terraform to setup OVH, but it wasn't that promising, was a bit old, and seemed to be using a 0.0.0.0.0.0.1 version of an ovh terraform provider
[18:09] <beantaxi> I figured best case, I'd blow a day getting it to work, and 1-day-each wouldn't scale very well to N providers, so I got to thinking about a quicker plan.
[18:11] <minimal> beantaxi: those are both OpenStack cloud-init DataSource, right? or ConfigDrive?
[18:16] <minimal> beantaxi: for OVHCloud aren't you using "nova boot" to start instances? It accepts a "--user-data" option
[19:58] <beantaxi_> minimal: I've not looked into nova boot .. I don't know what it is. I also don't know how OpenStack might figure into this. I don't know much about OpenStack. I'm just now making a foray into cloud providers outside the Big 3
[19:59] <beantaxi_> Even if I am able to solve the issue for OVH and IONOS, I'm interested in answers to my original questions, for my own cloud-init education.
[19:59] <beantaxi_> However, a short-term fix that lets me use OVH is appreciated! I'll have a look at `nova boot`
[20:52] <minimal> beantaxi: that was just from a OVHCloud document I found: https://help.ovhcloud.com/csm/en-gb-public-cloud-compute-launch-script-at-instance-creation?id=kb_article_view&sysparm_article=KB0050914
[20:53] <minimal> beantaxi: likewise info for IONOS: https://docs.ionos.com/cloud/compute-services/cubes/dcd-how-tos/boot-cloud-init-cubes
[20:54] <minimal> beantaxi_: ^^^
[22:12] <catred> beantaxi_: I think passing user-data to the instance when it's created is the best and most commonly used option but you can also use MIME text/x-shellscript-per-boot e.g. https://docs.cloud-init.io/en/latest/explanation/format.html#mime-multi-part-archive
[22:50] <holmanb> ani: thanks for filing the sysconfig renderer issue and PR!
[22:51] <holmanb> ani: I'll try to get in a review in tomorrow
[22:52] <holmanb> ani: just curious - I thought redhat switched to the network manager renderer, is that not the case?