yahoo-eng-team team mailing list archive

[OpenStack Infra <1605793@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/362822
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c153b9e3da5a6753225d4c367f33267ae19ee5ff
Submitter: Jenkins
Branch:    master

commit c153b9e3da5a6753225d4c367f33267ae19ee5ff
Author: Ihar Hrachyshka <ihrachys@xxxxxxxxxx>
Date:   Sat Aug 27 18:11:50 2016 +0000

    neutron: MTU is now re-calculated for existing networks
    
    With Iee4f5037bf10b73ba98464143b183aacb59c22f2 in for Newton, Neutron
    will re-calculate MTU values for all existing networks on controller
    restart in case MTU configuration options are touched.
    
    Change-Id: Ic6a3466291b881ee11d6044d4f02caf33574edb8
    Closes-Bug: #1605793


** Changed in: openstack-manuals
       Status: In Progress => 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/1605793

Title:
      Calculate MTU on every network fetch instead of on create

Status in neutron:
  Incomplete
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/336805
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit a984f9554cdcbe93c840a1d8f5c04302e9331e79
  Author: Ihar Hrachyshka <ihrachys@xxxxxxxxxx>
  Date:   Sat Jul 2 17:30:21 2016 +0200

      Calculate MTU on every network fetch instead of on create
      
      Today, existing networks may not reflect MTU configured for
      neutron-server, if they were created when neutron-server was using
      different MTU setup for its infrastructure, or when it was using bad
      default values for network MTUs (specifically, before Mitaka, all networks
      were getting MTU = 0 by default, disabling both advertisement and data
      path MTU size enforcement).
      
      This patch stops persisting MTU in the database on network create and
      instead calculate it on every network resource fetch.
      
      DocImpact Now changes to MTU configuration options immediately affect
                existing network MTUs, not just new networks.
      
      UpgradeImpact Existing networks with invalid MTU persisted in database
                    may change their MTU values to reflect configuration.
      
      Change-Id: Iee4f5037bf10b73ba98464143b183aacb59c22f2
      Closes-Bug: #1556182

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