On 2020-04-27 14:19 -0400, Noah Meyerhans wrote: > On Mon, Apr 27, 2020 at 01:05:34PM +0100, Wookey wrote: > > > There's new work in progress at: https://image-finder.debian.net/
> It should be linked from somewhere more prominent when it's actually > usable. It is not currently. OK. Noted. > > > > The 'genericcloud' and 'nocloud' images are amd64 only. Maybe they > > > > don't make sense for arm64 - what are they for? > > > > > > generic is most flexible, genericcloud has physical hardware drivers > > > disabled, > > > and nocloud is as minimal as possible. The tools, configs, and docs are > > > in > > > this repo: https://salsa.debian.org/cloud-team/debian-cloud-images/ > > > > OK. Sounds like arm64 should be enabled for these too. I'll have a look. > > What do you mean by "enabled"? "generic" arm64 images are available today at > e.g. > https://cloud.debian.org/images/cloud/sid/daily/20200427-245/ and > https://cloud.debian.org/images/cloud/buster/20200425-243/, both of > which are two clicks from https://cloud.debian.org/images/cloud/ Yes 'generic' is built for arm64 but 'genericcloud' and 'nocloud' aren't. By 'enabled' I meant build those other two images for arm64 as well. > > > > I don't know if there are other services that it would make sense to > > > > support, e.g packet provide arm64 online compute. https://www.packet.com > > > > They already provide debian 8,9,10 options, apparently built as docker > > > > images: https://github.com/packethost/packet-images > > > > > > I haven't heard that anyone on the team uses packet - but if someone > > > wanted to > > > extend support for their platform, I imagine we'd accept it. > > > > I've made contact with them to ask about what specific support is > > needed. It seems like a generic image should work, but there are some > > API support tools we could usefully add. I'll have a go with this and > > make changes to /debian-cloud-images/ if appropriate. > > Is packet based on OpenStack? I don't think so. This is what they told me: ---------start------- At Packet you can boot operating systems through our Custom iPXE setup, described in some detail at: https://www.packet.com/developers/docs/servers/operating-systems/custom-ipxe/ We should be able to boot any "server-ready" operating system that way, so long as the image contains NIC drivers for the hardware (typically Mellanox CX-4 in our Arm-based servers, or Intel x710 in our x86 servers). To make a given operating system directly provisionable at Packet we use "Packer" from Hashicorp, and there are some things we bake into the image - no daemons, but there are a few helper scripts for things like iSCSI attach for our block storage that get added to the base image. --------end------ > > Right. And maybe generic cloud works. > > Note that the arm64 cloud kernel is available in bullseye and sid, but > not buster. Arm64 buster images just use the regular ("generic") arm64 > kernel. Ah. OK so the 'generic' and 'genericcloud' names refer to the kernel used? Obviously we can't build an arm64 cloud-kernel version on buster if the package doesn't exist. > It's not necessarily the goal of the cloud kernel to support > every cloud infrastructure in existence, but if there are missing > drivers that prevent it from doing so, we can consider enabling them. Understood. Looks like so long as Mellanox CX-4 is enabled then that may be all that's needed. That seems to be mlx4_en and mlx4_core. Ah cool, and I see that https://cloud.debian.org/images/cloud/ has been updated. That's great, cheers. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature