)]}'
{
  "commit": "7253ff28e635a26bc8a3cdffd2524e6d7097d1f2",
  "tree": "2d179addb9c7490dda690ecb61160baa525f339a",
  "parents": [
    "1ab3d4ba2d9bcb4732e0bea97dcb78b0156299aa"
  ],
  "author": {
    "name": "Nikolay Titov",
    "email": "nikolay.titov@nokia.com",
    "time": "Mon Aug 14 18:24:17 2017 -0400"
  },
  "committer": {
    "name": "Nikolay Titov",
    "email": "nikolay.titov@nokia.com",
    "time": "Mon Aug 14 19:23:22 2017 -0400"
  },
  "message": "VOL-172: Support configuration of  traffic descriptor profile for upstream BW allocation to ONU\n\n * As an operator, I should be able to configure traffic descriptor profiles for upstream BW configuration.\n * As an operator, I should be able to retrieve the configured traffic descriptor profiles.\n\nAdditional Notes:\n * xPON Handler and xPON Agent should be able to handle the traffic descriptor configuration.\n * This story does not have impact on adapters until the traffic descriptor is referenced by a TCONT\n * The traffic descriptor profiles should be saved to the database(in memory until config/restore feature is ready).\n * The impact to HA-proxy for load-balancing \u0026 distributing of workload is still TBD. As of now, it can be assumed that profiles are available to all VOLTHA instances.\n\nVOL-173: Support configuration of TCONTs as per WT-385 and auto-allocation of alloc-ids\n\n * As an operator, I should be able to provision a TCONT for the ONU with an existing traffic descriptor profile\n * As an operator, I should be able to retrieve the provisioned TCONT\n * As an operator, I should be able to change the traffic descriptor profile for a TCONT\n\nAdditional Notes:\n\n * alloc-ids should be allocated for the TCONT\n * generic IAdapter interface to be provided that will be used by OLT and ONU adapters for TCONT/alloc-id/BW configuration\n * In the best interest of schedules/timing, in the first step(e.g. POC-3 \u0026 trial), assume the queueing model to be supported (to be detailed)  (i.e. no configuration of queueing model)\n * The concerned ONU should receive upstream grants upon provisioning of  TCONT for the ONU\n\nVOL-174: Support configuration of GEMs as per WT-385 and auto-allocation of gemport-ids\n\n * As an operator, I should be able to provision a GEMPORT object for the ONU and assign to a UNI\n * As an operator, I should be able to retrieve the provisioned GEMPORT\n\nAdditional Notes:\n\n * gemport-ids should be auto-allocated for the GEMPORT object\n * generic IAdapter interface to be provided that will be used by OLT and ONU adapters for GEM port configuration\n * In the best interest of schedules/timing, in the first step(e.g. POC-3 \u0026 trial), assume the queueing model to be supported (to be detailed) (i.e. no configuration of queueing model)\n * The concerned OLT and ONU should be configured with the allocated gemport-ids\n\nChange-Id: I5f4f4d61959604f0bb2565c3bbb0e4f33f4be2d3\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9136e67a4bd1a09d2ff93a1320899b3f357cbc9f",
      "old_mode": 33188,
      "old_path": "tests/itests/voltha/test_voltha_xpon.py",
      "new_id": "24134572a146ffc59932a9cfd8b49ed7fd602259",
      "new_mode": 33188,
      "new_path": "tests/itests/voltha/test_voltha_xpon.py"
    },
    {
      "type": "modify",
      "old_id": "18b60625608ef20193cd9bd72ba545f64a2962c7",
      "old_mode": 33188,
      "old_path": "voltha/core/xpon_handler.py",
      "new_id": "71949c3e9339a82d552eed3855953a3e02be8585",
      "new_mode": 33188,
      "new_path": "voltha/core/xpon_handler.py"
    }
  ]
}