Project

General

Profile

Feature #21694

Add MTU support for subnets

Added by Baptiste Agasse 9 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Category:
Network
Target version:
Team Backlog:
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

Related to Hammer CLI - Bug #23401: Subnet command does not display MTUClosed2018-04-26

Associated revisions

Revision f175f751 (diff)
Added by Baptiste Agasse 4 months ago

fixes #21694 - Add MTU to subnet

Revision 92c17a1a (diff)
Added by Baptiste Agasse 4 months ago

fixes #21694 - Add MTU to subnet and interface API

Revision 6b65706a (diff)
Added by Baptiste Agasse 4 months ago

fixes #21694 - Add consistency validation for MTU and VLAN

Revision d313cc81 (diff)
Added by Baptiste Agasse 4 months ago

fixes #21694 - Add MTU support for kickstart installations

History

#1 Updated by Marek Hulán 9 months ago

  • Tracker changed from Bug to Feature

#2 Updated by Ohad Levy 9 months ago

how about using a parameter?

#3 Updated by Baptiste Agasse 9 months 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.

#4 Updated by Marek Hulán 9 months 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.

#5 Updated by Baptiste Agasse 9 months ago

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

#6 Updated by The Foreman Bot 9 months ago

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

#7 Updated by Marek Hulán 9 months ago

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

#8 Updated by The Foreman Bot 9 months ago

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

#9 Updated by Timo Goebel 4 months ago

  • Legacy Backlogs Release (now unused) set to 330

#10 Updated by Anonymous 4 months ago

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

#11 Updated by Marek Hulán 4 months ago

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

Also available in: Atom PDF