yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1671634@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: In Progress => Won't Fix

** Changed in: neutron
       Status: Won't Fix => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1671634

Title:
  [RFE] Allow to set MTU for networks

Status in neutron:
  Fix Released

Bug description:
  ATM neutron does allow to configure MTU for networks to reflect
  underlying infrastructure, but only to operators, and only by changing
  configuration options.

  Ideally, users would be allowed to modify MTU for networks (to
  simplify matters, on creation only, though we can also look at
  resource updates) to accommodate for custom workloads relying on
  specific MTUs. Or maybe sometimes users want to get consistent MTUs
  across all their networks instead of having different MTUs based on
  network type backing their networks. Both of those use cases would be
  served by allowing PUT for 'mtu' network attribute.

  I guess it will require a fake extension to signal the change in
  behavior, even while the implementation may still lay in existing
  plugin code handling MTUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1671634/+subscriptions