Public bug reported:
(This is using the ML2 driver with the Linuxbridge agent, along with
libvirt and KVM. This is likely to be agent-specific, but I think at
least some other agents will have the problem.)
1. set Neutron's network_device_mtu to (say) 9000, assuming you've set up an
infrastruct
Public bug reported:
https://docs.openstack.org/neutron/pike/contributor/internals/segments.html
The segments extension says 'this lets you operate on segments',
basically. It doesn't say what a segment is (or refer to external
documentation that does) and it does not say why you might want an A
Public bug reported:
Nova requires some data from a Neutron port and its friends to populate
its port info cache, and ultimately to create the metadata constructs
that are passed on to VMs to inform them of their addresses and routes.
Today, it wanders the datastructures in Neutron, looking at por
Public bug reported:
Nova has opinions on which VIF types are acceptable, and these types
vary by circumstance. vhost-user can be used if QEMU is in use and
hugepages are used on the VM (specifically, if the VM's memory is backed
by an open file, in fact); exclusively virtio mechanisms like vhost
Public bug reported:
I'm trying to get a spec approved for Nova that would make it tell us
what binding types are available. This would seem like a golden
opportunity to clean the interface up.
At the moment Neutron works out a binding_type it will tell Nova (which
Nova must support or else). N
5 matches
Mail list logo
