yahoo-eng-team team mailing list archive

[xiewj <36429515@xxxxxx>]

Public bug reported:

'segment_mtu' appeared in the annotation of
'physical_network_mtus'，However,the ‘segment_mtu’ option of the ML2
configuration has been deprecated.

reference to http://docs.openstack.org/releasenotes/neutron/mitaka.html#id3
'''
Deprecation Notes 
The ‘segment_mtu’ option of the ML2 configuration has been deprecated and replaced with the ‘global_physnet_mtu’ option in the main Neutron configuration. 

'''

But ‘segment_mtu’ still appeared in the annotation of
'physical_network_mtus' in the following file:

In the ml2_conf.ini file:
[ml2]
# A list of mappings of physical networks to MTU values. The format of the
# mapping is <physnet>:<mtu val>. This mapping allows specifying a physical
# network MTU value that differs from the default segment_mtu value. (list
# value)
#physical_network_mtus =

'segment_mtu' still appeared in Comments section "# network MTU value
that differs from the default segment_mtu value."

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  'segment_mtu' appeared in the annotation of
  'physical_network_mtus'，However,the ‘segment_mtu’ option of the ML2
  configuration has been deprecated.

Status in neutron:
  New

Bug description:
  'segment_mtu' appeared in the annotation of
  'physical_network_mtus'，However,the ‘segment_mtu’ option of the ML2
  configuration has been deprecated.

  reference to http://docs.openstack.org/releasenotes/neutron/mitaka.html#id3
  '''
  Deprecation Notes 
  The ‘segment_mtu’ option of the ML2 configuration has been deprecated and replaced with the ‘global_physnet_mtu’ option in the main Neutron configuration. 

  '''

  But ‘segment_mtu’ still appeared in the annotation of
  'physical_network_mtus' in the following file:

  In the ml2_conf.ini file:
  [ml2]
  # A list of mappings of physical networks to MTU values. The format of the
  # mapping is <physnet>:<mtu val>. This mapping allows specifying a physical
  # network MTU value that differs from the default segment_mtu value. (list
  # value)
  #physical_network_mtus =

  'segment_mtu' still appeared in Comments section "# network MTU value
  that differs from the default segment_mtu value."

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