tree bbec68013b177060db72603febb00719ef9e76b4
parent 6ba7909e56902a580911495ede5499dd10a569b1
author Ievgeniia Zadorozhna <izadorozhna@mirantis.com> 1675350552 +0300
committer Ievgeniia Zadorozhna <izadorozhna@mirantis.com> 1675438081 +0300

Fixed setting the custom MTU at TF clouds by updating the ports

The MOS 22.5 cloud does not have TF version which can set the
custom MTU during the network creation. This is available only
since TF R21.4. Till that time, we can use the old way of
updating the VM ports, see [1].

Also, added the workaround for mtu field at MOS TF clouds
At the MOS TF clouds, the network payload from the API does not
containt 'mtu' attribute. Thus, we need to do the workaround. Here,
the workaround is done similarly to the CLI: it sets None for the mtu.

Also, made some PEP8 and codestile fixes.

[1] https://supportportal.juniper.net/s/article/Contrail-How-to-update-the-interface-MTU-of-an-exsiting-VMI-with-DHCP-option?language=en_US

Related-PROD: PROD-36943

Change-Id: Ieeb0dc50a29b3145b9ffaae2b7673543983fd915