)]}'
{"specs/newton/neutron-stadium.rst":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"88405de07ce5c9c23c854504894c51a70c6f5820","unresolved":false,"context_lines":[{"line_number":21,"context_line":"tough time making progress on a number of fronts, like adding new"},{"line_number":22,"context_line":"features, ensuring stability, etc. During the Kilo timeframe, a"},{"line_number":23,"context_line":"decomposition `effort \u003chttp://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html\u003e`_"},{"line_number":24,"context_line":"started, where the codebase got disaggregted into separate efforts, like"},{"line_number":25,"context_line":"the high level services, and the various third-party solutions for L2"},{"line_number":26,"context_line":"and L3 services."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_fd89b226","line":24,"updated":"2016-05-03 19:30:14.000000000","message":"typo","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":31,"context_line":"lack of oversight of the PTL and the Neutron drivers/core team. The proposed"},{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"vetting process altogether, and yet without ever formally be screened by the"},{"line_number":35,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":36,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":37,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_9a2404c7","line":34,"updated":"2016-05-03 18:54:31.000000000","message":"I am not 100% sure I agree with this sentiment.\n\nAs PTL, I was the one got us into this situation. I think you\u0027ve not identified things correctly, so let me see what I can do.\n\nWe originally booted stuff out of the neutron repository because no one was reviewing vendor code and just merging it under a trust model. We couldn\u0027t test it either. So we booted them all out and proved a way to do that. We also stopped requiring third-party CI because neither myself nor anyone else wanted to police it.\n\nAfter this, I brought these back into the neutron fold as part of the stadium. I was not going around the TC at all, I was merely adding in vendor drivers who we had kicked out of tree, and new APIs (L2GW, SFC, etc.). I find the comment that I was going around the TC particularly inflammatory and wrong.\n\nSo, where we find ourselves now is in a situation where we have these vendor drivers out with no path back in. That\u0027s fine, I\u0027ve spoken with ttx and I believe the solution is to punt this back to the Foundation and their marketplace. The Foundation can make the marketplace more of a place where these drivers are hosted, the Foundation can handle ensuring third-party CI works, and the Foundation can thus give the vendors the marketing muscle they wanted in the first place.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"85b7f90e372ede58073c25cbead02ab8b8c1c73a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"lack of oversight of the PTL and the Neutron drivers/core team. The proposed"},{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"vetting process altogether, and yet without ever formally be screened by the"},{"line_number":35,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":36,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":37,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_789e5008","line":34,"in_reply_to":"1a122d0e_58cc34bb","updated":"2016-05-03 19:50:02.000000000","message":"Ah, if you\u0027re referring to 1, then either I missed the point or your wording leads us down another path. Either way, your intent is now clear, so you can ignore me here. :)","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":31,"context_line":"lack of oversight of the PTL and the Neutron drivers/core team. The proposed"},{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"vetting process altogether, and yet without ever formally be screened by the"},{"line_number":35,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":36,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":37,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_58cc34bb","line":34,"in_reply_to":"1a122d0e_9a2404c7","updated":"2016-05-03 19:45:18.000000000","message":"I am referring to [1]. This is bypassing the TC, whose members defer to the PTL for project creation. I don\u0027t see where the inflammatory argument is to be honest. I can rephrase if you suggest how.\n\n[1] http://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"97abc0a333d69ee3a8dd7663f74286e45a0d68f7","unresolved":false,"context_lines":[{"line_number":59,"context_line":"for all aspects that pertain software development, from inception, to coding,"},{"line_number":60,"context_line":"testing, documentation and more."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":63,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":64,"context_line":"integrity be maintained over time when modifications to the list are required."},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_7382f3c9","line":62,"updated":"2016-05-03 20:45:35.000000000","message":"The -\u003e This","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a1a7c4d40b7f0ef8959c062fa539dc3d7bad1eb2","unresolved":false,"context_lines":[{"line_number":59,"context_line":"for all aspects that pertain software development, from inception, to coding,"},{"line_number":60,"context_line":"testing, documentation and more."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":63,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":64,"context_line":"integrity be maintained over time when modifications to the list are required."},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_e91f34b5","line":62,"in_reply_to":"1a122d0e_7382f3c9","updated":"2016-05-03 21:19:31.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"88405de07ce5c9c23c854504894c51a70c6f5820","unresolved":false,"context_lines":[{"line_number":66,"context_line":"When is a project part of the Stadium?"},{"line_number":67,"context_line":"--------------------------------------"},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"In order to be considered part of the stadium, a project must show a track"},{"line_number":70,"context_line":"record of alignment with the Neutron core project. This means showing proof"},{"line_number":71,"context_line":"of adoption of practices as led by the Neutron core team:"},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_fd909244","line":69,"updated":"2016-05-03 19:30:14.000000000","message":"Stadium capitalized","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"88405de07ce5c9c23c854504894c51a70c6f5820","unresolved":false,"context_lines":[{"line_number":71,"context_line":"of adoption of practices as led by the Neutron core team:"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":74,"context_line":"   developer, user/operator and API guide;"},{"line_number":75,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":76,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":77,"context_line":"   downstream CI, as Grafana support will be required);"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_9da23e99","line":74,"updated":"2016-05-03 19:30:14.000000000","message":"I\u0027d add reachable from docs.o.o.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a1a7c4d40b7f0ef8959c062fa539dc3d7bad1eb2","unresolved":false,"context_lines":[{"line_number":71,"context_line":"of adoption of practices as led by the Neutron core team:"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":74,"context_line":"   developer, user/operator and API guide;"},{"line_number":75,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":76,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":77,"context_line":"   downstream CI, as Grafana support will be required);"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_29edac8e","line":74,"in_reply_to":"1a122d0e_53ea5775","updated":"2016-05-03 21:19:31.000000000","message":"developer documentation is to be maintained in tree and this proposal doesn\u0027t change that. However there are efforts where docs is virtually non-existent.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"97abc0a333d69ee3a8dd7663f74286e45a0d68f7","unresolved":false,"context_lines":[{"line_number":71,"context_line":"of adoption of practices as led by the Neutron core team:"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":74,"context_line":"   developer, user/operator and API guide;"},{"line_number":75,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":76,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":77,"context_line":"   downstream CI, as Grafana support will be required);"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_53ea5775","line":74,"in_reply_to":"1a122d0e_9da23e99","updated":"2016-05-03 20:45:35.000000000","message":"Does /developer count?  \nExample: http://docs.openstack.org/developer/octavia/\nDue to the issues we have had with maintaining our docs via the docs team (arbitrary deletions, etc.) we would really like to maintain our docs in repo.  This lets the drivers be aware of actions on the docs and to make sure features include docs updates in a simple way.  Currently the only way for us to do this is by having them available via /developer.  There are some initiatives in play to support a docs plugin model[1] which we are hoping will help us integrate better with the main docs and eliminate the /developer path, these will take time.\n\n[1] https://review.openstack.org/#/c/301284/","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":80,"context_line":" * demonstrated ability to do rolling upgrades (where applicable);"},{"line_number":81,"context_line":" * adoption of neutron-lib (with related hacking rules applied), and unit test"},{"line_number":82,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_7dc80276","line":83,"range":{"start_line":83,"start_character":3,"end_line":83,"end_character":11},"updated":"2016-05-03 19:47:55.000000000","message":"non consistent camel case","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":80,"context_line":" * demonstrated ability to do rolling upgrades (where applicable);"},{"line_number":81,"context_line":" * adoption of neutron-lib (with related hacking rules applied), and unit test"},{"line_number":82,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_7325d35a","line":83,"range":{"start_line":83,"start_character":3,"end_line":83,"end_character":11},"in_reply_to":"1a122d0e_7dc80276","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":82,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_fda252ac","line":85,"range":{"start_line":85,"start_character":32,"end_line":85,"end_character":33},"updated":"2016-05-03 19:47:55.000000000","message":"\".\" -\u003e \";\"","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":82,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_132e1f42","line":85,"range":{"start_line":85,"start_character":32,"end_line":85,"end_character":33},"in_reply_to":"1a122d0e_fda252ac","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":89,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_ddc79662","line":86,"range":{"start_line":86,"start_character":3,"end_line":86,"end_character":11},"updated":"2016-05-03 19:47:55.000000000","message":"ditto","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":83,"context_line":" * Adoption of the neutron-api subproject: submission of any API change must"},{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":89,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_332b5b35","line":86,"range":{"start_line":86,"start_character":3,"end_line":86,"end_character":11},"in_reply_to":"1a122d0e_ddc79662","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"97abc0a333d69ee3a8dd7663f74286e45a0d68f7","unresolved":false,"context_lines":[{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":89,"context_line":""},{"line_number":90,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_ee33baf4","line":87,"updated":"2016-05-03 20:45:35.000000000","message":"Should we also include a statement about CLI?  CLI is another consistency issue.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a1a7c4d40b7f0ef8959c062fa539dc3d7bad1eb2","unresolved":false,"context_lines":[{"line_number":84,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":85,"context_line":"   neutron-specs may be required."},{"line_number":86,"context_line":" * Adoption of modular interfaces to provide networking services."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":89,"context_line":""},{"line_number":90,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_099710ec","line":87,"in_reply_to":"1a122d0e_ee33baf4","updated":"2016-05-03 21:19:31.000000000","message":"Good point. I\u0027ve had it on the back of my mind. This is in line with the OSC transition plan but yes let me elaborate it.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":90,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"},{"line_number":91,"context_line":"   Neutron developers more closely. This can only be achieved when API proposals"},{"line_number":92,"context_line":"   and changes are funneled through a single initiative."},{"line_number":93,"context_line":" * To provide composable networking solutions: the ML2/Service plugin framework"},{"line_number":94,"context_line":"   was introduced many cycles ago to enable users with freedom of choice. Many"},{"line_number":95,"context_line":"   solutions have switched to using ML2/Service plugins for high level services"},{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_fa61b839","line":93,"updated":"2016-05-03 18:54:31.000000000","message":"This composable networking solution seems like a new requirement.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"85b7f90e372ede58073c25cbead02ab8b8c1c73a","unresolved":false,"context_lines":[{"line_number":90,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"},{"line_number":91,"context_line":"   Neutron developers more closely. This can only be achieved when API proposals"},{"line_number":92,"context_line":"   and changes are funneled through a single initiative."},{"line_number":93,"context_line":" * To provide composable networking solutions: the ML2/Service plugin framework"},{"line_number":94,"context_line":"   was introduced many cycles ago to enable users with freedom of choice. Many"},{"line_number":95,"context_line":"   solutions have switched to using ML2/Service plugins for high level services"},{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_78b5b07c","line":93,"in_reply_to":"1a122d0e_b871087a","updated":"2016-05-03 19:50:02.000000000","message":"This one seemed particularly new. Not suggesting anything else.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":90,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"},{"line_number":91,"context_line":"   Neutron developers more closely. This can only be achieved when API proposals"},{"line_number":92,"context_line":"   and changes are funneled through a single initiative."},{"line_number":93,"context_line":" * To provide composable networking solutions: the ML2/Service plugin framework"},{"line_number":94,"context_line":"   was introduced many cycles ago to enable users with freedom of choice. Many"},{"line_number":95,"context_line":"   solutions have switched to using ML2/Service plugins for high level services"},{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_b871087a","line":93,"in_reply_to":"1a122d0e_fa61b839","updated":"2016-05-03 19:45:18.000000000","message":"These are all _new_ requirements. What are you suggesting?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   was introduced many cycles ago to enable users with freedom of choice. Many"},{"line_number":95,"context_line":"   solutions have switched to using ML2/Service plugins for high level services"},{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"},{"line_number":97,"context_line":"   interface to provide end-to-end solutions, the criterion to enforce the adoption"},{"line_number":98,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":99,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":100,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_5a59cc8d","line":97,"updated":"2016-05-03 18:54:31.000000000","message":"I\u0027d say \"core plugin interface\" instead of monolithic.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   was introduced many cycles ago to enable users with freedom of choice. Many"},{"line_number":95,"context_line":"   solutions have switched to using ML2/Service plugins for high level services"},{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"},{"line_number":97,"context_line":"   interface to provide end-to-end solutions, the criterion to enforce the adoption"},{"line_number":98,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":99,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":100,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_b84aa825","line":97,"in_reply_to":"1a122d0e_5a59cc8d","updated":"2016-05-03 19:45:18.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"},{"line_number":97,"context_line":"   interface to provide end-to-end solutions, the criterion to enforce the adoption"},{"line_number":98,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":99,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":100,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"},{"line_number":101,"context_line":"   open networking solutions."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_fdb7f2d4","line":99,"range":{"start_line":99,"start_character":3,"end_line":99,"end_character":50},"updated":"2016-05-03 19:47:55.000000000","message":"So, in this case, even if existing solution won\u0027t change from core interface to ML2, it still will be considered as Neutron Stadium project?\nMaybe I don\u0027t understand something, but in this case nothing will change and \"old\" things will/can stay without any updates.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":96,"context_line":"   over the years. Although some plugins still use what is known as the monolithic"},{"line_number":97,"context_line":"   interface to provide end-to-end solutions, the criterion to enforce the adoption"},{"line_number":98,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":99,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":100,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"},{"line_number":101,"context_line":"   open networking solutions."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_53a7f70a","line":99,"range":{"start_line":99,"start_character":3,"end_line":99,"end_character":50},"in_reply_to":"1a122d0e_fdb7f2d4","updated":"2016-05-03 20:03:35.000000000","message":"All projects that are part of the stadium must use the same abstractions and ML2 is one of them, so no.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":102,"context_line":""},{"line_number":103,"context_line":"When a project is to be considered part of the Stadium, proof of compliance to"},{"line_number":104,"context_line":"the aforementioned practices will have to be demonstrated typically for at"},{"line_number":105,"context_line":"least two OpenStack releases. Application for inclusion is to be considered"},{"line_number":106,"context_line":"only within the first milestone of each OpenStack cycle, which is the time when"},{"line_number":107,"context_line":"the PTL and Neutron team do release planning, and have the most time available"},{"line_number":108,"context_line":"to discuss governance issues."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_ddf15697","line":105,"range":{"start_line":105,"start_character":6,"end_line":105,"end_character":28},"updated":"2016-05-03 19:47:55.000000000","message":"two *full* releases? Without additional info, it could mean that when someone will get all the pieces working short before release of Newton, it would qualify project to submit application for M1 P-release.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":102,"context_line":""},{"line_number":103,"context_line":"When a project is to be considered part of the Stadium, proof of compliance to"},{"line_number":104,"context_line":"the aforementioned practices will have to be demonstrated typically for at"},{"line_number":105,"context_line":"least two OpenStack releases. Application for inclusion is to be considered"},{"line_number":106,"context_line":"only within the first milestone of each OpenStack cycle, which is the time when"},{"line_number":107,"context_line":"the PTL and Neutron team do release planning, and have the most time available"},{"line_number":108,"context_line":"to discuss governance issues."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_f38f2373","line":105,"range":{"start_line":105,"start_character":6,"end_line":105,"end_character":28},"in_reply_to":"1a122d0e_ddf15697","updated":"2016-05-03 20:03:35.000000000","message":"Realistically we\u0027re all going to busy until Ocata-1 to rationalize what we got in the current list so yes, P seems reasonable.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":105,"context_line":"least two OpenStack releases. Application for inclusion is to be considered"},{"line_number":106,"context_line":"only within the first milestone of each OpenStack cycle, which is the time when"},{"line_number":107,"context_line":"the PTL and Neutron team do release planning, and have the most time available"},{"line_number":108,"context_line":"to discuss governance issues."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"Projects part of the Neutron Stadium have typically the first milestone to get"},{"line_number":111,"context_line":"their house in order, during which time reassessment happen; once removed, a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_9a53646c","line":108,"updated":"2016-05-03 18:54:31.000000000","message":"If a project doesn\u0027t want to be a part of Neutron after reading this, I wonder if they just apply to the TC directly now.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":105,"context_line":"least two OpenStack releases. Application for inclusion is to be considered"},{"line_number":106,"context_line":"only within the first milestone of each OpenStack cycle, which is the time when"},{"line_number":107,"context_line":"the PTL and Neutron team do release planning, and have the most time available"},{"line_number":108,"context_line":"to discuss governance issues."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"Projects part of the Neutron Stadium have typically the first milestone to get"},{"line_number":111,"context_line":"their house in order, during which time reassessment happen; once removed, a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_5811d403","line":108,"in_reply_to":"1a122d0e_9a53646c","updated":"2016-05-03 19:45:18.000000000","message":"That\u0027s one option, as outlined in the next section.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":161,"context_line":"will continue to hold +W rights on both repos. It is noteworthy that members"},{"line_number":162,"context_line":"of the individual core teams are and will be considered as members of the"},{"line_number":163,"context_line":"drivers team on a regular basis. Level of participation in reviewing RFE"},{"line_number":164,"context_line":"submissions, experience with the Neutron codebase, and committment to the"},{"line_number":165,"context_line":"project are factors taken into account when identifying members of this team."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"The reason behind the existence of this effort and the requirement to go"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_1dbbce76","line":164,"range":{"start_line":164,"start_character":55,"end_line":164,"end_character":66},"updated":"2016-05-03 19:47:55.000000000","message":"typo: commitment","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":161,"context_line":"will continue to hold +W rights on both repos. It is noteworthy that members"},{"line_number":162,"context_line":"of the individual core teams are and will be considered as members of the"},{"line_number":163,"context_line":"drivers team on a regular basis. Level of participation in reviewing RFE"},{"line_number":164,"context_line":"submissions, experience with the Neutron codebase, and committment to the"},{"line_number":165,"context_line":"project are factors taken into account when identifying members of this team."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"The reason behind the existence of this effort and the requirement to go"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_73f2f307","line":164,"range":{"start_line":164,"start_character":55,"end_line":164,"end_character":66},"in_reply_to":"1a122d0e_1dbbce76","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":168,"context_line":"through neutron-specs for API proposals is two-fold: a) ensure continuous"},{"line_number":169,"context_line":"alignment across all APIs exposed from Neutron Stadium projects; b) provide"},{"line_number":170,"context_line":"a place in the OpenStack networking community to discuss and achieve consensus"},{"line_number":171,"context_line":"on networking abstractions."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"What happens to the current list of Neutron Stadium projects?"},{"line_number":174,"context_line":"-------------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_1ac63416","line":171,"updated":"2016-05-03 18:54:31.000000000","message":"This entire document seems to be very strict about everything EXCEPT what to me is important: Ditching extensions and adding resources to core attributes. We need to say \"this is the common API and you cannot extend things like ports, networks, subnets, and routers\" and be done. Otherwise, we\u0027re just dancing around this issue and it makes us look silly. I\u0027d expect that to be part of this evolution.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":168,"context_line":"through neutron-specs for API proposals is two-fold: a) ensure continuous"},{"line_number":169,"context_line":"alignment across all APIs exposed from Neutron Stadium projects; b) provide"},{"line_number":170,"context_line":"a place in the OpenStack networking community to discuss and achieve consensus"},{"line_number":171,"context_line":"on networking abstractions."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"What happens to the current list of Neutron Stadium projects?"},{"line_number":174,"context_line":"-------------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_58b6f4f9","line":171,"in_reply_to":"1a122d0e_1ac63416","updated":"2016-05-03 19:45:18.000000000","message":"Embracing microversioning or anything of that sorts (if this is what you\u0027re implying) can be considered a next step but I\u0027d rather not conflate the two argument together. This is a journey and it\u0027ll take us more than a single iteration to get to where we need to be.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"85b7f90e372ede58073c25cbead02ab8b8c1c73a","unresolved":false,"context_lines":[{"line_number":168,"context_line":"through neutron-specs for API proposals is two-fold: a) ensure continuous"},{"line_number":169,"context_line":"alignment across all APIs exposed from Neutron Stadium projects; b) provide"},{"line_number":170,"context_line":"a place in the OpenStack networking community to discuss and achieve consensus"},{"line_number":171,"context_line":"on networking abstractions."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"What happens to the current list of Neutron Stadium projects?"},{"line_number":174,"context_line":"-------------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_f8570024","line":171,"in_reply_to":"1a122d0e_58b6f4f9","updated":"2016-05-03 19:50:02.000000000","message":"I think it\u0027s a critical step IMHO, because without doing this, we\u0027re still not in control of the API itself. I guess if we\u0027re going to look closely at how people are \"refining\" the API to meet their own products we can use that as a tent pole for adding them into the stadium or not.\n\nOf course those who are \"refining\" the API are not gonna be in the stadium anyways.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":168,"context_line":"through neutron-specs for API proposals is two-fold: a) ensure continuous"},{"line_number":169,"context_line":"alignment across all APIs exposed from Neutron Stadium projects; b) provide"},{"line_number":170,"context_line":"a place in the OpenStack networking community to discuss and achieve consensus"},{"line_number":171,"context_line":"on networking abstractions."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"What happens to the current list of Neutron Stadium projects?"},{"line_number":174,"context_line":"-------------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_d3e1472c","line":171,"in_reply_to":"1a122d0e_f8570024","updated":"2016-05-03 20:03:35.000000000","message":"once we get to neutron-api we can devise mechanisms to restrain that, but until we get there the discussion is moot IMO","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":200,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":201,"context_line":""},{"line_number":202,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":203,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":204,"context_line":"* networking-l2gw: similarly to neutron-vpnaas, this needs to:"},{"line_number":205,"context_line":""},{"line_number":206,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_7d1f6270","line":203,"range":{"start_line":203,"start_character":27,"end_line":203,"end_character":49},"updated":"2016-05-03 19:47:55.000000000","message":"Does it mean, this project is excepted from Stadium transition? It has more time?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":200,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":201,"context_line":""},{"line_number":202,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":203,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":204,"context_line":"* networking-l2gw: similarly to neutron-vpnaas, this needs to:"},{"line_number":205,"context_line":""},{"line_number":206,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_1339ffa3","line":203,"range":{"start_line":203,"start_character":27,"end_line":203,"end_character":49},"in_reply_to":"1a122d0e_7d1f6270","updated":"2016-05-03 20:03:35.000000000","message":"no, I mean they started off on the right path, as they were developed in the main tree so I presume they would be able to comply right off the bat. It\u0027ll have to be revisited in Ocata 1 as all the others.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":241,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":242,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_9ada44e8","line":244,"updated":"2016-05-03 18:54:31.000000000","message":"We already support this (Hyper-V and KVM/Xen, there is no OVS support in ESX today).","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":241,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":242,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_b8c9085d","line":244,"in_reply_to":"1a122d0e_9ada44e8","updated":"2016-05-03 19:45:18.000000000","message":"What PowerVM? :)\n\nMy point is: any multi-hypervisor support under the current arrangement can only achieved within the context of OVN without the ability of leveraging third party solutions. More will have to be done even if OVN went ML2 in order to support ESX.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_dae4bcad","line":247,"updated":"2016-05-03 18:54:31.000000000","message":"Wow.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_535a57f3","line":247,"in_reply_to":"1a122d0e_1833dc14","updated":"2016-05-03 20:03:35.000000000","message":"As I always said publicly, contemplating such a thing can only be done on the basis that we\u0027re swapping oranges with oranges.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_f8c38036","line":247,"in_reply_to":"1a122d0e_dae4bcad","updated":"2016-05-03 19:45:18.000000000","message":"and?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"85b7f90e372ede58073c25cbead02ab8b8c1c73a","unresolved":false,"context_lines":[{"line_number":244,"context_line":"  * considered as a solution for multi-hypervisor deployments."},{"line_number":245,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_1833dc14","line":247,"in_reply_to":"1a122d0e_f8c38036","updated":"2016-05-03 19:50:02.000000000","message":"No, I was just surprised to see this brought up here, and by you no less. :)","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":251,"context_line":"    that the Neutron team develops against ML2."},{"line_number":252,"context_line":"  * Composability of services across the entire L2-L7 stack."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_faeff883","line":249,"updated":"2016-05-03 18:54:31.000000000","message":"We already support this with HW-VTEP support.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"85b7f90e372ede58073c25cbead02ab8b8c1c73a","unresolved":false,"context_lines":[{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":251,"context_line":"    that the Neutron team develops against ML2."},{"line_number":252,"context_line":"  * Composability of services across the entire L2-L7 stack."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_583d54dc","line":249,"in_reply_to":"1a122d0e_78e650e9","updated":"2016-05-03 19:50:02.000000000","message":"#truestory","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a9fc152a960432b42412bde17a403b292a3d29c5","unresolved":false,"context_lines":[{"line_number":246,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":247,"context_line":"    like for like."},{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":251,"context_line":"    that the Neutron team develops against ML2."},{"line_number":252,"context_line":"  * Composability of services across the entire L2-L7 stack."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_78e650e9","line":249,"in_reply_to":"1a122d0e_faeff883","updated":"2016-05-03 19:45:18.000000000","message":"That\u0027s not nearly enough and you know it.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":248,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":251,"context_line":"    that the Neutron team develops against ML2."},{"line_number":252,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":253,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":254,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_3aea1075","line":251,"updated":"2016-05-03 18:54:31.000000000","message":"This sounds nice!","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c16363abc5624b1d0e0490c590015cdd3bfc6f4d","unresolved":false,"context_lines":[{"line_number":249,"context_line":"    Neutron deployment."},{"line_number":250,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":251,"context_line":"    that the Neutron team develops against ML2."},{"line_number":252,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":253,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_1a9474e6","line":252,"updated":"2016-05-03 18:54:31.000000000","message":"One can dream, right?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":272,"context_line":"The Stadium creates a place for like-minded people to collaborate, innovate,"},{"line_number":273,"context_line":"and iterate on networking solutions, and provides a degree of guarantee that"},{"line_number":274,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":275,"context_line":"within the Stadium, thus inducing a  more sustainable maintenance effort on"},{"line_number":276,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsability of"},{"line_number":277,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_78565007","line":275,"range":{"start_line":275,"start_character":35,"end_line":275,"end_character":37},"updated":"2016-05-03 19:47:55.000000000","message":"nit: extra whitespace.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":272,"context_line":"The Stadium creates a place for like-minded people to collaborate, innovate,"},{"line_number":273,"context_line":"and iterate on networking solutions, and provides a degree of guarantee that"},{"line_number":274,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":275,"context_line":"within the Stadium, thus inducing a  more sustainable maintenance effort on"},{"line_number":276,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsability of"},{"line_number":277,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_13073fca","line":275,"range":{"start_line":275,"start_character":35,"end_line":275,"end_character":37},"in_reply_to":"1a122d0e_78565007","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"0a40064178127add9d57bfcb7db2b0973a8177fb","unresolved":false,"context_lines":[{"line_number":273,"context_line":"and iterate on networking solutions, and provides a degree of guarantee that"},{"line_number":274,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":275,"context_line":"within the Stadium, thus inducing a  more sustainable maintenance effort on"},{"line_number":276,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsability of"},{"line_number":277,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":279,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_387338b6","line":276,"range":{"start_line":276,"start_character":60,"end_line":276,"end_character":74},"updated":"2016-05-03 19:47:55.000000000","message":"typo: responsibility","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9e2326815756489408c639946c69c6e1aedc5b67","unresolved":false,"context_lines":[{"line_number":273,"context_line":"and iterate on networking solutions, and provides a degree of guarantee that"},{"line_number":274,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":275,"context_line":"within the Stadium, thus inducing a  more sustainable maintenance effort on"},{"line_number":276,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsability of"},{"line_number":277,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":279,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_93f34fe7","line":276,"range":{"start_line":276,"start_character":60,"end_line":276,"end_character":74},"in_reply_to":"1a122d0e_387338b6","updated":"2016-05-03 20:03:35.000000000","message":"Done","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"97abc0a333d69ee3a8dd7663f74286e45a0d68f7","unresolved":false,"context_lines":[{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":279,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"},{"line_number":280,"context_line":"process and have the same status of any other OpenStack Active Technical"},{"line_number":281,"context_line":"Contributor."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"What are the drawbacks of this proposal?"},{"line_number":284,"context_line":"----------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_0e06f684","line":281,"updated":"2016-05-03 20:45:35.000000000","message":"What about release management?  This seems to be a benefit under the stadium.","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a1a7c4d40b7f0ef8959c062fa539dc3d7bad1eb2","unresolved":false,"context_lines":[{"line_number":278,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":279,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"},{"line_number":280,"context_line":"process and have the same status of any other OpenStack Active Technical"},{"line_number":281,"context_line":"Contributor."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"What are the drawbacks of this proposal?"},{"line_number":284,"context_line":"----------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_a9889cc7","line":281,"in_reply_to":"1a122d0e_0e06f684","updated":"2016-05-03 21:19:31.000000000","message":"see line 277?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"97abc0a333d69ee3a8dd7663f74286e45a0d68f7","unresolved":false,"context_lines":[{"line_number":290,"context_line":"it should be clear by now that associating a bad connotation to projects that"},{"line_number":291,"context_line":"are not part of the Stadium is simply a misconception: some projects can indeed"},{"line_number":292,"context_line":"apply to be top-level projects in OpenStack, and others are simply better off"},{"line_number":293,"context_line":"by being independent initiatives."},{"line_number":294,"context_line":""},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"Are there any alternatives worth considering?"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_ce435eae","line":293,"updated":"2016-05-03 20:45:35.000000000","message":"We should also not gloss over the amount of work being asked of the teams not currently in compliance.  It\u0027s a trade off of working on new features vs. aligning with some of the *new-ish* requirements (neutron-api, neutron-lib, etc.).","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"a1a7c4d40b7f0ef8959c062fa539dc3d7bad1eb2","unresolved":false,"context_lines":[{"line_number":290,"context_line":"it should be clear by now that associating a bad connotation to projects that"},{"line_number":291,"context_line":"are not part of the Stadium is simply a misconception: some projects can indeed"},{"line_number":292,"context_line":"apply to be top-level projects in OpenStack, and others are simply better off"},{"line_number":293,"context_line":"by being independent initiatives."},{"line_number":294,"context_line":""},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"Are there any alternatives worth considering?"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a122d0e_89aa0019","line":293,"in_reply_to":"1a122d0e_ce435eae","updated":"2016-05-03 21:19:31.000000000","message":"yes, that\u0027s what I mean by line 286? Do you think I did not put enough emphasis on the matter?","commit_id":"8a8780a421343695b9295ba5ed4bdd85b2588e4a"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"bdc2fdff08e3898c97d8c3e483ca6b63207d69e4","unresolved":false,"context_lines":[{"line_number":242,"context_line":""},{"line_number":243,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":244,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":245,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":248,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_ada267ab","line":245,"updated":"2016-05-03 21:39:09.000000000","message":"so any Ml2 driver is part of the stadium?","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"1504a82eae0bc3e0c6ae90db0fbaf9ce057d2afc","unresolved":false,"context_lines":[{"line_number":242,"context_line":""},{"line_number":243,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":244,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":245,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":248,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_f021d49f","line":245,"in_reply_to":"1a122d0e_ada267ab","updated":"2016-05-03 21:56:19.000000000","message":"no.","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"bdc2fdff08e3898c97d8c3e483ca6b63207d69e4","unresolved":false,"context_lines":[{"line_number":248,"context_line":"    currently only true if a hypervisor runs Open vSwitch."},{"line_number":249,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":250,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":251,"context_line":"    like for like."},{"line_number":252,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":253,"context_line":"    Neutron deployment; hardware vtep support only is limiting a number"},{"line_number":254,"context_line":"    of potential bare metal scenarios that leverage third party solutions."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_6d996f79","line":251,"updated":"2016-05-03 21:39:09.000000000","message":"concern here is that currenly there is no metadata support - that is, of native DHCP and L3 are used how will metadata be done","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"1504a82eae0bc3e0c6ae90db0fbaf9ce057d2afc","unresolved":false,"context_lines":[{"line_number":248,"context_line":"    currently only true if a hypervisor runs Open vSwitch."},{"line_number":249,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":250,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":251,"context_line":"    like for like."},{"line_number":252,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":253,"context_line":"    Neutron deployment; hardware vtep support only is limiting a number"},{"line_number":254,"context_line":"    of potential bare metal scenarios that leverage third party solutions."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_3034ecdd","line":251,"in_reply_to":"1a122d0e_6d996f79","updated":"2016-05-03 21:56:19.000000000","message":"\u0027like for like\u0027 is exactly addressing your concern. No-one is suggesting we propose the switch tomorrow, if ever, but it\u0027d be nice to have at least the option whether we take it or not.","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"5af06db7e5a8ceea5a856d6b71cb8bb087c54fc6","unresolved":false,"context_lines":[{"line_number":263,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":264,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":265,"context_line":"  project."},{"line_number":266,"context_line":"* python-neutron-pd-driver: to be folded into python-neutronclient."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":269,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_ce66beba","line":266,"updated":"2016-05-03 20:41:52.000000000","message":"pd-driver isn\u0027t a client extension, it\u0027s an IPv6 prefix-delegation driver, so I don\u0027t understand the client relationship here.","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"04d996cbdfac3a232e23ba4cc4195282ea257951","unresolved":false,"context_lines":[{"line_number":263,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":264,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":265,"context_line":"  project."},{"line_number":266,"context_line":"* python-neutron-pd-driver: to be folded into python-neutronclient."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":269,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_9cd4f71f","line":266,"in_reply_to":"1a122d0e_41aefce7","updated":"2016-05-04 01:14:05.000000000","message":"Ok, if we want to prevent it from rotting it, then we should bring it in the Neutron tree. If not, I see no reason why it\u0027s enlisted in the Stadium, as no-one is involved with this. Its core team is Sam Betts and the repo has only 3 commits. As far as I can tell this is already broken/rotten.","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"dfec75d79ed02de8823a40e54263ec918135dcac","unresolved":false,"context_lines":[{"line_number":263,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":264,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":265,"context_line":"  project."},{"line_number":266,"context_line":"* python-neutron-pd-driver: to be folded into python-neutronclient."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":269,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_41aefce7","line":266,"in_reply_to":"1a122d0e_89396042","updated":"2016-05-04 00:07:04.000000000","message":"This python code was developed as a contingency in case the plan to use dibbler as a PD client didn\u0027t work out. Now we do use dibbler and we have a driver for it. I have not heard of users/distros having a problem with installing dibbler as a requirement. However, I don\u0027t know of any operators using prefix delegation with neutron.\n\nIMO we should keep the python-neutron-pd-driver code up our sleeve in case it is needed when prefix delegation becomes popular. But I don\u0027t know how \u0027up our sleeve\u0027 fits in the governance model.","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"775d495f7b386768a6b545989a61216f27361fb6","unresolved":false,"context_lines":[{"line_number":263,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":264,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":265,"context_line":"  project."},{"line_number":266,"context_line":"* python-neutron-pd-driver: to be folded into python-neutronclient."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":269,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_89396042","line":266,"in_reply_to":"1a122d0e_ce66beba","updated":"2016-05-03 21:31:58.000000000","message":"Thanks for looking into this. Do you know more about this effort? All I could find was [1], and I didn\u0027t delve into the patches themselves. Because of the naming convention I assumed it was a client extension, but I was clearly wrong, and I was hoping that some like you would chime in.\n\nThere are no docs I could find or anything else. I see two options: a) bring it back into neutron core tree and start testing to validate the use case this addresses or leave it as is and submit it to the same criteria as the others.\n\n[1] https://review.openstack.org/#/q/project:openstack/python-neutron-pd-driver","commit_id":"0e766ec920e927a5583ce6214253eb52383c239b"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"499d301cea31cdb6482dd2b9c90124f242487c35","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Define what the Neutron Stadium is."},{"line_number":14,"context_line":"* Define the meaning of the networking community within OpenStack."},{"line_number":15,"context_line":"* Define guidelines on how to maintain the Stadium over time."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_4daf532b","line":13,"updated":"2016-05-03 21:52:32.000000000","message":"I feel like there needs to be a more clear definition of what benefits there are to being in the Neutron Stadium versus out of it.  I think there is a misconception that being in the Neutron Stadium means you are \"blessed\" by the Neutron team as supported.  Assaf had a good idea that the word \"assisted\" is a more accurate term for projects in the stadium and \"independent\" for those not.  I like those because it does not imply any kind of blessing.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"e44860610bccb929a3d4f839e0354b39b971132f","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Define what the Neutron Stadium is."},{"line_number":14,"context_line":"* Define the meaning of the networking community within OpenStack."},{"line_number":15,"context_line":"* Define guidelines on how to maintain the Stadium over time."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_fc81abc4","line":13,"in_reply_to":"1a122d0e_10c9f0ac","updated":"2016-05-04 01:30:31.000000000","message":"I wasn\u0027t saying this proposal was saying the word \"blessed\" at all.  I was simply stating the fact that there has been a misconception about what the stadium has been, and many people I\u0027ve talked to that are not heavily involved in neutron have had the misconception that being in the stadium means you are \"blessed\".  I was suggesting that an explicit refutation that any project in the stadium is somehow blessed (or any other appropriate synonym) would maybe help with those misconceptions.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3227fb2daca3c15d8a04bf91ce3813c8d24fc81b","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Define what the Neutron Stadium is."},{"line_number":14,"context_line":"* Define the meaning of the networking community within OpenStack."},{"line_number":15,"context_line":"* Define guidelines on how to maintain the Stadium over time."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_10c9f0ac","line":13,"in_reply_to":"1a122d0e_4daf532b","updated":"2016-05-03 22:07:25.000000000","message":"Have you seen the use of word \u0027blessed\u0027 used anywhere in this proposal or even the etherpad? Section on line 285 should address your concern regarding benefits: if you can help me elaborate further I\u0027d appreciate it.\n\nAs for the use of assisted, independent etc I honestly struggle to see the point: we need to maintain a list of projects someone is ought to be responsible for whilst keeping sanity and consistency across them all. We follow the procedure that the TC has set out for all the openstack projects. Any attempt of layering a new nomenclature should be taken up with the TC and goes beyond the scope of this effort IMO.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"499d301cea31cdb6482dd2b9c90124f242487c35","unresolved":false,"context_lines":[{"line_number":84,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":85,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":86,"context_line":"   neutron-specs may be required;"},{"line_number":87,"context_line":" * adoption of modular interfaces to provide networking services;"},{"line_number":88,"context_line":" * develop client bindings and CLI according to OSC transition `plan \u003chttps://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst\u003e`_ (where applicable). This means that Neutron Stadium"},{"line_number":89,"context_line":"   projects will have their client side hosted in python-neutronclient."},{"line_number":90,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_ad642721","line":87,"updated":"2016-05-03 21:52:32.000000000","message":"does this mean neutron stadium projects must be pluggable? or the networking services must be plugins? i think this needs to be more clear.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3227fb2daca3c15d8a04bf91ce3813c8d24fc81b","unresolved":false,"context_lines":[{"line_number":84,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":85,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":86,"context_line":"   neutron-specs may be required;"},{"line_number":87,"context_line":" * adoption of modular interfaces to provide networking services;"},{"line_number":88,"context_line":" * develop client bindings and CLI according to OSC transition `plan \u003chttps://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst\u003e`_ (where applicable). This means that Neutron Stadium"},{"line_number":89,"context_line":"   projects will have their client side hosted in python-neutronclient."},{"line_number":90,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_1040d006","line":87,"in_reply_to":"1a122d0e_ad642721","updated":"2016-05-03 22:07:25.000000000","message":"I\u0027ll elaborate more.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"499d301cea31cdb6482dd2b9c90124f242487c35","unresolved":false,"context_lines":[{"line_number":101,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":102,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":103,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"},{"line_number":104,"context_line":"   open networking solutions."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"When a project is to be considered part of the Stadium, proof of compliance to"},{"line_number":107,"context_line":"the aforementioned practices will have to be demonstrated typically for at"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_2d7137df","line":104,"updated":"2016-05-03 21:52:32.000000000","message":"How will guarantees be made about the stability of the core plugin interface? (i.e. changes don\u0027t frequently break out-of-tree plugins).","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3227fb2daca3c15d8a04bf91ce3813c8d24fc81b","unresolved":false,"context_lines":[{"line_number":101,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":102,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":103,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"},{"line_number":104,"context_line":"   open networking solutions."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"When a project is to be considered part of the Stadium, proof of compliance to"},{"line_number":107,"context_line":"the aforementioned practices will have to be demonstrated typically for at"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_50f888c4","line":104,"in_reply_to":"1a122d0e_2d7137df","updated":"2016-05-03 22:07:25.000000000","message":"During code review we strive to ensure that changes and design implications do not break out of tree code irrespective of whether it\u0027s part of the stadium (eg. *-aas) or not (e.g plugin foo). This proposal does not affect nor improve that guarantee, at least not until we can get neutron-lib to take off.","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"499d301cea31cdb6482dd2b9c90124f242487c35","unresolved":false,"context_lines":[{"line_number":124,"context_line":"Furthermore, projects that interact with Neutron purely via its REST API should"},{"line_number":125,"context_line":"also be incentivized to seek other forms of governance, such as applying as"},{"line_number":126,"context_line":"top-level OpenStack project and follow the new project requirements as outlined"},{"line_number":127,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_, rather than going for Stadium inclusion."},{"line_number":128,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"},{"line_number":129,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":130,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_cd48838d","line":127,"range":{"start_line":127,"start_character":106,"end_line":127,"end_character":147},"updated":"2016-05-03 21:52:32.000000000","message":"nit: too long of a line","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3227fb2daca3c15d8a04bf91ce3813c8d24fc81b","unresolved":false,"context_lines":[{"line_number":124,"context_line":"Furthermore, projects that interact with Neutron purely via its REST API should"},{"line_number":125,"context_line":"also be incentivized to seek other forms of governance, such as applying as"},{"line_number":126,"context_line":"top-level OpenStack project and follow the new project requirements as outlined"},{"line_number":127,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_, rather than going for Stadium inclusion."},{"line_number":128,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"},{"line_number":129,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":130,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_30f34ce9","line":127,"range":{"start_line":127,"start_character":106,"end_line":127,"end_character":147},"in_reply_to":"1a122d0e_cd48838d","updated":"2016-05-03 22:07:25.000000000","message":"oops","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"499d301cea31cdb6482dd2b9c90124f242487c35","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":157,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":158,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":159,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":160,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":161,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":162,"context_line":"required. Each core team of projects belonging to the Stadium will have +2"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_4d5d9347","line":159,"updated":"2016-05-03 21:52:32.000000000","message":"does this mean that stadium projects who wish to expose new API resources will have add code in the neutron-api project instead of in the project itself?","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3227fb2daca3c15d8a04bf91ce3813c8d24fc81b","unresolved":false,"context_lines":[{"line_number":156,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":157,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":158,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":159,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":160,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":161,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":162,"context_line":"required. Each core team of projects belonging to the Stadium will have +2"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_900220b3","line":159,"in_reply_to":"1a122d0e_4d5d9347","updated":"2016-05-03 22:07:25.000000000","message":"yes","commit_id":"3017d169d405bac9d06fcadb465208a4c59c37e4"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_90d037cb","line":8,"updated":"2016-05-04 17:41:31.000000000","message":"Once the transformation is complete, please consider using a different term in place of \"Stadium\" - for instance \"Circus\"","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_0ebec8fe","line":8,"in_reply_to":"1a122d0e_90d037cb","updated":"2016-05-04 17:52:50.000000000","message":"I can\u0027t say I agree, but I never liked Stadium in the first place.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"d7101a8e2ef238f7ac2be180fa923c1e42484ab6","unresolved":false,"context_lines":[{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"`vetting \u003chttp://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d\u003e`_"},{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_1202793e","line":35,"updated":"2016-05-04 14:16:10.000000000","message":"I still have issues with this wording. The governance patch you list merely indicates that the additional repositories being \"rubber stamped\" by the TC chair (after PTL approval and a week sitting in the queue) were to further the project\u0027s mission. Also, there is no specific mention of Neutron in there, this applies for all projects. The wording here continues to imply there was some nefarious means to an end going on, which was never the case (and this is coming from me, the nasty PTL who got us into this mess you are cleaning us out of).\n\nIf we\u0027re codifying this, I want this section changed, either to removal the implication that there was some sort of TC bypass, or to just call me out as the bad guy. :)","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"691b04cc5ef090feba9af86c51488df62c98b735","unresolved":false,"context_lines":[{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"`vetting \u003chttp://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d\u003e`_"},{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_2bad7b88","line":35,"in_reply_to":"1a122d0e_1202793e","updated":"2016-05-04 16:10:16.000000000","message":"I\u0027ll rephrase, but if you have any suggestion I\u0027d be happy to take it.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"e194efac5e4edf6c94f3f1f785b7613b9081c560","unresolved":false,"context_lines":[{"line_number":32,"context_line":"`arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e`_ made it possible for"},{"line_number":33,"context_line":"projects to be _automatically_ enlisted as a Neutron project, bypassing the TC"},{"line_number":34,"context_line":"`vetting \u003chttp://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d\u003e`_"},{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_e94541b4","line":35,"in_reply_to":"1a122d0e_2bad7b88","updated":"2016-05-04 20:04:05.000000000","message":"How about this:\n\n\"The outcome of that initiative has yielded mixed results, nonetheless giving the various individual teams that came out of it the opportunity to iterate faster and reduce the time to feature. This has been due to the increased autonomy and trust relationship implicit in the current system. The proposed ``arrangement \u003chttps://review.openstack.org/#/c/175952/\u003e` made it possible for projects to be _automatically_ enlisted under the Neutron umbrella, making unnecessary the TC `vetting \u003chttp://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d\u003e`_ process. The trust model cannot scale if both sides do not adhere to it, so sadly this has meant we find ourselves in a situation where neither side trusts the other. The mission of the PTL/drivers team is to ensure consistency in the APIs, architecture, design, implementation and testing of the project. Once the trust model breaks down, this is no longer possible. To ensure a level of quality in how aspects such as documentation, inter-project communication, release management, and stable backports are dealt with, a new system needs to be put in place which extends beyond trust.\"","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"d7101a8e2ef238f7ac2be180fa923c1e42484ab6","unresolved":false,"context_lines":[{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"},{"line_number":39,"context_line":"of the project, and at the same time ensure a level of quality in how aspects,"},{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_52aa311a","line":38,"updated":"2016-05-04 14:16:10.000000000","message":"Consistency in the APIs without micro-versioning and allowing extensions on core resources? This is where I have a problem with this. It\u0027s like you\u0027re taking this all the way to the finish line, and then stopping just short and letting everyone else cross while we celebrate being near the end.\n\nI think we should just add in API consistency in this patch, codify micro-versions, and get to where Neutron should have been 4 years ago: A common consistent API across all the backends. Period.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"},{"line_number":39,"context_line":"of the project, and at the same time ensure a level of quality in how aspects,"},{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_6eadbc9a","line":38,"in_reply_to":"1a122d0e_13e71141","updated":"2016-05-04 17:52:50.000000000","message":"Not sure what your point is TBH. If you can rephrase, that\u0027ll help me capture your input.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"},{"line_number":39,"context_line":"of the project, and at the same time ensure a level of quality in how aspects,"},{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_13e71141","line":38,"in_reply_to":"1a122d0e_52aa311a","updated":"2016-05-04 17:41:31.000000000","message":"But what about \"innovation\" and  \"enabling unique features\"?\nDon\u0027t you think that neutron as a community needs them to thrive?\n\nFor the purpose of this proposal we can just say that the API has to be consistent though! Also because it\u0027s not just about the REST API, but also the plugin API ;)\n\n/me runs and ducks","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":35,"context_line":"process altogether, and yet without ever formally be screened by the"},{"line_number":36,"context_line":"PTL and/or the core team, not at inception, nor on an ongoing basis. While"},{"line_number":37,"context_line":"this may seem okay at first, the mission of the PTL/drivers team is to ensure"},{"line_number":38,"context_line":"consistency in the APIs, architecture, design, implementation and testing"},{"line_number":39,"context_line":"of the project, and at the same time ensure a level of quality in how aspects,"},{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_1daa8019","line":38,"in_reply_to":"1a122d0e_52aa311a","updated":"2016-05-04 17:38:03.000000000","message":"If we don\u0027t embark on the journey of centralizing the API and focus efforts in one place that\u0027s unachievable. I am surprised that you amongst all is the one taking such a strict stance.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"db15989658092da605b8cb4ef06881ead5b37df7","unresolved":false,"context_lines":[{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The existing arrangement of conceding autonomy, and striving for consistency"},{"line_number":44,"context_line":"was clearly paradoxical because of the two conflicting forces at play. A"},{"line_number":45,"context_line":"better balance must be struck in a way that Neutron development can continue on"},{"line_number":46,"context_line":"its trajectory of agile development without compromising consistency, and"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_5a307e07","line":43,"range":{"start_line":43,"start_character":4,"end_line":43,"end_character":12},"updated":"2016-05-04 17:11:54.000000000","message":"nit:  \"The existing arrangement ... was\".  I\u0027d either remove \"existing\" or change \"was\" to \"is\".  I think the former is what you\u0027re after.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"220de7fc3661637c6d17576f9a307b67c79bd69d","unresolved":false,"context_lines":[{"line_number":40,"context_line":"like documentation, inter-project communication, release management, stable"},{"line_number":41,"context_line":"backports etc are dealt with."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The existing arrangement of conceding autonomy, and striving for consistency"},{"line_number":44,"context_line":"was clearly paradoxical because of the two conflicting forces at play. A"},{"line_number":45,"context_line":"better balance must be struck in a way that Neutron development can continue on"},{"line_number":46,"context_line":"its trajectory of agile development without compromising consistency, and"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ee2eec8a","line":43,"in_reply_to":"1a122d0e_5a307e07","updated":"2016-05-04 17:40:58.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":43,"context_line":"The existing arrangement of conceding autonomy, and striving for consistency"},{"line_number":44,"context_line":"was clearly paradoxical because of the two conflicting forces at play. A"},{"line_number":45,"context_line":"better balance must be struck in a way that Neutron development can continue on"},{"line_number":46,"context_line":"its trajectory of agile development without compromising consistency, and"},{"line_number":47,"context_line":"without making the PTL, and the Neutron team a bottleneck in the day to day"},{"line_number":48,"context_line":"management duties of the project."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_3307adca","line":46,"updated":"2016-05-04 17:41:31.000000000","message":"was Neutron development ever agile?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":43,"context_line":"The existing arrangement of conceding autonomy, and striving for consistency"},{"line_number":44,"context_line":"was clearly paradoxical because of the two conflicting forces at play. A"},{"line_number":45,"context_line":"better balance must be struck in a way that Neutron development can continue on"},{"line_number":46,"context_line":"its trajectory of agile development without compromising consistency, and"},{"line_number":47,"context_line":"without making the PTL, and the Neutron team a bottleneck in the day to day"},{"line_number":48,"context_line":"management duties of the project."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_6eb2dce6","line":46,"in_reply_to":"1a122d0e_3307adca","updated":"2016-05-04 17:52:50.000000000","message":"some people may say it has improved, but your mileage may vary.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":64,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":65,"context_line":"the Neutron team and PTL claim responsability for when producing Neutron"},{"line_number":66,"context_line":"deliverables throughout the release cycles."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_cf134eb6","line":65,"updated":"2016-05-04 07:27:58.000000000","message":"%s/responsability/reponsibility/g","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":64,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":65,"context_line":"the Neutron team and PTL claim responsability for when producing Neutron"},{"line_number":66,"context_line":"deliverables throughout the release cycles."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_9d6cd009","line":65,"in_reply_to":"1a122d0e_cf134eb6","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"ef888b5b04eb05db6179b9ad4b995ffe755c1474","unresolved":false,"context_lines":[{"line_number":63,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":64,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":65,"context_line":"the Neutron team and PTL claim responsability for when producing Neutron"},{"line_number":66,"context_line":"deliverables throughout the release cycles."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":69,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_9c96b7ed","line":66,"updated":"2016-05-04 01:31:44.000000000","message":"Ah this is pretty much what I was suggesting in PS4.  Thanks.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":63,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":64,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":65,"context_line":"the Neutron team and PTL claim responsability for when producing Neutron"},{"line_number":66,"context_line":"deliverables throughout the release cycles."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":69,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_dd5da849","line":66,"in_reply_to":"1a122d0e_9c96b7ed","updated":"2016-05-04 17:38:03.000000000","message":"I figured I could be more explicit, but I am sure that some can still be confused if they wanted to :)","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":95,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":96,"context_line":"   flavor framework as necessary."},{"line_number":97,"context_line":" * develop client bindings and CLI according to OSC transition `plan \u003chttps://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst\u003e`_ (where applicable). This means that Neutron Stadium"},{"line_number":98,"context_line":"   projects will have their client side hosted in python-neutronclient."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The last two criteria are particularly important for the following reasons:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ca4e9c6d","line":97,"updated":"2016-05-04 07:27:58.000000000","message":"Is there any criteria about holding separate IRC\u0027s for each sub-projects?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":95,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":96,"context_line":"   flavor framework as necessary."},{"line_number":97,"context_line":" * develop client bindings and CLI according to OSC transition `plan \u003chttps://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst\u003e`_ (where applicable). This means that Neutron Stadium"},{"line_number":98,"context_line":"   projects will have their client side hosted in python-neutronclient."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The last two criteria are particularly important for the following reasons:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_bd1f0c6f","line":97,"in_reply_to":"1a122d0e_ca4e9c6d","updated":"2016-05-04 17:38:03.000000000","message":"no, any team working on Neutron is free to meet in any shape or form, as it\u0027s always been.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"db15989658092da605b8cb4ef06881ead5b37df7","unresolved":false,"context_lines":[{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"},{"line_number":103,"context_line":"   Neutron developers more closely. This can only be achieved when API proposals"},{"line_number":104,"context_line":"   and changes are funneled through a single initiative."},{"line_number":105,"context_line":" * To provide composable networking solutions: the ML2/Service plugin framework"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_bdbeecfd","line":102,"range":{"start_line":102,"start_character":59,"end_line":102,"end_character":67},"updated":"2016-05-04 17:11:54.000000000","message":"operators","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"220de7fc3661637c6d17576f9a307b67c79bd69d","unresolved":false,"context_lines":[{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":" * To provide a consistent API experience to Neutron users/opertors and assist"},{"line_number":103,"context_line":"   Neutron developers more closely. This can only be achieved when API proposals"},{"line_number":104,"context_line":"   and changes are funneled through a single initiative."},{"line_number":105,"context_line":" * To provide composable networking solutions: the ML2/Service plugin framework"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_8e565804","line":102,"in_reply_to":"1a122d0e_bdbeecfd","updated":"2016-05-04 17:40:58.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":129,"context_line":"What if a project cannot be considered part of the Stadium?"},{"line_number":130,"context_line":"-----------------------------------------------------------"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"The aforementioned criteria imply that the Neutron PTL is unable to favorably"},{"line_number":133,"context_line":"consider a project for inclusion, unless all the criteria are met. This in turn"},{"line_number":134,"context_line":"imposes that new initiatives start as standalone projects hosted on the"},{"line_number":135,"context_line":"openstack.org namespace, as outlined in the `creator guide \u003chttp://docs.openstack.org/infra/manual/creators.html\u003e`_."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_331a0d7d","line":132,"updated":"2016-05-04 17:41:31.000000000","message":"I think the PTL should not be into governance, otherwise it would be called PGTL ;)\n\nI think should be up to the core or drivers team to accept or reject applications - which  I have anyhow no idea about how they should be made.\n\nI\u0027m asking because I\u0027ve got a great project I would like to add the stadium (or Circus). It\u0027s called HDN.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":129,"context_line":"What if a project cannot be considered part of the Stadium?"},{"line_number":130,"context_line":"-----------------------------------------------------------"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"The aforementioned criteria imply that the Neutron PTL is unable to favorably"},{"line_number":133,"context_line":"consider a project for inclusion, unless all the criteria are met. This in turn"},{"line_number":134,"context_line":"imposes that new initiatives start as standalone projects hosted on the"},{"line_number":135,"context_line":"openstack.org namespace, as outlined in the `creator guide \u003chttp://docs.openstack.org/infra/manual/creators.html\u003e`_."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ae399441","line":132,"in_reply_to":"1a122d0e_331a0d7d","updated":"2016-05-04 17:52:50.000000000","message":"The point here is to give objective rules whereby anyone can make a fair decision. If I understand HDN to be [1], then the answer would be the project be rejected because of the inability to use CI/CD upstream resources.\n\n[1] https://github.com/salv-orlando/hdn","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":144,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":145,"context_line":"software development: from code to infrastructure and testing."},{"line_number":146,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":147,"context_line":"(e.g. vpnaas, fwaas), but these should be seen as the exception rather than the"},{"line_number":148,"context_line":"norm."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_8fdf96d5","line":147,"updated":"2016-05-04 07:27:58.000000000","message":"dynamic-routing as well","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"db15989658092da605b8cb4ef06881ead5b37df7","unresolved":false,"context_lines":[{"line_number":144,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":145,"context_line":"software development: from code to infrastructure and testing."},{"line_number":146,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":147,"context_line":"(e.g. vpnaas, fwaas), but these should be seen as the exception rather than the"},{"line_number":148,"context_line":"norm."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_7d00d466","line":147,"in_reply_to":"1a122d0e_8fdf96d5","updated":"2016-05-04 17:11:54.000000000","message":"@Vikram:  dynamic-routing doesn\u0027t host such extensions at this time.  Are you saying it is a forgone conclusion that it will?  I hope that the dynamic routing project can allow proprietary extensions without necessarily hosting them within the project.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":144,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":145,"context_line":"software development: from code to infrastructure and testing."},{"line_number":146,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":147,"context_line":"(e.g. vpnaas, fwaas), but these should be seen as the exception rather than the"},{"line_number":148,"context_line":"norm."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_1d060020","line":147,"in_reply_to":"1a122d0e_8fdf96d5","updated":"2016-05-04 17:38:03.000000000","message":"I am not listing them all, these are examples.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":151,"context_line":"with the Neutron core team to address integration issues with the core platform."},{"line_number":152,"context_line":"Projects outside the Stadium are fully responsible when dealing with the"},{"line_number":153,"context_line":"end-to-end SLDC of their solutions, and thus empowered."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"How do we build a Networking Community?"},{"line_number":156,"context_line":"---------------------------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_2e4f446b","line":153,"updated":"2016-05-04 17:41:31.000000000","message":"I think you should be very careful about removing project from the Stadium.. I heard that some very valuable contributors have gone on hunger strike to protest against these changes!","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":151,"context_line":"with the Neutron core team to address integration issues with the core platform."},{"line_number":152,"context_line":"Projects outside the Stadium are fully responsible when dealing with the"},{"line_number":153,"context_line":"end-to-end SLDC of their solutions, and thus empowered."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"How do we build a Networking Community?"},{"line_number":156,"context_line":"---------------------------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ae67d44f","line":153,"in_reply_to":"1a122d0e_2e4f446b","updated":"2016-05-04 17:52:50.000000000","message":"I am happy to step down, dissolve the core team and call for elections if that helps.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"155c5b1657eb1f6da1c5881d5decf023796e3785","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":151,"context_line":"with the Neutron core team to address integration issues with the core platform."},{"line_number":152,"context_line":"Projects outside the Stadium are fully responsible when dealing with the"},{"line_number":153,"context_line":"end-to-end SLDC of their solutions, and thus empowered."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"How do we build a Networking Community?"},{"line_number":156,"context_line":"---------------------------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_89adad33","line":153,"in_reply_to":"1a122d0e_ae67d44f","updated":"2016-05-04 20:11:43.000000000","message":"In all seriousness (and I have to say that given this is Salv\u0027s comment thread I\u0027m replying to), none of the code goes away, and in fact, most project teams won\u0027t notice any difference after they have put outside the Neutron Circus. This is evident by how many have ignored this discussion up to this point, which has been going on for months now.\n\nAlso, can you as the PTL dissolve the core team? I think if you tried that the TC would step in. Would certainly be fun to watch!","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":164,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":165,"context_line":"fashion."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":168,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_4e2560ac","line":167,"updated":"2016-05-04 17:41:31.000000000","message":"neutron-api seems a bit out of scope here?\n\nI mean it might be a good thing, but it seems that there a fairly big amount of technical details to discuss","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"9491337544db353f53613ceb37e92f015264bbf1","unresolved":false,"context_lines":[{"line_number":164,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":165,"context_line":"fashion."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":168,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_4e5f2075","line":167,"in_reply_to":"1a122d0e_4e2560ac","updated":"2016-05-04 17:52:50.000000000","message":"Can you elaborate? Out of scope how?\n\nWe went down the path of working on neutron-lib based on similar premises.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":4187,"name":"Ryan Tidwell","email":"rtidwell@suse.com","username":"ryan-tidwell"},"change_message_id":"fb5f4fd9c44cdac4a5751ea82ef43b84ce5d4fd0","unresolved":false,"context_lines":[{"line_number":164,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":165,"context_line":"fashion."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":168,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_efd41cea","line":167,"in_reply_to":"1a122d0e_4e5f2075","updated":"2016-05-04 23:28:10.000000000","message":"I see mentions of neutron-api throughout. Because it doesn\u0027t exist, it might help to soften the tone with regard to neutron-api in later sections where you discuss how projects must adopt it. To me this section is entirely appropriate in the context of what you\u0027re trying to achieve here.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2b5491b5cc310703366bf32f8d5bb8f24788c8b0","unresolved":false,"context_lines":[{"line_number":164,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":165,"context_line":"fashion."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":168,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_e516fd47","line":167,"in_reply_to":"1a122d0e_efd41cea","updated":"2016-05-05 00:24:43.000000000","message":"not sure what you\u0027re suggesting. Can you please elaborate?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":171,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":172,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":173,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":174,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":175,"context_line":"required. The resulting code will end up being located in neutron-api itself."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_4a3bacc8","line":172,"updated":"2016-05-04 07:27:58.000000000","message":"How about neutron/services like (QoS, VLAN-trunking etc)? We would like to keep it as part of neutron main tree/move it to neutron-api layer/ spin it out as separate effort?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":169,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":170,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":171,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":172,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":173,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":174,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":175,"context_line":"required. The resulting code will end up being located in neutron-api itself."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_700bdb24","line":172,"in_reply_to":"1a122d0e_4a3bacc8","updated":"2016-05-04 17:38:03.000000000","message":"the proposal is: *all* API for Stadium projects must be centralized.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"73955bd20ee3142d1205cb58a926041cd73a0eb6","unresolved":false,"context_lines":[{"line_number":174,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":175,"context_line":"required. The resulting code will end up being located in neutron-api itself."},{"line_number":176,"context_line":"Each core team of projects belonging to the Stadium will have +2"},{"line_number":177,"context_line":"rights on both neutron-specs and neutron-api projects. The neutron drivers"},{"line_number":178,"context_line":"will continue to hold +W rights on both repos. It is noteworthy that members"},{"line_number":179,"context_line":"of the individual core teams are and will be considered as members of the"},{"line_number":180,"context_line":"drivers team on a regular basis. Level of participation in reviewing RFE"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_8a99447c","line":177,"updated":"2016-05-04 07:36:53.000000000","message":"AFAIK, currently each sub-projects maintains there own spec folder.. Do we need to remove them off? Ex: https://github.com/openstack/networking-bgpvpn/tree/master/specs","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":174,"context_line":"with submission of specification documents to neutron-specs, if deemed"},{"line_number":175,"context_line":"required. The resulting code will end up being located in neutron-api itself."},{"line_number":176,"context_line":"Each core team of projects belonging to the Stadium will have +2"},{"line_number":177,"context_line":"rights on both neutron-specs and neutron-api projects. The neutron drivers"},{"line_number":178,"context_line":"will continue to hold +W rights on both repos. It is noteworthy that members"},{"line_number":179,"context_line":"of the individual core teams are and will be considered as members of the"},{"line_number":180,"context_line":"drivers team on a regular basis. Level of participation in reviewing RFE"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_f017eb42","line":177,"in_reply_to":"1a122d0e_8a99447c","updated":"2016-05-04 17:38:03.000000000","message":"yes","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7787,"name":"Kevin Benton","email":"kevin@benton.pub","username":"blak111"},"change_message_id":"afbe6ac41f6622556c6fd271561af787da8de0aa","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_16b3a80b","line":202,"updated":"2016-05-03 23:22:25.000000000","message":"what about extensions?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7787,"name":"Kevin Benton","email":"kevin@benton.pub","username":"blak111"},"change_message_id":"c173476c8a42f69caa7436439522fbbdeec93fae","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_9657b825","line":202,"in_reply_to":"1a122d0e_1659e88e","updated":"2016-05-03 23:48:49.000000000","message":"All of the ones defined in the neutron/extensions directory. e.g. allowed address pairs, portbinding, etc.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ebe00db19d88d011931a8451e438d6b2420a6ed4","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_1659e88e","line":202,"in_reply_to":"1a122d0e_16b3a80b","updated":"2016-05-03 23:37:17.000000000","message":"what extensions are you referring to? You don\u0027t give me much to go by.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"f9f2c336d53b6ac8399f4f15fc70107ea670903f","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_9c06b7cb","line":202,"in_reply_to":"1a122d0e_9657b825","updated":"2016-05-04 01:11:21.000000000","message":"they should move as hinted in line 171.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_af80928c","line":202,"in_reply_to":"1a122d0e_9c06b7cb","updated":"2016-05-04 07:27:58.000000000","message":"Does the CLI also needs to be developed as extensions or we can leave them as it for now?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":199,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":202,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":203,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_7022bba4","line":202,"in_reply_to":"1a122d0e_af80928c","updated":"2016-05-04 17:38:03.000000000","message":"They need to follow the OSC transition plan.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":209,"context_line":"* neutron-lbaas: this existence of this project is now questioned by the"},{"line_number":210,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."},{"line_number":211,"context_line":"  In a nutshell, this project will be phased out in favor of Octavia being"},{"line_number":212,"context_line":"  an OpenStack top-level project."},{"line_number":213,"context_line":"* neutron-vpnaas: this project has seen the least amount of traction during"},{"line_number":214,"context_line":"  the last few `cycle \u003chttp://docs.openstack.org/releasenotes/neutron-vpnaas/mitaka.html\u003e`_."},{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_2f6c8207","line":212,"updated":"2016-05-04 07:27:58.000000000","message":"Let\u0027s add a newline after this for better readability.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":209,"context_line":"* neutron-lbaas: this existence of this project is now questioned by the"},{"line_number":210,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."},{"line_number":211,"context_line":"  In a nutshell, this project will be phased out in favor of Octavia being"},{"line_number":212,"context_line":"  an OpenStack top-level project."},{"line_number":213,"context_line":"* neutron-vpnaas: this project has seen the least amount of traction during"},{"line_number":214,"context_line":"  the last few `cycle \u003chttp://docs.openstack.org/releasenotes/neutron-vpnaas/mitaka.html\u003e`_."},{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_f02ecb8a","line":212,"in_reply_to":"1a122d0e_2f6c8207","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"77f21da081f59192f2a11b4fe40e572477c008a3","unresolved":false,"context_lines":[{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":216,"context_line":"  will have to:"},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":219,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_85112007","line":218,"updated":"2016-05-04 15:34:55.000000000","message":"at the moment neutron-api is an idea. so adopting something that does not exist is kind of a big ask at the moment","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":4187,"name":"Ryan Tidwell","email":"rtidwell@suse.com","username":"ryan-tidwell"},"change_message_id":"fb5f4fd9c44cdac4a5751ea82ef43b84ce5d4fd0","unresolved":false,"context_lines":[{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":216,"context_line":"  will have to:"},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":219,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_6fb5aceb","line":218,"in_reply_to":"1a122d0e_454c289d","updated":"2016-05-04 23:28:10.000000000","message":"+1 to this. I\u0027d allow more time for folks to adopt neutron-api. The Ocata-1 timeframe seems a little aggressive. Perhaps you say at the time of Ocata feature freeze? Of course I think this is all predicated on how neutron-api evolves.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2b5491b5cc310703366bf32f8d5bb8f24788c8b0","unresolved":false,"context_lines":[{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":216,"context_line":"  will have to:"},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":219,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_c53ae1cc","line":218,"in_reply_to":"1a122d0e_6fb5aceb","updated":"2016-05-05 00:24:43.000000000","message":"I think that during the spin-out the API should not change. We\u0027re already busy as we are in Newton to formalize a plan to evolve the API. Having said that the goal of consolidating all API efforts (as we know them today) in a single place and making the switch is entirely feasible in the span of seven months, at least based on past experiences.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aed2716234cdb47a75f8cd101300a8b59bbbcb56","unresolved":false,"context_lines":[{"line_number":215,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":216,"context_line":"  will have to:"},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":219,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_454c289d","line":218,"in_reply_to":"1a122d0e_85112007","updated":"2016-05-04 15:38:18.000000000","message":"I started formalizing it at line 155. Why don\u0027t you help me in the process? I am not asking anyone to buy into these unconditionally. I am asking for constructive feedback.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""},{"line_number":222,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":223,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":224,"context_line":"* networking-l2gw: similarly to neutron-vpnaas, this needs to:"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_2f43e26d","line":223,"updated":"2016-05-04 07:27:58.000000000","message":"Let\u0027s add a newline after this for better readability.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":220,"context_line":"  * switch to OSC plugin;"},{"line_number":221,"context_line":""},{"line_number":222,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":223,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":224,"context_line":"* networking-l2gw: similarly to neutron-vpnaas, this needs to:"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_304fa36b","line":223,"in_reply_to":"1a122d0e_2f43e26d","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":253,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":254,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":255,"context_line":""},{"line_number":256,"context_line":"* networking-ofagent: this is deprecated and marked for removal."},{"line_number":257,"context_line":"* networking-onos: the core team will have to:"},{"line_number":258,"context_line":""},{"line_number":259,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_4f58de57","line":256,"updated":"2016-05-04 07:27:58.000000000","message":"Let\u0027s add a newline after this for better readability.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":253,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":254,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":255,"context_line":""},{"line_number":256,"context_line":"* networking-ofagent: this is deprecated and marked for removal."},{"line_number":257,"context_line":"* networking-onos: the core team will have to:"},{"line_number":258,"context_line":""},{"line_number":259,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_307683a3","line":256,"in_reply_to":"1a122d0e_4f58de57","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":273,"context_line":"    of potential bare metal scenarios that leverage third party solutions."},{"line_number":274,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":275,"context_line":"    that the Neutron team develops against ML2."},{"line_number":276,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":277,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ef2f2aa5","line":276,"updated":"2016-05-04 07:27:58.000000000","message":"Let\u0027s add a newline after this for better readability.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":273,"context_line":"    of potential bare metal scenarios that leverage third party solutions."},{"line_number":274,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":275,"context_line":"    that the Neutron team develops against ML2."},{"line_number":276,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":277,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_7070fba4","line":276,"in_reply_to":"1a122d0e_ef2f2aa5","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":280,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":281,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":284,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_ca005c03","line":281,"updated":"2016-05-04 07:27:58.000000000","message":"What is meant by \"moving the client side code to python-neutronclient\"? Currently, networking-sfc has developed it\u0027s CLI via extension framework (https://github.com/openstack/networking-sfc/tree/master/networking_sfc/cli). Do we need to change this approach?","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":280,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":281,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":284,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_70847b0a","line":281,"in_reply_to":"1a122d0e_ca005c03","updated":"2016-05-04 17:38:03.000000000","message":"For consistency, ideally yes. The problem stems from the fact that some service extensions do not release on pypi (like fw, vpn or lb) thus it\u0027s difficult to get hold of client extensions where they need to be used. SFC and L2GW for instance do release on pypi so that is not so much a problem for them. In theory their client extensions can stay colocated within their tree but that would make more difficult the alignment to the OSC plugin model.\n\nSince the recommendation from the client folks (amotoki et al) is to keep extensions in the python-neutronclient tree, I think it\u0027s better to have a consistent approach where *all* stadium client extensions are part of the python-neutronclient tree to avoid confusion when dealing with exceptions to the rule.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"876323fb951736de02781185e67505802e8af224","unresolved":false,"context_lines":[{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":284,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":285,"context_line":"  project."},{"line_number":286,"context_line":"* python-neutron-pd-driver: this is a project that depends on Neutron IPv6"},{"line_number":287,"context_line":"  support and introduces another prefix delegation driver besides the one"},{"line_number":288,"context_line":"  available in tree. It looks unmaintained, undocumented and not continously"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_8a178444","line":285,"updated":"2016-05-04 07:27:58.000000000","message":"Let\u0027s add a newline after this for better readability.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* octavia: this is being tackled in the context of neutron-lbaas. In a"},{"line_number":284,"context_line":"  nutshell, this will eventually be considered as top-level OpenStack"},{"line_number":285,"context_line":"  project."},{"line_number":286,"context_line":"* python-neutron-pd-driver: this is a project that depends on Neutron IPv6"},{"line_number":287,"context_line":"  support and introduces another prefix delegation driver besides the one"},{"line_number":288,"context_line":"  available in tree. It looks unmaintained, undocumented and not continously"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_d07bcf27","line":285,"in_reply_to":"1a122d0e_8a178444","updated":"2016-05-04 17:38:03.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"ca3ae86d82236be09e1aaa6921b064f22e47de8b","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  available in tree. It looks unmaintained, undocumented and not continously"},{"line_number":289,"context_line":"  tested; the team may choose to bring the code in the neutron tree next to"},{"line_number":290,"context_line":"  the other prefix delegation driver, and take on the maintainance burden,"},{"line_number":291,"context_line":"  otherwise it will rot (if not already)."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":294,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_0d253cc1","line":291,"updated":"2016-05-04 14:27:34.000000000","message":"Talked to one of the authors of this code, and with the in-tree implementation of dibbler this isn\u0027t as necessary any more. Dropping it in O-1 seems fine it noone picks it up by then.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"163923b02a52eb34db9a90d04d19638c58b25f65","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  available in tree. It looks unmaintained, undocumented and not continously"},{"line_number":289,"context_line":"  tested; the team may choose to bring the code in the neutron tree next to"},{"line_number":290,"context_line":"  the other prefix delegation driver, and take on the maintainance burden,"},{"line_number":291,"context_line":"  otherwise it will rot (if not already)."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":294,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_f0708b42","line":291,"in_reply_to":"1a122d0e_0d253cc1","updated":"2016-05-04 17:38:03.000000000","message":"ack, thanks for following up.","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"db15989658092da605b8cb4ef06881ead5b37df7","unresolved":false,"context_lines":[{"line_number":313,"context_line":"What are the drawbacks of this proposal?"},{"line_number":314,"context_line":"----------------------------------------"},{"line_number":315,"context_line":""},{"line_number":316,"context_line":"The cost of sanitizing the Stadium and keep it sane over time is non negligible,"},{"line_number":317,"context_line":"though the criteria have been designed to be lightweight and impose minimal"},{"line_number":318,"context_line":"burden on the teams once the Stadium is up and running. This is the trade-off"},{"line_number":319,"context_line":"to keep all the networking related efforts working in symbiosis. Hopefully,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_d0dc6f76","line":316,"range":{"start_line":316,"start_character":39,"end_line":316,"end_character":43},"updated":"2016-05-04 17:11:54.000000000","message":"*keeping","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"220de7fc3661637c6d17576f9a307b67c79bd69d","unresolved":false,"context_lines":[{"line_number":313,"context_line":"What are the drawbacks of this proposal?"},{"line_number":314,"context_line":"----------------------------------------"},{"line_number":315,"context_line":""},{"line_number":316,"context_line":"The cost of sanitizing the Stadium and keep it sane over time is non negligible,"},{"line_number":317,"context_line":"though the criteria have been designed to be lightweight and impose minimal"},{"line_number":318,"context_line":"burden on the teams once the Stadium is up and running. This is the trade-off"},{"line_number":319,"context_line":"to keep all the networking related efforts working in symbiosis. Hopefully,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_aea994df","line":316,"range":{"start_line":316,"start_character":39,"end_line":316,"end_character":43},"in_reply_to":"1a122d0e_d0dc6f76","updated":"2016-05-04 17:40:58.000000000","message":"Done","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"27f2ee44bdc04c214b2c35fb3bbca9fece25bfc0","unresolved":false,"context_lines":[{"line_number":314,"context_line":"----------------------------------------"},{"line_number":315,"context_line":""},{"line_number":316,"context_line":"The cost of sanitizing the Stadium and keep it sane over time is non negligible,"},{"line_number":317,"context_line":"though the criteria have been designed to be lightweight and impose minimal"},{"line_number":318,"context_line":"burden on the teams once the Stadium is up and running. This is the trade-off"},{"line_number":319,"context_line":"to keep all the networking related efforts working in symbiosis. Hopefully,"},{"line_number":320,"context_line":"it should be clear by now that associating a bad connotation to projects that"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a122d0e_8e7bf87a","line":317,"updated":"2016-05-04 17:41:31.000000000","message":"I wonder what the list would have been if the criteria were \"heavyweight\" ;)","commit_id":"ccb66349b7b913f3708982718caba5d7a7afee3b"},{"author":{"_account_id":4694,"name":"Miguel Lavalle","email":"miguel@mlavalle.com","username":"minsel"},"change_message_id":"0fd1ea85fbb3fdea3d113b35b566465085eb990f","unresolved":false,"context_lines":[{"line_number":35,"context_line":"affiliation. While this may seem okay at first, the mission of the PTL/drivers"},{"line_number":36,"context_line":"team is to ensure consistency in the APIs, architecture, design, implementation"},{"line_number":37,"context_line":"and testing of the project, and at the same time ensure a level of quality in"},{"line_number":38,"context_line":"how aspects, like documentation, inter-project communication, release"},{"line_number":39,"context_line":"management, stable backports etc are dealt with. The point about uniform APIs"},{"line_number":40,"context_line":"is particularly important, because the Neutron platform is so flexible that"},{"line_number":41,"context_line":"a project can take a totally different turn in the way it exposes functionality,"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_dff3aa07","line":38,"range":{"start_line":38,"start_character":0,"end_line":38,"end_character":3},"updated":"2016-05-05 16:07:21.000000000","message":"s/how/all","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":35,"context_line":"affiliation. While this may seem okay at first, the mission of the PTL/drivers"},{"line_number":36,"context_line":"team is to ensure consistency in the APIs, architecture, design, implementation"},{"line_number":37,"context_line":"and testing of the project, and at the same time ensure a level of quality in"},{"line_number":38,"context_line":"how aspects, like documentation, inter-project communication, release"},{"line_number":39,"context_line":"management, stable backports etc are dealt with. The point about uniform APIs"},{"line_number":40,"context_line":"is particularly important, because the Neutron platform is so flexible that"},{"line_number":41,"context_line":"a project can take a totally different turn in the way it exposes functionality,"}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_776248da","line":38,"range":{"start_line":38,"start_character":0,"end_line":38,"end_character":3},"in_reply_to":"1a122d0e_dff3aa07","updated":"2016-05-05 21:22:12.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"82b6f03c505173cd58081ef5e87e71904ab2e640","unresolved":false,"context_lines":[{"line_number":68,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":69,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":70,"context_line":"the Neutron team and PTL claim responsibility for when producing Neutron"},{"line_number":71,"context_line":"deliverables throughout the release cycles."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":74,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_bd3fff23","line":71,"updated":"2016-05-04 22:44:28.000000000","message":"Do the stadium projects reside in the same repo as neutron or separate repo?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"447c40cd1bbda90892b7f142c9df0618d713c067","unresolved":false,"context_lines":[{"line_number":68,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"},{"line_number":69,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":70,"context_line":"the Neutron team and PTL claim responsibility for when producing Neutron"},{"line_number":71,"context_line":"deliverables throughout the release cycles."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":74,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_626e6301","line":71,"in_reply_to":"1a122d0e_bd3fff23","updated":"2016-05-05 00:20:36.000000000","message":"separate repo","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"82b6f03c505173cd58081ef5e87e71904ab2e640","unresolved":false,"context_lines":[{"line_number":69,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":70,"context_line":"the Neutron team and PTL claim responsibility for when producing Neutron"},{"line_number":71,"context_line":"deliverables throughout the release cycles."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":74,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":75,"context_line":"integrity be maintained over time when modifications to the list are required."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_bd26df13","line":72,"updated":"2016-05-04 22:44:28.000000000","message":"Could you clarify what you mean by \"producing Neutron\ndeliverables throughout the release cycles\"? Are all neutron stadium projects going to be packaged together with Neutron as a single deliverable?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"447c40cd1bbda90892b7f142c9df0618d713c067","unresolved":false,"context_lines":[{"line_number":69,"context_line":"projects, or an upper tier within OpenStack. It is simply the list of projects"},{"line_number":70,"context_line":"the Neutron team and PTL claim responsibility for when producing Neutron"},{"line_number":71,"context_line":"deliverables throughout the release cycles."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"This spec proposes how the current list (as of May 2016) needs to be revised in"},{"line_number":74,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":75,"context_line":"integrity be maintained over time when modifications to the list are required."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_a274fbce","line":72,"in_reply_to":"1a122d0e_bd26df13","updated":"2016-05-05 00:20:36.000000000","message":"No, they are still gonna be packaged separately and according to their release model. Please find more info on:\n\nhttps://github.com/openstack/releases","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"82b6f03c505173cd58081ef5e87e71904ab2e640","unresolved":false,"context_lines":[{"line_number":88,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":89,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":90,"context_line":" * adherence to deprecation and stable backports policies;"},{"line_number":91,"context_line":" * demonstrated ability to do rolling upgrades (where applicable);"},{"line_number":92,"context_line":" * adoption of neutron-lib (with related hacking rules applied), and unit test"},{"line_number":93,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":94,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_ccca0e4f","line":91,"updated":"2016-05-04 22:44:28.000000000","message":"Could you clarify what you mean by rolling upgrade? Does it just mean DB live upgrade? If not, do you have any link to this?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"447c40cd1bbda90892b7f142c9df0618d713c067","unresolved":false,"context_lines":[{"line_number":88,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":89,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":90,"context_line":" * adherence to deprecation and stable backports policies;"},{"line_number":91,"context_line":" * demonstrated ability to do rolling upgrades (where applicable);"},{"line_number":92,"context_line":" * adoption of neutron-lib (with related hacking rules applied), and unit test"},{"line_number":93,"context_line":"   CI reporting against neutron-lib changes;"},{"line_number":94,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_224f4b93","line":91,"in_reply_to":"1a122d0e_ccca0e4f","updated":"2016-05-05 00:20:36.000000000","message":"I should probably say just upgrades here, sa there are two levels of upgrades:\n\n http://governance.openstack.org/reference/tags/assert_supports-upgrade.html#tag-assert-supports-upgrade\n\n http://governance.openstack.org/reference/tags/assert_supports-rolling-upgrade.html#tag-assert-supports-rolling-upgrade","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"da3724c67761e58afe7405cfa479cefe6afbc090","unresolved":false,"context_lines":[{"line_number":110,"context_line":"   the recommendation is to keep extensions in the python-neutronclient"},{"line_number":111,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"},{"line_number":112,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":113,"context_line":"   confusion when dealing with exceptions to the rule."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_3ebbdb10","line":113,"updated":"2016-05-05 06:39:10.000000000","message":"Will there be any changes to the release process (https://github.com/openstack/neutron/blob/master/doc/source/stadium/sub_project_guidelines.rst#releases)?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":110,"context_line":"   the recommendation is to keep extensions in the python-neutronclient"},{"line_number":111,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"},{"line_number":112,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":113,"context_line":"   confusion when dealing with exceptions to the rule."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_37dd6071","line":113,"in_reply_to":"1a122d0e_3ebbdb10","updated":"2016-05-05 21:22:12.000000000","message":"projects will still be released according to their release model. Since the Stadium projects are release managed projects the process may evolve slightly but not so much. We have a release Liaison who is in charge of release matters but anyone is welcome to help out and target openstack/releases when it\u0027s time to generate a release and ask for a blessing.\n\nWe\u0027ll revise instructions accordingly.\n\nI\u0027ll add a note to the end","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"91ce9b924e0f65f376c57afefece40a259a75673","unresolved":false,"context_lines":[{"line_number":110,"context_line":"   the recommendation is to keep extensions in the python-neutronclient"},{"line_number":111,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"},{"line_number":112,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":113,"context_line":"   confusion when dealing with exceptions to the rule."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_9f7e3ae2","line":113,"in_reply_to":"dab17558_37dd6071","updated":"2016-05-16 16:20:51.000000000","message":"Note that I have instruction revision at: https://review.openstack.org/#/c/308984/ that could use some attention from PTL.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"ef5b7529c1b8209aae6d3e7a262808215905beb7","unresolved":false,"context_lines":[{"line_number":192,"context_line":"belonging to the Stadium will have +2 rights on both neutron-specs and"},{"line_number":193,"context_line":"neutron-api projects. The neutron drivers will continue to hold +W rights"},{"line_number":194,"context_line":"on both repos. It is noteworthy that members of the individual core teams"},{"line_number":195,"context_line":"are and will be considered as members of the drivers team on a regular basis."},{"line_number":196,"context_line":"Level of participation in reviewing RFE submissions, experience with the"},{"line_number":197,"context_line":"Neutron codebase, and commitment to the project are factors taken into"},{"line_number":198,"context_line":"account when identifying members of this team."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_16008daa","line":195,"range":{"start_line":195,"start_character":27,"end_line":195,"end_character":40},"updated":"2016-05-05 02:57:39.000000000","message":"for membership in","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":192,"context_line":"belonging to the Stadium will have +2 rights on both neutron-specs and"},{"line_number":193,"context_line":"neutron-api projects. The neutron drivers will continue to hold +W rights"},{"line_number":194,"context_line":"on both repos. It is noteworthy that members of the individual core teams"},{"line_number":195,"context_line":"are and will be considered as members of the drivers team on a regular basis."},{"line_number":196,"context_line":"Level of participation in reviewing RFE submissions, experience with the"},{"line_number":197,"context_line":"Neutron codebase, and commitment to the project are factors taken into"},{"line_number":198,"context_line":"account when identifying members of this team."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_77e7e840","line":195,"range":{"start_line":195,"start_character":27,"end_line":195,"end_character":40},"in_reply_to":"1a122d0e_16008daa","updated":"2016-05-05 21:22:12.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"69fa9aedb5ca4f02cdc3c0be45934a4ec94e9425","unresolved":false,"context_lines":[{"line_number":209,"context_line":"-------------------------------------------------------------"},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"At the time of writing the Stadium contains the projects as outlined below."},{"line_number":212,"context_line":"Based on the aforementioned considerations, all of individual teams will have"},{"line_number":213,"context_line":"to work during the Newton timeframe to make the current proposal a reality."},{"line_number":214,"context_line":"More precisely, to be considered for inclusion (continue to be part of the"},{"line_number":215,"context_line":"Stadium list), the following plan must be put in place:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_e8ac00ef","line":212,"updated":"2016-05-05 11:36:52.000000000","message":"\"all of the\"","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":209,"context_line":"-------------------------------------------------------------"},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"At the time of writing the Stadium contains the projects as outlined below."},{"line_number":212,"context_line":"Based on the aforementioned considerations, all of individual teams will have"},{"line_number":213,"context_line":"to work during the Newton timeframe to make the current proposal a reality."},{"line_number":214,"context_line":"More precisely, to be considered for inclusion (continue to be part of the"},{"line_number":215,"context_line":"Stadium list), the following plan must be put in place:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_57e4643a","line":212,"in_reply_to":"1a122d0e_e8ac00ef","updated":"2016-05-05 21:22:12.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"69fa9aedb5ca4f02cdc3c0be45934a4ec94e9425","unresolved":false,"context_lines":[{"line_number":215,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":216,"context_line":""},{"line_number":217,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":218,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":219,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_8882ac50","line":218,"updated":"2016-05-05 11:36:52.000000000","message":"Insert a blank line after line 218.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":215,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":216,"context_line":""},{"line_number":217,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":218,"context_line":"  the api models/definitions out of the neutron repo."},{"line_number":219,"context_line":"* neutron-fwaas: the fwaas core team will have to:"},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"  * complete the transition to fwaas v2;"}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_b7cf90b2","line":218,"in_reply_to":"1a122d0e_8882ac50","updated":"2016-05-05 21:22:12.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"69fa9aedb5ca4f02cdc3c0be45934a4ec94e9425","unresolved":false,"context_lines":[{"line_number":222,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":223,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"* neutron-lbaas: this existence of this project is now questioned by the"},{"line_number":226,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."},{"line_number":227,"context_line":"  In a nutshell, this project will be phased out in favor of Octavia being"},{"line_number":228,"context_line":"  an OpenStack top-level project."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_a87de86e","line":225,"updated":"2016-05-05 11:36:52.000000000","message":"Replace the first \"this\" with \"the.\"","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":222,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":223,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"* neutron-lbaas: this existence of this project is now questioned by the"},{"line_number":226,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."},{"line_number":227,"context_line":"  In a nutshell, this project will be phased out in favor of Octavia being"},{"line_number":228,"context_line":"  an OpenStack top-level project."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_97d40c48","line":225,"in_reply_to":"1a122d0e_a87de86e","updated":"2016-05-05 21:22:12.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"da3724c67761e58afe7405cfa479cefe6afbc090","unresolved":false,"context_lines":[{"line_number":248,"context_line":"* networking-bagpipe: the core team will have to:"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":251,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":254,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_1e8a5f64","line":251,"updated":"2016-05-05 06:39:10.000000000","message":"As pointed out in the previous PS, repo\u0027s having their own spec folder need to remove them off. How this transition will happen?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4133598f1a1b6a05d6e085d185e453e75c464ad5","unresolved":false,"context_lines":[{"line_number":248,"context_line":"* networking-bagpipe: the core team will have to:"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":251,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":254,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_57bbc40e","line":251,"in_reply_to":"1a122d0e_1e8a5f64","updated":"2016-05-05 21:23:40.000000000","message":"I\u0027ll elaborate more","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"da3724c67761e58afe7405cfa479cefe6afbc090","unresolved":false,"context_lines":[{"line_number":276,"context_line":"* networking-onos: the core team will have to:"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":279,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":282,"context_line":"  To be considered for Stadium inclusion, the core team should consider"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_7e827353","line":279,"updated":"2016-05-05 06:39:10.000000000","message":"networking-onos currently doesn\u0027t have any DB of its own, hence rolling-update is not required for this project.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4133598f1a1b6a05d6e085d185e453e75c464ad5","unresolved":false,"context_lines":[{"line_number":276,"context_line":"* networking-onos: the core team will have to:"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":279,"context_line":"  * complete docs, end-to-end testing, and demonstrate rolling upgrades;"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":282,"context_line":"  To be considered for Stadium inclusion, the core team should consider"}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_17481c2d","line":279,"in_reply_to":"1a122d0e_7e827353","updated":"2016-05-05 21:23:40.000000000","message":"as I said, this makes sense where it applies. We\u0027ll discuss more on a case by case basis.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"69fa9aedb5ca4f02cdc3c0be45934a4ec94e9425","unresolved":false,"context_lines":[{"line_number":280,"context_line":""},{"line_number":281,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":282,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":283,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":284,"context_line":""},{"line_number":285,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":286,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_e848802f","line":283,"updated":"2016-05-05 11:36:52.000000000","message":"\"switching back to an ML2 driver.\"","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4133598f1a1b6a05d6e085d185e453e75c464ad5","unresolved":false,"context_lines":[{"line_number":280,"context_line":""},{"line_number":281,"context_line":"* networking-ovn: the OVN project chose to adopt a monolithic interface."},{"line_number":282,"context_line":"  To be considered for Stadium inclusion, the core team should consider"},{"line_number":283,"context_line":"  switching back. This is beneficial for the following reasons:"},{"line_number":284,"context_line":""},{"line_number":285,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":286,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_775528c5","line":283,"in_reply_to":"1a122d0e_e848802f","updated":"2016-05-05 21:23:40.000000000","message":"Done","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":4187,"name":"Ryan Tidwell","email":"rtidwell@suse.com","username":"ryan-tidwell"},"change_message_id":"4314f5d799852e15ea4262154e86476a87a7abe0","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_0f74f8fb","line":314,"updated":"2016-05-04 23:28:27.000000000","message":"This seems a little aggressive if neutron-api is considered as criteria for compliance.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"447c40cd1bbda90892b7f142c9df0618d713c067","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_42188784","line":314,"in_reply_to":"1a122d0e_0f74f8fb","updated":"2016-05-05 00:20:36.000000000","message":"Ocata-1 is roughly end of December: do you really believe that 7 months is not enough?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3fcf17a6cf55f94d0ac241ee6376d92e91505d22","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_45fff100","line":314,"in_reply_to":"1a122d0e_42188784","updated":"2016-05-05 00:21:02.000000000","message":"What would you like to see instead?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":4187,"name":"Ryan Tidwell","email":"rtidwell@suse.com","username":"ryan-tidwell"},"change_message_id":"80e857e6645d6c313f2c11f3aea0b09ab1879a50","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1a122d0e_bf306e08","line":314,"in_reply_to":"1a122d0e_45fff100","updated":"2016-05-05 16:18:02.000000000","message":"I\u0027m fine with Ocata-1 as long as neutron-api comes to life quickly. My point here was that we\u0027re putting a deadline in place to adopt something that doesn\u0027t yet exist. How quickly can we get neutron-api off the ground?","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7cf53fd5d99c1f7670cede799a7d479b8ac38ff6","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_3768c0ba","line":314,"in_reply_to":"1a122d0e_bf306e08","updated":"2016-05-05 21:22:12.000000000","message":"I am hoping to tackle it as first item, and surely finish it by Newton.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":4187,"name":"Ryan Tidwell","email":"rtidwell@suse.com","username":"ryan-tidwell"},"change_message_id":"bf2d155a18a7f7dcfb3997faab547c3fc9fcb815","unresolved":false,"context_lines":[{"line_number":311,"context_line":"  if no-one picks it up by then."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":314,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will have to"},{"line_number":315,"context_line":"be removed by the Neutron Stadium. All things considered, a team can decide"},{"line_number":316,"context_line":"not to adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":317,"context_line":"timeframe."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dab17558_05262268","line":314,"in_reply_to":"dab17558_3768c0ba","updated":"2016-05-05 22:27:09.000000000","message":"Perfect, I can get behind that.","commit_id":"e183a9feaddf3e16fd08c27da8265ab6b26ceada"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":34,"context_line":"made it possible for projects to be `automatically \u003chttp://git.openstack.org/cgit/openstack/governance/commit/?id\u003d321a020cbcaada01976478ea9f677ebb4df7bd6d\u003e`_"},{"line_number":35,"context_line":"enlisted as a Neutron project based simply on description, and desire for"},{"line_number":36,"context_line":"affiliation. With the ever growing number of inclusions, the mission of the"},{"line_number":37,"context_line":"PTL/drivers team of ensuring consistency in the APIs, architecture, design,"},{"line_number":38,"context_line":"implementation and testing of the project, as well as a level of quality in"},{"line_number":39,"context_line":"all aspects, like documentation, inter-project communication, release"},{"line_number":40,"context_line":"management, stable backports etc are dealt with have become harder and harder."},{"line_number":41,"context_line":"The point about uniform APIs is particularly important, because the Neutron"},{"line_number":42,"context_line":"platform is so flexible that a project can take a totally different turn in"},{"line_number":43,"context_line":"the way it exposes functionality, that it is virtually impossible for the"},{"line_number":44,"context_line":"PTL and the drivers team to ensure that good API design principles are being"},{"line_number":45,"context_line":"followed over time. In a situation where each project is on its own, that"},{"line_number":46,"context_line":"might be acceptable, but allowing independent API evolution while still under"},{"line_number":47,"context_line":"the Neutron umbrella is counterproductive."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"In a nutshell, the existing arrangement of conceding autonomy, and striving"},{"line_number":50,"context_line":"for consistency is clearly challenging because of the two conflicting forces"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_690c2043","line":47,"range":{"start_line":37,"start_character":29,"end_line":47,"end_character":42},"updated":"2016-05-06 05:27:09.000000000","message":"Totally agree with the highlighted text.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":75,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":76,"context_line":"integrity be maintained over time when modifications to the list are required."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"When is a project part of the Stadium?"},{"line_number":79,"context_line":"--------------------------------------"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to be considered part of the Stadium, a project must show a track"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_e4fe7704","line":78,"updated":"2016-05-06 05:27:09.000000000","message":"Let\u0027s please use clear terminology. In the Neutron stadium, there are projects, sub-projects and drivers/plugins. I am not sure why you are referring to all of them as \"projects\". Please update the terminology in the proposal so its clear.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"b604d83dabd8fe3031afb2a3e4c43887d6c16799","unresolved":false,"context_lines":[{"line_number":75,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":76,"context_line":"integrity be maintained over time when modifications to the list are required."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"When is a project part of the Stadium?"},{"line_number":79,"context_line":"--------------------------------------"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to be considered part of the Stadium, a project must show a track"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_3d6348de","line":78,"in_reply_to":"dab17558_47cc8e35","updated":"2016-05-07 02:17:27.000000000","message":"What is a project? A repository? Please describe clearly in the proposal what you refer to as a project as this has implications on the drivers this proposal does not talk about.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":75,"context_line":"order to maintain the integrity of the Stadium, and how to ensure this"},{"line_number":76,"context_line":"integrity be maintained over time when modifications to the list are required."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"When is a project part of the Stadium?"},{"line_number":79,"context_line":"--------------------------------------"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to be considered part of the Stadium, a project must show a track"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_47cc8e35","line":78,"in_reply_to":"dab17558_e4fe7704","updated":"2016-05-06 16:10:24.000000000","message":"I don\u0027t understand why we need a classification within the classification; besides your distinction is flawed because a single project can contain many different pluggable pieces, so in the end they are all openstack projects.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":85,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":86,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":87,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":88,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":89,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":90,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":91,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_c403730c","line":88,"updated":"2016-05-06 05:27:09.000000000","message":"Trying to clarify this further. Not sure how upstream CI ensures the points around stadium consistency are solved? Isn\u0027t the goal to achieve consistency in models, API, docs, testing, quality and not sure how a location of a CI can determine that?","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"b604d83dabd8fe3031afb2a3e4c43887d6c16799","unresolved":false,"context_lines":[{"line_number":85,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":86,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":87,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":88,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":89,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":90,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":91,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_05ba7923","line":88,"in_reply_to":"dab17558_27fd0a3b","updated":"2016-05-07 02:17:27.000000000","message":"Seems like you overlooked some part of the comment.\n\nHow does the \"location\" of the CI ensure stability and reliability of the solution? :)","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":85,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":86,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":87,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":88,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":89,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":90,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":91,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_27fd0a3b","line":88,"in_reply_to":"dab17558_c403730c","updated":"2016-05-06 16:10:24.000000000","message":"consistency wrt stability and reliability of the solution (broken vs non broken?)","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"02a48465968038d1a1025adc2646832bf18a4444","unresolved":false,"context_lines":[{"line_number":108,"context_line":"   confusion when dealing with exceptions to the rule."},{"line_number":109,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":110,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":111,"context_line":"   neutron-specs may be required;"},{"line_number":112,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":113,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":114,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_7f9cd269","line":111,"updated":"2016-05-06 06:24:23.000000000","message":"does this mean, a project which aims to be a part of the stadium, should follow the rfe/spec process even before inclusion?\nor showing the will is enough?\n\n(i\u0027m thinking about tap-as-a-service)","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":108,"context_line":"   confusion when dealing with exceptions to the rule."},{"line_number":109,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":110,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":111,"context_line":"   neutron-specs may be required;"},{"line_number":112,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":113,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":114,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_62dd4014","line":111,"in_reply_to":"dab17558_7f9cd269","updated":"2016-05-06 16:10:24.000000000","message":"Let\u0027s consider a couple of examples: a) bgp: this one started within neutron to then be spinned out. The spec/api was discussed within the neutron platform and thus it already met the criteria; b) neutron-lib: this one started right as a separate project but its RFEs/BPs have been directly proposed within Neutron.\n\nAs for tap-as-a-service, I would expect that to be considered for inclusion a submission of the API (as known at the time of submission) to neutron-spec and its definition to neutron-api will have to be agreed and approved in rapid succession. Then and only then one can assume that any further proposal go via Neutron RFE submission process. Having said that, the approval of the API will have to be assessed having a fair degree of confidence that other criteria are also being met or being pretty close to being met.\n\nDoes that answer your question?\n\nI\u0027ll elaborate a bit more in a follow up.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":153,"context_line":"openstack.org namespace, as outlined in the `creator guide \u003chttp://docs.openstack.org/infra/manual/creators.html\u003e`_."},{"line_number":154,"context_line":"Furthermore, projects that interact with Neutron purely via its REST API should"},{"line_number":155,"context_line":"also be incentivized to seek other forms of governance, such as applying as"},{"line_number":156,"context_line":"top-level OpenStack project and follow the new project requirements as outlined"},{"line_number":157,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_,"},{"line_number":158,"context_line":"rather than going for Stadium inclusion."},{"line_number":159,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_e44cb778","line":156,"updated":"2016-05-06 05:27:09.000000000","message":"Again, there is a difference between project, sub-project and drivers. I doubt the new projects requirements apply the same to all.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":153,"context_line":"openstack.org namespace, as outlined in the `creator guide \u003chttp://docs.openstack.org/infra/manual/creators.html\u003e`_."},{"line_number":154,"context_line":"Furthermore, projects that interact with Neutron purely via its REST API should"},{"line_number":155,"context_line":"also be incentivized to seek other forms of governance, such as applying as"},{"line_number":156,"context_line":"top-level OpenStack project and follow the new project requirements as outlined"},{"line_number":157,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_,"},{"line_number":158,"context_line":"rather than going for Stadium inclusion."},{"line_number":159,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_22dcd811","line":156,"in_reply_to":"dab17558_e44cb778","updated":"2016-05-06 16:10:24.000000000","message":"see above.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":160,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":161,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":162,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":163,"context_line":"software development: from code to infrastructure and testing."},{"line_number":164,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":165,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":166,"context_line":"than the norm."}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_a41d8f68","line":163,"updated":"2016-05-06 05:27:09.000000000","message":"What if a driver/plugin adheres to pretty much all the requirements in line #78?","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":161,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":162,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":163,"context_line":"software development: from code to infrastructure and testing."},{"line_number":164,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":165,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":166,"context_line":"than the norm."},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_24207f9b","line":164,"updated":"2016-05-06 05:27:09.000000000","message":"What\u0027s the criteria for inclusion of drivers under these sub-projects like fwaas, lbaas? Please capture the details in the proposal.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":161,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":162,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":163,"context_line":"software development: from code to infrastructure and testing."},{"line_number":164,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":165,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":166,"context_line":"than the norm."},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_a20c4895","line":164,"in_reply_to":"dab17558_24207f9b","updated":"2016-05-06 16:10:24.000000000","message":"the decision would be left to the individual projects, however new initiatives (like BGP), should already promote out-of-tree development.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"db47f76df8b08e0b76576d577f63afc0a697cc6c","unresolved":false,"context_lines":[{"line_number":183,"context_line":"fashion."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":186,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":187,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":188,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":189,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_c9f26c6f","line":186,"updated":"2016-05-06 05:03:38.000000000","message":"I am interested contributing towards neutron-api effort. You can count on me ;)","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":183,"context_line":"fashion."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":186,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":187,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":188,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":189,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_427e3ce5","line":186,"in_reply_to":"dab17558_c9f26c6f","updated":"2016-05-06 16:10:24.000000000","message":"Let me formalize a bit more on what\u0027s required, this may as well turn out to be just a one man\u0027s job","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"02a48465968038d1a1025adc2646832bf18a4444","unresolved":false,"context_lines":[{"line_number":186,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":187,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":188,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":189,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":190,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":191,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":192,"context_line":"with submission of specification documents to neutron-specs, if deemed"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_fff722f3","line":189,"range":{"start_line":189,"start_character":54,"end_line":189,"end_character":68},"updated":"2016-05-06 06:24:23.000000000","message":"ml2/extensions is merely ml2 implementations of extensions.\nis it appropriate to have in neutron-api?  i guess not.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":186,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":187,"context_line":"The neutron-api project can be a passive component to be consumed by"},{"line_number":188,"context_line":"Neutron Stadium projects, and to be started off as a spinout of the neutron"},{"line_number":189,"context_line":"api codebase such as neutron/api, neutron/extensions, ml2/extensions, and"},{"line_number":190,"context_line":"any other project (e.g. bgp, l2gw, sfc, etc) that is considered for Stadium"},{"line_number":191,"context_line":"inclusion. Contributions to this project will follow the Neutron RFE process"},{"line_number":192,"context_line":"with submission of specification documents to neutron-specs, if deemed"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_a283a8cb","line":189,"in_reply_to":"dab17558_fff722f3","updated":"2016-05-06 16:10:24.000000000","message":"there\u0027s some stuff under the extension drivers like dns and qos","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"02a48465968038d1a1025adc2646832bf18a4444","unresolved":false,"context_lines":[{"line_number":269,"context_line":""},{"line_number":270,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":273,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* networking-odl: the core team will have to:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_1fa5c603","line":272,"updated":"2016-05-06 06:24:23.000000000","message":"what to do for these extensions?\npropose to neutron-api?\n\nhttps://github.com/openstack/networking-midonet/tree/master/midonet/neutron/extensions","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":269,"context_line":""},{"line_number":270,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":273,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* networking-odl: the core team will have to:"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_02e394a4","line":272,"in_reply_to":"dab17558_1fa5c603","updated":"2016-05-06 16:10:24.000000000","message":"Thanks for chiming in on the midonet project! When I looked at it I saw that there were extensions in tree. To be considered for inclusion, you\u0027d have to propose the API via neutron-specs and assess steps for an open implementation.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"02a48465968038d1a1025adc2646832bf18a4444","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":273,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* networking-odl: the core team will have to:"},{"line_number":276,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_6489e7ca","line":273,"updated":"2016-05-06 06:24:23.000000000","message":"what to do about this client code?\n\nhttps://github.com/openstack/networking-midonet/tree/master/midonet/neutronclient","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":273,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* networking-odl: the core team will have to:"},{"line_number":276,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_a2b60888","line":273,"in_reply_to":"dab17558_6489e7ca","updated":"2016-05-06 16:10:24.000000000","message":"Once the all the other requirements are cleared, and the client extensions are compliant with the OSC transition plan, we can move these to a /midonet module under the python-neutronclient.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"2879bc99221bba706814c1b81959cc3d8b75321b","unresolved":false,"context_lines":[{"line_number":358,"context_line":"Are there any alternatives worth considering?"},{"line_number":359,"context_line":"---------------------------------------------"},{"line_number":360,"context_line":""},{"line_number":361,"context_line":"Open to suggestions."},{"line_number":362,"context_line":""},{"line_number":363,"context_line":"References"},{"line_number":364,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_a44bcf58","line":361,"updated":"2016-05-06 05:27:09.000000000","message":"Seems like a complex proposal and I see it leading to problems as described here [1]. Why not keep it simple:\n\nA) Common libs + advanced services + reference implementations as OVS or OVN [Neutron Stadium]\nB) Everything else [Not Neutron stadium]\n\nThis will bring even lesser load on the core team and focus on making the reference implementation robust rather than the team vouching for N number of implementations. Also helps avoid all the problem described here [1]. I am still not convinced on the three tier approach you are proposing from any angle. \n\n[1] http://lists.openstack.org/pipermail/openstack-dev/2016-April/093561.html","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"90e4a25a8c469f30727327d9c8395ae5e1f03380","unresolved":false,"context_lines":[{"line_number":358,"context_line":"Are there any alternatives worth considering?"},{"line_number":359,"context_line":"---------------------------------------------"},{"line_number":360,"context_line":""},{"line_number":361,"context_line":"Open to suggestions."},{"line_number":362,"context_line":""},{"line_number":363,"context_line":"References"},{"line_number":364,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_d648315e","line":361,"in_reply_to":"dab17558_a44bcf58","updated":"2016-05-06 16:10:24.000000000","message":"let\u0027s not go back and forth between email and gerrit. Please consider adding drawbacks to the previous section.\n\nTo your point in complexity: what you describe may as well be the one realistic outcome based on the free will of teams to decide to adhere to the development guidelines presented in this proposal","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"b604d83dabd8fe3031afb2a3e4c43887d6c16799","unresolved":false,"context_lines":[{"line_number":358,"context_line":"Are there any alternatives worth considering?"},{"line_number":359,"context_line":"---------------------------------------------"},{"line_number":360,"context_line":""},{"line_number":361,"context_line":"Open to suggestions."},{"line_number":362,"context_line":""},{"line_number":363,"context_line":"References"},{"line_number":364,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":7,"id":"dab17558_dd65dce1","line":361,"in_reply_to":"dab17558_d648315e","updated":"2016-05-07 02:17:27.000000000","message":"In simple words, seems like no alternatives can be entertained here.","commit_id":"c428cc5875fd24635fc0aedf1f4293a21f6ac76f"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"8070565a9720b2068a1937ed954b09bcfb045ef3","unresolved":false,"context_lines":[{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":88,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":89,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":90,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":91,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":92,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":93,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_7d2670bb","line":90,"updated":"2016-05-07 02:17:10.000000000","message":"Seems like you overlooked some part of the comment in the last patch.\n\nHow does the \"location\" of the CI ensure stability and reliability of the solution? :)","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"1144caf8d3edb4497dc0b02dd4248cd7fcbabb06","unresolved":false,"context_lines":[{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":88,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":89,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":90,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":91,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":92,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":93,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_7dddd013","line":90,"in_reply_to":"dab17558_7d2670bb","updated":"2016-05-07 02:54:49.000000000","message":"No I didn\u0027t. Access to CI resources and historical data is key to taking over a project. How else shall I put this, it seems like a pretty obvious statement as it is?","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"ed70767f6fb036f32b068eee9c9e94fad77b8d60","unresolved":false,"context_lines":[{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":88,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":89,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":90,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":91,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":92,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":93,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_84874fd6","line":90,"in_reply_to":"dab17558_7dddd013","updated":"2016-05-09 17:29:34.000000000","message":"Well, all the data can made available regardless of the location of the CI, but sure.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5bb2707b823c368ed6d16c8383ea7043b36d3e4d","unresolved":false,"context_lines":[{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":88,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":89,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":90,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":91,"context_line":"   downstream CI, as Grafana support will be required);"},{"line_number":92,"context_line":" * good release footprint, according to the chosen release model;"},{"line_number":93,"context_line":" * adherence to deprecation and stable backports policies;"}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_18ee20ec","line":90,"in_reply_to":"dab17558_84874fd6","updated":"2016-05-09 18:49:10.000000000","message":"It\u0027s not just access the plain historical data.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"8070565a9720b2068a1937ed954b09bcfb045ef3","unresolved":false,"context_lines":[{"line_number":164,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":165,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":166,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_dd379ce1","line":167,"updated":"2016-05-07 02:17:10.000000000","message":"What if a driver/plugin adheres to pretty much all the requirements in line #78?","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5bb2707b823c368ed6d16c8383ea7043b36d3e4d","unresolved":false,"context_lines":[{"line_number":164,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":165,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":166,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_f8cfdc7c","line":167,"in_reply_to":"dab17558_2408232c","updated":"2016-05-09 18:49:10.000000000","message":"Ok, I\u0027ll reply there","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"ed70767f6fb036f32b068eee9c9e94fad77b8d60","unresolved":false,"context_lines":[{"line_number":164,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":165,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":166,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_2408232c","line":167,"in_reply_to":"dab17558_bde738e3","updated":"2016-05-09 17:29:34.000000000","message":"To achieve the goals of the efforts around stability, common APIs etc, setting aside the open vs non open nature, what if a Neutron driver adheres to all the requirements listed above from line #81 to #138. Anyway, I am adding a comment on the latest patchset, where we should be able to wrap up all this back and forth.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"1144caf8d3edb4497dc0b02dd4248cd7fcbabb06","unresolved":false,"context_lines":[{"line_number":164,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":165,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":166,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_bde738e3","line":167,"in_reply_to":"dab17558_dd379ce1","updated":"2016-05-07 02:54:49.000000000","message":"What are you getting at? I don\u0027t get it! Can you be more specific?","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"8070565a9720b2068a1937ed954b09bcfb045ef3","unresolved":false,"context_lines":[{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":173,"context_line":"with the Neutron core team to address integration issues with the core platform."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_bd6e18c7","line":170,"updated":"2016-05-07 02:17:10.000000000","message":"Seems inconsistent on the existing drivers as all the things you talk about quality, consistency go void right here. How is the stadium integrity ensured here?","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"ed70767f6fb036f32b068eee9c9e94fad77b8d60","unresolved":false,"context_lines":[{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":173,"context_line":"with the Neutron core team to address integration issues with the core platform."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_c73679e6","line":170,"in_reply_to":"dab17558_7dc79012","updated":"2016-05-09 17:29:34.000000000","message":"Sure Armando. I am okay to accept it but exceptions here (quite a few of them) clearly conflict with the one of the main goals of the proposal :) Just want to make sure we are aware of this.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"1144caf8d3edb4497dc0b02dd4248cd7fcbabb06","unresolved":false,"context_lines":[{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":173,"context_line":"with the Neutron core team to address integration issues with the core platform."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_7dc79012","line":170,"in_reply_to":"dab17558_bd6e18c7","updated":"2016-05-07 02:54:49.000000000","message":"a) if you had paid attention you might as well realize that the *-aas services may end up being no longer included for different reasons, so your point seems moot; and b) one thing is dealing with countless drivers that neutron dealt with at one point, and about a dozen or two among fw, vpn and lb combined.\n\nFinally, as I mentioned, a decision will have to be made on a case by case basis at it very much depend on the nature and maturity of the project, nonetheless out-of-tree should be preferred.\n\nIf you think this will still lead to lack of integrity, I would beg to differ, as it\u0027s still a huge step in the right direction.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5bb2707b823c368ed6d16c8383ea7043b36d3e4d","unresolved":false,"context_lines":[{"line_number":167,"context_line":"software development: from code to infrastructure and testing."},{"line_number":168,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":169,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":170,"context_line":"than the norm."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"Any team supporting any project (in or out the Stadium) is encouraged to work"},{"line_number":173,"context_line":"with the Neutron core team to address integration issues with the core platform."}],"source_content_type":"text/x-rst","patch_set":8,"id":"dab17558_78892c26","line":170,"in_reply_to":"dab17558_c73679e6","updated":"2016-05-09 18:49:10.000000000","message":"The exceptions have been documented. Knowing the state of some these initiatives, I don\u0027t feel there\u0027s cause for concern.","commit_id":"f4d4f1ffae31d0a73a8197565b8b0b1fbbe34169"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"badba7daf9c452b405077e93f72ef0b6f4308c54","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_87bab16c","line":8,"updated":"2016-05-09 17:39:18.000000000","message":"Thanks for addressing the earlier comments. \n\nThere are a few things I would like to see captured in the proposal that we cover all the stakeholders.\n\nThis proposal talks very well about whats part of the stadium. Please also capture information in the proposal about where would all the sub-projects (that are not part of the stadium anymore) will reside?\n\nMy assumption is they are part of the big tent? My concern here is if they are not part of the Neutron stadium (means Neutron does not care about them) and they are part of the big tent, what does it mean to be part of the big tent?\n\nLet\u0027s take a scenario. A Neutron ML2 driver/core plugin which didn\u0027t make it to the stadium despite fulfilling all the requirements around consistency etc and only because its non-open similar to how Nova has vsphere/hyperV drivers. Under what criteria, this Neutron ML2 driver/plugin can be part of the big tent?\n\nIf we start calling them \"projects\" under big tent, as per this page [1], it does not make sense for these Neutron plugins to be part of the big tent because they clearly violate the project requirements listed here [1].\n\nI\u0027m still not clear. In the sense that Neutron is part of the core OpenStack. Opening up the door and pushing all these plugins to the big tent is dangerous. The \u00273rd party plugins\u0027 should be outside of the stadium (if we follow your/Kyle\u0027s logic), but still within Neutron. In this way is always part of the base definition of OpenStack rather than a complex (quite frankly a chaos) system it will introduce. \n\nI hope this brings more clarity on what I have trying to get to and you better able to understand the issues I have been trying to point out. \n\n[1] http://governance.openstack.org/reference/new-projects-requirements.html","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_d8f49888","line":8,"in_reply_to":"dab17558_87bab16c","updated":"2016-05-09 20:50:28.000000000","message":"What about section starting a line 153?\n\nYou still seem to confuse the actual essence of the Stadium (which I tried to define on line 57): it\u0027s not that if a project is not included in the Stadium, \u0027Neutron\u0027 (which is not a person) doesn\u0027t care about it. It means that some other collectivity besides the Neutron team is in charge of it.\n\nThe wider Neutron community decided to open up different initiatives to develop independently and that means that separate teams must be made accountable. Otherwise there is the perception that the Neutron team is charge of when it isn\u0027t: it doesn\u0027t seem like we can have it both ways. The trade off here is that different initiatives are handled by different teams. The counterargument is that everything goes back into one big bucket with all the implications involved, but I don\u0027t believe you yourself are contemplating such a thing.\n\nThe integration code to proprietary platforms can still be part of openstack.org and get access to the same resources other projects use. It may meet all the four O\u0027s but it does not need to show up in the governance.openstack.org because they are one layer underneath to what these projects are about.\n\nSo it seems to me that you are somewhat conflating the essence of governance.openstack.org with the essence of a place where driver certification is demonstrated and that\u0027s definitely not what governance.openstack.org is for.\n\nDoes that help address your concern?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_abcc9b6a","line":8,"in_reply_to":"dab17558_c7a5c2a2","updated":"2016-05-10 18:59:22.000000000","message":"Ok, will do.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"9cb16d3ee368e7f3b6196777849dbf941106c748","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Neutron Stadium Evolution"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The objective of this specification is three-fold:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_c7a5c2a2","line":8,"in_reply_to":"dab17558_d8f49888","updated":"2016-05-10 06:58:41.000000000","message":"Thanks. That does clarify and address the concerns I had. \n\nLine 153 is quite confusing to be honest and I would request you to update the contents to reflect the comment you just made so its clear.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"73ed7a0926e22262b5b1c60703ee6b679318349f","unresolved":false,"context_lines":[{"line_number":112,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"},{"line_number":113,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":114,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":115,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":116,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":117,"context_line":"   neutron-specs may be required;"},{"line_number":118,"context_line":" * adoption of modular interfaces to provide networking services: this means"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_b1cc0e6b","line":115,"range":{"start_line":115,"start_character":19,"end_line":115,"end_character":41},"updated":"2016-05-10 20:06:05.000000000","message":"Nit: perhaps add a note that neutron-api is outlined below as it hasn\u0027t been described yet in this doc.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"21d4163b68dc4c5b3803c6dd0ca9e9e298879c42","unresolved":false,"context_lines":[{"line_number":112,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"},{"line_number":113,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":114,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":115,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":116,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":117,"context_line":"   neutron-specs may be required;"},{"line_number":118,"context_line":" * adoption of modular interfaces to provide networking services: this means"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_9a22bf50","line":115,"in_reply_to":"dab17558_b1cc0e6b","updated":"2016-05-10 20:51:13.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":2888,"name":"Mathieu Rohon","email":"mathieu.rohon@gmail.com","username":"mathieu-rohon"},"change_message_id":"8b5644f3aebf9f03731d9df8089d0a172b773db8","unresolved":false,"context_lines":[{"line_number":113,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":114,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":115,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":116,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":117,"context_line":"   neutron-specs may be required;"},{"line_number":118,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a30d09ea","line":116,"range":{"start_line":116,"start_character":14,"end_line":116,"end_character":44},"updated":"2016-05-10 08:21:40.000000000","message":"link to http://docs.openstack.org/developer/neutron/policies/blueprints.html#rfe-submission-guidelines ?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":113,"context_line":"   client extensions are part of the python-neutronclient tree to avoid"},{"line_number":114,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":115,"context_line":" * adoption of the neutron-api subproject: submission of any API change must"},{"line_number":116,"context_line":"   follow the Neutron RFE submission process, where specifications to"},{"line_number":117,"context_line":"   neutron-specs may be required;"},{"line_number":118,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_cbbf5fa8","line":116,"in_reply_to":"dab17558_a30d09ea","updated":"2016-05-10 18:59:22.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"cce89e69365a672dcce3a9b535120606b6930868","unresolved":false,"context_lines":[{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":120,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":121,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":122,"context_line":"   flavor framework as necessary."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_e7ec46f5","line":122,"updated":"2016-05-10 07:02:42.000000000","message":"i feel this (core plugin vs ml2 driver) is a bit controversial and ought to be a separate discussion.\n\ni guess ml2 still needs some improvements to be a \"single\" plugin interface.\neg. it should stop hardcoding supported extensions.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"2de8e9468b7084272bba5322c90e508e7cda7e29","unresolved":false,"context_lines":[{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":120,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":121,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":122,"context_line":"   flavor framework as necessary."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_59017c37","line":122,"in_reply_to":"dab17558_3e0a9e79","updated":"2016-05-11 03:10:28.000000000","message":"how so? Can you provide a practical example where the application of this criterion may result counterproductive?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"19286edbbb60e613dcf63d8b8450f02ee3c81dc0","unresolved":false,"context_lines":[{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":120,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":121,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":122,"context_line":"   flavor framework as necessary."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_7ff1bf6a","line":122,"in_reply_to":"dab17558_59017c37","updated":"2016-05-11 05:44:05.000000000","message":"nothing counterproductive, as far as it\u0027s considered in deadline section.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"d529e816614c33906fec3c9a881b7e58e5d7c84a","unresolved":false,"context_lines":[{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":120,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":121,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":122,"context_line":"   flavor framework as necessary."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_3e0a9e79","line":122,"in_reply_to":"dab17558_ab049b49","updated":"2016-05-11 02:17:41.000000000","message":"i agree the direction, but i feel it\u0027s too early to enforce.\nbut let\u0027s see.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":119,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":120,"context_line":"   service plugins respectively. A service plugin can expose a driver"},{"line_number":121,"context_line":"   interface to support multiple backend technologies, and/or adopt the"},{"line_number":122,"context_line":"   flavor framework as necessary."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The last two criteria are particularly important for the following reasons:"},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_ab049b49","line":122,"in_reply_to":"dab17558_e7ec46f5","updated":"2016-05-10 18:59:22.000000000","message":"How so, can you elaborate? The adoption of the pattern is overwhelming and any solution that\u0027s been proposed so far started off as an ML2 driver. Surely, it needs attention and improvement as you point out, and being explicit that the Neutron team is focussed on ML2 only keeps energy focussed in one place, which is beneficial in addressing the very point you raised.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":7812,"name":"Franklin Naval","email":"franklin.naval@gmail.com","username":"fnaval"},"change_message_id":"f187e565fc75d1bb9387894251973b41b2abfed7","unresolved":false,"context_lines":[{"line_number":147,"context_line":"to discuss governance issues."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Projects part of the Neutron Stadium have typically the first milestone to get"},{"line_number":150,"context_line":"their house in order, during which time reassessment happen; once removed, a"},{"line_number":151,"context_line":"project cannot reapply within the same release cycle it has been evicted."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"What if a project cannot be considered part of the Stadium?"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_587e1ae5","line":150,"range":{"start_line":150,"start_character":53,"end_line":150,"end_character":59},"updated":"2016-05-07 04:27:54.000000000","message":"happens","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":147,"context_line":"to discuss governance issues."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Projects part of the Neutron Stadium have typically the first milestone to get"},{"line_number":150,"context_line":"their house in order, during which time reassessment happen; once removed, a"},{"line_number":151,"context_line":"project cannot reapply within the same release cycle it has been evicted."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"What if a project cannot be considered part of the Stadium?"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_d878182e","line":150,"in_reply_to":"dab17558_587e1ae5","updated":"2016-05-09 20:50:28.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":7812,"name":"Franklin Naval","email":"franklin.naval@gmail.com","username":"fnaval"},"change_message_id":"f187e565fc75d1bb9387894251973b41b2abfed7","unresolved":false,"context_lines":[{"line_number":163,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_,"},{"line_number":164,"context_line":"rather than going for Stadium inclusion."},{"line_number":165,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"},{"line_number":166,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":167,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":168,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":169,"context_line":"software development: from code to infrastructure and testing."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_988882e9","line":166,"range":{"start_line":166,"start_character":3,"end_line":166,"end_character":4},"updated":"2016-05-07 04:27:54.000000000","message":"be","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":163,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_,"},{"line_number":164,"context_line":"rather than going for Stadium inclusion."},{"line_number":165,"context_line":"Finally, solutions that leverage proprietary software and/or hardware will also"},{"line_number":166,"context_line":"not considered for inclusion into the Neutron Stadium, due to the barrier on"},{"line_number":167,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":168,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":169,"context_line":"software development: from code to infrastructure and testing."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_1873c04e","line":166,"in_reply_to":"dab17558_988882e9","updated":"2016-05-09 20:50:28.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"cce89e69365a672dcce3a9b535120606b6930868","unresolved":false,"context_lines":[{"line_number":167,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":168,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":169,"context_line":"software development: from code to infrastructure and testing."},{"line_number":170,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":171,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":172,"context_line":"than the norm."},{"line_number":173,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_240bec8f","line":170,"range":{"start_line":170,"start_character":59,"end_line":170,"end_character":81},"updated":"2016-05-10 07:02:42.000000000","message":"does \"extensions\" here means vendor drivers rather than api extensions?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":167,"context_line":"access to the technology for dev/test and CI integration, as well as the inability"},{"line_number":168,"context_line":"for the core team to provide effective feedback during review for any aspect of"},{"line_number":169,"context_line":"software development: from code to infrastructure and testing."},{"line_number":170,"context_line":"Some Neutron projects may still decide to host software to proprietary extensions"},{"line_number":171,"context_line":"(e.g. vpnaas, fwaas, etc), but these should be seen as the exception rather"},{"line_number":172,"context_line":"than the norm."},{"line_number":173,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_ebfa2342","line":170,"in_reply_to":"dab17558_240bec8f","updated":"2016-05-10 18:59:22.000000000","message":"the former, I\u0027ll clarify.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"ab54f68b40a6c879b496cc4752cfc59d33791c10","unresolved":false,"context_lines":[{"line_number":193,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":194,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":195,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":196,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":197,"context_line":"project will follow the Neutron RFE process with submission of specification"},{"line_number":198,"context_line":"documents to neutron-specs, if deemed required. The resulting code will end"},{"line_number":199,"context_line":"up being located in neutron-api itself, whilst specs will be hosted on"},{"line_number":200,"context_line":"neutron-specs. Each core team of projects belonging to the Stadium will"},{"line_number":201,"context_line":"have +2 rights on both neutron-specs and neutron-api projects. The neutron"},{"line_number":202,"context_line":"drivers will continue to hold +W rights on both repos. It is noteworthy that"},{"line_number":203,"context_line":"members of the individual core teams are and will be considered for membership"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a06f9229","line":200,"range":{"start_line":196,"start_character":52,"end_line":200,"end_character":13},"updated":"2016-05-10 21:54:32.000000000","message":"Perhaps a naive question, but I\u0027m trying to make sure I understand the process with neutron-api in the picture from an neutron dev perspective when submitting a new \"feature request\" that touches the API. Let\u0027s suppose I\u0027m submitting a new neutron extension feature...\n\n--\nI will still submit my single RFE, but since it touches the API \u0027neutron-api\u0027 will be an effected project for the bug to get \"API eyes on it\". In this example \u0027neutron\u0027 would also be an affected project on the bug. Once I get both API and core eyes on the RFE, that may result in a spec (neutron-specs) which again must be approved. Now I\u0027m ready to code; I factor a patch for the API (extension logic in this example) for the neutron-api project (git repo) and another (1 or more) for the actual implementation, which, in this example would be to neutron project (git repo). Obviously my neutron+neutron-api patches have implicit dependency here... Once all my code is approved (both project repos) I\u0027m done.\n--\n\n\nAssuming my workflow above is close to correct, the main benefits here are to get \"API eyes\" on the RFE+spec+API code where applicable, and also to consolidate the neutron \"stadium\" API code into a single repo (git project)... Am I understanding properly? I\u0027m asking because a potential alternative might be just to have tags or something for API related RFEs/specs/patches that gets the API eyes on them, but that leaves the actual code as-is today (e.g. a tactical, less disruptive approach).\n\n\nDoes the fact that this process requires a separate change set for the API portion of the change introduce any complexity into our dev workflow (ex: unit tests that require both the API and core patch sets to run properly)?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"d450edf2aa03692751459fc9c93aed53fd4d0519","unresolved":false,"context_lines":[{"line_number":197,"context_line":"project will follow the Neutron RFE process with submission of specification"},{"line_number":198,"context_line":"documents to neutron-specs, if deemed required. The resulting code will end"},{"line_number":199,"context_line":"up being located in neutron-api itself, whilst specs will be hosted on"},{"line_number":200,"context_line":"neutron-specs. Each core team of projects belonging to the Stadium will"},{"line_number":201,"context_line":"have +2 rights on both neutron-specs and neutron-api projects. The neutron"},{"line_number":202,"context_line":"drivers will continue to hold +W rights on both repos. It is noteworthy that"},{"line_number":203,"context_line":"members of the individual core teams are and will be considered for membership"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_23cd67b7","line":200,"in_reply_to":"dab17558_a06f9229","updated":"2016-05-11 03:08:27.000000000","message":"Thanks for bringing up the point. I don\u0027t think it\u0027s naive at all.\n\nThe use of bug tags to get API eyes over certain proposal makes sense, but it may be easily overlooked, whereas the proposed arrangement is explicitly introducing a \u0027gate\u0027 in between the proposal and the code, which I think is less prone to error. This clearly introduced an extra step in getting your change hit the road, but it\u0027s the step that should at least allow us to keep the Neutron API nice and consistent.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"73ed7a0926e22262b5b1c60703ee6b679318349f","unresolved":false,"context_lines":[{"line_number":222,"context_line":"More precisely, to be considered for inclusion (continue to be part of the"},{"line_number":223,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":226,"context_line":"  the api models/definitions out of the neutron repo. Developer documentation"},{"line_number":227,"context_line":"  on the `Neutron Stadium \u003chttp://docs.openstack.org/developer/neutron/#neutron-stadium\u003e`_"},{"line_number":228,"context_line":"  will be revised according to the guidelines outlined in this proposal."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_d45d4016","line":225,"range":{"start_line":225,"start_character":38,"end_line":225,"end_character":58},"updated":"2016-05-10 20:06:05.000000000","message":"This there going to be a separate spec for neutron-api, or is this considered that spec?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"21d4163b68dc4c5b3803c6dd0ca9e9e298879c42","unresolved":false,"context_lines":[{"line_number":222,"context_line":"More precisely, to be considered for inclusion (continue to be part of the"},{"line_number":223,"context_line":"Stadium list), the following plan must be put in place:"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"* neutron: the core team will have to stand up neutron-api, and transition"},{"line_number":226,"context_line":"  the api models/definitions out of the neutron repo. Developer documentation"},{"line_number":227,"context_line":"  on the `Neutron Stadium \u003chttp://docs.openstack.org/developer/neutron/#neutron-stadium\u003e`_"},{"line_number":228,"context_line":"  will be revised according to the guidelines outlined in this proposal."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_baece3f3","line":225,"in_reply_to":"dab17558_d45d4016","updated":"2016-05-10 20:51:13.000000000","message":"I\u0027ll put any further detail here, rather than create another spec.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":7812,"name":"Franklin Naval","email":"franklin.naval@gmail.com","username":"fnaval"},"change_message_id":"f187e565fc75d1bb9387894251973b41b2abfed7","unresolved":false,"context_lines":[{"line_number":231,"context_line":""},{"line_number":232,"context_line":"  * complete the transition to fwaas v2;"},{"line_number":233,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":234,"context_line":"  * complete docs, end-to-end testing, and demonstrate abilityto upgrade;"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"* neutron-lbaas: the existence of this project is now questioned by the"},{"line_number":237,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_782b1eec","line":234,"range":{"start_line":234,"start_character":55,"end_line":234,"end_character":64},"updated":"2016-05-07 04:27:54.000000000","message":"ability to","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":231,"context_line":""},{"line_number":232,"context_line":"  * complete the transition to fwaas v2;"},{"line_number":233,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":234,"context_line":"  * complete docs, end-to-end testing, and demonstrate abilityto upgrade;"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"* neutron-lbaas: the existence of this project is now questioned by the"},{"line_number":237,"context_line":"  presence of Octavia. This is elaborated more in `spinout \u003chttps://review.openstack.org/#/c/310805/\u003e`_ spec."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_78900c44","line":234,"in_reply_to":"dab17558_782b1eec","updated":"2016-05-09 20:50:28.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"a38513fc697f78ea86aa88896e8602da6932189e","unresolved":false,"context_lines":[{"line_number":250,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":251,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":252,"context_line":""},{"line_number":253,"context_line":"* networking-l2gw: similarly to neutron-vpnaas, this needs to:"},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":256,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_61b326ea","line":253,"updated":"2016-05-10 05:40:17.000000000","message":"+1 - this requires a lot of work","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"8da8c9ebfabf8a7778ee216ec99606fdfc82c685","unresolved":false,"context_lines":[{"line_number":339,"context_line":"----------------------------------------------------------"},{"line_number":340,"context_line":""},{"line_number":341,"context_line":"There are projects currently hosted on OpenStack that are not part of the"},{"line_number":342,"context_line":"Neutron governance list, for example neutron-classifier, and there may be more"},{"line_number":343,"context_line":"that may be created in the future. Such initiatives should consider being"},{"line_number":344,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":345,"context_line":"collaboration already established across the teams involved. As mentioned"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_3ad473bb","line":342,"updated":"2016-05-10 21:12:37.000000000","message":"In the Austin summit, we had a meeting discussion on \"common flow classifier\" and will kick start the design and development work in Neutron. My understanding is that the work on neutron-classifier is very primitive and the goal of \"common flow classifier\" is to replace \"neutron-classifier\". Is that in line with your thought? Could you clarify why there is a need for neutron-classifier to apply for inclusion?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"d450edf2aa03692751459fc9c93aed53fd4d0519","unresolved":false,"context_lines":[{"line_number":339,"context_line":"----------------------------------------------------------"},{"line_number":340,"context_line":""},{"line_number":341,"context_line":"There are projects currently hosted on OpenStack that are not part of the"},{"line_number":342,"context_line":"Neutron governance list, for example neutron-classifier, and there may be more"},{"line_number":343,"context_line":"that may be created in the future. Such initiatives should consider being"},{"line_number":344,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":345,"context_line":"collaboration already established across the teams involved. As mentioned"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_680bcc2a","line":342,"in_reply_to":"dab17558_3ad473bb","updated":"2016-05-11 03:08:27.000000000","message":"Are you suggesting that you are going to create yet another project, when the work can be done in the context of the neutron-classifier repo [1]?\n\nBut let me try to answer with another question: why do you think that the classifier effort needs to be included right off the bat?\n\n[1] https://github.com/openstack/neutron-classifier","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":7812,"name":"Franklin Naval","email":"franklin.naval@gmail.com","username":"fnaval"},"change_message_id":"f187e565fc75d1bb9387894251973b41b2abfed7","unresolved":false,"context_lines":[{"line_number":345,"context_line":"collaboration already established across the teams involved. As mentioned"},{"line_number":346,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":347,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":348,"context_line":"mutual collaboration existed over time, the more likely it is that there"},{"line_number":349,"context_line":"is a good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":350,"context_line":"a formality."},{"line_number":351,"context_line":"In order to succeed in an application, a project should first and foremost"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_f826ee14","line":348,"range":{"start_line":348,"start_character":21,"end_line":348,"end_character":28},"updated":"2016-05-07 04:27:54.000000000","message":"exist","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":345,"context_line":"collaboration already established across the teams involved. As mentioned"},{"line_number":346,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":347,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":348,"context_line":"mutual collaboration existed over time, the more likely it is that there"},{"line_number":349,"context_line":"is a good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":350,"context_line":"a formality."},{"line_number":351,"context_line":"In order to succeed in an application, a project should first and foremost"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_b89a7461","line":348,"in_reply_to":"dab17558_f826ee14","updated":"2016-05-09 20:50:28.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"cce89e69365a672dcce3a9b535120606b6930868","unresolved":false,"context_lines":[{"line_number":346,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":347,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":348,"context_line":"mutual collaboration existed over time, the more likely it is that there"},{"line_number":349,"context_line":"is a good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":350,"context_line":"a formality."},{"line_number":351,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":352,"context_line":"make sure that these criteria are met:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_0454e8c7","line":349,"range":{"start_line":349,"start_character":56,"end_line":349,"end_character":60},"updated":"2016-05-10 07:02:42.000000000","message":"extra a","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":346,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":347,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":348,"context_line":"mutual collaboration existed over time, the more likely it is that there"},{"line_number":349,"context_line":"is a good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":350,"context_line":"a formality."},{"line_number":351,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":352,"context_line":"make sure that these criteria are met:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_0b9cc70d","line":349,"in_reply_to":"dab17558_0454e8c7","updated":"2016-05-10 18:59:22.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"cce89e69365a672dcce3a9b535120606b6930868","unresolved":false,"context_lines":[{"line_number":356,"context_line":"* client extensions available as OSC plugins;"},{"line_number":357,"context_line":"* adoption of neutron-lib;"},{"line_number":358,"context_line":""},{"line_number":359,"context_line":"The request for application would then need to submitted with and RFE and"},{"line_number":360,"context_line":"subsequent spec submission where the following information is provided:"},{"line_number":361,"context_line":""},{"line_number":362,"context_line":"* pointers to user and developer documentations;"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_04198822","line":359,"range":{"start_line":359,"start_character":62,"end_line":359,"end_character":65},"updated":"2016-05-10 07:02:42.000000000","message":"an ?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":7812,"name":"Franklin Naval","email":"franklin.naval@gmail.com","username":"fnaval"},"change_message_id":"f187e565fc75d1bb9387894251973b41b2abfed7","unresolved":false,"context_lines":[{"line_number":356,"context_line":"* client extensions available as OSC plugins;"},{"line_number":357,"context_line":"* adoption of neutron-lib;"},{"line_number":358,"context_line":""},{"line_number":359,"context_line":"The request for application would then need to submitted with and RFE and"},{"line_number":360,"context_line":"subsequent spec submission where the following information is provided:"},{"line_number":361,"context_line":""},{"line_number":362,"context_line":"* pointers to user and developer documentations;"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_d8232a04","line":359,"range":{"start_line":359,"start_character":46,"end_line":359,"end_character":47},"updated":"2016-05-07 04:27:54.000000000","message":"be","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4124ad1343bcc4beaae4cc3a4a342c94520b1e42","unresolved":false,"context_lines":[{"line_number":356,"context_line":"* client extensions available as OSC plugins;"},{"line_number":357,"context_line":"* adoption of neutron-lib;"},{"line_number":358,"context_line":""},{"line_number":359,"context_line":"The request for application would then need to submitted with and RFE and"},{"line_number":360,"context_line":"subsequent spec submission where the following information is provided:"},{"line_number":361,"context_line":""},{"line_number":362,"context_line":"* pointers to user and developer documentations;"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_6b9d9309","line":359,"in_reply_to":"dab17558_04198822","updated":"2016-05-10 18:59:22.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5ca3cc153a32ec4cb3aa13d91ef752cebc9d2e1d","unresolved":false,"context_lines":[{"line_number":356,"context_line":"* client extensions available as OSC plugins;"},{"line_number":357,"context_line":"* adoption of neutron-lib;"},{"line_number":358,"context_line":""},{"line_number":359,"context_line":"The request for application would then need to submitted with and RFE and"},{"line_number":360,"context_line":"subsequent spec submission where the following information is provided:"},{"line_number":361,"context_line":""},{"line_number":362,"context_line":"* pointers to user and developer documentations;"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_989df05b","line":359,"in_reply_to":"dab17558_d8232a04","updated":"2016-05-09 20:50:28.000000000","message":"Done","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"73ed7a0926e22262b5b1c60703ee6b679318349f","unresolved":false,"context_lines":[{"line_number":366,"context_line":"* pointers to stable backports and release deliverables;"},{"line_number":367,"context_line":"* pointers to API specification and definitions;"},{"line_number":368,"context_line":""},{"line_number":369,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":370,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":371,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":372,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_1454e8fc","line":369,"range":{"start_line":369,"start_character":0,"end_line":369,"end_character":40},"updated":"2016-05-10 20:06:05.000000000","message":"Evaluated and approved via the standard RFE process (e.g. driver team; PTL + cores) I assume; or is there a different process for this type of RFE?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"21d4163b68dc4c5b3803c6dd0ca9e9e298879c42","unresolved":false,"context_lines":[{"line_number":366,"context_line":"* pointers to stable backports and release deliverables;"},{"line_number":367,"context_line":"* pointers to API specification and definitions;"},{"line_number":368,"context_line":""},{"line_number":369,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":370,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":371,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":372,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_5ab21707","line":369,"in_reply_to":"dab17558_1454e8fc","updated":"2016-05-10 20:51:13.000000000","message":"No, there won\u0027t be.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"ab54f68b40a6c879b496cc4752cfc59d33791c10","unresolved":false,"context_lines":[{"line_number":366,"context_line":"* pointers to stable backports and release deliverables;"},{"line_number":367,"context_line":"* pointers to API specification and definitions;"},{"line_number":368,"context_line":""},{"line_number":369,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":370,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":371,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":372,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_7ac9db58","line":369,"in_reply_to":"dab17558_5ab21707","updated":"2016-05-10 21:54:32.000000000","message":"Possible to just add that here for clarity? e.g. \"Once evaluated and successfully approved using the standard RFE process...\"","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"8da8c9ebfabf8a7778ee216ec99606fdfc82c685","unresolved":false,"context_lines":[{"line_number":382,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":383,"context_line":"within the Stadium, thus inducing a more sustainable maintenance effort on"},{"line_number":384,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsibility of"},{"line_number":385,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":386,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":387,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"},{"line_number":388,"context_line":"process and have the same status of any other OpenStack Active Technical"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a5c68497","line":385,"updated":"2016-05-10 21:12:37.000000000","message":"It is still not clear to me what is meant by \"Neutron team takes responsibility of the deliverables produced by Stadium project\"? Currently the sub-project team lead/core applied for release of that sub-project. How is this going to be changed? Who will be responsible for release of the stadium project feature such as applying for release, docs, release notes etc.? What is meant by \"Neutron team\"? Do you mean \"Neutron core members\"? Does the \"Neutron team\" include core members of the included stadium projects?","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"d450edf2aa03692751459fc9c93aed53fd4d0519","unresolved":false,"context_lines":[{"line_number":382,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":383,"context_line":"within the Stadium, thus inducing a more sustainable maintenance effort on"},{"line_number":384,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsibility of"},{"line_number":385,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":386,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":387,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"},{"line_number":388,"context_line":"process and have the same status of any other OpenStack Active Technical"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_b9e348a3","line":385,"in_reply_to":"dab17558_a5c68497","updated":"2016-05-11 03:08:27.000000000","message":"Today the PTL works with the various individuals to move things along, it\u0027s a team effort and as a team that is made of the collection of the individual people involved in the various Stadium initiatives, we should make sure that all things are in order throughout the release and nothing falls through the cracks.\n\nWe may have people in specific \u0027informal\u0027 capacities, a doc liaison, a release liaison, etc. These are people who \u0027volunteer\u0027 to address Stadium-wide issues, and at the same time, some of these issues are inherently addressed collaboratively (like building release notes) by a multitude of contributors.\n\nAnyone is welcome to step up, but at the same time there are responsibilities that must be fulfilled for the sake of the project, and for these I would expect that core members play a key role.\n\nNot sure if that answers your question.","commit_id":"2a9d889c97b3524dc2fe3af9f58bbbb6c6983f6a"},{"author":{"_account_id":9396,"name":"igordcard","email":"igordcard@gmail.com","username":"igordcard"},"change_message_id":"957890b63c75bf9ec6270030e267809349bb8806","unresolved":false,"context_lines":[{"line_number":81,"context_line":"In order to be considered part of the Stadium, a project must show a track"},{"line_number":82,"context_line":"record of alignment with the Neutron core project. This means showing proof"},{"line_number":83,"context_line":"of adoption of practices as led by the Neutron core team. Some of these"},{"line_number":84,"context_line":"practices are typically already followed by the most mature Openstack"},{"line_number":85,"context_line":"projects and should not be perceived as particularly stringent:"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_e5fd196f","line":84,"range":{"start_line":84,"start_character":60,"end_line":84,"end_character":69},"updated":"2016-05-11 09:23:15.000000000","message":"OpenStack","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":81,"context_line":"In order to be considered part of the Stadium, a project must show a track"},{"line_number":82,"context_line":"record of alignment with the Neutron core project. This means showing proof"},{"line_number":83,"context_line":"of adoption of practices as led by the Neutron core team. Some of these"},{"line_number":84,"context_line":"practices are typically already followed by the most mature Openstack"},{"line_number":85,"context_line":"projects and should not be perceived as particularly stringent:"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":" * exhaustive documentation: it is expected that each project will have a"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_25ccab60","line":84,"range":{"start_line":84,"start_character":60,"end_line":84,"end_character":69},"in_reply_to":"dab17558_e5fd196f","updated":"2016-05-13 17:48:47.000000000","message":"Done","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":9396,"name":"igordcard","email":"igordcard@gmail.com","username":"igordcard"},"change_message_id":"957890b63c75bf9ec6270030e267809349bb8806","unresolved":false,"context_lines":[{"line_number":171,"context_line":"these initiatives (as past experiences demonstrate), and in fact any team is"},{"line_number":172,"context_line":"encouraged to seek collaboration in order to address integration issues with the"},{"line_number":173,"context_line":"core Neutron platform. Teams for projects outside the Stadium are simply fully"},{"line_number":174,"context_line":"responsible of dealing with the end-to-end SLDC of their solutions, and thus"},{"line_number":175,"context_line":"empowered. The integration code to external systems can still be hosted on openstack.org"},{"line_number":176,"context_line":"irrespective of their nature and get access to the same resources any other"},{"line_number":177,"context_line":"OpenStack project uses. It is noteworthy that it may not be useful for them to seek"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_e59eb905","line":174,"range":{"start_line":174,"start_character":43,"end_line":174,"end_character":47},"updated":"2016-05-11 09:23:15.000000000","message":"SDLC?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":171,"context_line":"these initiatives (as past experiences demonstrate), and in fact any team is"},{"line_number":172,"context_line":"encouraged to seek collaboration in order to address integration issues with the"},{"line_number":173,"context_line":"core Neutron platform. Teams for projects outside the Stadium are simply fully"},{"line_number":174,"context_line":"responsible of dealing with the end-to-end SLDC of their solutions, and thus"},{"line_number":175,"context_line":"empowered. The integration code to external systems can still be hosted on openstack.org"},{"line_number":176,"context_line":"irrespective of their nature and get access to the same resources any other"},{"line_number":177,"context_line":"OpenStack project uses. It is noteworthy that it may not be useful for them to seek"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_05fec76a","line":174,"range":{"start_line":174,"start_character":43,"end_line":174,"end_character":47},"in_reply_to":"dab17558_2e985e6a","updated":"2016-05-13 17:48:47.000000000","message":"Done","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":8279,"name":"Fawad Khaliq","email":"fawadkq@gmail.com","username":"fawadkhaliq"},"change_message_id":"caad85363669647b051738668d91d3fe225c5015","unresolved":false,"context_lines":[{"line_number":171,"context_line":"these initiatives (as past experiences demonstrate), and in fact any team is"},{"line_number":172,"context_line":"encouraged to seek collaboration in order to address integration issues with the"},{"line_number":173,"context_line":"core Neutron platform. Teams for projects outside the Stadium are simply fully"},{"line_number":174,"context_line":"responsible of dealing with the end-to-end SLDC of their solutions, and thus"},{"line_number":175,"context_line":"empowered. The integration code to external systems can still be hosted on openstack.org"},{"line_number":176,"context_line":"irrespective of their nature and get access to the same resources any other"},{"line_number":177,"context_line":"OpenStack project uses. It is noteworthy that it may not be useful for them to seek"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_fba3c8fd","line":174,"range":{"start_line":174,"start_character":43,"end_line":174,"end_character":47},"in_reply_to":"dab17558_e59eb905","updated":"2016-05-12 04:13:22.000000000","message":"software development life cycle","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":9396,"name":"igordcard","email":"igordcard@gmail.com","username":"igordcard"},"change_message_id":"15c21fb42cf1b1ae3e91abc3e5a938472d1aa69c","unresolved":false,"context_lines":[{"line_number":171,"context_line":"these initiatives (as past experiences demonstrate), and in fact any team is"},{"line_number":172,"context_line":"encouraged to seek collaboration in order to address integration issues with the"},{"line_number":173,"context_line":"core Neutron platform. Teams for projects outside the Stadium are simply fully"},{"line_number":174,"context_line":"responsible of dealing with the end-to-end SLDC of their solutions, and thus"},{"line_number":175,"context_line":"empowered. The integration code to external systems can still be hosted on openstack.org"},{"line_number":176,"context_line":"irrespective of their nature and get access to the same resources any other"},{"line_number":177,"context_line":"OpenStack project uses. It is noteworthy that it may not be useful for them to seek"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_2e985e6a","line":174,"range":{"start_line":174,"start_character":43,"end_line":174,"end_character":47},"in_reply_to":"dab17558_fba3c8fd","updated":"2016-05-12 10:33:40.000000000","message":"Yes, so s/SLDC/SDLC. Unless SLDC is correct and pointing to some other term that I don\u0027t know about.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6524,"name":"Henry Gessau","email":"HenryG@gessau.net","username":"gessau"},"change_message_id":"3f26a701c58664395a91d770f0fbc19e3d81b927","unresolved":false,"context_lines":[{"line_number":205,"context_line":""},{"line_number":206,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":207,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_c22d39ff","line":209,"range":{"start_line":208,"start_character":0,"end_line":209,"end_character":8},"updated":"2016-05-12 02:32:14.000000000","message":"We already have the neutron-lib repo which contains common stuff for projects that integrate with neutron. Can we add the common api stuff there and avoid yet another repo?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"ef811e86c73ab5856a2afd0beee497fa5d1ececd","unresolved":false,"context_lines":[{"line_number":205,"context_line":""},{"line_number":206,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":207,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_f60abf77","line":209,"range":{"start_line":208,"start_character":0,"end_line":209,"end_character":8},"in_reply_to":"dab17558_82769103","updated":"2016-05-12 05:42:16.000000000","message":"AFAIU, neutron-api is not a library rather is a place to hold agreed API\u0027s. IMO, getting API merged needs more control and hence a separate repo will be better.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"769d818c55bc20bd6a3b0225e01bc41650703b94","unresolved":false,"context_lines":[{"line_number":205,"context_line":""},{"line_number":206,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":207,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_82769103","line":209,"range":{"start_line":208,"start_character":0,"end_line":209,"end_character":8},"in_reply_to":"dab17558_c22d39ff","updated":"2016-05-12 02:34:56.000000000","message":"I did present that as a possibility during the design summit discussion and there\u0027s no technical reason why we\u0027d need yet another repo, if nothing else adopting two different release models. \u0027neutron-lib\u0027 might not be as evocative as \u0027neutron-api\u0027 but the idea of piggybacking neutron-lib it\u0027s definitely worth considering.\n\nThanks for raising the point.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":205,"context_line":""},{"line_number":206,"context_line":"In order to resolve this problem, the Neutron team should consider the"},{"line_number":207,"context_line":"adoption of a neutron-api initiative where API proposals are consolidated."},{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_a5237aa6","line":209,"range":{"start_line":208,"start_character":0,"end_line":209,"end_character":8},"in_reply_to":"dab17558_f60abf77","updated":"2016-05-13 17:48:47.000000000","message":"Targeting neutron-lib to start off might help us get to the end goal faster though. I don\u0027t expect access rights between neutron-api and neutron-lib to be wildly different, so this might actually be worth considering.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"4d6dd1f95709025b7db0db59facff577aba42c4e","unresolved":false,"context_lines":[{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"},{"line_number":213,"context_line":"documents to neutron-specs, if deemed required. The resulting code will end"},{"line_number":214,"context_line":"up being located in neutron-api itself, whilst specs will be hosted on"},{"line_number":215,"context_line":"neutron-specs. Each core team of projects belonging to the Stadium will"},{"line_number":216,"context_line":"have +2 rights on both neutron-specs and neutron-api projects. The neutron"},{"line_number":217,"context_line":"drivers will continue to hold +W rights on both repos. It is noteworthy that"},{"line_number":218,"context_line":"members of the individual core teams are and will be considered for membership"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_36b910cd","line":215,"range":{"start_line":211,"start_character":52,"end_line":215,"end_character":13},"updated":"2016-05-11 12:50:44.000000000","message":"Back to my comments on this section from patch set 9....\n\n(a) Is it possible for you to add a sentence about how this impacts the feature dev process as well as the code process? e.g. \"The feature request (RFE) process doesn\u0027t change with this proposal, however contributors must factor their code patches accordingly such that the API portion lands in the neutron-api repo while the backing implementation lands in its respective repo\". Something very simple is fine; it just wasn\u0027t overly clear to me if/how this impacted that process.\n\n\n(b) I didn\u0027t see a response to my question \"Does the fact that this process requires a separate change set for the API portion of the change introduce any complexity into our dev workflow (ex: unit tests that require both the API and core patch sets to run properly)?\"","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":208,"context_line":"The neutron-api project can be a component to be consumed by Neutron Stadium"},{"line_number":209,"context_line":"projects, and to be started off as a spinout of the neutron api codebase such"},{"line_number":210,"context_line":"as neutron/api, neutron/extensions, and any other project (e.g. bgp, l2gw,"},{"line_number":211,"context_line":"sfc, etc) that is considered for Stadium inclusion. Contributions to this"},{"line_number":212,"context_line":"project will follow the Neutron RFE process with submission of specification"},{"line_number":213,"context_line":"documents to neutron-specs, if deemed required. The resulting code will end"},{"line_number":214,"context_line":"up being located in neutron-api itself, whilst specs will be hosted on"},{"line_number":215,"context_line":"neutron-specs. Each core team of projects belonging to the Stadium will"},{"line_number":216,"context_line":"have +2 rights on both neutron-specs and neutron-api projects. The neutron"},{"line_number":217,"context_line":"drivers will continue to hold +W rights on both repos. It is noteworthy that"},{"line_number":218,"context_line":"members of the individual core teams are and will be considered for membership"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_c5179f52","line":215,"range":{"start_line":211,"start_character":52,"end_line":215,"end_character":13},"in_reply_to":"dab17558_36b910cd","updated":"2016-05-13 17:48:47.000000000","message":"a) I am not sure the point is worth making. OpenStack development that\u0027s not a simple fix already may involve multiple repos, client, server, *aas, nova, heat, devstack. It seems pretty obvious but I can see if I can sneak something in.\n\nb) I thought I had with: \"This clearly introduced an extra step in getting your change hit the road, but it\u0027s the step that should at least allow us to keep the Neutron API nice and consistent.\" So yes, having yet another repo to worry about definitely add some complexity, but I cannot quantify this complexity to date, though I hope the complexity will be small especially if we consider reusing neutron-lib for api purposes.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":2888,"name":"Mathieu Rohon","email":"mathieu.rohon@gmail.com","username":"mathieu-rohon"},"change_message_id":"faec0ed5a0eb6f56d78f626848ef0be46094682c","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":282,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":283,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":284,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_a8cc8bbb","line":281,"range":{"start_line":281,"start_character":10,"end_line":281,"end_character":21},"updated":"2016-05-11 07:09:41.000000000","message":"same question as Takashi line 294 : will we have to rediscuss our API extension through RFE/blueprint on neutron-api, or will it be accepted de facto, since it has already been discussed by bgpvpn actors?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":282,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":283,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":284,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_c52b1f32","line":281,"in_reply_to":"dab17558_0c78e68e","updated":"2016-05-13 17:48:47.000000000","message":"I would expect a relatively quick rubber stamping since it would be insane to go through a complete overhaul at this stage. Anything that may be spotted as not adequate will need to go through iterations on top of what is considered starting point of v1 if you will. I thought it was implicit but I\u0027ll clarify.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"ef811e86c73ab5856a2afd0beee497fa5d1ececd","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":282,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":283,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":284,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_36d447ea","line":281,"range":{"start_line":281,"start_character":10,"end_line":281,"end_character":21},"in_reply_to":"dab17558_a8cc8bbb","updated":"2016-05-12 05:42:16.000000000","message":"+1 for clarify this as most of us will have this query.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":12021,"name":"Thomas Morin","email":"tmmorin.orange@gmail.com","username":"tmorin"},"change_message_id":"436927f7c40c07b65895f9cba2e94588f729a191","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":282,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":283,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":284,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_b75e5510","line":281,"range":{"start_line":281,"start_character":10,"end_line":281,"end_character":21},"in_reply_to":"dab17558_a8cc8bbb","updated":"2016-05-12 15:09:03.000000000","message":"I agree this is an important point to clarify for all current stadium projects, not only BGPVPN.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"0dcbe141e3fb5449e08e65dbafa2f203c6b6cc9d","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":280,"context_line":""},{"line_number":281,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":282,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":283,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":284,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_0c78e68e","line":281,"in_reply_to":"dab17558_b75e5510","updated":"2016-05-12 19:59:25.000000000","message":"+1, this is an important point that needs clarification. All project API patches should have been discussed/debated/reviewed for months, gone through many iterations, and project team members eventually reached consensus before they were merged.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"166ab511cb33b4ed48d5444dea21a7ebe5ee037e","unresolved":false,"context_lines":[{"line_number":291,"context_line":""},{"line_number":292,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":293,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":294,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"* networking-odl: the core team will have to:"},{"line_number":297,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_5ee68215","line":294,"updated":"2016-05-11 02:15:55.000000000","message":"i have a question.\n\nwe need to submit a RFE for the existing extensions and associated client code.  if it\u0027s accepted, fine.  but what happens if rejected?  is it allowed to keep them as local extensions?  for compat reasons we can\u0027t drop them easily i guess.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4867f25a9b6db1ff7780ecd2896652bf5fffd9ee","unresolved":false,"context_lines":[{"line_number":291,"context_line":""},{"line_number":292,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":293,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":294,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"* networking-odl: the core team will have to:"},{"line_number":297,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_7979e0c7","line":294,"in_reply_to":"dab17558_5ee68215","updated":"2016-05-11 03:14:09.000000000","message":"Are you talking about midonet? If rejected, then the project would be taken off the list.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"e225e876380d13647f4aa75fde0887e7f03231f2","unresolved":false,"context_lines":[{"line_number":291,"context_line":""},{"line_number":292,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":293,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":294,"context_line":"  * move client side code to python-neutronclient and switch to OSC plugin;"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"* networking-odl: the core team will have to:"},{"line_number":297,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_19fed3ad","line":294,"in_reply_to":"dab17558_7979e0c7","updated":"2016-05-11 05:18:16.000000000","message":"ok.\n\nmy main concern is midonet but the question is general.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"166ab511cb33b4ed48d5444dea21a7ebe5ee037e","unresolved":false,"context_lines":[{"line_number":305,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":306,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"* networking-ovn: on top of the requirements, as mentioned for the other"},{"line_number":309,"context_line":"  projects in this list, the OVN project will need to consider switching"},{"line_number":310,"context_line":"  back to an ML2 driver. This is beneficial for the following reasons:"},{"line_number":311,"context_line":""},{"line_number":312,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_5ea2029a","line":309,"range":{"start_line":308,"start_character":46,"end_line":309,"end_character":23},"updated":"2016-05-11 02:15:55.000000000","message":"i couldn\u0027t find this mentioned for the other projects.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4867f25a9b6db1ff7780ecd2896652bf5fffd9ee","unresolved":false,"context_lines":[{"line_number":306,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"* networking-ovn: on top of the requirements, as mentioned for the other"},{"line_number":309,"context_line":"  projects in this list, the OVN project will need to consider switching"},{"line_number":310,"context_line":"  back to an ML2 driver. This is beneficial for the following reasons:"},{"line_number":311,"context_line":""},{"line_number":312,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_396bd8f2","line":309,"in_reply_to":"dab17558_5ea2029a","updated":"2016-05-11 03:14:09.000000000","message":"I\u0027ll revise.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"166ab511cb33b4ed48d5444dea21a7ebe5ee037e","unresolved":false,"context_lines":[{"line_number":307,"context_line":""},{"line_number":308,"context_line":"* networking-ovn: on top of the requirements, as mentioned for the other"},{"line_number":309,"context_line":"  projects in this list, the OVN project will need to consider switching"},{"line_number":310,"context_line":"  back to an ML2 driver. This is beneficial for the following reasons:"},{"line_number":311,"context_line":""},{"line_number":312,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":313,"context_line":"    currently only true if a hypervisor runs Open vSwitch."},{"line_number":314,"context_line":"  * present itself as a viable alternative to supplant the ovs mech_driver"},{"line_number":315,"context_line":"    in the OpenStack gate: this can only be done  so if we are swapping"},{"line_number":316,"context_line":"    like for like."},{"line_number":317,"context_line":"  * do bare-metal and virtual provisioning in the context of the same"},{"line_number":318,"context_line":"    Neutron deployment; hardware vtep support only is limiting a number"},{"line_number":319,"context_line":"    of potential bare metal scenarios that leverage third party solutions."},{"line_number":320,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":321,"context_line":"    that the Neutron team develops against ML2."},{"line_number":322,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":325,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_1eb7daf5","line":322,"range":{"start_line":310,"start_character":25,"end_line":322,"end_character":60},"updated":"2016-05-11 02:15:55.000000000","message":"i guess most of these ought to be moved out of networking-ovn section.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4867f25a9b6db1ff7780ecd2896652bf5fffd9ee","unresolved":false,"context_lines":[{"line_number":319,"context_line":"    of potential bare metal scenarios that leverage third party solutions."},{"line_number":320,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":321,"context_line":"    that the Neutron team develops against ML2."},{"line_number":322,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":325,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_f9bdd068","line":322,"in_reply_to":"dab17558_1eb7daf5","updated":"2016-05-11 03:14:09.000000000","message":"I suppose I can, but the message remains the same.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":319,"context_line":"    of potential bare metal scenarios that leverage third party solutions."},{"line_number":320,"context_line":"  * getting access to a number of performance/reliability enhancements"},{"line_number":321,"context_line":"    that the Neutron team develops against ML2."},{"line_number":322,"context_line":"  * Composability of services across the entire L2-L7 stack."},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"* networking-sfc: the core team will have to:"},{"line_number":325,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_c525dfae","line":322,"in_reply_to":"dab17558_f9bdd068","updated":"2016-05-13 17:48:47.000000000","message":"on second thought, this is very ovn specific, at least a few bullets are.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"166ab511cb33b4ed48d5444dea21a7ebe5ee037e","unresolved":false,"context_lines":[{"line_number":344,"context_line":"timeframe."},{"line_number":345,"context_line":""},{"line_number":346,"context_line":"This deadline is considered to be firm, but will be revised according to"},{"line_number":347,"context_line":"how fast we can make neutron-api and neutron-lib mature to a point of"},{"line_number":348,"context_line":"effective consumption by the `neutron \u003chttps://github.com/openstack/neutron\u003e`_"},{"line_number":349,"context_line":"project and once thorough documentation is provided to help the various"},{"line_number":350,"context_line":"parties through the transition."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_5ed042f6","line":347,"range":{"start_line":347,"start_character":21,"end_line":347,"end_character":55},"updated":"2016-05-11 02:15:55.000000000","message":"and neutron-side improvements necessary for ml2 transition?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"4867f25a9b6db1ff7780ecd2896652bf5fffd9ee","unresolved":false,"context_lines":[{"line_number":344,"context_line":"timeframe."},{"line_number":345,"context_line":""},{"line_number":346,"context_line":"This deadline is considered to be firm, but will be revised according to"},{"line_number":347,"context_line":"how fast we can make neutron-api and neutron-lib mature to a point of"},{"line_number":348,"context_line":"effective consumption by the `neutron \u003chttps://github.com/openstack/neutron\u003e`_"},{"line_number":349,"context_line":"project and once thorough documentation is provided to help the various"},{"line_number":350,"context_line":"parties through the transition."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_f964b022","line":347,"in_reply_to":"dab17558_5ed042f6","updated":"2016-05-11 03:14:09.000000000","message":"are there any you could think of that may prevent the transition in the first place?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"e225e876380d13647f4aa75fde0887e7f03231f2","unresolved":false,"context_lines":[{"line_number":344,"context_line":"timeframe."},{"line_number":345,"context_line":""},{"line_number":346,"context_line":"This deadline is considered to be firm, but will be revised according to"},{"line_number":347,"context_line":"how fast we can make neutron-api and neutron-lib mature to a point of"},{"line_number":348,"context_line":"effective consumption by the `neutron \u003chttps://github.com/openstack/neutron\u003e`_"},{"line_number":349,"context_line":"project and once thorough documentation is provided to help the various"},{"line_number":350,"context_line":"parties through the transition."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_395597c5","line":347,"in_reply_to":"dab17558_f964b022","updated":"2016-05-11 05:18:16.000000000","message":"i\u0027m not aware of anything except hardcoded supported extensions right now.\nbut i guess we will find more during transition.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":11907,"name":"cathy","email":"cathy.h.zhang@huawei.com","username":"cathy"},"change_message_id":"0dcbe141e3fb5449e08e65dbafa2f203c6b6cc9d","unresolved":false,"context_lines":[{"line_number":354,"context_line":"----------------------------------------------------------"},{"line_number":355,"context_line":""},{"line_number":356,"context_line":"There are projects currently hosted on OpenStack that are not part of the"},{"line_number":357,"context_line":"Neutron governance list, for example neutron-classifier, and there may be more"},{"line_number":358,"context_line":"that may be created in the future. Such initiatives should consider being"},{"line_number":359,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":360,"context_line":"collaboration already established across the teams involved. As mentioned"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_ace6fa13","line":357,"updated":"2016-05-12 19:59:25.000000000","message":"To add on my comments on patch set 9, I am not suggesting creating another stadium project for neutron-classifier. I am thinking this feature be developed inside Neutron as a bug fix similar to what is being done for \"openswitch Openflow pipeline extensibility\". Or are you suggesting doing this feature as a separate stadium project?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":354,"context_line":"----------------------------------------------------------"},{"line_number":355,"context_line":""},{"line_number":356,"context_line":"There are projects currently hosted on OpenStack that are not part of the"},{"line_number":357,"context_line":"Neutron governance list, for example neutron-classifier, and there may be more"},{"line_number":358,"context_line":"that may be created in the future. Such initiatives should consider being"},{"line_number":359,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":360,"context_line":"collaboration already established across the teams involved. As mentioned"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_054c0641","line":357,"in_reply_to":"dab17558_ace6fa13","updated":"2016-05-13 17:48:47.000000000","message":"It all depends on how the resulting design looks like IMO. I think about the classifier as a reusable component across different projects and thus it needed to exist on its own to guarantee a good degree of decoupling. The Openflow pipeline extensibility instead is a pluggability mechanism into the OVS agent and thus would need to be more cohesive with the OVS agent module.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"b603471f051c23930d2cc2174c59675c05e842bc","unresolved":false,"context_lines":[{"line_number":359,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":360,"context_line":"collaboration already established across the teams involved. As mentioned"},{"line_number":361,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":362,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":363,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":364,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":365,"context_line":"a formality."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_5cc04950","line":362,"updated":"2016-05-11 04:43:32.000000000","message":"typo: responsibility","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":359,"context_line":"part of the Neutron Stadium if and only if there is a mutual and beneficial"},{"line_number":360,"context_line":"collaboration already established across the teams involved. As mentioned"},{"line_number":361,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":362,"context_line":"PTL and the Neutron team take responsability for. The more involvement and"},{"line_number":363,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":364,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":365,"context_line":"a formality."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_cabb2c74","line":362,"in_reply_to":"dab17558_5cc04950","updated":"2016-05-13 17:48:47.000000000","message":"Done","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"4d6dd1f95709025b7db0db59facff577aba42c4e","unresolved":false,"context_lines":[{"line_number":381,"context_line":"* pointers to stable backports and release deliverables;"},{"line_number":382,"context_line":"* pointers to API specification and definitions;"},{"line_number":383,"context_line":""},{"line_number":384,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":385,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":386,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":387,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_3663d043","line":384,"range":{"start_line":384,"start_character":19,"end_line":384,"end_character":40},"updated":"2016-05-11 12:50:44.000000000","message":"Nit: As per my comments on patch set 9, it would be nice to clarify this statement. e.g. \"successfully approved using the standard RFE process\". When I read this it wasn\u0027t clear if there was a separate process for review+approval of stadium projects.","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":9396,"name":"igordcard","email":"igordcard@gmail.com","username":"igordcard"},"change_message_id":"957890b63c75bf9ec6270030e267809349bb8806","unresolved":false,"context_lines":[{"line_number":384,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":385,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":386,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":387,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"},{"line_number":388,"context_line":"spec submission to neutron-specs where deemed necessary from that point"},{"line_number":389,"context_line":"forward."},{"line_number":390,"context_line":""},{"line_number":391,"context_line":""},{"line_number":392,"context_line":"Why is this Stadium arrangement beneficial?"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_b89b3865","line":389,"range":{"start_line":387,"start_character":71,"end_line":389,"end_character":8},"updated":"2016-05-11 09:23:15.000000000","message":"Does this also mean that no specs submitted internally to the Neutron Stadium projects are allowed?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"58a5f04a2b260ac36cdb43b7840081b204476f1c","unresolved":false,"context_lines":[{"line_number":384,"context_line":"Once evaluated and successfully approved, the teams will work together to"},{"line_number":385,"context_line":"transition API and client components respectively in the  neutron-api and"},{"line_number":386,"context_line":"python-neutronclient repos. The newly added project pledge to adopt the"},{"line_number":387,"context_line":"Neutron RFE submission process for API changes (and API changes alone) and"},{"line_number":388,"context_line":"spec submission to neutron-specs where deemed necessary from that point"},{"line_number":389,"context_line":"forward."},{"line_number":390,"context_line":""},{"line_number":391,"context_line":""},{"line_number":392,"context_line":"Why is this Stadium arrangement beneficial?"}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_25682b21","line":389,"range":{"start_line":387,"start_character":71,"end_line":389,"end_character":8},"in_reply_to":"dab17558_b89b3865","updated":"2016-05-13 17:48:47.000000000","message":"not sure what you mean by \u0027submitted internally to Neutron\u0027. Can you elaborate?","commit_id":"a91449bce74e114906d0e500737870ba6ac9b2a7"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":38,"context_line":"PTL/drivers team of ensuring consistency in the APIs, architecture, design,"},{"line_number":39,"context_line":"implementation and testing of the project, as well as a level of quality in"},{"line_number":40,"context_line":"all aspects, like documentation, inter-project communication, release"},{"line_number":41,"context_line":"management, stable backports etc are dealt with have become harder and harder."},{"line_number":42,"context_line":"The point about uniform APIs is particularly important, because the Neutron"},{"line_number":43,"context_line":"platform is so flexible that a project can take a totally different turn in"},{"line_number":44,"context_line":"the way it exposes functionality, that it is virtually impossible for the"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_95b062df","line":41,"range":{"start_line":41,"start_character":29,"end_line":41,"end_character":32},"updated":"2016-05-19 14:13:30.000000000","message":"super-nit: , etc,","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":39,"context_line":"implementation and testing of the project, as well as a level of quality in"},{"line_number":40,"context_line":"all aspects, like documentation, inter-project communication, release"},{"line_number":41,"context_line":"management, stable backports etc are dealt with have become harder and harder."},{"line_number":42,"context_line":"The point about uniform APIs is particularly important, because the Neutron"},{"line_number":43,"context_line":"platform is so flexible that a project can take a totally different turn in"},{"line_number":44,"context_line":"the way it exposes functionality, that it is virtually impossible for the"},{"line_number":45,"context_line":"PTL and the drivers team to ensure that good API design principles are being"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_550be5d5","line":42,"updated":"2016-06-01 15:59:35.000000000","message":"Perhaps insert \"For the networking-* projects that extend the Neutron API, \" at the start of this sentence.  Because I would guess that a large fraction of the networking-* projects are just backend implementations that implement the current Neutron API and do not introduce any extensions of their own.\n\n(At least this is true for networking-calico; I admit that I haven\u0027t recently checked for any others.)\n\nIf that is true, it seems strange to be making a point here that doesn\u0027t apply to a large fraction of the problem space; and my suggested qualification would address that.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aa8fa37fc2ce5165a4aeb280eef19634bbf5d8b7","unresolved":false,"context_lines":[{"line_number":39,"context_line":"implementation and testing of the project, as well as a level of quality in"},{"line_number":40,"context_line":"all aspects, like documentation, inter-project communication, release"},{"line_number":41,"context_line":"management, stable backports etc are dealt with have become harder and harder."},{"line_number":42,"context_line":"The point about uniform APIs is particularly important, because the Neutron"},{"line_number":43,"context_line":"platform is so flexible that a project can take a totally different turn in"},{"line_number":44,"context_line":"the way it exposes functionality, that it is virtually impossible for the"},{"line_number":45,"context_line":"PTL and the drivers team to ensure that good API design principles are being"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_4b6df4ca","line":42,"in_reply_to":"9abb7d3a_550be5d5","updated":"2016-06-01 21:29:41.000000000","message":"Point is valid, and even though I am not sure about the actual breakdown, I\u0027d expect the ones that stick to core APIs to be the minority or roughly half of it. Either way, the message I am trying to get across won\u0027t change even with the preamble. If I must, I\u0027ll respin :)","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":65,"context_line":"The list includes projects that the Neutron PTL and core team are directly"},{"line_number":66,"context_line":"involved in, and manage on a day to day basis. To do so, the PTL and team"},{"line_number":67,"context_line":"ensure that common practices and guidelines are followed throughout the Stadium,"},{"line_number":68,"context_line":"for all aspects that pertain software development, from inception, to coding,"},{"line_number":69,"context_line":"testing, documentation and more."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"The Stadium is not to be intended as a VIP club for OpenStack networking"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_35f101ce","line":68,"updated":"2016-06-01 15:59:35.000000000","message":"Nit: s/pertain/pertain to/","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":87,"context_line":"projects and should not be perceived as particularly stringent:"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":" * exhaustive documentation: it is expected that each project will have a"},{"line_number":90,"context_line":"   developer, user/operator and API guide, reachable from docs.o.o;"},{"line_number":91,"context_line":" * exhaustive OpenStack CI coverage (unit, functional, tempest), using"},{"line_number":92,"context_line":"   OpenStack CI (upstream) resources (this means using infra CI, not just"},{"line_number":93,"context_line":"   downstream CI, as Grafana support will be required); access to CI"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_d57caa22","line":90,"range":{"start_line":90,"start_character":58,"end_line":90,"end_character":66},"updated":"2016-05-19 14:13:30.000000000","message":"nit: docs.openstack.org just to make it clear, even if it was to me","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"e00d9bf953608b960d82f8c7e1097c9cb519f4d6","unresolved":false,"context_lines":[{"line_number":109,"context_line":"   release on pypi (like fw, vpn or lb) thus it is difficult to get hold of"},{"line_number":110,"context_line":"   client extensions where they need to be used. SFC and L2GW, for example,"},{"line_number":111,"context_line":"   do release on pypi so that is not so much a problem for them. In theory"},{"line_number":112,"context_line":"   their client extensions can stay colocated within their tree but that"},{"line_number":113,"context_line":"   would make more difficult the alignment to the OSC plugin model. Since"},{"line_number":114,"context_line":"   the recommendation is to keep extensions in the python-neutronclient"},{"line_number":115,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_3d7366b3","line":112,"range":{"start_line":112,"start_character":36,"end_line":112,"end_character":45},"updated":"2016-05-18 12:35:57.000000000","message":"collocated","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"0d26e999c289b4b2eff1981b90de83b5a5a3e384","unresolved":false,"context_lines":[{"line_number":109,"context_line":"   release on pypi (like fw, vpn or lb) thus it is difficult to get hold of"},{"line_number":110,"context_line":"   client extensions where they need to be used. SFC and L2GW, for example,"},{"line_number":111,"context_line":"   do release on pypi so that is not so much a problem for them. In theory"},{"line_number":112,"context_line":"   their client extensions can stay colocated within their tree but that"},{"line_number":113,"context_line":"   would make more difficult the alignment to the OSC plugin model. Since"},{"line_number":114,"context_line":"   the recommendation is to keep extensions in the python-neutronclient"},{"line_number":115,"context_line":"   tree, it is beneficial to have a consistent approach where all Stadium"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_5a54f21f","line":112,"range":{"start_line":112,"start_character":36,"end_line":112,"end_character":45},"in_reply_to":"bab6814e_3d7366b3","updated":"2016-05-31 14:58:11.000000000","message":"I believe either is valid: http://grammarist.com/spelling/collocate-vs-colocate/","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"e3b3b6367ae34842d88abf1a65f5db8d22612f8c","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_d8ac06a1","line":120,"updated":"2016-06-02 06:57:39.000000000","message":"Can the sub-projects have their own spec repo? I can find a proposal from networking-odl for the same ----https://review.openstack.org/#/c/324052","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5dfa302ba694c2aad7392132c536b709e2f2f3d4","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_329b1a74","line":120,"in_reply_to":"7aa08908_08226d01","updated":"2016-06-07 19:41:32.000000000","message":"each stadium project may or may not have a launchpad site used to track issues and/or features. The devref held in the project repo can contain design documents and the subteam may choose the depth of content as they see fit.\n\nHowever, should a change pertain end-user facing issues that affect the API or the way the system works with other components of the Neutron platform or others, the RFE submission should be passed through the Neutron RFE process so that wider scrutiny is ensured. The outcome of the RFE process may be determined depending on the issue, it may be a spec in neutron-specs, a devref, or any other advice as determined once the RFE is assessed.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"6086f158798471f9d9a5aad0de7aba02c32562c0","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_f74e8e6d","line":120,"in_reply_to":"7aa08908_329b1a74","updated":"2016-06-08 06:39:20.000000000","message":"Thanks for the clarification Armando.. I feel a word about this will be better.. I also had the same perception as Amotoki so raised this query..","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"196d2ab297deaae5f2d02817a3a523fccaf0785c","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_7f66db2a","line":120,"in_reply_to":"7aa08908_f74e8e6d","updated":"2016-06-08 12:33:17.000000000","message":"it\u0027ll never be enough....let\u0027s write a constitution...","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"15e17a0b479e0f7eb75e0df6c8f90b768f5955ed","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_fe10cd5b","line":120,"in_reply_to":"9abb7d3a_d8ac06a1","updated":"2016-06-06 22:40:52.000000000","message":"My understanding is that sub-projects which want to be in the stadium must follow the process. They don\u0027t need to create a separate repo for spec.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":333,"name":"Isaku Yamahata","email":"isaku.yamahata@gmail.com","username":"yamahata"},"change_message_id":"1e5e84d294c6edf86939db0da7ca0b3a045d5857","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_da7f8f64","line":120,"in_reply_to":"9abb7d3a_d8ac06a1","updated":"2016-06-06 22:25:43.000000000","message":"Vikram, I\u0027m afraid you misunderstood it.\n\nnetworking-odl spec is intended to track networking-odl specific tasks which isn\u0027t suitable for core neutron.\nFor example, v2 driver journaling and its jorunal recovery.\n\nneutron API or common neutron stuff should go to neutron spec.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":333,"name":"Isaku Yamahata","email":"isaku.yamahata@gmail.com","username":"yamahata"},"change_message_id":"70fc16c9776cb59ac51bd9cd2c844dc8b3b399e0","unresolved":false,"context_lines":[{"line_number":117,"context_line":"   confusion when dealing with exceptions to the rule;"},{"line_number":118,"context_line":" * adoption of neutron-api: submission of any API change must follow the"},{"line_number":119,"context_line":"   Neutron `RFE submission process \u003chttp://docs.openstack.org/developer/neutron/policies/blueprints.html\u003e`_,"},{"line_number":120,"context_line":"   where specifications to neutron-specs may be required;"},{"line_number":121,"context_line":" * adoption of modular interfaces to provide networking services: this means"},{"line_number":122,"context_line":"   that L2/7 services are provided in the form of ML2 mech drivers and"},{"line_number":123,"context_line":"   service plugins respectively. A service plugin can expose a driver"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_08226d01","line":120,"in_reply_to":"9abb7d3a_fe10cd5b","updated":"2016-06-06 23:51:51.000000000","message":"For example, should the followings be reviewed/stored in neutron-spec?\n\n - https://review.openstack.org/#/c/325836/2/doc/source/specs/journal-recovery.rst\n - https://review.openstack.org/#/c/324052/1/doc/source/specs/newton/sfc-driver.rst\n\n\nThey are very specific to networking-odl internals.\n\nIf yes, who is responsible for reviewing/approving it?\n\nIf no, probably the different terminology other than spec should be used in order to avoid confusion.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":136,"context_line":"   to provide end-to-end solutions, the criterion to enforce the adoption"},{"line_number":137,"context_line":"   of ML2 and service plugins for Neutron Stadium projects does not invalidate,"},{"line_number":138,"context_line":"   nor does make monolithic solutions deprecated. It is simply a reflection of the"},{"line_number":139,"context_line":"   fact that the Neutron team stands behind composability as one of the promise of"},{"line_number":140,"context_line":"   open networking solutions. During code review the Neutron team will continue"},{"line_number":141,"context_line":"   to ensure that changes and design implications do not have a negative impact"},{"line_number":142,"context_line":"   on out of tree code irrespective of whether it is part of the Stadium project"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_d554aa55","line":139,"range":{"start_line":139,"start_character":72,"end_line":139,"end_character":79},"updated":"2016-05-19 14:13:30.000000000","message":"nit: promises","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":149,"context_line":"the PTL and Neutron team do release planning, and have the most time available"},{"line_number":150,"context_line":"to discuss governance issues."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Projects part of the Neutron Stadium have typically the first milestone to get"},{"line_number":153,"context_line":"their house in order, during which time reassessment happens; once removed, a"},{"line_number":154,"context_line":"project cannot reapply within the same release cycle it has been evicted."},{"line_number":155,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_c0486a30","line":152,"range":{"start_line":152,"start_character":51,"end_line":152,"end_character":52},"updated":"2016-05-19 14:13:30.000000000","message":"nit: until","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":162,"context_line":"openstack.org namespace, as outlined in the `creator guide \u003chttp://docs.openstack.org/infra/manual/creators.html\u003e`_."},{"line_number":163,"context_line":"Furthermore, projects that interact with Neutron purely via its REST API should"},{"line_number":164,"context_line":"also be incentivized to seek other forms of governance, such as applying as"},{"line_number":165,"context_line":"top-level OpenStack project and follow the new project requirements as outlined"},{"line_number":166,"context_line":"by the `OpenStack Governance \u003chttp://governance.openstack.org/reference/new-projects-requirements.html\u003e`_,"},{"line_number":167,"context_line":"rather than going for Stadium inclusion."},{"line_number":168,"context_line":"Drivers that leverage proprietary software and/or hardware will also not be"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_3593c1fb","line":165,"updated":"2016-06-01 15:59:35.000000000","message":"nits: s/top-level/a top-level/\ns/follow/following/","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"22888d02b39855dc5c59f55e7d6083d7113447c7","unresolved":false,"context_lines":[{"line_number":189,"context_line":"------------------------------------------------------------------------------------------------"},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Today\u0027s reality is that some Neutron projects still host drivers to proprietary"},{"line_number":192,"context_line":"systems, like vpnaas, fwaas, and lbaas/octavia; even though the decision of accepting"},{"line_number":193,"context_line":"new drivers lies with the respective teams, it is strongly encouraged that these be"},{"line_number":194,"context_line":"exceptions rather than the norm. This point becomes less relevant if, in the long run"},{"line_number":195,"context_line":"some of these efforts will no longer be considered responsibility of the Neutron team."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_a81b391b","line":192,"range":{"start_line":192,"start_character":39,"end_line":192,"end_character":46},"updated":"2016-05-14 21:49:55.000000000","message":"Octavia does not host proprietary drivers today.  Only lbaas.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":6995,"name":"Sridar Kandaswamy","email":"skandasw@yahoo.com","username":"skandasw"},"change_message_id":"5edb4abe55d476f82abc956baf0fc88078952e20","unresolved":false,"context_lines":[{"line_number":189,"context_line":"------------------------------------------------------------------------------------------------"},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Today\u0027s reality is that some Neutron projects still host drivers to proprietary"},{"line_number":192,"context_line":"systems, like vpnaas, fwaas, and lbaas/octavia; even though the decision of accepting"},{"line_number":193,"context_line":"new drivers lies with the respective teams, it is strongly encouraged that these be"},{"line_number":194,"context_line":"exceptions rather than the norm. This point becomes less relevant if, in the long run"},{"line_number":195,"context_line":"some of these efforts will no longer be considered responsibility of the Neutron team."}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_28654d1d","line":192,"range":{"start_line":192,"start_character":22,"end_line":192,"end_character":27},"updated":"2016-05-20 21:33:53.000000000","message":"On fwaas, vendors will remove their drivers by Newton-2. They can be hosted on vendor repos.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"cfc1d51391cf73f8a70dfe8817c6ff3aeeda697a","unresolved":false,"context_lines":[{"line_number":189,"context_line":"------------------------------------------------------------------------------------------------"},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Today\u0027s reality is that some Neutron projects still host drivers to proprietary"},{"line_number":192,"context_line":"systems, like vpnaas, fwaas, and lbaas/octavia; even though the decision of accepting"},{"line_number":193,"context_line":"new drivers lies with the respective teams, it is strongly encouraged that these be"},{"line_number":194,"context_line":"exceptions rather than the norm. This point becomes less relevant if, in the long run"},{"line_number":195,"context_line":"some of these efforts will no longer be considered responsibility of the Neutron team."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_6df63e90","line":192,"range":{"start_line":192,"start_character":39,"end_line":192,"end_character":46},"in_reply_to":"dab17558_a81b391b","updated":"2016-05-16 23:00:17.000000000","message":"agreed, though that\u0027s expect to change, isn\u0027t it?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":192,"context_line":"systems, like vpnaas, fwaas, and lbaas/octavia; even though the decision of accepting"},{"line_number":193,"context_line":"new drivers lies with the respective teams, it is strongly encouraged that these be"},{"line_number":194,"context_line":"exceptions rather than the norm. This point becomes less relevant if, in the long run"},{"line_number":195,"context_line":"some of these efforts will no longer be considered responsibility of the Neutron team."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"How do we build a Networking Community?"},{"line_number":198,"context_line":"---------------------------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_c679a231","line":195,"range":{"start_line":195,"start_character":50,"end_line":195,"end_character":51},"updated":"2016-05-19 14:13:30.000000000","message":"nit: the","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":7776,"name":"Paul Carver","email":"pcarver@att.com","username":"pcarver"},"change_message_id":"3fd3d30881854e3c98d991bea8895e89f0e5323f","unresolved":false,"context_lines":[{"line_number":202,"context_line":"are proposed and agreed on. There have been deadlocks and stalemates as"},{"line_number":203,"context_line":"in any other project, and one way to resolve these stalemates is to"},{"line_number":204,"context_line":"allow individual initiatives to experiment in isolation: ultimately code"},{"line_number":205,"context_line":"wins. Even though this might seem okay at first, Neutron still lack the"},{"line_number":206,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":207,"context_line":"fashion."},{"line_number":208,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_b0929b49","line":205,"range":{"start_line":205,"start_character":63,"end_line":205,"end_character":67},"updated":"2016-05-19 12:52:27.000000000","message":"lack -\u003e lacks","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":202,"context_line":"are proposed and agreed on. There have been deadlocks and stalemates as"},{"line_number":203,"context_line":"in any other project, and one way to resolve these stalemates is to"},{"line_number":204,"context_line":"allow individual initiatives to experiment in isolation: ultimately code"},{"line_number":205,"context_line":"wins. Even though this might seem okay at first, Neutron still lack the"},{"line_number":206,"context_line":"ability to reconcile all these initiatives back together in a coherent"},{"line_number":207,"context_line":"fashion."},{"line_number":208,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_0149d45f","line":205,"range":{"start_line":205,"start_character":63,"end_line":205,"end_character":67},"updated":"2016-05-19 14:13:30.000000000","message":"nit: lacks","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":229,"context_line":"landing end-to-end code changes."},{"line_number":230,"context_line":""},{"line_number":231,"context_line":"The reason behind the existence of this effort and the requirement to go"},{"line_number":232,"context_line":"through neutron-specs for API proposals is two-fold: a) ensure continuous"},{"line_number":233,"context_line":"alignment across all APIs exposed from Neutron Stadium projects; b) provide"},{"line_number":234,"context_line":"a place in the OpenStack networking community to discuss and achieve consensus"},{"line_number":235,"context_line":"on networking abstractions; and c) as a robust foundation to build"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_d82141a1","line":232,"range":{"start_line":232,"start_character":43,"end_line":232,"end_character":46},"updated":"2016-05-19 14:13:30.000000000","message":"three ?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":261,"context_line":"  an OpenStack top-level project."},{"line_number":262,"context_line":""},{"line_number":263,"context_line":"* neutron-vpnaas: this project has seen the least amount of traction during"},{"line_number":264,"context_line":"  the last few `cycle \u003chttp://docs.openstack.org/releasenotes/neutron-vpnaas/mitaka.html\u003e`_."},{"line_number":265,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":266,"context_line":"  will have to:"},{"line_number":267,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_783bf59c","line":264,"range":{"start_line":264,"start_character":16,"end_line":264,"end_character":21},"updated":"2016-05-19 14:13:30.000000000","message":"nit: cycles","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":262,"context_line":""},{"line_number":263,"context_line":"* neutron-vpnaas: this project has seen the least amount of traction during"},{"line_number":264,"context_line":"  the last few `cycle \u003chttp://docs.openstack.org/releasenotes/neutron-vpnaas/mitaka.html\u003e`_."},{"line_number":265,"context_line":"  Testing and documentation is not adequate therefore the vpnaas core team"},{"line_number":266,"context_line":"  will have to:"},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_d8cb01a4","line":265,"range":{"start_line":265,"start_character":28,"end_line":265,"end_character":30},"updated":"2016-05-19 14:13:30.000000000","message":"nit: are","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":270,"context_line":"  * switch to OSC plugin;"},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"* neutron-dynamic-routing: this is a spinout of BGP code that landed"},{"line_number":273,"context_line":"  in the Mitaka timeframe. Currently in progress."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* networking-l2gw: this needs to:"},{"line_number":276,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_78d77523","line":273,"range":{"start_line":273,"start_character":48,"end_line":273,"end_character":49},"updated":"2016-05-19 14:13:30.000000000","message":";","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"9770b685dc821d9a8082741b7a21e4016b75a03d","unresolved":false,"context_lines":[{"line_number":283,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":284,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":285,"context_line":""},{"line_number":286,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":287,"context_line":""},{"line_number":288,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":289,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_fce7c63d","line":286,"updated":"2016-05-15 00:04:54.000000000","message":"unrelated but why is this project not folded into the networking-dynamic-routing?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"cfc1d51391cf73f8a70dfe8817c6ff3aeeda697a","unresolved":false,"context_lines":[{"line_number":283,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":284,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":285,"context_line":""},{"line_number":286,"context_line":"* networking-bgpvpn: the core team will have to:"},{"line_number":287,"context_line":""},{"line_number":288,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":289,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_6d3d9e2a","line":286,"in_reply_to":"dab17558_fce7c63d","updated":"2016-05-16 23:00:17.000000000","message":"if it\u0027s unrelated I am not gonna answer here :)\n\nIn all seriousness I think the answer was already given to the ML at some point. These tackle two different use cases and were born out of two different situations.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":291,"context_line":""},{"line_number":292,"context_line":"* networking-calico: the core team will have to:"},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_a88118fd","line":294,"updated":"2016-06-01 15:59:35.000000000","message":"Does neutron-api apply, if networking-calico doesn\u0027t propose any API extensions beyond Neutron core?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aa8fa37fc2ce5165a4aeb280eef19634bbf5d8b7","unresolved":false,"context_lines":[{"line_number":291,"context_line":""},{"line_number":292,"context_line":"* networking-calico: the core team will have to:"},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_cb61e4d4","line":294,"in_reply_to":"9abb7d3a_a88118fd","updated":"2016-06-01 21:29:41.000000000","message":"no, for anything new you have in the making it would though.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":292,"context_line":"* networking-calico: the core team will have to:"},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":298,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_c8245c0e","line":295,"updated":"2016-06-01 15:59:35.000000000","message":"Otherwise agreed.  In addition I think we would need to work with core Neutron to address the issue that currently motivates us sometimes to run as a core plugin.  Namely, that if there are multiple ML2 mechanism drivers, how is it possible to sometimes use one kind of implementation of L3 services - such as floating IPs - and sometimes another, depending on which mechanism driver has been used on each host?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aa8fa37fc2ce5165a4aeb280eef19634bbf5d8b7","unresolved":false,"context_lines":[{"line_number":292,"context_line":"* networking-calico: the core team will have to:"},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":298,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_2b7eb069","line":295,"in_reply_to":"9abb7d3a_c8245c0e","updated":"2016-06-01 21:29:41.000000000","message":"this is an interesting use case, perhaps to be elaborate further to better understand what you\u0027re after. My hope is that if we all focus in one area of development we can increase efforts and yield higher benefits for everybody","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":298,"context_line":""},{"line_number":299,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_6b98ca1c","line":296,"updated":"2016-06-01 15:59:35.000000000","message":"Another relevant question, I think, is whether the Neutron core team _wants_ to have more involvement in particular networking-* projects.  Obviously the answer will depend on the composition of the Neutron core team at any time - but that is a team that evolves relatively slowly, so I think it could be useful to have an indication on that point from the current team.\n\nFor networking-calico, I guess that you might - because the routed networks spec has just been merged, and networking-calico is currently (AFAIK) the only available driver that implements some of the concepts of that spec in software.\n\nIt would make a practical difference, to me and my team, to know that, because continuing proactive interest from the core Neutron team is likely to be a great help in achieving the points noted above.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aa8fa37fc2ce5165a4aeb280eef19634bbf5d8b7","unresolved":false,"context_lines":[{"line_number":293,"context_line":""},{"line_number":294,"context_line":"  * adopt neutron-api, and neutron-lib;"},{"line_number":295,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":296,"context_line":""},{"line_number":297,"context_line":"* networking-midonet: the core team will have to:"},{"line_number":298,"context_line":""},{"line_number":299,"context_line":"  * adopt neutron-api, and neutron-lib;"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_ebbb08c2","line":296,"in_reply_to":"9abb7d3a_6b98ca1c","updated":"2016-06-01 21:29:41.000000000","message":"Another good point. I think that involvement of an individual in multiple projects can happen in two ways:\n\na) developer from project networking-xxx starts being heavily involved with neutron and other areas of the stadium (neutron-lib, python-neutronclient, etc). He/she does so much good work that the he/she becomes core for neutron (or the specific area of involvement). The virtuous circle continues from there.\n\nb) a developer from project neutron becomes more interested in project networking-xxx, he/she starts being heavily involved. He/she does so much good work that the he/she becomes core for project networking-xxx. The virtuous circle continues from there.\n\nEither way, I don\u0027t think we\u0027re in the position we can codify or be explicit that the Neutron team wants to have more involvement. That something that happens \u0027naturally\u0027.\n\nMy objective here is to bring down barriers caused by projects being different in the way they tackle the areas I have identified above (testing, docs, etc). Once the barriers are down, it should be easier to foster collaboration.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c7bc6b27f97425987f0fab4a6be402a6eea7be09","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_8e3773af","line":316,"updated":"2016-05-13 18:58:46.000000000","message":"This is being done here [1]. I give that a 50/50 chance of merging before this stadium patch does, in which case we can just update this document.\n\n[1] https://review.openstack.org/#/c/312705/","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"aa8fa37fc2ce5165a4aeb280eef19634bbf5d8b7","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_8b423cac","line":316,"in_reply_to":"9abb7d3a_6b50ca0b","updated":"2016-06-01 21:29:41.000000000","message":"With ML2 two backends may coexist and based on the nature of the ML2 driver they may either be able to control the same fabric (e.g. ovs and l2pop or sriov) or disjoint fabric (e.g. ovs and odl). Migration is a wild beast, worth considering if there\u0027s an interest, but it goes beyond this proposal.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":8410,"name":"Richard Theis","email":"rtheis@us.ibm.com","username":"rtheis"},"change_message_id":"ede6a4e8acb86db5058fa5716346215306df2f71","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_03b0dcdc","line":316,"in_reply_to":"9abb7d3a_8b423cac","updated":"2016-06-04 10:12:53.000000000","message":"The conversion to ML2 just merged: https://review.openstack.org/#/c/318095/","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"6522f6e95c28863b21965aa5f7d6884a7cb8d30a","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_a3a645a8","line":316,"in_reply_to":"dab17558_660761ca","updated":"2016-05-17 18:03:01.000000000","message":"We could for sure, but I think the ML2 approach makes more sense here.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"9770b685dc821d9a8082741b7a21e4016b75a03d","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_9cd83a81","line":316,"in_reply_to":"dab17558_8e3773af","updated":"2016-05-15 00:04:54.000000000","message":"i find it kind of clunky that the OVN supports ML2 just to be in the stadium. The better model for it is a monolithic plugin.\nWill OVN have gating on both drivers?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"7a7e5280f4999b6b951334af6c84d3f7f857e36a","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_a2efb185","line":316,"in_reply_to":"dab17558_9cd83a81","updated":"2016-05-16 13:27:06.000000000","message":"It\u0027s not supporting ML2 only be in the stadium, though clearly that has some benefits. The main reason to convert is that there is no migration path way from the python agents to OVN if it\u0027s a core plugin. As an ML2 driver, you can see a clear path to migrate agent implementations to OVN. You can also see it being tested in the gate easier as well.\n\nAnd no, we don\u0027t plan to support both models, that seems like a lot of work. It\u0027s something we could do though, Russell and I have talked about it.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"6d73ef06e17e1dd35036dd89a7351523b5ae1fc2","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_660761ca","line":316,"in_reply_to":"dab17558_a2efb185","updated":"2016-05-17 12:18:55.000000000","message":"if the migration path is the motivation then we can consider something that Aaron is working on - that is a way of migrating from one plugin to another. Its called an API replayer.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"ed2ab7cfce5156c82303cb6bdbdf7f06d2feef10","unresolved":false,"context_lines":[{"line_number":313,"context_line":"  * complete docs, end-to-end testing, and demonstrate ability to upgrade;"},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"* networking-ovn: the OVN project will need to consider switching back to"},{"line_number":316,"context_line":"  an ML2 driver. This is beneficial for the following reasons:"},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * considered as a solution for multi-hypervisor deployments: this is"},{"line_number":319,"context_line":"    currently only true if a hypervisor runs Open vSwitch."}],"source_content_type":"text/x-rst","patch_set":12,"id":"9abb7d3a_6b50ca0b","line":316,"in_reply_to":"dab17558_a3a645a8","updated":"2016-06-01 15:59:35.000000000","message":"FWIW my general impression - although not yet fully informed - is that ML2 supports multiple networking implementations in terms of common code paths and internal APIs, but not yet really in terms of multiple networking implementations working at the same time alongside each other - including migration scenarios such as this, but also intentionally hybrid deployments.\n\nIf that\u0027s right, it would certainly be valuable for us all to take that on, but it could be a lot of work.","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"e00d9bf953608b960d82f8c7e1097c9cb519f4d6","unresolved":false,"context_lines":[{"line_number":351,"context_line":"These projects and their respective core teams will be given time to comply"},{"line_number":352,"context_line":"until Ocata Milestone-1, after which, if not compliant, they will be removed"},{"line_number":353,"context_line":"from the Neutron Stadium. All things considered, a team can decide not to"},{"line_number":354,"context_line":"adopt the aforementioned plan and ask to be removed during the Netwon"},{"line_number":355,"context_line":"timeframe."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"This deadline is considered to be firm, but will be revised according to"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_3d5fe673","line":354,"range":{"start_line":354,"start_character":63,"end_line":354,"end_character":69},"updated":"2016-05-18 12:35:57.000000000","message":"Newton","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"371cb900670a7ee41be50e9ea573f04f6b6285b0","unresolved":false,"context_lines":[{"line_number":371,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":372,"context_line":"PTL and the Neutron team take responsibility for. The more involvement and"},{"line_number":373,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":374,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":375,"context_line":"a formality."},{"line_number":376,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":377,"context_line":"make sure that these criteria are met:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_e4870eb3","line":374,"range":{"start_line":374,"start_character":54,"end_line":374,"end_character":58},"updated":"2016-05-16 11:30:52.000000000","message":"a","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"e00d9bf953608b960d82f8c7e1097c9cb519f4d6","unresolved":false,"context_lines":[{"line_number":371,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":372,"context_line":"PTL and the Neutron team take responsibility for. The more involvement and"},{"line_number":373,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":374,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":375,"context_line":"a formality."},{"line_number":376,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":377,"context_line":"make sure that these criteria are met:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_bd73d64c","line":374,"range":{"start_line":374,"start_character":8,"end_line":374,"end_character":18},"updated":"2016-05-18 12:35:57.000000000","message":"alignment","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"cfc1d51391cf73f8a70dfe8817c6ff3aeeda697a","unresolved":false,"context_lines":[{"line_number":371,"context_line":"above, the Stadium is not an elite club but simply the projects that the"},{"line_number":372,"context_line":"PTL and the Neutron team take responsibility for. The more involvement and"},{"line_number":373,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":374,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":375,"context_line":"a formality."},{"line_number":376,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":377,"context_line":"make sure that these criteria are met:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_cd464abf","line":374,"range":{"start_line":374,"start_character":54,"end_line":374,"end_character":58},"in_reply_to":"dab17558_e4870eb3","updated":"2016-05-16 23:00:17.000000000","message":"well spotted!","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":372,"context_line":"PTL and the Neutron team take responsibility for. The more involvement and"},{"line_number":373,"context_line":"mutual collaboration exist over time, the more likely it is that there"},{"line_number":374,"context_line":"is good alignement and thus Stadium inclusion becomes a a little more than"},{"line_number":375,"context_line":"a formality."},{"line_number":376,"context_line":"In order to succeed in an application, a project should first and foremost"},{"line_number":377,"context_line":"make sure that these criteria are met:"},{"line_number":378,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_38468dbf","line":375,"updated":"2016-05-19 14:13:30.000000000","message":"blank line","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":9396,"name":"igordcard","email":"igordcard@gmail.com","username":"igordcard"},"change_message_id":"2b8f24785a47296fcee29f8f1e03eec459238a01","unresolved":false,"context_lines":[{"line_number":395,"context_line":"together to transition API and client components respectively to api module"},{"line_number":396,"context_line":"and python-neutronclient repos. The newly added project pledge to"},{"line_number":397,"context_line":"adopt the Neutron RFE submission process for API changes (and API changes"},{"line_number":398,"context_line":"alone) and spec submission to neutron-specs where deemed necessary from that"},{"line_number":399,"context_line":"point forward."},{"line_number":400,"context_line":""},{"line_number":401,"context_line":"Why is this Stadium arrangement beneficial?"},{"line_number":402,"context_line":"-------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_2b9bbeca","line":399,"range":{"start_line":398,"start_character":10,"end_line":399,"end_character":14},"updated":"2016-05-15 10:46:34.000000000","message":"Igor Duarte Cardoso\n05-11 10:23\nDoes this also mean that no specs submitted internally to the Neutron Stadium projects are allowed?\n\nArmando Migliaccio\n05-13 18:48\nnot sure what you mean by \u0027submitted internally to Neutron\u0027. Can you elaborate?\n\n--\nI mean, in 2 cycles time, when a Neutron Stadium project wants to develop a new feature with such dimensions or context that would justify creating a spec - does the spec always go to neutron-specs? And how does that differ when there are or aren\u0027t API changes?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"cfc1d51391cf73f8a70dfe8817c6ff3aeeda697a","unresolved":false,"context_lines":[{"line_number":395,"context_line":"together to transition API and client components respectively to api module"},{"line_number":396,"context_line":"and python-neutronclient repos. The newly added project pledge to"},{"line_number":397,"context_line":"adopt the Neutron RFE submission process for API changes (and API changes"},{"line_number":398,"context_line":"alone) and spec submission to neutron-specs where deemed necessary from that"},{"line_number":399,"context_line":"point forward."},{"line_number":400,"context_line":""},{"line_number":401,"context_line":"Why is this Stadium arrangement beneficial?"},{"line_number":402,"context_line":"-------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_cda76a4e","line":399,"range":{"start_line":398,"start_character":10,"end_line":399,"end_character":14},"in_reply_to":"dab17558_2b9bbeca","updated":"2016-05-16 23:00:17.000000000","message":"yes","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":405,"context_line":"and iterate on networking solutions, and provides a degree of guarantee that"},{"line_number":406,"context_line":"a project belonging to the Stadium behaves similarly to any other project"},{"line_number":407,"context_line":"within the Stadium, thus inducing a more sustainable maintenance effort on"},{"line_number":408,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsibility of"},{"line_number":409,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":410,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":411,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_7899351f","line":408,"range":{"start_line":408,"start_character":18,"end_line":408,"end_character":35},"updated":"2016-05-19 14:13:30.000000000","message":"Additionally ?","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"b5515200e85439055c112b15aace757628867b24","unresolved":false,"context_lines":[{"line_number":407,"context_line":"within the Stadium, thus inducing a more sustainable maintenance effort on"},{"line_number":408,"context_line":"the Neutron team. On the other hand, the Neutron team takes responsibility of"},{"line_number":409,"context_line":"the deliverables produced by Stadium project (docs, release notes, etc), and"},{"line_number":410,"context_line":"therefore giving these initiatives higher visibility to downstream consumers."},{"line_number":411,"context_line":"Contributors of Neutron Stadium projects participate in the Neutron PTL election"},{"line_number":412,"context_line":"process and have the same status of any other OpenStack Active Technical"},{"line_number":413,"context_line":"Contributor."}],"source_content_type":"text/x-rst","patch_set":12,"id":"bab6814e_18046948","line":410,"range":{"start_line":410,"start_character":10,"end_line":410,"end_character":16},"updated":"2016-05-19 14:13:30.000000000","message":"gives","commit_id":"ae1c7893a18ebe15d814680e35e4b7f8ea91cefa"}]}