)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Parent:     7e905651 (Merge \"Remove test_list_servers_by_limits\")"},{"line_number":2,"context_line":"Author:     Mark T. Voelker \u003cmvoelker@vmware.com\u003e"},{"line_number":3,"context_line":"AuthorDate: 2017-06-09 14:26:39 -0400"},{"line_number":4,"context_line":"Commit:     Mark T. Voelker \u003cmvoelker@vmware.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"5f2577a7_67bb2972","line":1,"range":{"start_line":1,"start_character":21,"end_line":1,"end_character":65},"updated":"2017-09-12 22:00:12.000000000","message":"not sure if this the right parent.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"}],"doc/source/process/ExtensionPrograms.rst":[{"author":{"_account_id":7822,"name":"Chris Hoge (not involved in upstream development)","email":"chris@hogepodge.com","username":"hogepodge"},"change_message_id":"678da64ead40210f3887b4977bfad7b2e0362127","unresolved":false,"context_lines":[{"line_number":18,"context_line":"in order to foster conversation and useful feedback."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"In this document we describe two new categories of programs under"},{"line_number":21,"context_line":"development: \"vertical\" programs and \"add-on\" programs.  We will also"},{"line_number":22,"context_line":"discuss the current \"OpenStack Powered\" program as a means of comparison."},{"line_number":23,"context_line":"It is important to note that of these, only the \"OpenStack Powered\" program is"},{"line_number":24,"context_line":"currently an established program approved by the OpenStack Foundation"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f287b81_a4a6280e","line":21,"range":{"start_line":21,"start_character":37,"end_line":21,"end_character":45},"updated":"2017-08-30 04:03:58.000000000","message":"I\u0027m going to just say \"extension\" here, because I like that word better. Assume that comment applies throughout.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":18,"context_line":"in order to foster conversation and useful feedback."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"In this document we describe two new categories of programs under"},{"line_number":21,"context_line":"development: \"vertical\" programs and \"add-on\" programs.  We will also"},{"line_number":22,"context_line":"discuss the current \"OpenStack Powered\" program as a means of comparison."},{"line_number":23,"context_line":"It is important to note that of these, only the \"OpenStack Powered\" program is"},{"line_number":24,"context_line":"currently an established program approved by the OpenStack Foundation"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_b3bce5bb","line":21,"range":{"start_line":21,"start_character":37,"end_line":21,"end_character":45},"in_reply_to":"7f287b81_a4a6280e","updated":"2017-09-11 03:57:56.000000000","message":"Per meeting last week, sounds like the marketing team has settled on \"add-on\" so I\u0027ll leave it that way for now.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7822,"name":"Chris Hoge (not involved in upstream development)","email":"chris@hogepodge.com","username":"hogepodge"},"change_message_id":"678da64ead40210f3887b4977bfad7b2e0362127","unresolved":false,"context_lines":[{"line_number":23,"context_line":"It is important to note that of these, only the \"OpenStack Powered\" program is"},{"line_number":24,"context_line":"currently an established program approved by the OpenStack Foundation"},{"line_number":25,"context_line":"and in use today.  The \"add-ons\" and \"verticals\" programs have not yet"},{"line_number":26,"context_line":"been finalized and are still in development (though early discussion has"},{"line_number":27,"context_line":"been carried out in several public forums to date, including Interop WG"},{"line_number":28,"context_line":"meetings, Board of Directors meetings, the PTG, etc)."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f287b81_44b7843b","line":26,"range":{"start_line":26,"start_character":23,"end_line":26,"end_character":43},"updated":"2017-08-30 04:03:58.000000000","message":"Worth noting that we now have a target implementation date of January 2018 for extensions.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":23,"context_line":"It is important to note that of these, only the \"OpenStack Powered\" program is"},{"line_number":24,"context_line":"currently an established program approved by the OpenStack Foundation"},{"line_number":25,"context_line":"and in use today.  The \"add-ons\" and \"verticals\" programs have not yet"},{"line_number":26,"context_line":"been finalized and are still in development (though early discussion has"},{"line_number":27,"context_line":"been carried out in several public forums to date, including Interop WG"},{"line_number":28,"context_line":"meetings, Board of Directors meetings, the PTG, etc)."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_93b1e9e4","line":26,"range":{"start_line":26,"start_character":23,"end_line":26,"end_character":43},"in_reply_to":"7f287b81_44b7843b","updated":"2017-09-11 03:57:56.000000000","message":"Done","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":118,"context_line":"   `specification \u003c../../working_materials/interop_test_spec.rst\u003e`_"},{"line_number":119,"context_line":"   created by the Interop Working Group in 2016."},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"4. Interoperability Guidelines contain a list of"},{"line_number":122,"context_line":"   `Designated Sections \u003c../DesignatedSections.rst\u003e`_ of community-developed"},{"line_number":123,"context_line":"   source code that must be used to provide the required Capabilities."},{"line_number":124,"context_line":"   Designated sections are used to ensure that products calling themselves"},{"line_number":125,"context_line":"   \"OpenStack\" are actually using OpenStack code rather than a substitute"},{"line_number":126,"context_line":"   implementation of the same API that is not developed by the OpenStack"},{"line_number":127,"context_line":"   community."},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"In order to validate that a product adheres to a Guideline, the vendor"},{"line_number":130,"context_line":"must submit results of the tests listed in a Guideline.  Typically, this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_63822052","line":127,"range":{"start_line":121,"start_character":3,"end_line":127,"end_character":12},"updated":"2017-06-21 02:40:04.000000000","message":"Before we dive into add-on and verticals, what are the mechanism InterOP WG use to validate that submission adhere to this requirement?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":118,"context_line":"   `specification \u003c../../working_materials/interop_test_spec.rst\u003e`_"},{"line_number":119,"context_line":"   created by the Interop Working Group in 2016."},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"4. Interoperability Guidelines contain a list of"},{"line_number":122,"context_line":"   `Designated Sections \u003c../DesignatedSections.rst\u003e`_ of community-developed"},{"line_number":123,"context_line":"   source code that must be used to provide the required Capabilities."},{"line_number":124,"context_line":"   Designated sections are used to ensure that products calling themselves"},{"line_number":125,"context_line":"   \"OpenStack\" are actually using OpenStack code rather than a substitute"},{"line_number":126,"context_line":"   implementation of the same API that is not developed by the OpenStack"},{"line_number":127,"context_line":"   community."},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"In order to validate that a product adheres to a Guideline, the vendor"},{"line_number":130,"context_line":"must submit results of the tests listed in a Guideline.  Typically, this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_c81664f2","line":127,"range":{"start_line":121,"start_character":3,"end_line":127,"end_character":12},"in_reply_to":"5f201791_63822052","updated":"2017-06-23 02:46:17.000000000","message":"Legal language in the trademark agreement (e.g. the vendor is signing a legally binding agreement certifying compliance) and community policing.  Are you saying you\u0027d like that stated here?  Personally I\u0027d prefer to boot that elsewhere, as this is meant to be an overview of the program\u0027s requirements rather than an in-depth discussion covering everything down to enforcement policy.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":132,"context_line":"which is an OpenStack project independent of the Interop Working Group"},{"line_number":133,"context_line":"but closely involved.  Prior to the passage of the"},{"line_number":134,"context_line":"`TC resolution on location of tests \u003chttps://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html\u003e`_"},{"line_number":135,"context_line":"the RefStack project had already implemented the means to accept results"},{"line_number":136,"context_line":"of tests that do not reside in the Tempest project tree, but use the"},{"line_number":137,"context_line":"`Tempest plugin interface \u003chttps://docs.openstack.org/developer/tempest/plugin.html\u003e`_.  This detail becomes somewhat important to note before we discuss"},{"line_number":138,"context_line":"programs currently under development below."},{"line_number":139,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_23ae682e","line":136,"range":{"start_line":135,"start_character":0,"end_line":136,"end_character":55},"updated":"2017-06-21 02:40:04.000000000","message":"Where do we define which of the Tempest tests that are developed via plugin interface are part of Interop tests, and what is the process of approval by TC?/Board? on inclusion of these test for interop?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"cc445f8fb79ae62bdf0b67106a8d52cba686e265","unresolved":false,"context_lines":[{"line_number":132,"context_line":"which is an OpenStack project independent of the Interop Working Group"},{"line_number":133,"context_line":"but closely involved.  Prior to the passage of the"},{"line_number":134,"context_line":"`TC resolution on location of tests \u003chttps://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html\u003e`_"},{"line_number":135,"context_line":"the RefStack project had already implemented the means to accept results"},{"line_number":136,"context_line":"of tests that do not reside in the Tempest project tree, but use the"},{"line_number":137,"context_line":"`Tempest plugin interface \u003chttps://docs.openstack.org/developer/tempest/plugin.html\u003e`_.  This detail becomes somewhat important to note before we discuss"},{"line_number":138,"context_line":"programs currently under development below."},{"line_number":139,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f287b81_e6e61417","line":136,"range":{"start_line":135,"start_character":0,"end_line":136,"end_character":55},"in_reply_to":"5f201791_15edf48a","updated":"2017-08-23 16:51:12.000000000","message":"Rockg: note that the document in line 105 was drafted for the OpenStack Powered program, not vertical/extension programs.  In fact, it was drafted before the vertical programs had even been designed.  The TC could not even have considered vertical programs in that document since they didn\u0027t exist yet (additionally, there\u0027s been a lot of discussion on the role of tempest and which tests should be in it\u0027s tree since then...but that\u0027s probably a topic for another time).  The current thinking is that in some cases we\u0027ll be including projects in these programs that don\u0027t have tests in Tempest, and that shouldn\u0027t necessarily be a gating factor since RefStack can already handle data from tests written with a plugin.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":132,"context_line":"which is an OpenStack project independent of the Interop Working Group"},{"line_number":133,"context_line":"but closely involved.  Prior to the passage of the"},{"line_number":134,"context_line":"`TC resolution on location of tests \u003chttps://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html\u003e`_"},{"line_number":135,"context_line":"the RefStack project had already implemented the means to accept results"},{"line_number":136,"context_line":"of tests that do not reside in the Tempest project tree, but use the"},{"line_number":137,"context_line":"`Tempest plugin interface \u003chttps://docs.openstack.org/developer/tempest/plugin.html\u003e`_.  This detail becomes somewhat important to note before we discuss"},{"line_number":138,"context_line":"programs currently under development below."},{"line_number":139,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_15edf48a","line":136,"range":{"start_line":135,"start_character":0,"end_line":136,"end_character":55},"in_reply_to":"5f201791_23ae682e","updated":"2017-06-28 23:36:53.000000000","message":"Go look at ln#105 above.  The test must reside in Tempest.  The Plugin interface can run those tests, but I think that\u0027s in the dev doc on tempest below in ln#137\n\nWe might need to create a request to TC for test inclusion in Tempest for the new projects, or new tests for that matter, or, the discussion currently happening may change the test location requirement.  Since this is still overview, best to leave the process detail out.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":143,"context_line":"As OpenStack has matured, it has found traction in a variety of use cases."},{"line_number":144,"context_line":"Some of these use cases have requirements that may differ somewhat from"},{"line_number":145,"context_line":"those of other use cases.  They may require additional capabilities to be"},{"line_number":146,"context_line":"offered by a cloud, some of which may be less frequently used or even"},{"line_number":147,"context_line":"offered by more general-purpose clouds.  Some such capabilities might"},{"line_number":148,"context_line":"not meet the `Criteria \u003c../CoreCriteria.rst\u003e`_ for inclusion in the"},{"line_number":149,"context_line":"OpenStack Powered programs now or in the foreseeable future due to their"},{"line_number":150,"context_line":"focus on core, broadly applicable capabilities rather than those more"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_c3621417","line":147,"range":{"start_line":146,"start_character":62,"end_line":147,"end_character":39},"updated":"2017-06-21 02:40:04.000000000","message":"NOT offered by general clouds?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":143,"context_line":"As OpenStack has matured, it has found traction in a variety of use cases."},{"line_number":144,"context_line":"Some of these use cases have requirements that may differ somewhat from"},{"line_number":145,"context_line":"those of other use cases.  They may require additional capabilities to be"},{"line_number":146,"context_line":"offered by a cloud, some of which may be less frequently used or even"},{"line_number":147,"context_line":"offered by more general-purpose clouds.  Some such capabilities might"},{"line_number":148,"context_line":"not meet the `Criteria \u003c../CoreCriteria.rst\u003e`_ for inclusion in the"},{"line_number":149,"context_line":"OpenStack Powered programs now or in the foreseeable future due to their"},{"line_number":150,"context_line":"focus on core, broadly applicable capabilities rather than those more"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_68dd1041","line":147,"range":{"start_line":146,"start_character":62,"end_line":147,"end_character":39},"in_reply_to":"5f201791_c3621417","updated":"2017-06-23 02:46:17.000000000","message":"Good catch, thanks","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":154,"context_line":"the same projects, use many of the same capabilities, and have development"},{"line_number":155,"context_line":"governed and supported by the same bodies (such as the Technical Committee"},{"line_number":156,"context_line":"and Board of Directors).  Within the constraints of the use case being"},{"line_number":157,"context_line":"addressed, there is also an interest in interoperable implementations."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"To illustrate, we might use the example of Network Functions"},{"line_number":160,"context_line":"Virtualization (NFV).  If a provider wishes to use OpenStack as part of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_86b1cae4","line":157,"range":{"start_line":157,"start_character":69,"end_line":157,"end_character":70},"updated":"2017-06-21 02:40:04.000000000","message":"I think we need to bring key question on the table.\nDo vertical require core OpenStack services or not?\nIf not then what is OpenStack and what does it mean to have openstack logo, in general.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":154,"context_line":"the same projects, use many of the same capabilities, and have development"},{"line_number":155,"context_line":"governed and supported by the same bodies (such as the Technical Committee"},{"line_number":156,"context_line":"and Board of Directors).  Within the constraints of the use case being"},{"line_number":157,"context_line":"addressed, there is also an interest in interoperable implementations."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"To illustrate, we might use the example of Network Functions"},{"line_number":160,"context_line":"Virtualization (NFV).  If a provider wishes to use OpenStack as part of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_c872e449","line":157,"range":{"start_line":157,"start_character":69,"end_line":157,"end_character":70},"in_reply_to":"5f201791_86b1cae4","updated":"2017-06-23 02:46:17.000000000","message":"See 5a and 6 below: vertical programs should not conflict with OpenStack Powered at a minimum.  Said another way: there\u0027s no reason that a product that meets the requirements for a vertical program (like, say, \"OpenStack Ready NFV\") couldn\u0027t also meet the requirements for OpenStack Powered and badge itself with both logos.  I could imagine there might be some cases where a product might choose not to offer everything required for Powered but still meet the requirements for a vertical program.  We don\u0027t have real-life examples of that on the radar today though.  The choice here was to not put in a requirement that you meet the requirements for Powered as a prerequisite for *all* vertical programs, but rather make that something we decide on for each individual vertical program as it\u0027s being designed.  Ultimately all vertical programs have to be approved by both the InteropWG and the Board of Directors, so this provides us with a very strong feedback loop as to how the Foundation wishes to approach a given vertical on a case-by-case basis.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7822,"name":"Chris Hoge (not involved in upstream development)","email":"chris@hogepodge.com","username":"hogepodge"},"change_message_id":"678da64ead40210f3887b4977bfad7b2e0362127","unresolved":false,"context_lines":[{"line_number":165,"context_line":"exposed to the provider.  A provider building an NFV offering may wish to"},{"line_number":166,"context_line":"have some assurance of interoperability when selecting which OpenStack"},{"line_number":167,"context_line":"products to use--but the OpenStack Powered(TM) program may be too general"},{"line_number":168,"context_line":"to be very useful."},{"line_number":169,"context_line":""},{"line_number":170,"context_line":"In order to foster development of these \"vertical\" use cases, the community"},{"line_number":171,"context_line":"is considering whether and how to build interoperability programs that"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f287b81_04d5fc43","line":168,"updated":"2017-08-30 04:03:58.000000000","message":"as an additional use case, I think it\u0027s illustrative to consider standalone Cinder and Ironic for verticals also. These are small but useful cases and bring value to the larger community, especially for collaborating with adjacent communities like K8s.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":165,"context_line":"exposed to the provider.  A provider building an NFV offering may wish to"},{"line_number":166,"context_line":"have some assurance of interoperability when selecting which OpenStack"},{"line_number":167,"context_line":"products to use--but the OpenStack Powered(TM) program may be too general"},{"line_number":168,"context_line":"to be very useful."},{"line_number":169,"context_line":""},{"line_number":170,"context_line":"In order to foster development of these \"vertical\" use cases, the community"},{"line_number":171,"context_line":"is considering whether and how to build interoperability programs that"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_d3dc111a","line":168,"in_reply_to":"7f287b81_04d5fc43","updated":"2017-09-11 03:57:56.000000000","message":"Done","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":204,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":205,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":206,"context_line":"   if it is widely used among NFV deployments."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":209,"context_line":"   programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_c61342b8","line":206,"range":{"start_line":206,"start_character":45,"end_line":206,"end_character":46},"updated":"2017-06-21 02:40:04.000000000","message":"Suggest adding a bullet for the code base of the solution.\nIs all code of the inter-operable solution is part of OpenStack, subject to new nomenclature of replacement to big tent?\n\nIs testing for vertical only covers APIs that are defined by OpenStack? If not why is it part of OpenStack interop testing?\n\nExpect that the answer is that it is OpenStack API with the configuration targeted for specific vertical with extended Tempest tests to cover it. \n\nMy concern that we are jumped into how to implement it without defining what it is first.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":204,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":205,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":206,"context_line":"   if it is widely used among NFV deployments."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":209,"context_line":"   programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_53d021f8","line":206,"range":{"start_line":206,"start_character":45,"end_line":206,"end_character":46},"in_reply_to":"5f201791_a862083d","updated":"2017-09-11 03:57:56.000000000","message":"Done","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":204,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":205,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":206,"context_line":"   if it is widely used among NFV deployments."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":209,"context_line":"   programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_b848755c","line":206,"range":{"start_line":206,"start_character":45,"end_line":206,"end_character":46},"in_reply_to":"5f201791_a862083d","updated":"2017-06-28 23:36:53.000000000","message":"There is also the case where just having the APIs validated doesn\u0027t demonstrate that the nessesary scenarios are achievable.  Tempest Scenario tests are still in the Tempest tree and part of the process for verticals might be validation of the apis and validation of a set of scenarios, but also, verification that only the apis listed as part of the interop are actually used.  So, demonstrate necessary *and* sufficient and no unidentified apis used.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":204,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":205,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":206,"context_line":"   if it is widely used among NFV deployments."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":209,"context_line":"   programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_73eb1db0","line":206,"range":{"start_line":206,"start_character":45,"end_line":206,"end_character":46},"in_reply_to":"5f201791_b848755c","updated":"2017-09-11 03:57:56.000000000","message":"Done","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":204,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":205,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":206,"context_line":"   if it is widely used among NFV deployments."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":209,"context_line":"   programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_a862083d","line":206,"range":{"start_line":206,"start_character":45,"end_line":206,"end_character":46},"in_reply_to":"5f201791_c61342b8","updated":"2017-06-23 02:46:17.000000000","message":"\u003e Is all code of the inter-operable solution is part of OpenStack, \n\u003e subject to new nomenclature of replacement to big tent?\n\nPer item 1, we\u0027re using the same schemas to define these programs that we do for Powered today.  That means each vertical program will include Designated Sections of code.  As of today, the definition of Designated Sections [1] includes a provision that the code exist in the OpenStack gerrit namespace.  While I could imagine a theoretical possibility that some vertical programs might want to include code from elsewhere, I don\u0027t know that that would really make much sense from a logo perspective, and I doubt that the OpenStack Foundation\u0027s Board of Directors (who must approve any new program involving foundation assets like the trademark or logo) would approve such a program.  If you think it\u0027s worth clarifying that here further, I\u0027m ok with that.\n\n[1] http://git.openstack.org/cgit/openstack/interop/tree/doc/source/process/Lexicon.rst#n51 and for more detail see also:  http://git.openstack.org/cgit/openstack/interop/tree/doc/source/process/DesignatedSections.rst\n\n\u003e Is testing for vertical only covers APIs that are defined by OpenStack?\n\u003e If not why is it part of OpenStack interop testing?\n\nOpenStack is more than just API\u0027s, and it is conceivable that programs would want to require other things than just API\u0027s.  As an example: Heat has a fairly small set of API\u0027s, but a much larger range of resources that can be included in templates.  A vertical program might wish to require that certain resources must be supported.  Thus, we don\u0027t include a specific provision here that tests only cover API\u0027s.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":213,"context_line":"   or Cloud Foundry communities in the design of a program oriented"},{"line_number":214,"context_line":"   at container or PaaS use cases."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"   b. Adjacent communities may be able to help us with determining the"},{"line_number":217,"context_line":"   merits of various capabilities, design of Criteria, or may even"},{"line_number":218,"context_line":"   have tests we can take advantage of."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"   c. It is also goes without saying that relevant groups within the"},{"line_number":221,"context_line":"   OpenStack community are welcome to provide input too.  For example,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_46273214","line":218,"range":{"start_line":216,"start_character":4,"end_line":218,"end_character":39},"updated":"2017-06-21 02:40:04.000000000","message":"If tests are on OpenStack API level - yes.\nIf not, say on the level of VNF modules, then it is no longer OpenStack interoperability.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":213,"context_line":"   or Cloud Foundry communities in the design of a program oriented"},{"line_number":214,"context_line":"   at container or PaaS use cases."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"   b. Adjacent communities may be able to help us with determining the"},{"line_number":217,"context_line":"   merits of various capabilities, design of Criteria, or may even"},{"line_number":218,"context_line":"   have tests we can take advantage of."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"   c. It is also goes without saying that relevant groups within the"},{"line_number":221,"context_line":"   OpenStack community are welcome to provide input too.  For example,"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_685cf07d","line":218,"range":{"start_line":216,"start_character":4,"end_line":218,"end_character":39},"in_reply_to":"5f201791_46273214","updated":"2017-06-23 02:46:17.000000000","message":"See example above about Heat template resources: I think there\u0027s a wider universe of things to consider than just API\u0027s, although I would certainly agree that will likely be the main focus (as it is today in the Powered programs).  Still, the main point here is just that we should be willing to work with adjacent communities in terms of finding out what\u0027s valuable from an interoperability perspective.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":226,"context_line":"4. Some changes to restrictions on tests may be necessary depending on the"},{"line_number":227,"context_line":"   use case."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"   a. For example: some use cases might be dependent on administrative"},{"line_number":230,"context_line":"   capabilities or API\u0027s, as OpenStack may be an underpinning component"},{"line_number":231,"context_line":"   of an offering rather than directly exposed to end users.  In such"},{"line_number":232,"context_line":"   cases, we might discard the requirement that tests not use"},{"line_number":233,"context_line":"   administrator credentials."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"   b. Acceptable locations for tests used by such programs may also be"},{"line_number":236,"context_line":"   reconsidered.  It is important to note that vertical programs did"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_e61d1ebe","line":233,"range":{"start_line":229,"start_character":5,"end_line":233,"end_character":29},"updated":"2017-06-21 02:40:04.000000000","message":"yes, as long as these are OpenStack defined capabilities and APIs for them.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":226,"context_line":"4. Some changes to restrictions on tests may be necessary depending on the"},{"line_number":227,"context_line":"   use case."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"   a. For example: some use cases might be dependent on administrative"},{"line_number":230,"context_line":"   capabilities or API\u0027s, as OpenStack may be an underpinning component"},{"line_number":231,"context_line":"   of an offering rather than directly exposed to end users.  In such"},{"line_number":232,"context_line":"   cases, we might discard the requirement that tests not use"},{"line_number":233,"context_line":"   administrator credentials."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"   b. Acceptable locations for tests used by such programs may also be"},{"line_number":236,"context_line":"   reconsidered.  It is important to note that vertical programs did"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_a8f0c868","line":233,"range":{"start_line":229,"start_character":5,"end_line":233,"end_character":29},"in_reply_to":"5f201791_e61d1ebe","updated":"2017-06-23 02:46:17.000000000","message":"Correct","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":236,"context_line":"   reconsidered.  It is important to note that vertical programs did"},{"line_number":237,"context_line":"   not exist and were not considered by the Technical Committee when it"},{"line_number":238,"context_line":"   created it\u0027s"},{"line_number":239,"context_line":"   `resolution \u003chttps://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html\u003e`_ in 2016.  Some vertical programs may use"},{"line_number":240,"context_line":"   projects that are less widely deployed generally, and migrating"},{"line_number":241,"context_line":"   their tests into Tempest may create an undue burden for multiple"},{"line_number":242,"context_line":"   parties (including the project team and QA team).  Since RefStack"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_98b3794e","line":239,"updated":"2017-06-28 23:36:53.000000000","message":"Move the \"somve vertical....\" text to the next line for readability, please","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":236,"context_line":"   reconsidered.  It is important to note that vertical programs did"},{"line_number":237,"context_line":"   not exist and were not considered by the Technical Committee when it"},{"line_number":238,"context_line":"   created it\u0027s"},{"line_number":239,"context_line":"   `resolution \u003chttps://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html\u003e`_ in 2016.  Some vertical programs may use"},{"line_number":240,"context_line":"   projects that are less widely deployed generally, and migrating"},{"line_number":241,"context_line":"   their tests into Tempest may create an undue burden for multiple"},{"line_number":242,"context_line":"   parties (including the project team and QA team).  Since RefStack"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_d305317c","line":239,"in_reply_to":"5f201791_98b3794e","updated":"2017-09-11 03:57:56.000000000","message":"Done","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":243,"context_line":"   already has the ability to use tests using the Tempest plugin"},{"line_number":244,"context_line":"   interface, the technical barrier is relatively small for RefStack"},{"line_number":245,"context_line":"   to be able to consume them in many cases:"},{"line_number":246,"context_line":"   it\u0027s more a question of how best to govern the tests."},{"line_number":247,"context_line":""},{"line_number":248,"context_line":"5. Guidelines for vertical programs would still need to be approved by"},{"line_number":249,"context_line":"   the Board of Directors and would likely take a similar cadence to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_a67de6e8","line":246,"range":{"start_line":246,"start_character":3,"end_line":246,"end_character":56},"updated":"2017-06-21 02:40:04.000000000","message":"right on the money!","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":249,"context_line":"   the Board of Directors and would likely take a similar cadence to the"},{"line_number":250,"context_line":"   OpenStack Powered program."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   a. Ultimately, any use of the OpenStack trademarks and any new"},{"line_number":253,"context_line":"   trademarks and logos are the property of the OpenStack Foundation."},{"line_number":254,"context_line":"   It\u0027s Board of Directors is the final authority on licensing of"},{"line_number":255,"context_line":"   those assets."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"6. Whenever possible, vertical programs should build on the existing"},{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_2652f668","line":255,"range":{"start_line":252,"start_character":3,"end_line":255,"end_character":16},"updated":"2017-06-21 02:40:04.000000000","message":"This is interesting. Do we as OpenStack foundation have the rights to use, say Cloud Foundry vertical, without approval of Cloud Foundry board?\nFor generic terms, like NFV and PaaS I do not forsee issues but for some vertical we may bump into these issues. Assume that board will consider it as part of approval of the specific vertical program.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":249,"context_line":"   the Board of Directors and would likely take a similar cadence to the"},{"line_number":250,"context_line":"   OpenStack Powered program."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   a. Ultimately, any use of the OpenStack trademarks and any new"},{"line_number":253,"context_line":"   trademarks and logos are the property of the OpenStack Foundation."},{"line_number":254,"context_line":"   It\u0027s Board of Directors is the final authority on licensing of"},{"line_number":255,"context_line":"   those assets."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"6. Whenever possible, vertical programs should build on the existing"},{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_e8fda03a","line":255,"range":{"start_line":252,"start_character":3,"end_line":255,"end_character":16},"in_reply_to":"5f201791_2652f668","updated":"2017-06-23 02:46:17.000000000","message":"Definitely not: the OpenStack Foundation doesn\u0027t own the CloudFoundry trademark. [1]  You are correct that the OpenStack Board of Directors would have to approve these programs and would presumably consult their legal council in making such decisions.\n\n\n[1] https://www.cloudfoundry.org/trademark/","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":249,"context_line":"   the Board of Directors and would likely take a similar cadence to the"},{"line_number":250,"context_line":"   OpenStack Powered program."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   a. Ultimately, any use of the OpenStack trademarks and any new"},{"line_number":253,"context_line":"   trademarks and logos are the property of the OpenStack Foundation."},{"line_number":254,"context_line":"   It\u0027s Board of Directors is the final authority on licensing of"},{"line_number":255,"context_line":"   those assets."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"6. Whenever possible, vertical programs should build on the existing"},{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_38ca25a1","line":255,"range":{"start_line":252,"start_character":3,"end_line":255,"end_character":16},"in_reply_to":"5f201791_e8fda03a","updated":"2017-06-28 23:36:53.000000000","message":"This is also a great argument for involving the adjacent communuity(ies) in creating the test guidelines.  Let the tech teams determine the appropriate tests and the lawyers negotiate the reciprocal use of trademarks, or appropriate wording to identify the tradmarks and owners","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":255,"context_line":"   those assets."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"6. Whenever possible, vertical programs should build on the existing"},{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"},{"line_number":259,"context_line":"   requirements."},{"line_number":260,"context_line":""},{"line_number":261,"context_line":"   a. It is likely that the Capabilities required in the OpenStack Powered"},{"line_number":262,"context_line":"   program are a subset of the capabilities needed for a specific use"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_6c39ed3f","line":259,"range":{"start_line":258,"start_character":30,"end_line":259,"end_character":15},"updated":"2017-06-21 02:40:04.000000000","message":"what does that mean?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":255,"context_line":"   those assets."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"6. Whenever possible, vertical programs should build on the existing"},{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"},{"line_number":259,"context_line":"   requirements."},{"line_number":260,"context_line":""},{"line_number":261,"context_line":"   a. It is likely that the Capabilities required in the OpenStack Powered"},{"line_number":262,"context_line":"   program are a subset of the capabilities needed for a specific use"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_e8ab601a","line":259,"range":{"start_line":258,"start_character":30,"end_line":259,"end_character":15},"in_reply_to":"5f201791_6c39ed3f","updated":"2017-06-23 02:46:17.000000000","message":"When possible: use the requirements of the Powered program as a basis for building a vertical program (in simpler terms: include the same requirements as Powered and then add whatever additional requirements are relevant to the vertical).  \n\n\nHowever there may be cases where that doesn\u0027t make sense...for example, imagine a theoretical program where we need only Ironic or Zun or Magnum but not Nova.  If I\u0027m a product vendor and I ship a distribution that ships [Ironic|Zun|Magnum] but also ships Nova, it should be possible for the distribution to qualify both for the Powered program and the vertical program.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"},{"line_number":259,"context_line":"   requirements."},{"line_number":260,"context_line":""},{"line_number":261,"context_line":"   a. It is likely that the Capabilities required in the OpenStack Powered"},{"line_number":262,"context_line":"   program are a subset of the capabilities needed for a specific use"},{"line_number":263,"context_line":"   case or vertical."},{"line_number":264,"context_line":""},{"line_number":265,"context_line":"   b. Some Capabilities required by the OpenStack Powered program may not"},{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_4c275114","line":263,"range":{"start_line":261,"start_character":6,"end_line":263,"end_character":19},"updated":"2017-06-21 02:40:04.000000000","message":"correct. That brings us back to what is OpenStack.\nWhat are OpenStack services/project required for it to be called OpenStack and use OpenStack logo for any vertical.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":258,"context_line":"   OpenStack Powered program--or should at least not contain conflicting"},{"line_number":259,"context_line":"   requirements."},{"line_number":260,"context_line":""},{"line_number":261,"context_line":"   a. It is likely that the Capabilities required in the OpenStack Powered"},{"line_number":262,"context_line":"   program are a subset of the capabilities needed for a specific use"},{"line_number":263,"context_line":"   case or vertical."},{"line_number":264,"context_line":""},{"line_number":265,"context_line":"   b. Some Capabilities required by the OpenStack Powered program may not"},{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_c8a66454","line":263,"range":{"start_line":261,"start_character":6,"end_line":263,"end_character":19},"in_reply_to":"5f201791_4c275114","updated":"2017-06-23 02:46:17.000000000","message":"See above comments.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7822,"name":"Chris Hoge (not involved in upstream development)","email":"chris@hogepodge.com","username":"hogepodge"},"change_message_id":"678da64ead40210f3887b4977bfad7b2e0362127","unresolved":false,"context_lines":[{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"},{"line_number":267,"context_line":"   conflict with the Capabilities a vertical program would rely on."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"   c. In the very worst case, a Capability required of a vertical program"},{"line_number":270,"context_line":"   might directly conflict with a Capability required of the OpenStack"},{"line_number":271,"context_line":"   Powered program.  We expect such cases to be very rare and these"},{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f287b81_84c8cca5","line":273,"range":{"start_line":269,"start_character":6,"end_line":273,"end_character":69},"updated":"2017-08-30 04:03:58.000000000","message":"The board is quite opposed to conflicts between programs, and expressed this in Boston.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"},{"line_number":267,"context_line":"   conflict with the Capabilities a vertical program would rely on."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"   c. In the very worst case, a Capability required of a vertical program"},{"line_number":270,"context_line":"   might directly conflict with a Capability required of the OpenStack"},{"line_number":271,"context_line":"   Powered program.  We expect such cases to be very rare and these"},{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_8c8209c8","line":273,"range":{"start_line":269,"start_character":6,"end_line":273,"end_character":69},"updated":"2017-06-21 02:40:04.000000000","message":"do we have an example of it?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"},{"line_number":267,"context_line":"   conflict with the Capabilities a vertical program would rely on."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"   c. In the very worst case, a Capability required of a vertical program"},{"line_number":270,"context_line":"   might directly conflict with a Capability required of the OpenStack"},{"line_number":271,"context_line":"   Powered program.  We expect such cases to be very rare and these"},{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_e82ec0a3","line":273,"range":{"start_line":269,"start_character":6,"end_line":273,"end_character":69},"in_reply_to":"5f201791_8c8209c8","updated":"2017-06-23 02:46:17.000000000","message":"Personally I don\u0027t, today.  One could imagine that this might happen though.  Some time ago you could run either nova-net or neutron in your cloud, but not both.  IIRC when LBaaSv2 was introduced, you couldn\u0027t run both v1 and v2 from the same Neutron server (memory hazy though, don\u0027t quote me on it).  In both of those cases it\u0027s unlikely that one of the mutually-incompatible choices should be in the OpenStack Powered program anyway...if the Powered program required LBaaSv1 or nova-net and a vertical program depended on LBaaSv2 or Neutron, that should be a terribly obvious red flag for us to go scrutinize whether the former should be in the Powered program at all.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":266,"context_line":"   be useful for particular vertical programs, but also likely don\u0027t"},{"line_number":267,"context_line":"   conflict with the Capabilities a vertical program would rely on."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"   c. In the very worst case, a Capability required of a vertical program"},{"line_number":270,"context_line":"   might directly conflict with a Capability required of the OpenStack"},{"line_number":271,"context_line":"   Powered program.  We expect such cases to be very rare and these"},{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_7339dd3f","line":273,"range":{"start_line":269,"start_character":6,"end_line":273,"end_character":69},"in_reply_to":"7f287b81_84c8cca5","updated":"2017-09-11 03:57:56.000000000","message":"I think we\u0027re all in agreement here...the idea behind the section is to spell out what would happen if we\u0027re considering capabilities that would create a conflict (e.g. we\u0027d likely drop either the one in Powered, the one in the extension program, or both because the conflict is darn good indicator that they\u0027re actually not interoperable capabilities).  I\u0027ll clarify the wording a bit and add a note that we\u0027ve discussed this with the BoD and they\u0027re also opposed to creating conflicting programs.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"The OpenStack community has created a large number of software projects"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_ecf97d4d","line":275,"range":{"start_line":275,"start_character":0,"end_line":275,"end_character":17},"updated":"2017-06-21 02:40:04.000000000","message":"We need to make it clear that this is targeted for projects that are part of openstack and are part of \"big tent\" or its equivalent.\nIt is not applicable to some add-on that a vendor decides to add to its openstack distributions. You need at least 2 vendors that deliver add-on openstack project in their distribution for add-on project to be considered for interop. Replace \"2\" with whatever # the interop group want to propose.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"The OpenStack community has created a large number of software projects"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_333b5539","line":275,"range":{"start_line":275,"start_character":0,"end_line":275,"end_character":17},"in_reply_to":"5f201791_38a90590","updated":"2017-09-11 03:57:56.000000000","message":"I\u0027ll add a note just spelling out that these programs are for projects under OpenStack governance and leave it at that.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"The OpenStack community has created a large number of software projects"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_38a90590","line":275,"range":{"start_line":275,"start_character":0,"end_line":275,"end_character":17},"in_reply_to":"5f201791_de4f3ebb","updated":"2017-06-28 23:36:53.000000000","message":"current state of TC and dev community thinking on this: 1. dissolving the big tent and striking all mention of if from the OpenStack archives. 2. OpenStack \"Official\" projects vs. everything else.  You must apply and get under governance to be \"official\"  Everything else will eventually get a name but it\u0027s mostly \"repo hosted by OpenStack.\"  I think both the board and TC will want some jurisdiction over what gets approved as an \"add-on\"","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":272,"context_line":"   would likely cause us to re-evaluate whether the two Capabilities"},{"line_number":273,"context_line":"   in question actually meet the Criteria for the requisite programs."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"\"Add-On\" Programs"},{"line_number":276,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"The OpenStack community has created a large number of software projects"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_de4f3ebb","line":275,"range":{"start_line":275,"start_character":0,"end_line":275,"end_character":17},"in_reply_to":"5f201791_ecf97d4d","updated":"2017-06-23 02:46:17.000000000","message":"\u003e We need to make it clear that this is targeted for projects that are\n\u003e part of openstack and are part of \"big tent\" or its equivalent.\n\nSure, seems like a reasonable thing to spell out.\n\n\u003e You need at least 2 vendors that deliver add-on openstack project in\n\u003e their distribution for add-on project to be considered for interop.\n\u003e Replace \"2\" with whatever # the interop group want to propose.\n\nHmmm...this bit I have concerns about.  It feels like a bit of a chicken-and-egg problem.  There\u0027s been a lot of discussion about making considering interoperability something that project teams start considering as early as possible, and that might include projects that aren\u0027t yet part of a commercial offering.  If a project develops it\u0027s standard of interoperability early, then vendors looking at including the project know what they need to offer immediately.  That said, I understand and agree with the sentiment that maybe not every project in the tent needs to have an add-on program approved by the BoD.  Key for me here is the separation between a project deciding what interop looks like for it and actually getting into a logo program: I think the former can happen at any point and the latter can happen when the InteropWG and BoD agree that there\u0027s enough adoption to merit creating a logo program.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":298,"context_line":"   than incur the extra cost of including them."},{"line_number":299,"context_line":""},{"line_number":300,"context_line":"2. Test requirements.  By a similar measure, many projects today do"},{"line_number":301,"context_line":"   not place their tests in the Tempest tree, or only put some of their"},{"line_number":302,"context_line":"   tests in Tempest.  Many instead house the tests in the project tree"},{"line_number":303,"context_line":"   (often but not always using the Tempest plugin interface).  Moving"},{"line_number":304,"context_line":"   test for all projects into Tempest would create a heavy burden on the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_6ca32d51","line":301,"range":{"start_line":301,"start_character":32,"end_line":301,"end_character":44},"updated":"2017-06-21 02:40:04.000000000","message":"suggest to add a reference.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":298,"context_line":"   than incur the extra cost of including them."},{"line_number":299,"context_line":""},{"line_number":300,"context_line":"2. Test requirements.  By a similar measure, many projects today do"},{"line_number":301,"context_line":"   not place their tests in the Tempest tree, or only put some of their"},{"line_number":302,"context_line":"   tests in Tempest.  Many instead house the tests in the project tree"},{"line_number":303,"context_line":"   (often but not always using the Tempest plugin interface).  Moving"},{"line_number":304,"context_line":"   test for all projects into Tempest would create a heavy burden on the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_3ea2b24c","line":301,"range":{"start_line":301,"start_character":32,"end_line":301,"end_character":44},"in_reply_to":"5f201791_6ca32d51","updated":"2017-06-23 02:46:17.000000000","message":"Just to clarify, did you mean a reference along the lines of:\n\n\n...do not place their tests in the Tempest tree (for example: Senlin\u0027s Tempest tests are in the `Senlin project tree \u003chttp://git.openstack.org/cgit/openstack/senlin/tree/senlin/tests/tempest\u003e`_ )...","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"2cf4a47f6bf78c8307c10649b54499e4fda1670b","unresolved":false,"context_lines":[{"line_number":299,"context_line":""},{"line_number":300,"context_line":"2. Test requirements.  By a similar measure, many projects today do"},{"line_number":301,"context_line":"   not place their tests in the Tempest tree, or only put some of their"},{"line_number":302,"context_line":"   tests in Tempest.  Many instead house the tests in the project tree"},{"line_number":303,"context_line":"   (often but not always using the Tempest plugin interface).  Moving"},{"line_number":304,"context_line":"   test for all projects into Tempest would create a heavy burden on the"},{"line_number":305,"context_line":"   QA team and on the projects.  The benefits of doing so may also"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f231b9d_992102b8","line":302,"range":{"start_line":302,"start_character":22,"end_line":302,"end_character":65},"updated":"2017-06-12 20:36:10.000000000","message":"Tempest is mentioned in multiple places, but here in particular - is this getting too into the internal details of how we do things? To the point that this could be confusing to the targeted consumer of this documentation?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"53bfd2151e887ade7b64c05956139d832e8bfbbc","unresolved":false,"context_lines":[{"line_number":299,"context_line":""},{"line_number":300,"context_line":"2. Test requirements.  By a similar measure, many projects today do"},{"line_number":301,"context_line":"   not place their tests in the Tempest tree, or only put some of their"},{"line_number":302,"context_line":"   tests in Tempest.  Many instead house the tests in the project tree"},{"line_number":303,"context_line":"   (often but not always using the Tempest plugin interface).  Moving"},{"line_number":304,"context_line":"   test for all projects into Tempest would create a heavy burden on the"},{"line_number":305,"context_line":"   QA team and on the projects.  The benefits of doing so may also"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7f231b9d_d8288d87","line":302,"range":{"start_line":302,"start_character":22,"end_line":302,"end_character":65},"in_reply_to":"7f231b9d_992102b8","updated":"2017-06-13 02:15:22.000000000","message":"Well, currently the target consumer of this particular doc is mostly OpenStack devs and product owners, so my personal opinion is that it is isn\u0027t to much detail (I\u0027ll readily concede there are other opinions out there though!).  For example: the RefStack project team needs to know where the tests the RefStack client needs to run are, how to run the tests, and how to interpret the results.  The Designate/Trove/other project teams who might want to create add-on programs for their projects need to understand where their tests can live and where they can\u0027t (and I think the majority are already at least somewhat familiar with Tempest).  The TC needs to decide if their existing resolution that tests used for trademark programs should be moved into Tempest should apply here, or if these new programs that didn\u0027t exist when that resolution was created warrant new consideration.  The point being: the mechanics of where tests live, how they\u0027re versioned, who owns them, and how we run and interpret them actually matter quite a bit, and IMHO warrant enough detail for discussion here.  \n\n\nThat said: if these programs are eventually created, then people that just want to prove a product\u0027s adherence to a Guideline may need substantially less detail depending on how we implement things...e.g. with a bit of elbow grease we could conceivably just say something along the lines of \"Step 1: download refstack-client, Step 2: run refstack-client with the \u0027--add-on-programs\u003dtrove,designate\u0027 flag.\"  \n\n\nThis document is really to inform community discussion into the design of the programs, though.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":310,"context_line":"   with the Guidelines and make sure that if changes substantial enough"},{"line_number":311,"context_line":"   to call interoperability into question were made to a test, those"},{"line_number":312,"context_line":"   changes would be discussed appropriately in the context of the"},{"line_number":313,"context_line":"   OpenStack Powered program.  Within the bounds of a program targeting"},{"line_number":314,"context_line":"   an individual project, there may be somewhat less need for review by"},{"line_number":315,"context_line":"   a cross-project team, particularly if the individual project team"},{"line_number":316,"context_line":"   is aware of the same Criteria, tooling, and general principals"},{"line_number":317,"context_line":"   (as they presumably would be if they are drafting a Guideline"},{"line_number":318,"context_line":"   themselves rather than the Interop Working Group doing so)."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"3. Changing Criteria.  The Criteria for the existing OpenStack Powered"},{"line_number":321,"context_line":"   program were created with the \"core\" of OpenStack in mind, and the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_ec7cddb6","line":318,"range":{"start_line":313,"start_character":31,"end_line":318,"end_character":62},"updated":"2017-06-21 02:40:04.000000000","message":"Do we place a requirement for a project under consideration for add-on that project must be in good standing in OpenStack and have at least 2 contributing \"companies\"?\nWe may leave it to \"big tent\" replacement and piggy back on their new definition on what OpenStack project is.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":310,"context_line":"   with the Guidelines and make sure that if changes substantial enough"},{"line_number":311,"context_line":"   to call interoperability into question were made to a test, those"},{"line_number":312,"context_line":"   changes would be discussed appropriately in the context of the"},{"line_number":313,"context_line":"   OpenStack Powered program.  Within the bounds of a program targeting"},{"line_number":314,"context_line":"   an individual project, there may be somewhat less need for review by"},{"line_number":315,"context_line":"   a cross-project team, particularly if the individual project team"},{"line_number":316,"context_line":"   is aware of the same Criteria, tooling, and general principals"},{"line_number":317,"context_line":"   (as they presumably would be if they are drafting a Guideline"},{"line_number":318,"context_line":"   themselves rather than the Interop Working Group doing so)."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"3. Changing Criteria.  The Criteria for the existing OpenStack Powered"},{"line_number":321,"context_line":"   program were created with the \"core\" of OpenStack in mind, and the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_18eac9ab","line":318,"range":{"start_line":313,"start_character":31,"end_line":318,"end_character":62},"in_reply_to":"5f201791_be02420a","updated":"2017-06-28 23:36:53.000000000","message":"See my comments earlier","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":310,"context_line":"   with the Guidelines and make sure that if changes substantial enough"},{"line_number":311,"context_line":"   to call interoperability into question were made to a test, those"},{"line_number":312,"context_line":"   changes would be discussed appropriately in the context of the"},{"line_number":313,"context_line":"   OpenStack Powered program.  Within the bounds of a program targeting"},{"line_number":314,"context_line":"   an individual project, there may be somewhat less need for review by"},{"line_number":315,"context_line":"   a cross-project team, particularly if the individual project team"},{"line_number":316,"context_line":"   is aware of the same Criteria, tooling, and general principals"},{"line_number":317,"context_line":"   (as they presumably would be if they are drafting a Guideline"},{"line_number":318,"context_line":"   themselves rather than the Interop Working Group doing so)."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"3. Changing Criteria.  The Criteria for the existing OpenStack Powered"},{"line_number":321,"context_line":"   program were created with the \"core\" of OpenStack in mind, and the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_be02420a","line":318,"range":{"start_line":313,"start_character":31,"end_line":318,"end_character":62},"in_reply_to":"5f201791_ec7cddb6","updated":"2017-06-23 02:46:17.000000000","message":"Good point--that might be worth spelling out a bit here.  I think the general notion we\u0027ve discussed is that if the project is under TC governance, that\u0027s good enough for us to at least consider it at least eligible.  Per above though, the InteropWG and BoD have to approve these programs so it\u0027s perhaps unlikely that every project in the tent will actually end up with an add-on program (I18n is in http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml for example, but it would be a little hard to fathom what an add-on program for that would look like).","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":317,"context_line":"   (as they presumably would be if they are drafting a Guideline"},{"line_number":318,"context_line":"   themselves rather than the Interop Working Group doing so)."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"3. Changing Criteria.  The Criteria for the existing OpenStack Powered"},{"line_number":321,"context_line":"   program were created with the \"core\" of OpenStack in mind, and the"},{"line_number":322,"context_line":"   OpenStack Powered mark was intended to convey support for \"core\" level"},{"line_number":323,"context_line":"   of interoperability.  Adding a potentially large number of projects"},{"line_number":324,"context_line":"   that are not as widely adopted to this mark would substantially alter"},{"line_number":325,"context_line":"   it\u0027s meaning, and would create some confusion in the market."},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"4. Increased workload on the Interop Working Group.  Careful consideration"},{"line_number":328,"context_line":"   of capabilities for the projects already in the OpenStack Powered"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_d7188e76","line":325,"range":{"start_line":320,"start_character":3,"end_line":325,"end_character":63},"updated":"2017-06-21 02:40:04.000000000","message":"Does one distribution get multiple Powered by OpenStack Logos? Say one for \"core\", one for \"vertical\" and several for add-ons? If yes, is it a single submission or separate submission for each logo?\n\nIf vendor need to change configuration for their distro deployment for different LOGOs how does Interop group capture it in submission? Is there a requirement for a submission for a vendor to provide additional info with submission, like config, with submission results?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":317,"context_line":"   (as they presumably would be if they are drafting a Guideline"},{"line_number":318,"context_line":"   themselves rather than the Interop Working Group doing so)."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"3. Changing Criteria.  The Criteria for the existing OpenStack Powered"},{"line_number":321,"context_line":"   program were created with the \"core\" of OpenStack in mind, and the"},{"line_number":322,"context_line":"   OpenStack Powered mark was intended to convey support for \"core\" level"},{"line_number":323,"context_line":"   of interoperability.  Adding a potentially large number of projects"},{"line_number":324,"context_line":"   that are not as widely adopted to this mark would substantially alter"},{"line_number":325,"context_line":"   it\u0027s meaning, and would create some confusion in the market."},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"4. Increased workload on the Interop Working Group.  Careful consideration"},{"line_number":328,"context_line":"   of capabilities for the projects already in the OpenStack Powered"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_d954f8cc","line":325,"range":{"start_line":320,"start_character":3,"end_line":325,"end_character":63},"in_reply_to":"5f201791_d7188e76","updated":"2017-06-23 02:46:17.000000000","message":"Good question: yes, it should absolutely be possible for a single product to qualify for multiple logos.  Theoretical example: if I ship an OpenStack distribution, it might provide everything needed for \"OpenStack Powered Platform\" and also meet the additional requirements of \"OpenStack Ready NFV\".  The way we envision the testing happening is basically that you run a battery of tests and submit the results to RefStack.  Refstack can show you how those results stack up against any approved guideline that follows the schema, so one submission could theoretically suffice for multiple programs.  Again, this goes back to the concept that whenever possible, a vertical program should be mutually exclusive with OpenStack Powered.  That said, it might be possible that two vertical programs are mutually exclusive to each other or require a product (let\u0027s use the example of a distribution again since those tend to be malleable) to be configured differently in order to meet two different programs\u0027 requirements.  If we come to that bridge and need to cross it, I don\u0027t see any particular reason why two submissions would not suffice.\n\n\nWe do not plan on making a blanket assertion about additional information in this document.  Rather, that\u0027s something we will define when we actually get down to the point of creating a program (and frankly that may stem from feedback from the Foundation).  Think of it in much the same way that we deal with Powered today: when the Powered program was first introduced we merely required test results (could be from Tempest, could be from Refstack client running Tempest, could be just the required tests, could be all tests, meh).  Over time those requirements changed (for example, we now require results to be submitted via Refstack as that centralizes information and makes the Foundation\u0027s life easier).","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":324,"context_line":"   that are not as widely adopted to this mark would substantially alter"},{"line_number":325,"context_line":"   it\u0027s meaning, and would create some confusion in the market."},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"4. Increased workload on the Interop Working Group.  Careful consideration"},{"line_number":328,"context_line":"   of capabilities for the projects already in the OpenStack Powered"},{"line_number":329,"context_line":"   program is already a very demanding task.  Going through the same"},{"line_number":330,"context_line":"   process for a potentially much larger list of projects would create"},{"line_number":331,"context_line":"   a bottleneck."},{"line_number":332,"context_line":""},{"line_number":333,"context_line":"With that said, the OpenStack community would still like to address the"},{"line_number":334,"context_line":"desire for interoperable implementations for those who do choose to deploy"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_b775129b","line":331,"range":{"start_line":327,"start_character":3,"end_line":331,"end_character":16},"updated":"2017-06-21 02:40:04.000000000","message":"How do we capture anonymous submission of Tempest results for add-ons and verticals to gauge adoption?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":324,"context_line":"   that are not as widely adopted to this mark would substantially alter"},{"line_number":325,"context_line":"   it\u0027s meaning, and would create some confusion in the market."},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"4. Increased workload on the Interop Working Group.  Careful consideration"},{"line_number":328,"context_line":"   of capabilities for the projects already in the OpenStack Powered"},{"line_number":329,"context_line":"   program is already a very demanding task.  Going through the same"},{"line_number":330,"context_line":"   process for a potentially much larger list of projects would create"},{"line_number":331,"context_line":"   a bottleneck."},{"line_number":332,"context_line":""},{"line_number":333,"context_line":"With that said, the OpenStack community would still like to address the"},{"line_number":334,"context_line":"desire for interoperable implementations for those who do choose to deploy"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_39ae4c98","line":331,"range":{"start_line":327,"start_character":3,"end_line":331,"end_character":16},"in_reply_to":"5f201791_b775129b","updated":"2017-06-23 02:46:17.000000000","message":"Likely the same way we do for Powered today.  We currently recommend that vendors run all Tempest tests rather than just the ones required for Powered so that next time we do scoring, we can go look at those test results and see if a capability we\u0027re thinking about adding is something a lot of products appear to support (note: we currently do not *require* vendors to run all Tempest tests, though that\u0027s something being discussed).  I\u0027d envision that these programs would work similarly: if we\u0027re creating a program for Designate we\u0027d ask that vendors run all the Designate tests even though we only require them to pass a certain subset.  \n\nJust to note here for those that might not be aware: that the current Guideline schema has a field to list test repositories (currently they\u0027re all Tempest, but you could also point to project trees without changing the schema), so when we say \"all\" here we\u0027re definitely not talking \"all tests in all projects in all repositories in the OpenStack git space\". \u003d)","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":8434,"name":"Rochelle Grober","email":"rochelle.grober@huawei.com","username":"rockyg"},"change_message_id":"4731d1ba4d9b3b0df9db2ef8290b4c39af6cb861","unresolved":false,"context_lines":[{"line_number":367,"context_line":"   Designate (which was deployed in only 8% of production clouds"},{"line_number":368,"context_line":"   in the `April 2017 User Survey \u003chttps://www.openstack.org/assets/survey/April2017SurveyReport.pdf\u003e`_),"},{"line_number":369,"context_line":"   the criteria might be read as \"widely deployed among products that"},{"line_number":370,"context_line":"   include Trove\".  Creating a recordset with the v2 API might be"},{"line_number":371,"context_line":"   a capability that most Trove deployments provide, even if that"},{"line_number":372,"context_line":"   is a small subnet of overall OpenStack implementations provide."},{"line_number":373,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_385a2583","line":370,"range":{"start_line":370,"start_character":3,"end_line":370,"end_character":17},"updated":"2017-06-28 23:36:53.000000000","message":"You state Designate above then say widely deployed among products that include Trove ???? Do you mean Designate here?","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"7f12d62d0cc61461e119394d347e0d7a349f57e4","unresolved":false,"context_lines":[{"line_number":367,"context_line":"   Designate (which was deployed in only 8% of production clouds"},{"line_number":368,"context_line":"   in the `April 2017 User Survey \u003chttps://www.openstack.org/assets/survey/April2017SurveyReport.pdf\u003e`_),"},{"line_number":369,"context_line":"   the criteria might be read as \"widely deployed among products that"},{"line_number":370,"context_line":"   include Trove\".  Creating a recordset with the v2 API might be"},{"line_number":371,"context_line":"   a capability that most Trove deployments provide, even if that"},{"line_number":372,"context_line":"   is a small subnet of overall OpenStack implementations provide."},{"line_number":373,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f2577a7_d361b13b","line":370,"range":{"start_line":370,"start_character":3,"end_line":370,"end_character":17},"in_reply_to":"5f201791_385a2583","updated":"2017-09-11 03:57:56.000000000","message":"Any project name suffices here really; it\u0027s just illustrating a concept.  But sure--may as well make it more consistent with the rest of the doc.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"a8e5fafbed76b0a611332b0111939bb2afab9d9d","unresolved":false,"context_lines":[{"line_number":369,"context_line":"   the criteria might be read as \"widely deployed among products that"},{"line_number":370,"context_line":"   include Trove\".  Creating a recordset with the v2 API might be"},{"line_number":371,"context_line":"   a capability that most Trove deployments provide, even if that"},{"line_number":372,"context_line":"   is a small subnet of overall OpenStack implementations provide."},{"line_number":373,"context_line":""},{"line_number":374,"context_line":"3. Project teams should be directly responsible for the selection of"},{"line_number":375,"context_line":"   capabilities, tests, and designated sections for their add-on programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_b261a03c","line":372,"range":{"start_line":372,"start_character":14,"end_line":372,"end_character":20},"updated":"2017-06-21 02:40:04.000000000","message":"subnet -\u003e subset","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":6754,"name":"Mark T. Voelker","email":"markvoelker@gmail.com","username":"mvoelker"},"change_message_id":"8b634c333ceeaed07c4815e248cbf7d0ad675af6","unresolved":false,"context_lines":[{"line_number":369,"context_line":"   the criteria might be read as \"widely deployed among products that"},{"line_number":370,"context_line":"   include Trove\".  Creating a recordset with the v2 API might be"},{"line_number":371,"context_line":"   a capability that most Trove deployments provide, even if that"},{"line_number":372,"context_line":"   is a small subnet of overall OpenStack implementations provide."},{"line_number":373,"context_line":""},{"line_number":374,"context_line":"3. Project teams should be directly responsible for the selection of"},{"line_number":375,"context_line":"   capabilities, tests, and designated sections for their add-on programs."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_f98fb42b","line":372,"range":{"start_line":372,"start_character":14,"end_line":372,"end_character":20},"in_reply_to":"5f201791_b261a03c","updated":"2017-06-23 02:46:17.000000000","message":"Thanks, good catch.","commit_id":"1538f7ff29dc6c5b92a3c7f556a164d700edb90d"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":22,"context_line":"discuss the current \"OpenStack Powered\" program as a means of comparison."},{"line_number":23,"context_line":"It is important to note that of these, only the \"OpenStack Powered\" program is"},{"line_number":24,"context_line":"currently an established program approved by the OpenStack Foundation"},{"line_number":25,"context_line":"and in use today.  The \"add-ons\" and \"verticals\" programs have not yet"},{"line_number":26,"context_line":"been finalized and are still in development with a target implementation"},{"line_number":27,"context_line":"date of January 2018 (though early discussion have"},{"line_number":28,"context_line":"been carried out in several public forums to date, including Interop WG"},{"line_number":29,"context_line":"meetings, Board of Directors meetings, the PTG, etc)."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_7d9cda5c","line":26,"range":{"start_line":25,"start_character":20,"end_line":26,"end_character":43},"updated":"2017-09-12 22:00:12.000000000","message":"Recommend we get feedback from UC SIGs as UC have multiple SIG already that are focused on vertical use cases and formed by user communities that are using OpenStack: https://wiki.openstack.org/wiki/Category:Working_Groups\n\nIt is also good to formally align interop vertical use cases with the UC WG. That is preference for creating interop use-case logo program should be given to existing UC WG. Interop WG should not create its own use cases separately from UC WG since there is no user community asking for application interoperability for it.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":32,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"OpenStack is tremendously flexible, feature-rich, powerful software that can"},{"line_number":35,"context_line":"be used to create clouds that fit a wide variety of use cases including"},{"line_number":36,"context_line":"software development, web services and e-commerce, network functions"},{"line_number":37,"context_line":"virtualization (NFV), video processing, and content delivery to name a few."},{"line_number":38,"context_line":"Commercial offerings built on OpenStack are available as public clouds,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_dddd0e15","line":35,"range":{"start_line":35,"start_character":18,"end_line":35,"end_character":24},"updated":"2017-09-12 22:00:12.000000000","message":"do we want to restrict ourselves to cloud? Or deal with definition of what cloud is?\nSpecifically, if we have a use-case of using subset of OpenStack projects for IaaS for container env is it a cloud? is swift object storage a cloud?","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":157,"context_line":"and Board of Directors).  Within the constraints of the use case being"},{"line_number":158,"context_line":"addressed, there is also an interest in interoperable implementations."},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"To illustrate, we might use the example of Network Functions"},{"line_number":161,"context_line":"Virtualization (NFV).  If a provider wishes to use OpenStack as part of"},{"line_number":162,"context_line":"an NFV offering, the provider might need some capabilities from OpenStack"},{"line_number":163,"context_line":"that are currently not required under the OpenStack Powered (TM) program."},{"line_number":164,"context_line":"These might include capabilities like SR-IOV support, NUMA-aware scheduling,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_d88f5c21","line":161,"range":{"start_line":160,"start_character":0,"end_line":161,"end_character":20},"updated":"2017-09-12 22:00:12.000000000","message":"Love this example.\nFirst, we have NFV WG under UC because we have a large user community that ask for support of this use case, drive requirements for this use case, and work in various projects so that functionality is developed and delivered.\nThen they worried about application portability and interoperability across openstack solution providers for this use-case.\n\nPerfect example of tied to user community WG in UC that asks for it. We should make this a requirement for the future use-case interop program creation.\n\nThe current 3 logo programs are defined by initial OpenStack public/private cloud use case.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":181,"context_line":""},{"line_number":182,"context_line":".. figure:: ../images/vertical-program-conceptual.png"},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"Our current inclination for these programs is to re-use as much of the"},{"line_number":185,"context_line":"process, tooling, and framework established in the creation of the"},{"line_number":186,"context_line":"OpenStack Powered (TM) program as is practical.  The following points"},{"line_number":187,"context_line":"indicate our current thinking on these programs:"},{"line_number":188,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_d3e97f1a","line":185,"range":{"start_line":184,"start_character":0,"end_line":185,"end_character":8},"updated":"2017-09-12 22:00:12.000000000","message":"Before we dive into how to create and run it, let define what is the goal, what is value proposition we are delivering to users/operators/customers with logo for specific use-case.\n\nThen we can talk about implementation details.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":203,"context_line":"   for the existing OpenStack Powered program, but applied to a narrower"},{"line_number":204,"context_line":"   audience that has an interest in the specific use case."},{"line_number":205,"context_line":""},{"line_number":206,"context_line":"   a. For example, one Criteria used in the OpenStack Powered program is"},{"line_number":207,"context_line":"   \"widely deployed\".  If we were to create a vertical program for"},{"line_number":208,"context_line":"   NFV, the criteria might be read as \"widely deployed among OpenStack"},{"line_number":209,"context_line":"   products used for NFV\".  Thus, a project or capability that doesn\u0027t"},{"line_number":210,"context_line":"   qualify as \"widely deployed\" for a general audience might qualify"},{"line_number":211,"context_line":"   if it is widely used among NFV deployments."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"   b. As with the OpenStack Powered program vertical programs are"},{"line_number":214,"context_line":"   designed to include Designated Sections of code that are under"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_336fa393","line":211,"range":{"start_line":206,"start_character":3,"end_line":211,"end_character":45},"updated":"2017-09-12 22:00:12.000000000","message":"suggest adding another criteria. That is multiple vendors that are ready to participate in this vertical use-case program and submit their solution results for logo.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":214,"context_line":"   designed to include Designated Sections of code that are under"},{"line_number":215,"context_line":"   OpenStack governance."},{"line_number":216,"context_line":""},{"line_number":217,"context_line":"3. When possible, embrace adjacent communities in the design of vertical"},{"line_number":218,"context_line":"   programs."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"   a. For example: we might work with the OPNFV community in the design"},{"line_number":221,"context_line":"   of a program targeted at NFV use cases, or with the Kubernetes"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_f3eb5bd9","line":218,"range":{"start_line":217,"start_character":3,"end_line":218,"end_character":11},"updated":"2017-09-12 22:00:12.000000000","message":"+1\nsuggest extend this as defined UC WG for this adjacent community.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"cc6bb1dad5437a2ef05aeec9d341b5c66b178ba8","unresolved":false,"context_lines":[{"line_number":295,"context_line":"in the"},{"line_number":296,"context_line":"`April 2017 User Survey \u003chttps://www.openstack.org/assets/survey/April2017SurveyReport.pdf\u003e`_)."},{"line_number":297,"context_line":"Others are less widely adopted, but are still seen as very important to"},{"line_number":298,"context_line":"those users who do choose to deploy them.  Deployers of these projects"},{"line_number":299,"context_line":"would like to have some assurances about interoperable implementations, just"},{"line_number":300,"context_line":"as users of the more widely adopted set receive via the OpenStack Powered"},{"line_number":301,"context_line":"program today."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"However, there are some challenges to including these projects in the"},{"line_number":304,"context_line":"OpenStack Powered program since it is targeted at widely used, \"core\""}],"source_content_type":"text/x-rst","patch_set":7,"id":"5f2577a7_33d683c5","line":301,"range":{"start_line":298,"start_character":43,"end_line":301,"end_character":13},"updated":"2017-09-12 22:00:12.000000000","message":"SO what is the use-case for these add-on projects?\nAre they extensions of existing public/private cloud original use-case of OpenStack? \nIf yes, then the UC WG should drive prioritization of projects to add for base use-case.\n\nWho are the customers that are asking for interoperability of they applications that depend on these add-on functionality. These customers are the consumers of interop results and we need to bring them into review and decision making.","commit_id":"32b8fb2f27a509eeba69583ae8d8f11a217359eb"}]}