)]}'
{
  "commit": "a389128dba4ce7d7051b86f3ac7db4164d24b95f",
  "tree": "e710951f79fd50d61eaa5663be3937cab590fcf3",
  "parents": [
    "427a4e1a9b7f20a8be0ad5091f2229945ce711a8"
  ],
  "author": {
    "name": "Lucas Alvares Gomes",
    "email": "lucasagomes@gmail.com",
    "time": "Tue Jul 18 16:31:28 2023 +0100"
  },
  "committer": {
    "name": "Dr. Jens Harbott",
    "email": "frickler@offenerstapel.de",
    "time": "Mon Sep 04 13:38:23 2023 +0000"
  },
  "message": "OVN: Let ironic manage the OVN startup in it\u0027s case.\n\nIn order for Ironic perform full testing with devstack, it uses\nvirtual machines attached to a ovs bridge network to simulate\nbare metal machines. This worked great for OVS because often\nOVS was already running on the nodes due to the package, and\nwe could just apply configuration and be done with it when\nIronic\u0027s devstack plugin was applying initial configuration and\nsetting up the test environment.\n\nWith OVN, and the requirement of a specific co-installed OVS\nversion, Ironic has discovered that we cannot perform this same\nconfiguration without having already started OVN during the\ninitial system setup. Which is fine, but we can\u0027t initialize\nand start OVN twice. It just doesn\u0027t work.\n\nThe original form of this patch was proposed by lucasgnomes\nin order to validate that we, did, indeed, need to do this\nto enable Ironic to successfully test an OVN based\nconfiguration, and is now being revised to handle that case\nautomatically when Ironic is the selected virt plugin.\n\nCo-Authored-By: Julia Kreger \u003cjuliaashleykreger@gmail.com\u003e\nChange-Id: Ifbfdaaa97fdbe75ede49dc47235e92a8035d1de6\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e90ada8929737b023deb6b3b2d35e92e45bfca3a",
      "old_mode": 33188,
      "old_path": "lib/neutron",
      "new_id": "5407f8a7b80341ef5d6da60122f1205c4a2fbc34",
      "new_mode": 33188,
      "new_path": "lib/neutron"
    }
  ]
}