add support for "decrement-container-interfaces-mtu" config option

Bug #1569802 reported by Dimiter Naydenov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
High
Unassigned

Bug Description

Juju should allow passing a "decrement-container-interfaces-mtu" bootstrap option (immutable once set), with a default value of 50.

This will then be used to configure container interfaces MTU based on the parent bridge interfaces on the host machine, in order to support VLANs and more complex networking setups (e.g. neutron-gateway running in an lxd container).

IRC log from the discussion: http://paste.ubuntu.com/15807627/

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta4 → 2.0-rc1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-rc1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta6 → 2.0-beta7
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta7 → 2.0-beta8
Changed in juju-core:
milestone: 2.0-beta8 → 2.0-rc1
Changed in juju-core:
milestone: 2.0-rc1 → 2.0.0
Changed in juju-core:
milestone: 2.0.0 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

Ante, you mentioned in the last chat we had that you think this might be unnecessary after all.
Could you please add a comment to clarify?

Changed in juju:
status: Triaged → Incomplete
Revision history for this message
Ante Karamatić (ivoks) wrote :

There must have been a change in how bridges on LXC and LXD are created, because I don't see this being needed anymore with LXD containers. I don't have same issues I had before, when only LXC was used.

Changed in juju:
status: Incomplete → Invalid
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.