Re: Generic image not working with IPv6 only
>>>>> "Jeremy" == Jeremy Stanley <fungi@yuggoth.org> writes:
Jeremy> 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.
Jeremy> I don't find it confusing, just pointing out that Bastian's
Jeremy> recommendation was presented as an assumption that all users
Jeremy> uploading images into OpenStack clouds control the
Jeremy> underlying configuration of those clouds.
Speaking as an relative outsider, I do find it confusing.
I'd expect the generic cloud image to be generally usable in a wide
set of openstack clouds.
Especially for things with generic in their name, I'd expect Debian to
be fairly sensitive to incompatibilities between those images and
libre cloud options.
I'd expect the members of the team who do work for proprietary cloud providers
or who do spend a significant chunk of their time working with
proprietary solutions to be particularly sensitive to issues in this
area including naming.
Debian should be perceived as supporting the free software community in
all its activities.
The current state, and this thread does not achieve that.
Some possible solutions:
* be somewhat more permissive in what goes into the cloud kernel.
* If the cloud kernel really is going to be the proprietry cloud kernel,
retire the generic cloud image, and just have a generic image.
Reply to: