On Fri, Aug 16, 2024 at 10:28:00AM -0400, Noah Meyerhans wrote:
>
> This is 100% exactly the reason why we recommend using the generic
> images for OpenStack. The fact that there are hundreds of independent
> OpenStack providers around the world, all of which may choose to present
> their own VM device model, is exactly why we don't try to target them
> with the cloud kernel. Use the generic kernel in the generic images and
> be happy. It all works.
This is a bit out of scope for the Debian Cloud list, but perhaps
those who are frustated that there is a huge variability in what
kernel drivers are needed for some random OpenStack installation could
take that back to the OpenStack developers, and see if they can try to
drive some standardized, or at least default, set of virtualized
devices. If the goal is to complete with the hyperscaler cloud
providers, the fact that you have no idea what is needed for a VM
image for "some random OpenStack provider" is a bug, not a feature.
And of course, there's nothing Debian can do, since if we add one
driver, then someone else will very likely pop up with some other
example of some other OpenStack setup that requires some other driver.
Lather. Rinse. Repeat.
> I'm not sure where the confusion lies.
With the users of OpenStack? :-)
- Ted
