)]}'
{
  "commit": "eefcdb607b6ba0303213fdb8dc681faf069ea661",
  "tree": "0952b16770d1dba66965dba41a2d6e4956b50b8c",
  "parents": [
    "2efa0c599b9b809ed925874d949926a4508c4036"
  ],
  "author": {
    "name": "schillinge",
    "email": "ablu@mail.uni-paderborn.de",
    "time": "Thu Feb 14 11:13:21 2019 +0100"
  },
  "committer": {
    "name": "schillinge",
    "email": "ablu@mail.uni-paderborn.de",
    "time": "Thu Feb 14 11:21:53 2019 +0100"
  },
  "message": "Fixed port chain direction and linking\n\nGiven a port chain of two port pair groups ppg1 and ppg2, which each\nconsist of a single port pair (ppg1\u003d[pp1], ppg2\u003d[pp2]), where\npp1\u003d(ingress: p1, egress: p2), p2\u003d(ingress: p3, egress: p4) the\nfollowing forwarding chain was generated:\n\n    /----\\ /----\\\n    | s1 | | s2 |\n    \\i--e/ \\i--e/\n     v  ^   v  ^\n     |  |   |  |\n     \\--/   \\--/\n\nThis, for once, mixed ingress and egress, but also did not actually link\nthe servers.\n\nThis patch corrects the linking to:\n\n    /----\\ /----\\\n    | s1 | | s2 |\n    \\i--e/ \\i--e/\n     ^  v   ^  v\n     |  |   |  |\n    -/  \\---/  \\-\u003e\n\nChange-Id: Iabc48a6950f864562a93f8d17f41890598d65ac6\nSigned-off-by: schillinge \u003cablu@mail.uni-paderborn.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7dcd834239061821d9ca9eb5aaec01d7a016e34d",
      "old_mode": 33188,
      "old_path": "src/emuvim/api/openstack/resources/port_chain.py",
      "new_id": "f727acfdf995da8398d323b712deaad500591bbb",
      "new_mode": 33188,
      "new_path": "src/emuvim/api/openstack/resources/port_chain.py"
    }
  ]
}