)]}'
{
  "log": [
    {
      "commit": "41513bfe35218ffd6964e54cb468a4671688b516",
      "tree": "bc7f84f459de0b0ce59253edc519014c37313401",
      "parents": [
        "16138de840ace426ef58d10011b73bc4cca88336"
      ],
      "author": {
        "name": "Zack Williams",
        "email": "zdw@opennetworking.org",
        "time": "Sat Jul 07 20:08:35 2018 -0700"
      },
      "committer": {
        "name": "Zack Williams",
        "email": "zdw@opennetworking.org",
        "time": "Sat Jul 07 22:45:38 2018 -0700"
      },
      "message": "Fixes to pass license check\n\nChange-Id: If9a17321030490c70d9a8fdd49adfe8b912c6fe7\n"
    },
    {
      "commit": "4ea26639bdfe2c1ebef177080382069b37e5f72e",
      "tree": "bc3b1f99438cc6ecffc5c5527b773ddce7b63b2d",
      "parents": [
        "1fd9eb2702b722ce12883d5aa5dd4dff29c701a1"
      ],
      "author": {
        "name": "Richard Jankowski",
        "email": "rjankows@ciena.com",
        "time": "Mon May 14 17:45:38 2018 -0400"
      },
      "committer": {
        "name": "khenaidoo Nursimulu",
        "email": "knursimu@ciena.com",
        "time": "Tue May 15 18:38:23 2018 +0000"
      },
      "message": "VOL-794: Assignment lists in etcd not updated correctly in presence of vcore failures\n\n* Fixed coordinator method _sanitize_member_list\n* Fixed keys-only GET operation for etcd KV store\n* Fixed key DELETE operation for etcd KV store\n* Modified vcore manifest to allow a failed pod to be re-spawned on a\n  different host but with the same pod name\n* Modified zookeeper manifest to allow a failed pod to be re-spawned\n  on a different host. With the current manifest, when all 3 zookeeper\n  pods are scheduled on the same node and that node fails, none of the\n  pods get re-spawned.\n* Added NodePort for the Envoy service\n* Removed anti-affinity rule from OFAgent and NetConf manifests to allow\n  the deployment of multiple pods on the same node\n\nChange-Id: I052d952d81a81cafb96acfc1d57a192596e2e9a1\n"
    },
    {
      "commit": "d445438eff7f10faaa5bdf0ed5f8cb67438aee47",
      "tree": "66dbb20ecbbb2f382011652e84928926931fd32e",
      "parents": [
        "01e23a8e86042a7f9c06b4682ea84176c0b87968"
      ],
      "author": {
        "name": "Richard Jankowski",
        "email": "rjankows@ciena.com",
        "time": "Thu Feb 08 16:21:43 2018 -0500"
      },
      "committer": {
        "name": "khenaidoo Nursimulu",
        "email": "knursimu@ciena.com",
        "time": "Mon Feb 12 14:31:47 2018 +0000"
      },
      "message": "VOL-569: Create kubernetes deployment configuration for each voltha service\n\nThis update:\n- organizes all Voltha components under their own namespace, \"voltha\". If\n  you have a script for deploying Voltha, then add namespace.yml at the top.\n- adds host volume mounts for Consul\u0027s data and config directories\n- fixes a bug in Envoy where it was aborting because it couldn\u0027t find Consul\n  even though it was getting the Voltha assignments from Etcd.\n\nChange-Id: I45eaf2d65428c0184df06971ce3797b9122d3055\n"
    },
    {
      "commit": "c3c291c685a780732ec3c1aff82e04647a1ffb83",
      "tree": "32ca5b0ee5b87003e25f53959477bf5bb70551e6",
      "parents": [
        "10a7a7e7563255e1d805c0cca33259c1a5175daf"
      ],
      "author": {
        "name": "Richard Jankowski",
        "email": "rjankows@ciena.com",
        "time": "Fri Feb 02 13:57:33 2018 -0500"
      },
      "committer": {
        "name": "khenaidoo Nursimulu",
        "email": "knursimu@ciena.com",
        "time": "Tue Feb 06 16:53:47 2018 +0000"
      },
      "message": "VOL-569: Create kubernetes deployment configuration for each voltha service\n\nThis update:\n- renames all voltha images referenced in kubernetes deployment files\n  to the \u0027voltha-\u003ccomponent\u003e\u0027 format\n- adds the kubernetes deployment files for grafana, dashd, and shovel\n- adds deployment files for an Ingress resource and an nginx-based ingress\n  controller to allow access to the Consul and Grafana UIs from outside\n  the cluster\n\nManifest file ingress/05-namespace.yml sets up a namespace \u0027ingress-nginx\u0027\nfor all ingress-related resources. This file will be deleted once we move\nall voltha components, including ingress, to a \u0027voltha\u0027 namespace.\n\nDeployment instructions for the ingress resources are provided in README.md.\n\nChange-Id: I0459e838318c43e21f40e83b314f77fc9e0456f8\n"
    },
    {
      "commit": "15274590011ce59a1d70dffe136a0e5ff43457bd",
      "tree": "71685abd7d3e0a26db687c3e9fc32b0df3454809",
      "parents": [
        "d582367242e7b39a7501637d3f596e99f8da62b5"
      ],
      "author": {
        "name": "Richard Jankowski",
        "email": "rjankows@ciena.com",
        "time": "Tue Dec 12 15:52:37 2017 -0500"
      },
      "committer": {
        "name": "Richard Jankowski",
        "email": "rjankows@ciena.com",
        "time": "Tue Dec 12 15:52:37 2017 -0500"
      },
      "message": "VOL-580: Update envoy to support either consul or etcd in a kubernetes cluster\n\nEnvoy is refactored such that it interworks with either consul or etcd. The refactoring\nshould not have changed any of envoy\u0027s behaviour with consul. The update was tested with\nonly the vcli, envoy, vcore, and KV-store (consul or etcd) containers:\n- tested with consul on a kubernetes 3-node cluster\n- tested with etcd on a kubernetes 3-node cluster\n- tested with consul on a 3-node docker swarm\n- container and node failure testing not performed\n\nThis update enables some experimentation of envoy in the kubernetes environment.\nThere is more work to be done.  Future updates could:\n- replace the current polling of etcd\u0027s assignment key with an asynchronous technique\n- make use of data consistency options in etcd get requests\n- make greater use of object orientation\n\nChange-Id: Ia22893cdf331967eee4d13e060fd2c5ba7adb321\n"
    }
  ]
}