)]}'
{
  "commit": "c66ee65578061fb32c30d180a64fcf9b80642f0c",
  "tree": "a0c8040c099ab8c54f57f65eed1f525a80e9d9bf",
  "parents": [
    "920fe25915b2bc349d7e7c2d7ca3a11bfda8a0ea"
  ],
  "author": {
    "name": "Attila Fazekas",
    "email": "afazekas@redhat.com",
    "time": "Thu Jan 31 06:56:13 2013 +0100"
  },
  "committer": {
    "name": "Attila Fazekas",
    "email": "afazekas@redhat.com",
    "time": "Thu Jan 31 07:28:00 2013 +0100"
  },
  "message": "Proposed EC2 OpenStack extension\n\n\u0027PAUSED\u0027 OS instance status is not mappable to any EC2 status correctly.\nAdding a \u0027paused\u0027 status seams to the only viable way to handle this.\n\nNormally you cannot reach this status just with the EC2 API, but all other\ndefined EC2 statuses are schematically incorrect for status mapping.\n\nA suspend can be considered as a \u0027stopped\u0027 status.\n\u0027rebooting\u0027 can be considered as \u0027pending\u0027 status.\n\nUsing the \u0027paused\u0027 status is only valid when the VM paused because\nof the user\u0027s explicit request, so it is not temporary pause because\nof an internal operation sequence. If the nova just pauses the VM\njust temporary it must report \u0027pending\u0027 (or \u0027running\u0027 ) status.\n\nChange-Id: Id4500dd6e38e078d0b0b76fb0dd6a81c054ef646\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7031fe211bfe6305be514d2ff6258bab17e3d7d1",
      "old_mode": 33188,
      "old_path": "tempest/testboto.py",
      "new_id": "ab79f3c5317108c98a659a23a0f2745c2c5f5d95",
      "new_mode": 33188,
      "new_path": "tempest/testboto.py"
    }
  ]
}