Brocade Switch: Enable jumbo frames for ports

[naved001]

This was suggested by @radonm

For the other 2 switches we support, we only need to enable jumbo frames for the whole switch, which is a one time thing. But for brocade we need to do it for every port. Right now an administrator has to do it manually.

Also, Openstack can work with a standard MTU of 1500 bytes, but it is really slow so we change it to 9100 (Jumbo Frames), which means the underlying physical network's switches' should have Jump frames enabled.

Edit: changed size to 9100 after reading the comment

[radonm]

9100 actually

On 7.4.2017 г. 15:57 ч., Naved Ansari wrote:

This was suggested by @radonm https://github.com/radonm

For the other 2 switches we support, we only need to enable jumbo frames for the whole switch, which is a one time thing. But for brocade we need to do it for every port. Right now an administrator has to do it manually.

Also, Openstack can work with a standard MTU of 1500 bytes, but it is really slow so we change it to 9000 (Jumbo Frames), which means the underlying physical network's switches' should have Jump frames enabled.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/CCI-MOC/hil/issues/755, or mute the thread https://github.com/notifications/unsubscribe-auth/ABfSVxqunpQmr9kJWBlyTFoBoAWw7PRRks5rtpVBgaJpZM4M3UzR.

[henn]

This is dependent on #840.

[naved001]

Just had a discussion with @radonm about jumbo frames.

• Do we need to expose this via HIL at all? @radonm thinks that we should just outright enable jumbo frames on every switch/port registered in HIL. What are some real use cases that tenants/users might want to set a lower MTU? Realistically, will HIL be in an environment where hosts/switches can't work with jumbo frames?

• @radonm suggested having this for the administrators because it can be a pain to enable jumbo frames on every switchport in a brocade fabric. We can specify the port range, but not the range for rbridge-id. Is this reason enough to have this API?

@pjd-nu @okrieg @zenhack @SahilTikale @apoorvemohan curious to your thoughts.

[naved001]

I had talked with @okrieg in person, and he said that we can remove this from the milestone for now unless somebody really needs it. Current strategy is that we just enable jumbo frames on all ports/switches controlled by HIL.

[zenhack]

Unless there's a use case for toggling jumbo frames during normal HIL operation, I'd prefer to leave it out of the API. If it's something we're just doing on-set up, that can be an independent script.