> Andrew's question is a bit higher level than that, and mostly boils down > to "Which cloud environments do we actually want to support with the > cloud kernel?"
That's right. And I'd like it to include GCE, but there are a lot of cloud environments out there so drawing a line somewhere can help keep the cloud kernel lean, which appears to be one of the goals. > > specifically targeted Amazon EC2 and Microsoft Azure.” > Yes, this is the documented target. Where is it documented? https://wiki.debian.org/Cloud and https://wiki.debian.org/Cloud/SystemsComparison both imply at least AWS, Azure, GCP, and OpenStack, but I didn't find a document about the kernel specifically yet. I don't mean to disagree, but to understand. > We can support more clouds. It is just a matter of taking care of it. > > I currently play with splitting the modules into multiple different > sets, like almost all other distributions already do. We would not need > to do multiple builds then and more targeted packages would be possible > if needed. That could make sense. Some would not be split out, like virtio, I think, but others like gVNIC (gve) obviously could be. > We already backport the Microsoft MANA network driver. So at least > backports to stable are not that of a problem, if someone does it. Interesting. I assume there's probably some backporting of Amazon ENA (and EFA?) as well. To use GCP's current generation bare metal requires the Intel IDPF driver that landed in 6.7. Other OS vendors have backported it to various versions, so it ought to be possible to backport it to 6.1 for Debian. I'll talk to some people here about how we might do that. Kind regards, Andrew
