[15:19] Hello all ... I'm following the instructions on the cloud-init readthedocs for Hacking on cloud-init. I've signed the contributor license agreement, and from what I'm reading I should appear on the contributor-agreement-canonical group page. There's no mention of an approval process or a delay, but I'm not seeing myself on the list, so I want to make sure I'm not missing a step. Thanks! [15:22] beantaxi: i reckon most of the people who could approve you are on vacation for another week [15:39] meena: Makes sense :) Is it frowned upon to submit a PR before being approved? No urgency, just wanted to get my first PR in before the New Year as a purely arbitrary deadline. [15:40] beantaxi: it is not frowned upon [15:45] meena: Thanks! I'll try and hit my deadline [15:51] I also have a cloud-init question ... I've recently spun up an OVHCloud VPS. It does run cloud-init and `cloud-id` reports openstack. I've read the readthedocs on openstack, but I'm not sure where to start to `cloud-init` my instance initialization. Do I copy my script to /var/lib/cloud/scripts/per-instance, somehow trick the instance into thinking it's on its first boot, and then reboot? Or is there [15:51] something more direct. Thanks! [16:11] beantaxi: why is cloud-id reporting OpenStack? what does ds-identify say? [18:30] meena: Your question is Greek to me to be honest ... but after checking the docs, running the ds-identify command I found, and looking at the output, I believe your question to mean that there are a number of reasons why a VM would be identified as OpenStack and you are asking which one [18:30] From my outpui ... is_ds_enabled(IBMCloud) = true. [18:31] Is this what you are asking? If not I can look elsewhere [19:52] beantaxi: im just confused why an OVHCloud VPS would be identified as OpenStack, that seems… buggy, so i was wondering what ds-identify thinks [21:07] meena: I'm not familiar with OpenStack so I'm not sure. But OVHCloud makes a number of references to OpenStack and offers OpenStack techonlogies as a feature. [21:11] beantaxi: ah, [21:18] meena: go ooon ... :) [21:25] beantaxi: most clouds copy EC2, i didn't realize OVH was based or copying OpenStack :D [21:36] meena: Interesting! I didn't realize most clouds copy EC2. I guess a lot of them are actually on EC2 and so they get it for free [21:38] Revisiting my initial question, I think I can generalize it to I have a VPS, and that VPS uses cloud-init (hooray!), but I don't see anything like the AWS EC2 CLI command, or AWS Console field(s), which let me specify cloud-init scripts upon instance creation. Am I missing someething basic? And if not, and I have to copy a script to /v/l/c/s/per-instance, trick the instance into thinking it is new, [21:38] and then reboot ... if I have to do all that, then how do I do it? [22:12] in what ways does the cloud-init autoinstaller in ubuntu 20.04 depend on cloud init modules? The "autoinstall" section of the yaml seems to not be present in the cloud-init docs, is that an ubuntu-specific addon? Does subiquity just use cloud-init to process a particular subset for autoinstallation? I ask because I'm trying to mount a partition for the installer to use for installing APT packages, and [22:12] there seems to be https://curtin.readthedocs.io/en/latest/topics/storage.html vs disk-setup and mounts from cloud-init [23:53] are curtin and cloud-init related? or do they just share configuration formats? (or, something else?)