Open Stack

Hi Ihar,

Thanks for your comments.
Agree, kuryr need to load mtu in neutron network.

I submit a bug to track this:
https://bugs.launchpad.net/kuryr-libnetwork/+bug/1613528

And patch sets are here:
https://review.openstack.org/#/c/355712/
https://review.openstack.org/#/c/355714/


Generally, when kuryr create docker interface, it call
neturon network api to get mtu, then set it on the interface.

Thanks.


Regards,
Liping Mao

On 16/8/17 上午8:20, "Ihar Hrachyshka" <ihrachys at redhat.com> wrote:

>Liping Mao (limao) <limao at cisco.com> wrote:
>
>> Hi Kuryr team,
>>
>> When the network in neutron using overlay for vm,
>> it will use dhcp option to control the VM interface MTU,
>> but for docker, the ip address does not get from dhcp.
>> So it will not set up proper MTU in container.
>>
>> Two work-around in my mind now:
>> 1. Set the default MTU in docker to 1450 or less.
>> 2. Manually configure MTU after container start up.
>>
>> But both of these are not good, the idea way in my mind
>> is when libnetwork Call remote driver create network,
>> kuryr create neutron network, then return Proper MTU to libnetwork,
>> docker use this MTU for this network. But docker remote driver
>> does not support this.
>>
>> Or maybe let user config MTU in remote driver,
>> a little similar with overlay driver:
>> https://github.com/docker/libnetwork/pull/1349
>
>Please don’t allow to configure MTU in any specific way, just make sure
>that the MTU value on neutron network is applied on the container side.
>Also, enforcing it to 1450 is not going to work for lots and lots of
>cases.  
>Enforcing it to anything won’t work, because MTUs depend on network type.
>
>>
>> But now, seems like remote driver will not do similar things.
>>
>> Any idea to solve this problem? Thanks.
>>
>>
>> Regards,
>> Liping Mao
>>
>>
>> 
>>_________________________________________________________________________
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev