)]}' { "log": [ { "commit": "d9cc2e939271fec1ef177853b76a6ba14b9023ea", "tree": "26f8f40128d4775f074e9d1a75ba625026b16a3f", "parents": [ "09400bd45a6b75c41da754de43dfdd7a7a7337ff" ], "author": { "name": "Kent Hagerman", "email": "khagerma@ciena.com", "time": "Mon Nov 04 13:28:15 2019 -0500" }, "committer": { "name": "Kent Hagerman", "email": "khagerma@ciena.com", "time": "Thu Apr 09 09:35:29 2020 -0400" }, "message": "VOL-2868 Remove all uses of Proxy.RegisterCallback(...)\n\nChange-Id: I05d47a9915071adb80ebc3c5f9b129ed6c36b54b\n" }, { "commit": "d1afd661a07490540e8b20501188be3c5abfc05b", "tree": "f921cb8f522461f1eef46bab4f5ff89b27868ebe", "parents": [ "20dc641af42369b3196637f86e86b1fbc001f6f9" ], "author": { "name": "David Bainbridge", "email": "dbainbri@ciena.com", "time": "Thu Mar 26 18:27:41 2020 -0700" }, "committer": { "name": "David Bainbridge", "email": "dbainbri@ciena.com", "time": "Mon Mar 30 07:57:18 2020 -0700" }, "message": "VOL-2658, VOL-2840 - remove core compete code\n\nChange-Id: Ic34d030bc805c6948369c65db6f77f9739320570\n(cherry picked from commit fd27f4b45b3c8d89174a8da7192598b768b4907d)\n" }, { "commit": "408cd96a8da028341a7141602247ab3c81e66ece", "tree": "be68937498b56ff2846df71911845081813072bd", "parents": [ "8728525e8513196c30b7120a3d3c7332c6a03dff" ], "author": { "name": "Girish Gowdra", "email": "girish@opennetworking.org", "time": "Wed Mar 11 14:31:31 2020 -0700" }, "committer": { "name": "Girish Gowdra", "email": "girish@opennetworking.org", "time": "Wed Mar 18 12:50:46 2020 -0700" }, "message": "[VOL-2404] : RW-Core changes for handling OLT Reboot Scenario\n\n- When the OLT\u0027s connection status goes from REACHABLE to UNREACHABLE\n in ENABLED/DISABLED admin state, delete all the logical ports,\n child devices, logical device and device flows.\n\n- When OLT\u0027s connection status becomes reachable again, child devices,\n ports will be re-discovered again. The logical device will be recreated\n again.\n\n- Will not handle the case where OLT goes UNREACHABLE when OLT is disabled\n as part of voltha2.3 release\n\nChange-Id: I34c0c538b44afa19e889e9631f0a738060a58fef\n" }, { "commit": "442e7c79a650b83c0e84c5827d5f4e9f70b315fb", "tree": "90686a69e5f9fdb4d0c4f1f48e372eac5988477c", "parents": [ "18fa0c944878b68cea9174f6f31a10133d3513c8" ], "author": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Tue Mar 10 16:13:48 2020 -0400" }, "committer": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Tue Mar 17 16:04:32 2020 -0400" }, "message": "[VOL-2164] Update rw-core to use the Async Kafka API\n\nThis commit consists of the following:\n\n1. Process per-device requests in the Core in the order they are\nreceived. If there are lots of requests on a given device then\nthere will be some latencies introduced due to ordering. With\nrecent changes in the model along with keeping the request lock\nto a minimal then these latencies are reduced. Testing did not\nshow and noticeable latencies.\n\n2) Keep the request lock from the moment a request started\nprocessing to the moment that request is sent to kafka (when\napplicable). Adapter responses are received and processed\nasynchronously. Therefore, an adapter can takes all the time it\nneeds to process a transaction. The Core still has a context\nwith timeout (configurable) to cater for cases where the adapter\ndoes not return a response.\n\n3) Adapter requests are processed to completion before sending a\nreponse back to the adapter. Previously, in some cases, a\nseparate go routine was created to process the request and a\nsuccessful response is sent to the adapter. Now if the request\nfails then the adapter will receive an error. The adapter\nrequests for a given device are therefore processed in the\norder they are received.\n\n4) Some changes are made when retrieving a handler to execute\na device state transition. This was necessary as there was some\ntransition overlap found.\n\nUpdate after multiple reviews.\n\nChange-Id: I55a189efec1549a662f2d71e18e6eca9015a3a17\n" }, { "commit": "c704def6b3ea8c03b8c396fe8dbbc9be44087916", "tree": "dc6c7f34a2494cf258afe2c16aac871f47b5e193", "parents": [ "e8ad020e016d839e7b54c1fea5bcd84005f9c762" ], "author": { "name": "Hardik Windlass", "email": "hardik_windlass@infosys.com", "time": "Wed Feb 26 18:23:19 2020 +0000" }, "committer": { "name": "Andrea Campanella", "email": "andrea@opennetworking.org", "time": "Mon Mar 02 16:10:34 2020 +0000" }, "message": "[VOL-2573] Delete all logical ports on OLT Delete\n\nChange-Id: Id809e176fe3a902aabea8cbce573fbf9710d9b10\n" }, { "commit": "543df3ed7465c42389365a8910ea79c64db87636", "tree": "09224c11ba2517cb0e1834b3b0e02eced49054d1", "parents": [ "dcd4dcccc7f926721ed411065be28b493de2f1ef" ], "author": { "name": "Chaitrashree G S", "email": "Chaitrashree.S@radisys.com", "time": "Mon Feb 24 22:36:54 2020 -0500" }, "committer": { "name": "Chaitrashree G S", "email": "Chaitrashree.S@radisys.com", "time": "Wed Feb 26 19:42:48 2020 -0500" }, "message": "[VOL-1385] : Changes to support ONU delete\n Tested with,\n1. ONU disable-\u003edelete\n2. ONU delete\n3. OLT delete\n\nChange-Id: I8e6ff41a7ea8e94014700f274cb24fea73ac41f4\n" }, { "commit": "2ebbf220fe40b152e37df02d38fc4b1dcd2c9136", "tree": "836febe9e2b3c81ccf15291d0874244827a323b1", "parents": [ "e935b33392e67708b83292c27480ae5258c37724" ], "author": { "name": "David Bainbridge", "email": "dbainbri@ciena.com", "time": "Mon Feb 24 19:16:07 2020 +0000" }, "committer": { "name": "David Bainbridge", "email": "dbainbri@ciena.com", "time": "Mon Feb 24 19:16:07 2020 +0000" }, "message": "Revert \"[VOL-1385] : code changes to support ONU delete\"\n\nThis reverts commit e935b33392e67708b83292c27480ae5258c37724.\n\nChange-Id: Ibd10b43d8d6264a7b0b12386eb9833b5a4864ffd\n" }, { "commit": "e935b33392e67708b83292c27480ae5258c37724", "tree": "2024e0fda291242491fb863afec58537785c3662", "parents": [ "80b987ded390cc5e6422f92d126272b05f812dcb" ], "author": { "name": "Chaitrashree G S", "email": "Chaitrashree.S@radisys.com", "time": "Tue Feb 04 17:48:20 2020 -0500" }, "committer": { "name": "Chaitrashree G S", "email": "Chaitrashree.S@radisys.com", "time": "Sun Feb 23 18:18:50 2020 -0500" }, "message": "[VOL-1385] : code changes to support ONU delete\n\nChange-Id: Ic4436f53a2dbe36191ae44d56d5119bed1346c7a\n" }, { "commit": "820197cd6aa714dc34d2b3278d138fdfa884eb77", "tree": "527abb866e97771baaa746fe46fd408a3c9576e0", "parents": [ "16ce36a1d659ee84982d81399ef9bf0a4f015b1e" ], "author": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Thu Feb 13 16:35:33 2020 -0500" }, "committer": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Fri Feb 14 14:06:25 2020 -0500" }, "message": "[VOL-2576] Improve route calculation\n\nThis commit changes the way device routes are calculated. It\nreplaces the device graph method. The graph method relies on the\nshortest path calculation which is quite resource intensive. For\ninstance, generating the routes for a PON network with 1 OLT having\n8 PON ports, 64 ONUs per Port and 4 UNIs per ONUs took 96 secs to\ngenerate the 4096 routes. The new method creates the routes from\nthe devices data with no middle step. Generating routes for the\nabove topology now takes 4ms.\n\nChange-Id: I32bffe06d12ad0fea94002a39f217547dc55cdbf\n" }, { "commit": "467fe7536d85d096354b60fa49346f20a9e6f7f7", "tree": "8022b3eb7b2188716eb3649d8f12543e3b9ddb18", "parents": [ "b9cfcb167c2cbe01ea37cf1edd4e3dd9915b78d0" ], "author": { "name": "npujar", "email": "Nikhil.Pujar@radisys.com", "time": "Thu Jan 16 20:17:45 2020 +0530" }, "committer": { "name": "Kent Hagerman", "email": "khagerma@ciena.com", "time": "Tue Feb 04 11:25:40 2020 -0500" }, "message": "VOL-2180 context changes in voltha-go\n\nPassed context up as far as possible.\nWhere context reached the gRPC api, the context is passed through directly.\nWhere context reached the kafka api, context.TODO() was used (as this NBI does not support context or request cancelation)\nAnywhere a new thread is started, and the creating thread makes no attempt to wait, context.Background() was used.\nAnywhere a new thread is started, and the creating thread waits for completion, the ctx is passed through from the creating thread.\nCancelation of gRPC NBI requests should recursively cancel all the way through to the KV.\n\nChange-Id: I7a65b49ae4e8c1d5263c27d2627e0ffe4d1eb71b\n" }, { "commit": "2ae470fb773f92a43078574e343967263fb38c96", "tree": "52ef7d2f5cc889c7a8b8cfbf2293e20d76b94ccb", "parents": [ "0c89b3c7ea245bbb4861e497a72990520da0cf7c" ], "author": { "name": "serkant.uluderya", "email": "serkant.uluderya@netsia.com", "time": "Tue Jan 21 11:13:09 2020 -0800" }, "committer": { "name": "khenaidoo Nursimulu", "email": "knursimu@ciena.com", "time": "Fri Jan 24 16:24:16 2020 +0000" }, "message": "VOL-1643 Update voltha-go to use voltha-protos and voltha-lib-go v3.0.0\n\nChange-Id: I86744943d59de38e9285ed7f53adc49c3b047e62\n" }, { "commit": "09959ae1c1f0362b5cf0408dc8335c9e4fbf9f5c", "tree": "321519dc026cbf2bc0398d4e81f75ae1db6960e2", "parents": [ "7cf8e0b18db7e80a5cf9606fb149bca10f083c85" ], "author": { "name": "Esin Karaman", "email": "esin.karaman@netsia.com", "time": "Fri Nov 29 13:59:58 2019 +0000" }, "committer": { "name": "Matt Jeanneret", "email": "mj3580@att.com", "time": "Fri Jan 10 17:19:30 2020 +0000" }, "message": "VOL-2294 Flow-decomposer should not decompose multicast flows;\nit should leave it as it is.\n\nChange-Id: I6020b66257ed6f19145298dde34c2bae7b338650\n" }, { "commit": "6e55d9e4de4ce8646af9403a8ba4288a5db7bea4", "tree": "ac22e4a063e028e314e3d611c5eaf9328ab3c968", "parents": [ "5c28f5535132af97973165b74d1b46935cf20044" ], "author": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Thu Dec 12 18:26:26 2019 -0500" }, "committer": { "name": "khenaidoo", "email": "knursimu@ciena.com", "time": "Thu Dec 12 18:27:24 2019 -0500" }, "message": "[VOL-2318] - Fix for jenkins NBI Failure\n\nThis commit adds the latest devices and logical devices to the\ndevice agents and logical device agents respectively. Any GET\nis returned directly from these agents instead from the model.\nAnd any create/update results in the data being sent to the KV\nstore via the model and also results in the latest data in the\nagent being updated. If the Core dies and restart then the\nlatest data will be pulled from KV. These changes assumes\nthat a device or a logical device is always owned by one Core\nonly which is the case.\n\nChange-Id: Ie671cd70b38a58a3b32fa476eced5f218aeadad9\n" }, { "commit": "1d86a528896c873e6ed096b9327a73c25239327c", "tree": "f61adf27aa46507b5d42fa9499bd18bb3fd21c29", "parents": [ "03fe56f418015507af89d49fd8a7c8f1643b5065" ], "author": { "name": "npujar", "email": "Nikhil.Pujar@radisys.com", "time": "Thu Nov 14 17:11:16 2019 +0530" }, "committer": { "name": "khenaidoo Nursimulu", "email": "knursimu@ciena.com", "time": "Wed Nov 27 18:37:47 2019 +0000" }, "message": "VOL-1900 lint warning fixes rw_core\n\nChange-Id: Icaa84d7ce24163da90c91ff2babcbb78ff4e9141\n" } ] }