Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI
Dell - Internal Use - Confidential Normally I would say keep the original clis for a cycle but it also makes it more difficult to migrate them to using cliff. So I would vote for removing old entry points. Reworking any workflows consuming the old entry points, to use the new ones, should be pretty trivial. Thanks, dp From: Masayuki Igawa [mailto:masayuki.ig...@gmail.com] Sent: Monday, November 16, 2015 8:40 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI Hi tempest CLI users and developers, Now, we are improving Tempest CLI as we discussed at the summit[1] and migrating legacy commands to tempest cli[2]. In this situation, my concern is 'CLI compatibility'. If we'll drop old CLIs support(like my patch), it might break existing workflows. So I think there are two options. 1. Deprecate old tempest CLIs in this Mitaka cycle and we'll drop them at the beginning of the N cycle. 2. Drop old tempest CLIs in this Mitaka cycle when new CLIs will be implemented. # Actually, I'd like to just drop old CLIs. :) If you have question and/or opinion, please let me know. [1] https://etherpad.openstack.org/p/tempest-cli-improvements [2] https://review.openstack.org/#/c/240399/ Best Regards, -- Masayuki Igawa __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI
On Wed, Nov 18, 2015 at 8:16 AM Masayuki Igawawrote: > 2015年11月18日(水) 5:37 Matthew Treinish : > >> On Tue, Nov 17, 2015 at 01:39:34AM +, Masayuki Igawa wrote: >> > Hi tempest CLI users and developers, >> > >> > Now, we are improving Tempest CLI as we discussed at the summit[1] and >> > migrating legacy commands to tempest cli[2]. >> > >> > In this situation, my concern is 'CLI compatibility'. >> > If we'll drop old CLIs support(like my patch), it might break existing >> > workflows. >> > >> > So I think there are two options. >> > 1. Deprecate old tempest CLIs in this Mitaka cycle and we'll drop them >> at >> > the beginning of the N cycle. >> > 2. Drop old tempest CLIs in this Mitaka cycle when new CLIs will be >> > implemented. >> > # Actually, I'd like to just drop old CLIs. :) >> >> As would I, but I agree we need to worry about existing users out there >> and >> being nice to them. >> >> I think we should do option #1, but in [2] we also maintain the old entry >> point. >> We also have the function called by the old entry points emit a single >> warning >> that says to use the new CLI. This way we have the new entry points all >> setup >> and we indicate that everyone should move over to them. >> >> If you started with the tempest-verify-config script you actually would >> would >> fail because devstack currently uses it. So doing the switchover >> gracefully I >> think would be best, because this is the same issue users will >> potentially hit. >> > > Thank you for clarifying. > Sure, it sounds reasonable to me. I'll try to maintain the old entry > point, too. > +1, thank you! > > Best Regards, > -- Masayuki Igawa > > > >> >> > > > >> > If you have question and/or opinion, please let me know. >> > >> > [1] https://etherpad.openstack.org/p/tempest-cli-improvements >> > [2] https://review.openstack.org/#/c/240399/ >> > >> >> -Matt Treinish >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Andrea Frittoli __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI
2015年11月18日(水) 5:37 Matthew Treinish: > On Tue, Nov 17, 2015 at 01:39:34AM +, Masayuki Igawa wrote: > > Hi tempest CLI users and developers, > > > > Now, we are improving Tempest CLI as we discussed at the summit[1] and > > migrating legacy commands to tempest cli[2]. > > > > In this situation, my concern is 'CLI compatibility'. > > If we'll drop old CLIs support(like my patch), it might break existing > > workflows. > > > > So I think there are two options. > > 1. Deprecate old tempest CLIs in this Mitaka cycle and we'll drop them > at > > the beginning of the N cycle. > > 2. Drop old tempest CLIs in this Mitaka cycle when new CLIs will be > > implemented. > > # Actually, I'd like to just drop old CLIs. :) > > As would I, but I agree we need to worry about existing users out there and > being nice to them. > > I think we should do option #1, but in [2] we also maintain the old entry > point. > We also have the function called by the old entry points emit a single > warning > that says to use the new CLI. This way we have the new entry points all > setup > and we indicate that everyone should move over to them. > > If you started with the tempest-verify-config script you actually would > would > fail because devstack currently uses it. So doing the switchover > gracefully I > think would be best, because this is the same issue users will potentially > hit. > Thank you for clarifying. Sure, it sounds reasonable to me. I'll try to maintain the old entry point, too. Best Regards, -- Masayuki Igawa > > > > > If you have question and/or opinion, please let me know. > > > > [1] https://etherpad.openstack.org/p/tempest-cli-improvements > > [2] https://review.openstack.org/#/c/240399/ > > > > -Matt Treinish > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI
On Tue, Nov 17, 2015 at 01:39:34AM +, Masayuki Igawa wrote: > Hi tempest CLI users and developers, > > Now, we are improving Tempest CLI as we discussed at the summit[1] and > migrating legacy commands to tempest cli[2]. > > In this situation, my concern is 'CLI compatibility'. > If we'll drop old CLIs support(like my patch), it might break existing > workflows. > > So I think there are two options. > 1. Deprecate old tempest CLIs in this Mitaka cycle and we'll drop them at > the beginning of the N cycle. > 2. Drop old tempest CLIs in this Mitaka cycle when new CLIs will be > implemented. > # Actually, I'd like to just drop old CLIs. :) As would I, but I agree we need to worry about existing users out there and being nice to them. I think we should do option #1, but in [2] we also maintain the old entry point. We also have the function called by the old entry points emit a single warning that says to use the new CLI. This way we have the new entry points all setup and we indicate that everyone should move over to them. If you started with the tempest-verify-config script you actually would would fail because devstack currently uses it. So doing the switchover gracefully I think would be best, because this is the same issue users will potentially hit. > > If you have question and/or opinion, please let me know. > > [1] https://etherpad.openstack.org/p/tempest-cli-improvements > [2] https://review.openstack.org/#/c/240399/ > -Matt Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI
Hi tempest CLI users and developers, Now, we are improving Tempest CLI as we discussed at the summit[1] and migrating legacy commands to tempest cli[2]. In this situation, my concern is 'CLI compatibility'. If we'll drop old CLIs support(like my patch), it might break existing workflows. So I think there are two options. 1. Deprecate old tempest CLIs in this Mitaka cycle and we'll drop them at the beginning of the N cycle. 2. Drop old tempest CLIs in this Mitaka cycle when new CLIs will be implemented. # Actually, I'd like to just drop old CLIs. :) If you have question and/or opinion, please let me know. [1] https://etherpad.openstack.org/p/tempest-cli-improvements [2] https://review.openstack.org/#/c/240399/ Best Regards, -- Masayuki Igawa __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev