Add MTU support to client networks #144

New Issue

Closed

opened 2021-10-09 16:24:54 -04:00 by JoshuaBoniface · 11 comments

JoshuaBoniface commented

2021-10-09 16:24:54 -04:00

(Migrated from git.bonifacelabs.ca)

Add support for specifying the MTU of client networks (either managed or bridged). Normally, both will default to the underlying device MTU (or, for managed networks, 50 bytes less than the underlying device MTU). However it might be beneficial for administrators in some cases to specify a lower MTU value, especially for bridged networks.

Add support for specifying the MTU of client networks (either managed or bridged). Normally, both will default to the underlying device MTU (or, for managed networks, 50 bytes less than the underlying device MTU). However it might be beneficial for administrators in some cases to specify a lower MTU value, especially for bridged networks.

JoshuaBoniface commented

2021-10-09 16:25:05 -04:00

(Migrated from git.bonifacelabs.ca)

assigned to @JoshuaBoniface

assigned to @JoshuaBoniface

JoshuaBoniface commented

2021-10-09 16:34:15 -04:00

(Migrated from git.bonifacelabs.ca)

changed the description

changed the description

JoshuaBoniface commented

2021-10-09 16:35:36 -04:00

(Migrated from git.bonifacelabs.ca)

Actually the current code is severely flawed and will force bridged networks to use the MTU of the cluster NIC, which is not ideal.

Actually the current code is severely flawed and will force bridged networks to use the MTU of the cluster NIC, which is *not* ideal.

JoshuaBoniface commented

2021-10-09 17:11:48 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit f7a826bf52

mentioned in commit f7a826bf520c4aa40c30b07291fda4e6cf52e9a7

JoshuaBoniface commented

2021-10-09 17:35:38 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit 925141ed65

mentioned in commit 925141ed65ffb64448e1c58201b7c1430a3c0a1b

JoshuaBoniface commented

2021-10-09 19:24:19 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit b0b0b75605

mentioned in commit b0b0b756055dbac4dc8f7c43ccfa9fc4b4c0ae41

JoshuaBoniface commented

2021-10-09 19:24:19 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit 7f074847c4

mentioned in commit 7f074847c4d50080f6e7ed255f984221c4725a2a

JoshuaBoniface commented

2021-10-09 19:24:19 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit 40e7e04aad

mentioned in commit 40e7e04aada57cd875cee223fc8fc77531ba15cb

JoshuaBoniface commented

2021-10-09 19:24:19 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit 89f62318bd

mentioned in commit 89f62318bd4b42f3c879c926d5cb120c777c51d5

JoshuaBoniface commented

2021-10-09 19:24:36 -04:00

(Migrated from git.bonifacelabs.ca)

Implemented successfully and code flaw fixed.

Implemented successfully and code flaw fixed.

JoshuaBoniface commented

2021-10-09 19:24:36 -04:00

(Migrated from git.bonifacelabs.ca)

closed

closed

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Add handlers for client network MTUs

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Fix migration bugs and invalid vx_mtu

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Add MTU to network creation/modification

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Have VXNetworkInstance set MTU if unset

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Add MTU support to network add/modify commands

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Fix invalid schema key

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#144

No description provided.