)]}'
{
  "commit": "fa13ba685b64dd7d0371b385c16890cf7caacea7",
  "tree": "a60bf8a81a9e283e3fe676431cf12047aa3be211",
  "parents": [
    "0facf3c0322d76a3a6c8a0ed95f78deae0993770"
  ],
  "author": {
    "name": "Ievgeniia Zadorozhna",
    "email": "izadorozhna@mirantis.com",
    "time": "Sat Jun 18 02:03:09 2022 +0300"
  },
  "committer": {
    "name": "Ievgeniia Zadorozhna",
    "email": "izadorozhna@mirantis.com",
    "time": "Sat Jun 18 02:03:09 2022 +0300"
  },
  "message": "Added the possibility to set the custom MTU for the VMs\n\nIf \"default\" is set, the MTU will be set automatically\nfrom the newly created SPT internal networks. The default\nvalue in the networks comes from the Neutron configuration.\nIn case users want to test the bandwidth with some\nspecific custom MTU, they can set the value in integer or\nstring formates like 8950.\n\nThis possibility saves the time for QAs in case they want\nto test the bandwidth with some specific MTU at VMs. This\nalso helps when the default Neutron MTU seems to be not\ncorrect and QA needs to verify the bandwidth with some new\nvalue.\n\nChange-Id: I0f93b33c4f530b95a5dc214c02cfb3a9ddbd182b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "45b221315c1c0e3bc4aa82235366042c0d6b2fd7",
      "old_mode": 33188,
      "old_path": "README.md",
      "new_id": "36e7dc01c8658c6ae99f43d2a09e01da0c0a5764",
      "new_mode": 33188,
      "new_path": "README.md"
    },
    {
      "type": "modify",
      "old_id": "f6213ca0dad261d9150c8fc89a58e68c53d9b02a",
      "old_mode": 33188,
      "old_path": "global_config.yaml",
      "new_id": "025bd605cb4326ce44763c48dec4742421ec439f",
      "new_mode": 33188,
      "new_path": "global_config.yaml"
    },
    {
      "type": "modify",
      "old_id": "12aad1b9c314c6de91be5b9f6e0719e95be3bb77",
      "old_mode": 33188,
      "old_path": "utils/os_client.py",
      "new_id": "8ef55de15200aee0a093c7bacf885243c0053b80",
      "new_mode": 33188,
      "new_path": "utils/os_client.py"
    }
  ]
}