)]}'
{
  "log": [
    {
      "commit": "b7e8090f9f118f8ad372b3013facace36392e178",
      "tree": "66dfc1a091ac09246c389a08d4ec22818c320bf0",
      "parents": [
        "3bf8c1b6d34c21fa6e196ed058e29b49d0269568"
      ],
      "author": {
        "name": "A R Karthick",
        "email": "kramanar@ciena.com",
        "time": "Tue May 17 09:38:31 2016 -0700"
      },
      "committer": {
        "name": "A R Karthick",
        "email": "kramanar@ciena.com",
        "time": "Tue May 17 09:38:31 2016 -0700"
      },
      "message": "Add test cases to test subscriber multi-table support with ONOS using CPQD and a new ONOS app.\nThis would verify single channel multiple subscriber joins using cpqd.\nONOS multi-table support was found to be broken with cordmcast.\nHence a new app similar to cordmcast was added to verify if multi-table rules were provisioned with ONOS\ncpqd pipeline driver.\nUsing a different subscriber port per subscriber and provisioning an uplink port to be used\nfor IGMP traffic, it was found that ONOS cpqd driver fails to provision multi-table flows using group ids.\nThe subscriberMultiTable tests uses the new cordigmp multitable app to provision multicast flows in ONOS\nenabling the spring-open-cpqd pipeline driver with ONOS when using CPQD.\n\nIf you want to verify/run the subscriberMultiTable test, first rebuild the test container with cpqd using:\nsudo cord-test.py build test\nAnd then run the subscriberMultiTable test: test_subscriber_join_recv using:\ncord-test.run run --radius -t subscriberMultiTable:subscriber_exchange.test_subscriber_join_recv -k\n"
    }
  ]
}