)]}'
{
  "commit": "f35ff72b77d479d43c1ede6b9f691ae54a2c60a1",
  "tree": "732544455612488602ecba83c1bdd53c28e8ab59",
  "parents": [
    "9f52cd78f26c984803763c13ba520b92bb27132b"
  ],
  "author": {
    "name": "Sean Dague",
    "email": "sdague@linux.vnet.ibm.com",
    "time": "Thu May 16 16:31:12 2013 -0400"
  },
  "committer": {
    "name": "Sean Dague",
    "email": "sdague@linux.vnet.ibm.com",
    "time": "Thu May 16 18:05:47 2013 -0400"
  },
  "message": "add support for changing cinder perodic_interval\n\nAs discovered in tempest, when you create and delete volumes\nquickly, and have a small volume storage pool, you can get cinder\nscheduler to think you are \"out of space\" when you are not.\n\nThis is because cinder scheduler updates free space on it\u0027s\nperiodic job, which defaults to 60 seconds. We need control over\nthat value for the devstack gate otherwise we regularly get\noverruns if we run too many volume tests quickly.\n\nWork around for bug 1180976\n\nExpect that this will get removed later if cinder gets a more\nefficient way to update the scheduler for freed resources.\n\nAlso, don\u0027t be completely stupid about setting defaults....\n\nChange-Id: I20e52e66fcc94b224476cdd14c88bd6981b4e617\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "82e7454423228ed4242abeb813ce7d03e98e8adc",
      "old_mode": 33188,
      "old_path": "lib/cinder",
      "new_id": "7e9c2ba6e573828de25a8b6c5125e01ace633fcc",
      "new_mode": 33188,
      "new_path": "lib/cinder"
    }
  ]
}