Open Stack

On Tue, Nov 17, 2015 at 01:39:34AM +0000, 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151117/64dfed51/attachment.pgp>