)]}' { "log": [ { "commit": "176f1db67445b2419a1f25633aa2be9cd304686c", "tree": "fdec1ec1d7218166bdd70b555afc6ef126b56041", "parents": [ "c26a3c38cadda0d6fdd26e395ee777cb89854766" ], "author": { "name": "Nikolay Titov", "email": "nikolay.titov@nokia.com", "time": "Thu Aug 10 12:38:43 2017 -0400" }, "committer": { "name": "Nikolay Titov", "email": "nikolay.titov@nokia.com", "time": "Thu Aug 10 13:50:38 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: I451cd7c0eda57c7b9fa1d65d02c749ff2bf0db4b\n" }, { "commit": "89004ecb2921661e5a1079450b36195a782daffa", "tree": "b76933ca163b376c629975c606d8962537ba23d6", "parents": [ "08d48d2394ad67e873b3b5b663d1ebd734ba6cc5" ], "author": { "name": "Nikolay Titov", "email": "nikolay.titov@nokia.com", "time": "Mon Jun 19 18:22:42 2017 -0400" }, "committer": { "name": "Nikolay Titov", "email": "nikolay.titov@nokia.com", "time": "Fri Jun 30 12:42:19 2017 -0400" }, "message": "Adds support for BBF WT-385 xPON model:\n\nVOL-151: Framework for OLT PON Configuration Parameters\nVOL-152: Framework for ONU Configuration Parameters\nVOL-220: Support configuration(Create/Read/Delete) of Channel-Group,\n Channel-Partition, Channel-Pair \u0026 Channel-Termination Objects\n for XGS-PON\n\nChange-Id: I992a4e03e6e7b021d7aa9a49a5f8466876c8f07c\n" }, { "commit": "85200811de9b3fd2259a9be4c2b0ab06a0174d75", "tree": "48c87ee5ab28bdc1735d2f52e83fd1064867d78a", "parents": [ "80a7f57714406a8aa2eea19e9e211456992020f0" ], "author": { "name": "Sergio Slobodrian", "email": "sslobodr@ciena.com", "time": "Mon Apr 03 19:09:11 2017 -0400" }, "committer": { "name": "Sergio Slobodrian", "email": "sslobodr@ciena.com", "time": "Wed Apr 05 15:49:03 2017 -0400" }, "message": "Renamed the metrics to align with the agreed to names.\n\nChange-Id: I5662eeed51ee540d1bbc7b9c2342c4d5c4ec4dfa\n" }, { "commit": "4475a254554b0f4335100681b689a6e6f6e9b522", "tree": "e914eb4a278d12cb7ecc168c38e9c2c25705f69e", "parents": [ "a4b89c06d1107294b204e3cc4355adfc7b255201" ], "author": { "name": "Stephane Barbarie", "email": "sbarbari@ciena.com", "time": "Fri Mar 31 13:49:20 2017 -0400" }, "committer": { "name": "khenaidoo Nursimulu", "email": "knursimu@ciena.com", "time": "Wed Apr 05 12:13:23 2017 -0700" }, "message": "PONSIM: Generate alarms as FrameIO egress packets\n- Option to enable generation of alarms\n- Alarms are received by PONSIM OLT and submitted to kafka\n- Option to configure alarm frequency\n\nChange-Id: I93a05eaaae7eb2a6f25937ec76470c1b24c2842b\n" }, { "commit": "4f94062779d30ab9ad9d188610bc4f45fcac3911", "tree": "18fd7a1e44c31d7c90340309e2bde303bba960cc", "parents": [ "4236aded01351d54978d9a233e4b6ad2b632750b" ], "author": { "name": "Khen Nursimulu", "email": "knursimu@ciena.com", "time": "Fri Mar 17 17:45:02 2017 -0400" }, "committer": { "name": "khenaidoo Nursimulu", "email": "knursimu@ciena.com", "time": "Sat Mar 18 11:31:33 2017 -0700" }, "message": "Allow higher priority flows to take precedence when there is a match\n\nChange-Id: If5e92ba9f5801cb7cea423e4a82388b6ec845f1d\n" }, { "commit": "497921413665004f4878199f6b136c44e7e3cd7e", "tree": "60891bfff39269b0254451c3f05b7ba1b0337a55", "parents": [ "901bf4eae18167b0091b50883d6a30992528355f" ], "author": { "name": "Khen Nursimulu", "email": "knursimu@ciena.com", "time": "Fri Mar 17 12:34:05 2017 -0400" }, "committer": { "name": "khenaidoo Nursimulu", "email": "knursimu@ciena.com", "time": "Fri Mar 17 10:56:55 2017 -0700" }, "message": "[ 3289 ] remove debugging statements\n\nThis commit consists of:\n1) Change the flow match method in ponsim to handle multiple matches\n2) Add logical PORT change callback\n3) Clear all flows on a device when the device is disabled\n\nChange-Id: I82ddc9c4555dced917dee8f13d7d4f08ca4e1d03\n" }, { "commit": "98eff41b7ed9c70adad54919478d9879f69c33b5", "tree": "947b59827a5121cf8c753f3c59b2671d9124333d", "parents": [ "60c1ed3cdbdadb2cfb517187613b908acf378abd" ], "author": { "name": "Sergio Slobodrian", "email": "sslobodr@ciena.com", "time": "Wed Mar 15 14:46:30 2017 -0400" }, "committer": { "name": "Sergio Slobodrian", "email": "sslobodr@ciena.com", "time": "Wed Mar 15 14:52:57 2017 -0400" }, "message": "Added support for pm configuration and reporting to ponsim.\n\nChange-Id: I047627253f60beb624d38bde1e5da31adc42312e\n" }, { "commit": "3578a1c3ac3c9898acff32b1e8b940ef18ceac1e", "tree": "428c3eb476abaac4ca390972e0990340c3836d78", "parents": [ "6a5107c865a46df9a6c778d8d34e300621232264" ], "author": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Tue Jan 10 15:29:02 2017 -0800" }, "committer": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Tue Jan 10 20:20:30 2017 -0800" }, "message": "Expand field/action conversion scope of ofagent\n\nOfagent did not parse all fields back from protobuf to lexi,\nhence ONOS was not able to confirm downloaded flows. This\nmade her unhappy.\n\nAlso, DHCP config info is added to ONOS netcfg.json.\n\nChange-Id: I57ac5d3b4d14c8c52feb52e08bb420c15809238e\n" }, { "commit": "6a5107c865a46df9a6c778d8d34e300621232264", "tree": "02db17e968a9c323942b6741d70ce6b7a6fa187c", "parents": [ "6f746645ac6fa03c2c7c37c3ebbb33a2830f5d3f" ], "author": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Mon Jan 09 23:42:41 2017 -0800" }, "committer": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Tue Jan 10 00:54:50 2017 -0800" }, "message": "Adding support for OLT side metadata field\n\nDue to historic reasons, ONOS injects a metadata match field into one\nof the downstream unicats flow rules, which was not yet handled by voltha.\nThat is fixed and tested now.\n\nChange-Id: Ic8a47de515fa5837a70941be22da9e2d6539f614\n" }, { "commit": "656ecc6676367d7483667550fa91046d7a8c0719", "tree": "4f934b1feda7c7032da3a62d09f4e101929ff5fa", "parents": [ "313c4be4cfc0b0e1bb2551efed6489333b195bfb" ], "author": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Wed Dec 28 15:08:23 2016 -0800" }, "committer": { "name": "Zsolt Haraszti", "email": "zharaszt@ciena.com", "time": "Thu Dec 29 00:15:43 2016 -0800" }, "message": "PONSIM: PON simulator with real dataplane handling\n\nThis was needed because neither CPQD nor OVS can handle\nboth zero-tagged packets and 802.1ad (QinQ).\n\n- extensive unittest proves ponsim functional correctness\n (for the common use-cases needed in the PON scenario)\n- integrated with frameio and coupled with a rather\n simple gRPC NBI, ponsim can be operated from Voltha\n just like a real PON system\n- posim_olt/_onu adapters added to Voltha to work on\n ponsim\n- CLI can be used to preprovision and activate a PONSIM\n instance (e.g., preprovision_olt -t ponsim_olt -H localhost:50060)\n- Some of olt-oftest:olt-complex testcases can be run on\n the ponsim device (in vagrant/Ubuntu environment),\n but there are some remaining issues to work out:\n - barrier calls in OF do not guaranty that the flow\n is already installed on the device. This is a generic\n issue, not just for ponsim.\n - the whole test framework is inconsistent about zero-\n tagged vs. untagged frames at the ONUs, while ponsim\n is rather pedantica and does exactly what was defined\n in the flows.\n\nChange-Id: I0dd564c932416ae1566935492134cb5b08113bdc\n" } ] }