)]}'
{
  "commit": "e8bad5cd6a65821c54d66bbc5f7ba17091439d34",
  "tree": "5b20eca678b76ff893c9fbdd44b1fff7c1d18f69",
  "parents": [
    "24fa317234a1282478bc22b666d0f026b6cddad6"
  ],
  "author": {
    "name": "Chris Dent",
    "email": "cdent@anticdent.org",
    "time": "Wed Apr 25 13:01:03 2018 +0100"
  },
  "committer": {
    "name": "Chris Dent",
    "email": "cdent@anticdent.org",
    "time": "Wed Apr 25 14:55:59 2018 +0100"
  },
  "message": "Init placement before nova\n\nWith change I7e1e89cd66397883453935dcf7172d977bf82e84 the placement\nservice may optionally use its own database. In order for this to\nwork, however, the ordering of how both nova and placement are\nconfigured and initialized in stack.sh requires careful control.\n\n* nova.conf must be created first\n* then placement must make some adjustments to it\n* then lib/placement needs to create the placement database\n* before nova does a database sync (of both databases)\n\nOtherwise, when the placement_database/connection is defined, the nova\ndb_sync command will fail because the placement database does not yet\nexist. If we try to do a sync before the nova_api database is created\n_that_ sync will fail.\n\nThis patch adjusts the ordering and also removes a comment that will\nno longer be true when I7e1e89cd66397883453935dcf7172d977bf82e84 is\nmerged.\n\nChange-Id: Id5b5911c04d198fe7b94c7d827afeb5cdf43a076\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1d68f8a185e2ddc6a707455b156b5fd070f455c2",
      "old_mode": 33188,
      "old_path": "lib/placement",
      "new_id": "d70596734c63b53f0401960375a32d373a2a7ad8",
      "new_mode": 33188,
      "new_path": "lib/placement"
    },
    {
      "type": "modify",
      "old_id": "6899fa0d8b3e06e50c8c5248c8fb6942127b7f9c",
      "old_mode": 33261,
      "old_path": "stack.sh",
      "new_id": "30f24b6a3f4abb82d573e055dd13e17ca6e86436",
      "new_mode": 33261,
      "new_path": "stack.sh"
    }
  ]
}