)]}'
{
  "commit": "caa822fce46d0fab1163bbae4fb5d520745aef20",
  "tree": "9d00df157c14da17a71da15ca00abcc26ab2a01c",
  "parents": [
    "ac65a5cac01aa6d66857fba08fc022c9bc1f413c"
  ],
  "author": {
    "name": "Jianghua Wang",
    "email": "jianghua.wang@citrix.com",
    "time": "Fri Nov 11 18:23:17 2016 +0800"
  },
  "committer": {
    "name": "Jianghua Wang",
    "email": "jianghua.wang@citrix.com",
    "time": "Tue Nov 15 19:55:48 2016 +0800"
  },
  "message": "XenAPI: correct the ml2 configuration for neutron\n\nXenAPI requires two instances of L2Agent: the standard one manages OVS\nbridges in DomU and the service name is called as q-agt in Devstack;\nthe other new L2Agent manages OVS bridges in Dom0 and the service name\nis called as q-domuA. In order to support the new agent q-domuA, it\nrequires some XenAPI-specific configurations. But unfortunately those\nXenAPI-specific configurations were configured in the standard agent\nfile, meaning other changes made to the standard agent file would not\nhave the correct effect. So it has caused issues, for example, floating\nIP addresses are not reachable.\nThis fix is to move the XenAPI-specific configurations from the stardard\nagent configuration file to the XenAPI-specific agent configuration file\nso that it won\u0027t impact the standard agent\u0027s behavior.\n\nChange-Id: I45944e84a1f81d016aa00da6d782801ee8457ea4\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e27b8a634a9f51b875613b94541c26eb86a06c8d",
      "old_mode": 33188,
      "old_path": "lib/neutron_plugins/openvswitch_agent",
      "new_id": "0af2f2035c44aa32e8d3ed924e59e34411b30299",
      "new_mode": 33188,
      "new_path": "lib/neutron_plugins/openvswitch_agent"
    }
  ]
}