[openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Antoni Segura Puimedon celebdor at gmail.com
Tue Aug 16 21:44:53 UTC 2016


On Tue, Aug 16, 2016 at 6:29 AM, Liping Mao (limao) <limao at cisco.com> wrote:

> Hi Kuryr team,
>
> I just notice, this can be fixed in kuryr bind code.
> 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/


Thanks a lot Liping Mao! That's a nice way to solve it.


>
>
> Thanks.
>
> Regards,
> Liping Mao
>
> On 16/8/15 下午11:20, "Liping Mao (limao)" <limao at cisco.com> wrote:
>
> >Hi Kuryr team,
> >
> >I open an issue in docker-libnetwork:
> >https://github.com/docker/libnetwork/issues/1390
> >
> >Appreciate for any idea or comments. Thanks.
> >
> >Regards,
> >Liping Mao
> >
> >
> >On 16/8/12 下午4:08, "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
> >>
> >>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
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160816/688689d4/attachment.html>


More information about the OpenStack-dev mailing list