2023-11-02 14:29:08 <alethkit> Hello
2023-11-02 14:29:23 <alethkit> I presume this is the channel to talk about tiny-cloud as well?
2023-11-02 14:32:03 <ikke> yes
2023-11-02 18:35:52 <alethkit> Right. I was wondering what the specific options for networking configuration were, apart from DHCp
2023-11-02 18:35:59 <alethkit> because I notice I continue to be very confused
2023-11-02 18:42:06 <minimal> alethkit: so you're referring to tiny-cloud. What leads to think there is any method to specify network configuration with tiny-cloud NoCloud?
2023-11-02 18:42:16 <minimal> tomalok: maybe you want to jump in here?
2023-11-02 18:44:31 <ikke> iirc, tomolak is away
2023-11-02 18:45:31 <minimal> oh right, hiking or something?
2023-11-03 07:31:14 <ncopa> alethkit: the network options are very very barebones.
2023-11-03 07:32:09 <ncopa> but you can pass in an interfaces file
2023-11-04 15:48:05 <alethkit> ah, right
2023-11-04 15:48:11 <alethkit> probably not the right tool, then
2023-11-04 15:54:28 <minimal> it's not clear exactly what you're trying to do
2023-11-04 15:57:43 <minimal> alethkit: if you're wanting to use NoCloud-Net with a network-config v1 or v2 file fetched and applied, well even cloud-init doesn't (currently) support that
2023-11-04 16:40:20 <tomalok> alethkit: maybe start out by sharing what you're trying to accomplish in what environment, and what you've tried so far?
2023-11-04 16:41:32 <tomalok> because user-data can carry a shell script as a payload essentially anything is possible (as long as you can provide user-data in whatever environment you're in)
2023-11-04 21:44:52 <alethkit> oh, right
2023-11-04 21:45:40 <alethkit> I wanted to have the images receive IP configuration from an IMDS (Vultr, probably), but I also wanted the ability to set the address statically on my Proxmox cluster
2023-11-04 23:17:22 <minimal> alethkit: tiny-cloud doesn't have support for Vultr metadata server currently whereas cloud-init does
2023-11-04 23:22:44 <minimal> Proxmox uses NoCloud (or ConfigDrive) ISOs which cloud-init supports. I'm not sure about the extent of tiny-cloud's support for this
2023-11-05 00:08:03 <tomalok> from a glance at https://www.vultr.com/metadata it doesn't appear that Vultr is compatible with any of the currently supported clouds -- nor does there appear to be any sort of payload for "user-data"
2023-11-05 00:12:27 <tomalok> tiny-cloud's nocloud support will execute a script (first line starts with #!/bin/sh or similar)  if provieded as user-data content.  #cloud-config user-data content handler currently says "TODO", but Alpine is using a subset of this for an experimental autoconfig -- for this it's the tiny-cloud-alpine APK
2023-11-05 00:21:12 <minimal> tomalok: have a look at the cloud-init DS for Vultr, "user-data" is fetched from the IMDS, as is network config
2023-11-05 00:28:55 <tomalok> it doesn't appear to be a separate standalone kind of thing.  maybe you can tweak these settings individually, or grab whatever Vultr sets for you, but a per-instance generic payload doesn't seem to exist
2023-11-05 00:31:10 <tomalok> that said, setting up a "vultr" cloud that gets info from vultr IMDS and sets up various things would probably be relatively straightforward
2023-11-05 00:31:54 <minimal> tomalok: look at the cloud-init code: https://github.com/canonical/cloud-init/blob/main/cloudinit/sources/DataSourceVultr.py#L57
2023-11-05 00:32:26 <minimal> yes the Vultr Metadata docs doesn't seem to mention this put that doesn't mean it doesn't exist
2023-11-05 00:34:19 <tomalok> ah, yes.  have to love complete documentation.  (if and when you can find it)
2023-11-05 00:36:27 <minimal> and the same for Hetzner? and for Exoscale? and for Linode? etc.....then you're halfway to rewriting cloud-init lol
2023-11-28 14:54:25 <ncopa> i think we should support /etc/tiny-cloud.disabled in tinycloud
2023-11-28 14:54:36 <ncopa> see https://gitlab.alpinelinux.org/alpine/mkinitfs/-/merge_requests/133
2023-11-28 14:58:44 <ncopa> tomalok: ok with you? https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/merge_requests/99
2023-11-29 00:53:56 <tomalok> ncopa: is that a common way of disabling things?  assuming that's just a file touched into existence?
2023-11-29 00:54:18 <tomalok> also, what specific problem is that meant to solve?  ;)
2023-11-29 08:33:18 <ncopa> tomalok: maybe not very common, but it happens. openrc has some of those things for skipping fsck and similar IIRC
2023-11-29 08:35:06 <ncopa> the problem it solves is a way to prevent tiny-cloud to run - maybe due to some auto detection, and you have no control over the detection mechanism
2023-11-29 08:35:21 <ncopa> cloud-init has something similar
2023-11-29 08:35:44 <ncopa> https://cloudinit.readthedocs.io/en/latest/howto/disable_cloud_init.html#method-1-text-file
2023-11-29 14:29:17 <tomalok> ncopa: will try to take a look soon
2023-11-30 12:20:42 <ncopa> new alpine releases. I added cloud images to the release checklist: https://gitlab.alpinelinux.org/alpine/aports/-/issues/15521
2023-11-30 14:35:08 <tomalok> ncopa: all the way back to 3.15?
2023-11-30 14:38:47 <ikke> yes
2023-11-30 14:39:08 <ikke> 3.15.11, 3.16.8, 3.17.6 and 3.18.4
2023-11-30 14:39:16 <ikke> 3.18.5*
2023-11-30 15:05:11 <tomalok> will see if "end_of_life" can be extended in order to build it.
2023-11-30 15:05:52 <ncopa> we may not need create cloud images for the the EOL'ed
2023-11-30 15:06:06 <ncopa> woudl be nice, but not worth spending too much time on
2023-11-30 15:06:39 <tomalok> we'll see if the config value overrides what's picked up from the JSON
2023-11-30 15:08:12 <tomalok> looks like the value in JSON is authoritative
2023-11-30 15:12:21 <tomalok> might have found where i can override
2023-11-30 15:18:24 <tomalok> helps if one saves the config file containing the override