)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"ac20ac7d64ed0d1332c954a591f2de16711416a9","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Spec for IPv6 API testing parity in tempest"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This BP will add new IPv6 tests to bring parity between"},{"line_number":10,"context_line":"IPv4 and IPv6 tests."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I049367cb76f95dbec68af893fcc0dfe9326ed42b"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"baada198_2ca5b246","line":9,"updated":"2014-07-05 06:55:00.000000000","message":"Could you set the topic to the bp as well, as the sentence \"This BP will\" accidentally got your topic set to \"bp/will\"","commit_id":"192396dde4a6205b878bb51c1aa576fdde14d531"},{"author":{"_account_id":10257,"name":"Sridhar Gaddam","email":"sgaddam@redhat.com","username":"sridhargaddam"},"change_message_id":"e89ba1eea3fa31b182369bc6cbce631f8454729f","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Spec for IPv6 API testing parity in tempest"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This BP will add new IPv6 tests to bring parity between"},{"line_number":10,"context_line":"IPv4 and IPv6 tests."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I049367cb76f95dbec68af893fcc0dfe9326ed42b"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"baada198_079d2766","line":9,"in_reply_to":"baada198_2ca5b246","updated":"2014-07-05 09:39:53.000000000","message":"Done","commit_id":"192396dde4a6205b878bb51c1aa576fdde14d531"}],"specs/ipv6-testing-parity.rst":[{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"bcd5336c64ab28e24a913adc3cf407e6caaa1063","unresolved":false,"context_lines":[{"line_number":78,"context_line":"  Similarly, devstack needs to populate the flag during the setup. The required"},{"line_number":79,"context_line":"  changes in devstack would be addressed as part of the following BP."},{"line_number":80,"context_line":"  https://blueprints.launchpad.net/devstack/+spec/tempest-ipv6-attributes-support"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"- Neutron: Support Router Advertisement Daemon (radvd) for IPv6"},{"line_number":83,"context_line":"  https://review.openstack.org/#/c/101306/"},{"line_number":84,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_ec873ab3","line":81,"updated":"2014-07-05 06:53:02.000000000","message":"You will need something in devstack-gate as well to turn the devstack flag on/off depending on the branch under test.","commit_id":"192396dde4a6205b878bb51c1aa576fdde14d531"},{"author":{"_account_id":10257,"name":"Sridhar Gaddam","email":"sgaddam@redhat.com","username":"sridhargaddam"},"change_message_id":"e89ba1eea3fa31b182369bc6cbce631f8454729f","unresolved":false,"context_lines":[{"line_number":78,"context_line":"  Similarly, devstack needs to populate the flag during the setup. The required"},{"line_number":79,"context_line":"  changes in devstack would be addressed as part of the following BP."},{"line_number":80,"context_line":"  https://blueprints.launchpad.net/devstack/+spec/tempest-ipv6-attributes-support"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"- Neutron: Support Router Advertisement Daemon (radvd) for IPv6"},{"line_number":83,"context_line":"  https://review.openstack.org/#/c/101306/"},{"line_number":84,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_e793d358","line":81,"in_reply_to":"baada198_ec873ab3","updated":"2014-07-05 09:39:53.000000000","message":"@Andrea, thanks for the review comments. \n\nInitially I was also under the same impression of having some changes in devstack-gate, but Sean Dague clarified that since devstack uses branches it knows that it is running on a later version than stable/icehouse. There was a patch for devstack-gate and after detailed discussion the changes are now handled in devstack and tempest. \n\nPlease see the following patch for the background.\nhttps://review.openstack.org/#/c/96723/","commit_id":"192396dde4a6205b878bb51c1aa576fdde14d531"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"24c43a8c50ea0501fbe0b9bb184ffeb6cd325581","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"This BP would implement new test cases in tempest to bring in parity between"},{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_5cf602fa","line":31,"updated":"2014-07-07 07:44:08.000000000","message":"I guess we will not need another spec related to neutron ipv6 if this spec is approved, right? I hope this spec can cover all of neutron ipv6, and I\u0027d just like to confirmed it now.","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"fd1ed6d66adf4e0f16fd777aa1ceea41c7b52db4","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"This BP would implement new test cases in tempest to bring in parity between"},{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_e087ddd5","line":31,"in_reply_to":"baada198_195455c9","updated":"2014-07-09 00:11:54.000000000","message":"Thanks for your explanation, I got it.","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":10257,"name":"Sridhar Gaddam","email":"sgaddam@redhat.com","username":"sridhargaddam"},"change_message_id":"7df854e63e69ce432b9bba020c6a549f4d514b7b","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"This BP would implement new test cases in tempest to bring in parity between"},{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_195455c9","line":31,"in_reply_to":"baada198_4a59a68c","updated":"2014-07-08 19:21:23.000000000","message":"@Ken\u0027ichi, as you know, currently there are no provider network scenario tests in tempest. So the above mentioned provider network scenario tests spec is for both IPv4 and/or IPv6 scenario tests.","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":10257,"name":"Sridhar Gaddam","email":"sgaddam@redhat.com","username":"sridhargaddam"},"change_message_id":"c13d856832789d0f2db25b2acab979d7aa9d8e42","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"This BP would implement new test cases in tempest to bring in parity between"},{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_4a59a68c","line":31,"in_reply_to":"baada198_5cf602fa","updated":"2014-07-08 10:33:22.000000000","message":"@Ken\u0027ichi, thank you for the review comments.\n\nThe idea behind this BP is to add all the missing IPv6 \"API\" tests, as shown in the name of the BP. When we initially submitted patches in tempest, we noticed that we have to submit specs in the new format for the specs to be reviewed - so we submitted new specs including the tests that would be implemented along with the associated dependencies. \n\nAs you know, the etherpad/google-doc, way of tracking the tests/changes is kind of some recent announcement (at least I was not aware that this idea was in the pipeline). \n\nI would like to point you to another BP that is implementing the provider network \"scenario\" tests. As it was scenario tests, I\u0027ve submitted a different Spec (including the necessary dependencies). \nSpec: https://review.openstack.org/#/c/104098/\nPatch: https://review.openstack.org/#/c/100143\nThe above spec targets the following BP in neutron which is now merged - https://review.openstack.org/#/c/88043/\n\nPlease have a look at it and if you have any suggestions let me know.","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"24c43a8c50ea0501fbe0b9bb184ffeb6cd325581","unresolved":false,"context_lines":[{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"https://etherpad.openstack.org/p/ipv6-api-testing-parity"},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_9c497a33","line":33,"updated":"2014-07-07 07:44:08.000000000","message":"If works related to this spec is just for improving the test coverage gap between ipv4 and ipv6, I guess current description seems to create a lot of copy\u0026paste test code(copy ipv4 to ipv6 and change the parts of ipv4 for ipv6)?\n\nAre there any ideas for avoiding copy\u0026paste here?\nFor example, cinder-v2-api-tests.rst is for avoiding it on cinder API tests.","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"fd1ed6d66adf4e0f16fd777aa1ceea41c7b52db4","unresolved":false,"context_lines":[{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"https://etherpad.openstack.org/p/ipv6-api-testing-parity"},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_6073cd15","line":33,"in_reply_to":"baada198_182545ae","updated":"2014-07-09 00:11:54.000000000","message":"Perfect, that would be nice :-)","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"},{"author":{"_account_id":10257,"name":"Sridhar Gaddam","email":"sgaddam@redhat.com","username":"sridhargaddam"},"change_message_id":"c13d856832789d0f2db25b2acab979d7aa9d8e42","unresolved":false,"context_lines":[{"line_number":30,"context_line":"IPv4 and IPv6 tests. To start with, new tests would be required in Neutron,"},{"line_number":31,"context_line":"for port/security-group/subnet/FWaaS api tests."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The following etherpad link would be used to track the test cases."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"https://etherpad.openstack.org/p/ipv6-api-testing-parity"},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"baada198_182545ae","line":33,"in_reply_to":"baada198_9c497a33","updated":"2014-07-08 10:33:22.000000000","message":"No Ken\u0027ichi, we will not be copy/pasting the code. We\u0027ll extend the classes and overwrite the variables where ever necessary like its done in the file - https://github.com/openstack/tempest/blob/master/tempest/api/network/test_ports.py#L266\n\nThere could be some test-cases which are applicable ONLY for IPv6 (considering that IPv6 has different modes like SLAAC, DhcpV6 Stateless/Statefull etc). So new tests would be added for such use cases.  \n\nYou can be assured that we will not be duplicating the code :-)","commit_id":"accbbe9d1fe7feb6eaec07616d559f0f7ab136bb"}]}