yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51682
[Bug 1587253] [NEW] Make logic network mtu to be Configurable
Public bug reported:
In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow:
------- ------- -------
| VM1 | | VM2 | | VM3 |
------- ------- -------
| | |
| | |
| | |
----------- ----------- -----------
| tenant1 | | tenant2 | | tenant3 |
| network | | network | | network |
----------- ----------- -----------
| | |
| | |
| | |
-------------------------------------------------------
| |
| proivder network |
| mtu=9000 |
-------------------------------------------------------
| | |
| | |
| | |
----------- ----------- -----------
| Physic | | Physic | | physic |
| network1| | network2| | network3|
| mtu=1500| | mtu=1200| | mtu=9000|
----------- ----------- -----------
tenant1 network pass through physic network1
tenant2 network pass through physic network2
tenant3 network pass through physic network3
So, I suggest to make the logic network MTU to be configurable to solve
the problem.
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow:
- ------- ------- -------
- | VM1 | | VM2 | | VM3 |
- ------- ------- -------
- | | |
- | | |
- | | |
- ----------- ----------- -----------
- | tenant1 | | tenant2 | | tenant3 |
- | network | | network | | network |
- ----------- ----------- -----------
- | | |
- | | |
- | | |
- -------------------------------------------------------
- | |
- | proivder network |
- | mtu=9000 |
- -------------------------------------------------------
- | | |
- | | |
- | | |
- ----------- ----------- -----------
- | Physic | | Physic | | physic |
- | network1| | network2| | network3|
- | mtu=1500| | mtu=1200| | mtu=9000|
- ----------- ----------- -----------
+ ------- ------- -------
+ | VM1 | | VM2 | | VM3 |
+ ------- ------- -------
+ | | |
+ | | |
+ | | |
+ ----------- ----------- -----------
+ | tenant1 | | tenant2 | | tenant3 |
+ | network | | network | | network |
+ ----------- ----------- -----------
+ | | |
+ | | |
+ | | |
+ -------------------------------------------------------
+ | |
+ | proivder network |
+ | mtu=9000 |
+ -------------------------------------------------------
+ | | |
+ | | |
+ | | |
+ ----------- ----------- -----------
+ | Physic | | Physic | | physic |
+ | network1| | network2| | network3|
+ | mtu=1500| | mtu=1200| | mtu=9000|
+ ----------- ----------- -----------
tenant1 network pass through physic network1
tenant2 network pass through physic network2
tenant3 network pass through physic network3
So, I suggest to make the logic network MTU to be configurable to solve
the problem.
** Description changed:
In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow:
------- ------- -------
| VM1 | | VM2 | | VM3 |
------- ------- -------
- | | |
+ | | |
| | |
| | |
----------- ----------- -----------
| tenant1 | | tenant2 | | tenant3 |
| network | | network | | network |
----------- ----------- -----------
| | |
| | |
| | |
-------------------------------------------------------
| |
| proivder network |
| mtu=9000 |
-------------------------------------------------------
| | |
| | |
| | |
----------- ----------- -----------
| Physic | | Physic | | physic |
| network1| | network2| | network3|
| mtu=1500| | mtu=1200| | mtu=9000|
----------- ----------- -----------
tenant1 network pass through physic network1
tenant2 network pass through physic network2
tenant3 network pass through physic network3
So, I suggest to make the logic network MTU to be configurable to solve
the problem.
** Description changed:
In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow:
------- ------- -------
| VM1 | | VM2 | | VM3 |
------- ------- -------
- | | |
+ | | |
| | |
| | |
----------- ----------- -----------
| tenant1 | | tenant2 | | tenant3 |
| network | | network | | network |
----------- ----------- -----------
| | |
| | |
| | |
-------------------------------------------------------
| |
| proivder network |
| mtu=9000 |
-------------------------------------------------------
| | |
| | |
| | |
----------- ----------- -----------
| Physic | | Physic | | physic |
| network1| | network2| | network3|
| mtu=1500| | mtu=1200| | mtu=9000|
----------- ----------- -----------
tenant1 network pass through physic network1
tenant2 network pass through physic network2
tenant3 network pass through physic network3
So, I suggest to make the logic network MTU to be configurable to solve
the problem.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1587253
Title:
Make logic network mtu to be Configurable
Status in neutron:
New
Bug description:
In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow:
------- ------- -------
| VM1 | | VM2 | | VM3 |
------- ------- -------
| | |
| | |
| | |
----------- ----------- -----------
| tenant1 | | tenant2 | | tenant3 |
| network | | network | | network |
----------- ----------- -----------
| | |
| | |
| | |
-------------------------------------------------------
| |
| proivder network |
| mtu=9000 |
-------------------------------------------------------
| | |
| | |
| | |
----------- ----------- -----------
| Physic | | Physic | | physic |
| network1| | network2| | network3|
| mtu=1500| | mtu=1200| | mtu=9000|
----------- ----------- -----------
tenant1 network pass through physic network1
tenant2 network pass through physic network2
tenant3 network pass through physic network3
So, I suggest to make the logic network MTU to be configurable to
solve the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1587253/+subscriptions
Follow ups
