2022-01-06 18:03:50 tomalok: would it make sense to archive https://gitlab.alpinelinux.org/alpine/cloud/alpine-ec2-ami? 2022-01-07 00:52:36 ikke: i was thinking about clicking that button, but wasn't 100% sure what the consequences were going to be. 2022-01-07 05:09:26 Making it read-only and addi g a header 2022-01-07 18:12:26 Someone building alpine images for Azure: https://lists.alpinelinux.org/~alpine/devel/%3CDM6PR19MB3834274AB5359A813DE683D7A84D9%40DM6PR19MB3834.namprd19.prod.outlook.com%3E 2022-01-07 19:18:21 ikke: I've been building images for Azure, just haven't (yet) been testing them :-) 2022-01-07 19:54:10 just curious - has there been any demand for alpine cloud images? 2022-01-07 19:54:17 i particularly have azure in mind 2022-01-07 20:26:26 danieli: I think there are people out there using them, just not sure of numbers 2022-01-07 20:28:27 I guess it also depends on what type of images, the "official" alpine cloud images are intended to be AMIs (and the Azure, GCE, etc) equivalent easily usable by everyone. Whereas I have my own script for creating disk images tailored for various clouds that you have to run yourself to create your own tailored "local" AMIs/etc 2022-01-07 22:41:12 i replied to the guy, pointed him at https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images 2022-01-07 22:41:43 will poke at what he's done and see if there's anything useful when we get to developing an azure module 2022-01-07 22:43:32 at the moment i'm working on the "tiny-cloud" bootstrapper part of things: https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/tree/initial/tiny-cloud 2022-01-07 22:46:17 need to bring in the mdev stuff (EBS nvme / ENI secondary IPv4/IPv6) we used to have in alpine-ec2-ami into tiny-cloud and multi-cloud-ify that 2022-01-07 23:04:12 tomalok: I'm worked on reducing the cloud-init deps currently 2022-01-08 00:39:08 minimal: a noble cause... but pretty sure tiny-cloud will still be smaller :) (but perhaps with fewer bells & whistles). at some point in the near future, though, i do want to get the "cloudinit" bootstrap dimension working with alpine-cloud-images 2022-01-08 00:52:30 tomalok: yeah, its the size versus functionality conundrum 2022-01-31 00:25:04 FWIW, Tiny Cloud 2.0.0 has been released - https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud/-/releases/2.0.0 and APKs have been built... though i'm not quite sure why half of the arches for edge still say 2.0.0_rc3 (no difference between that and 2.0.0) 2022-01-31 00:50:54 x86_64/aarch64 are building qtwebengine, and s390x is stuck 2022-01-31 00:51:15 and i think ppc is too 2022-01-31 01:15:52 ah, cool, that makes sense, thanks! 2022-01-31 01:16:58 ^~^ 2022-01-31 11:48:27 Hey! Is there a reason Alpine solely releases cloud images on AWS and not generic cloudinit or openstack images? 2022-01-31 11:49:53 I see that cloud-init is in the community repository and not main, so suspect that might be the reason? As it's not officially supported 2022-01-31 11:50:17 hammothy: it's something we're working on 2022-01-31 11:50:30 We support AWS as someone in the community already had something for that 2022-01-31 11:51:19 oh nice! Do you have a timeline for that? I think I'm just gonna use https://github.com/alpinelinux/alpine-make-vm-image to generate some for myself 2022-01-31 11:51:48 hammothy: cloud-init is packaged for Alpine but there is currently no "official" Alpine cloud image using it 2022-01-31 11:51:53 I'm just not sure if that'll work for arm so it might require some messing with 2022-01-31 11:52:08 hammothy: I am the Alpine maintainer for cloud-init 2022-01-31 11:52:57 hammothy: you might want to look at my script as its specifically designed for creating cloud-init enabled images: https://github.com/dermotbradley/create-alpine-disk-image 2022-01-31 11:54:01 Ah! Thank you, I'll check that out 2022-01-31 11:55:53 basically the main direction of Alpine "official" cloud images seems to be to use an alternative "cloud-init compatible" solution that only supports a limited number of cloud providers 2022-01-31 15:50:04 hammothy: yesterday i released Tiny Cloud (https://gitlab.alpinelinux.org/alpine/cloud/tiny-cloud) which is the tiny alternative to cloud-init -- although it's primarily AWS at this point is basic functionality should also work with Azure, GCP, and OCI. (patches welcome for other clouds). 2022-01-31 16:02:10 hammothy: alpine-cloud-images (https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images) is our build system for building and publishing public images for all cloud image variants across a bunch of dimensions -- arch (x86_64/aarch64), firmware (bios/uefi), bootstrap (tiny), and cloud (aws) -- and it supports customization (i use it to build 2022-01-31 16:02:11 some tailor-made base images for another project). Now that Tiny Cloud is released, the plan is to also support and build cloud-init bootstrap and other cloud providers (GCP, OCI, Azure) -- it's all fairly modular, and of course patches welcome! 2022-01-31 17:10:37 tomalok: Having a look at tiny-cloud it’s missing one of the things I really liked about cloud-init being that cloud init works off loading data from a mounted disk and not from having to modify the disk of the VM. Would loading data from an extra mounted disk be completely out the window? 2022-01-31 18:10:11 hammothy: what kind of data? this might be something you could implement as a part of the instances' UserData script? 2022-01-31 20:01:59 tomalok: I believe he's referring to cloud-init's NoCloud DataSources' support from obtaining meta-data/user-data/network-config via a seperate ISOFS or VFAT formatted sr/sd device 2022-01-31 20:21:28 minimal: is it a virtual filesystem that maps to the instanc's IMDS? 2022-01-31 20:22:12 tomalok: I mentioned NOCloud, there is *no* IMDS (Metadata Server) 2022-01-31 20:22:56 basically its an ISO/VFAT fs with a label CIDATA containing 1 or more of those files specifically names 2022-01-31 20:24:05 have a look at the "cloud-localds" scripts containing in the cloud-utils package, its the usual method for creating these 2022-01-31 20:25:31 e.g. cloud-localds --verbose --disk-format raw --filesystem iso9660 --network-config=network-config-v2.yaml ../dhcp-seed.iso user-data.yaml meta-data.yaml 2022-01-31 20:26:02 that's how I generate a dhcp-seed.iso file I use with QEMU/Virtualbox and cloud-init NoCloud 2022-01-31 20:26:32 will take a look, thanks. in theory i assume it'd be possible to make a "cloud" plugin for "nocloud" so Tiny Cloud's imds client could pull data from that... 2022-01-31 20:28:19 ...but i do want to get cloud-init variants and the other major cloud providers in alpine-cloud-images soon 2022-01-31 20:28:53 should be simple, its just a filesystem with a specific label - if you run cloud-init with NoCloud and debug enabled you'll see it searching for available devices with the CIDATA label for it to mount to grab the YAML files from 2022-01-31 20:31:52 Openstack (used to) work in similar fashion to NoCloud using what they called a ConfigDrive, again (from memory) another ISO in a certain format