On 2024-08-16 10:28:00 -0400 (-0400), Noah Meyerhans wrote: > On Fri, Aug 16, 2024 at 02:21:53PM +0000, Jeremy Stanley wrote: > > > You are free to reconfigure OpenStack to use virtio for the cdrom. > > > > Well, the cloud provider may be free to. An end user of a public > > cloud typically doesn't have much influence over the choices that > > service provider has made, but I suppose they're free to take their > > business elsewhere if they want an environment where they can boot > > images that use Debian's cloud kernel. > > > > While OpenStack is increasingly popular for private cloud operations > > these days, it was originally designed for use as a public cloud > > service in competition with the well-known proprietary cloud > > providers. There are hundreds of public clouds worldwide whose > > services are really just OpenStack, though they often don't > > advertise that fact. (Known OpenStack public clouds account for more > > data centers and regions across the globe than the proprietary > > providers put together, at last count.) The biggest challenge, as > > this current concern highlights well, is that you can't assume the > > same images which work in one provider will work in another, due to > > the difference in configuration choices the provider might make. > > 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. > > I'm not sure where the confusion lies.
I don't find it confusing, just pointing out that Bastian's recommendation was presented as an assumption that all users uploading images into OpenStack clouds control the underlying configuration of those clouds. It *may* be possible for an end user to set hw_cdrom_bus=virtio on image properties if the cloud is using qemu/kvm for compute services, but that's not always going to be the case (especially if the underlying hypervisor is Xen or VMware). I'm agreeing with you, images based on Debian's generic kernel instead of the cloud kernel will be more widely supported because virtual machines in different OpenStack clouds need a variety of drivers based on choices made by the people who configured them. -- Jeremy Stanley
signature.asc
Description: PGP signature
