Project

General

Profile

Actions

Feature #21694

closed

Add MTU support for subnets

Added by Baptiste Agasse about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Network
Target version:
Fixed in Releases:
Found in Releases:

Description

Currently it's not possible to change the MTU value of a subnet, and all network interfaces are configured with the default MTU value without possibility to override it easily.
It would be nice to add an MTU field to subnet and use this value to configure the MTU of network interfaces in this subnet at provisioning time.


Related issues 1 (0 open1 closed)

Related to Hammer CLI - Bug #23401: Subnet command does not display MTUClosedMarek HulánActions
Actions #1

Updated by Marek Hulán about 6 years ago

  • Tracker changed from Bug to Feature
Actions #2

Updated by Ohad Levy about 6 years ago

how about using a parameter?

Actions #3

Updated by Baptiste Agasse about 6 years ago

We workaround the lack of MTU in subnet like this at this time. But we have some hosts with multiple interfaces with different MTUs (eg: admin iface with default MTU=1500, Storage ifces with MTU=9000,and sometimes ifaces with MTU=1496) and these cases not easy to handle.
If we add the MTU directly in the subnet, we can provision hosts, linked to multiple subnets and all interfaces of theses hosts will take the right MTU for all ifaces.

How I was thinking about it is:
  • Adding optional 'mtu' field to subnets
  • Modify provisioning templates to add MTU support and be backward compatible with foreman versions that don't support mtu in subnets (try if subnet respond to 'mtu'. If it's the case and the value is not blank, set the provided MTU, else don't touch anything).

Any pointers/advises are welcome.

Actions #4

Updated by Marek Hulán about 6 years ago

I think you can achieve the same with subnet parameters today but I agree that built-in support would be nice. Do you plan to work on the patch? Also the template does not have to be backwards compatible I think, we update all shipped template with every seed and we lock them. Since templates are now version (branch per release in community-repo) we can simply rely on the feature being present.

Actions #5

Updated by Baptiste Agasse about 6 years ago

Patches for foreman and templates are ready, I just wanted some feedback on this before pushing.

Actions #6

Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Baptiste Agasse
  • Pull request https://github.com/theforeman/foreman/pull/5017 added
Actions #7

Updated by Marek Hulán about 6 years ago

Obviously I can't speak for others but you have my thumb :-)

Actions #8

Updated by The Foreman Bot about 6 years ago

  • Pull request https://github.com/theforeman/community-templates/pull/442 added
Actions #9

Updated by Timo Goebel over 5 years ago

  • translation missing: en.field_release set to 330
Actions #10

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #11

Updated by Marek Hulán over 5 years ago

  • Related to Bug #23401: Subnet command does not display MTU added
Actions

Also available in: Atom PDF