)]}'
{
  "commit": "6fd4720e606ffa91a2db7d0bef1961128014e0ed",
  "tree": "b96c2ac5f5109f2a5d1a02a07d0c78b75aeb8f8c",
  "parents": [
    "3ffd5475bfa6c0d68228b9824238be6b096d6e49"
  ],
  "author": {
    "name": "Paul Michali",
    "email": "pc@michali.net",
    "time": "Mon Feb 23 17:07:48 2015 -0500"
  },
  "committer": {
    "name": "Paul Michali",
    "email": "pc@michali.net",
    "time": "Fri Feb 27 12:05:15 2015 -0500"
  },
  "message": "VPNaaS Support for StrongSwan driver.\n\nThe StrongSwan driver under development for kilo-3 will replace the\ndefault reference OpenSwan driver.\n\nIn the interim though, we need to be able to run functional tests\nfor both drivers. This change is intending to do the additional\nsteps that are needed to set up for Strongswan, so that when a\nfunctional test has IPSEC_PACKAGE\u003dstrongswan, everything will be\ncorrect.\n\nThe intent here is to explicitly set the device driver class in\nvpn_agent.ini, so that this will work for when OpenSwan is the\ndefault (currently), when no drivers are specified, and will work\nfor when StrongSwan is made the default in the code.\n\nFor Ubuntu, AppArmor is disabled for charon and stroke.\n\nNote: Both OpenSwan and StrongSwan cannot be installed on the\nhost at the same time.\n\nChange-Id: Ib8467e24633230d6643d812068e4ed6ffb33f104\nPartial-Bug: 1424757\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d27febf63d521811aebd3b2ff5c30c8c656b13c",
      "old_mode": 33261,
      "old_path": "lib/neutron",
      "new_id": "2f2c15f4ad5cec78b281b1a30c30d2a5706c0434",
      "new_mode": 33261,
      "new_path": "lib/neutron"
    },
    {
      "type": "modify",
      "old_id": "5912eab9ca0e19d15bbfe1a88495e5dee2462e6d",
      "old_mode": 33188,
      "old_path": "lib/neutron_plugins/services/vpn",
      "new_id": "4d6a2bf9a0bca0fe1b1c7e7d5d31884fe4bf8ddd",
      "new_mode": 33188,
      "new_path": "lib/neutron_plugins/services/vpn"
    }
  ]
}