Re: [openstack-dev] [all] removing XML testing completely from Tempest
On 11/25/2014 03:28 AM, Flavio Percoco wrote: On 24/11/14 08:56 -0500, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. Lets get rid of it, once and for all. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev This was discussed last night in the cross project meeting, and there was a pretty resounding *do it* - http://eavesdrop.openstack.org/meetings/project/2014/project.2014-11-25-21.01.log.html The patch stream to accomplish it is here - https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:rmxml,n,z +1s for non core members that are in favor, especially potentially affected PTLs, appreciated. -Sean -- Sean Dague http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
On 24/11/14 08:56 -0500, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. Lets get rid of it, once and for all. -- @flaper87 Flavio Percoco pgpYWQLd7puPx.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] removing XML testing completely from Tempest
Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
On 11/24/2014 08:56 AM, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. But Sean, without XML support, we will lose all of our enterprise customers! -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
We are in the process of removing XML support from Keystone [1] and have provided configuration options to Tempest for testing XML in older releases [2]. However, the identity client is still tightly coupled to XML test cases. We can either fix the 309 test cases that use the XML identity client or let those cases be removed from Tempest. I'd like to let this air out a bit before I start fixing the identity client XML issues, in case XML testing is completely removed from Tempest. [1] https://review.openstack.org/#/c/125738/ [2] https://review.openstack.org/#/c/127641/ https://review.openstack.org/#/c/130874/ https://review.openstack.org/#/c/126564/ On Mon, Nov 24, 2014 at 8:03 AM, Jay Pipes jaypi...@gmail.com wrote: On 11/24/2014 08:56 AM, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. But Sean, without XML support, we will lose all of our enterprise customers! -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
On 11/24/2014 12:36 PM, Lance Bragstad wrote: We are in the process of removing XML support from Keystone [1] and have provided configuration options to Tempest for testing XML in older releases [2]. However, the identity client is still tightly coupled to XML test cases. We can either fix the 309 test cases that use the XML identity client or let those cases be removed from Tempest. I'd like to let this air out a bit before I start fixing the identity client XML issues, in case XML testing is completely removed from Tempest. I fully support and am excited about removing the xml api support. [1] https://review.openstack.org/#/c/125738/ [2] https://review.openstack.org/#/c/127641/ https://review.openstack.org/#/c/130874/ https://review.openstack.org/#/c/126564/ On Mon, Nov 24, 2014 at 8:03 AM, Jay Pipes jaypi...@gmail.com wrote: On 11/24/2014 08:56 AM, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. But Sean, without XML support, we will lose all of our enterprise customers! -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
+1 to cleanup. -- dims On Mon, Nov 24, 2014 at 12:50 PM, Monty Taylor mord...@inaugust.com wrote: On 11/24/2014 12:36 PM, Lance Bragstad wrote: We are in the process of removing XML support from Keystone [1] and have provided configuration options to Tempest for testing XML in older releases [2]. However, the identity client is still tightly coupled to XML test cases. We can either fix the 309 test cases that use the XML identity client or let those cases be removed from Tempest. I'd like to let this air out a bit before I start fixing the identity client XML issues, in case XML testing is completely removed from Tempest. I fully support and am excited about removing the xml api support. [1] https://review.openstack.org/#/c/125738/ [2] https://review.openstack.org/#/c/127641/ https://review.openstack.org/#/c/130874/ https://review.openstack.org/#/c/126564/ On Mon, Nov 24, 2014 at 8:03 AM, Jay Pipes jaypi...@gmail.com wrote: On 11/24/2014 08:56 AM, Sean Dague wrote: Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. But Sean, without XML support, we will lose all of our enterprise customers! -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] removing XML testing completely from Tempest
-Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: Monday, November 24, 2014 10:57 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [all] removing XML testing completely from Tempest Having XML payloads was never a universal part of OpenStack services. During the Icehouse release the TC declared that being an OpenStack service requires having a JSON REST API. Projects could do what they wanted beyond that. Lots of them deprecated and have been removing the XML cruft since then. Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML API for a long time. Given that current branchless Tempest only supports as far back as Icehouse anyway, after these changes were made, I'd like to propose that all the XML code in Tempest should be removed. If a project wants to support something else beyond a JSON API that's on that project to test and document on their own. We've definitively blocked adding new XML tests in Tempest anyway, but getting rid of the XML debt in the project will simplify it quite a bit, make it easier for contributors to join in, and seems consistent with the direction of OpenStack as a whole. +1 for removing XML tests from Tempest. Now Tempest contains XML tests for Nova, Keystone, Cinder, Neutron and Ceilometer. On the other hand, it contains JSON tests for all projects. XML supports of both Nova and Keystone have been marked as deprecated in Icehouse. and the XML support of Neutron has been removed already. So the remaining projects are Cinder and Ceilometer only for Tempest XML tests. I don't think it is easy that clients switch JSON/XML for each project, and I think it is a right direction to concentrate on JSON. Thanks Ken'ichi Ohmichi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
