Roman, this was already discussed in [1]. The conclusion was that we will implement new features in both places so user will not have to use "old" fuelclient to do some things and the "new" to others. There were no progress with moving old commands to new CLI and I didn't seen plans to do so. IMHO without a detailed plan on migrating old commands to new client and without a person (or people) that will drive this task we *cannot* freeze old fuelclient as new one is still not fully usable. Best, Sebastian [1] http://lists.openstack.org/pipermail/openstack-dev/2015-July/070279.html 2015-10-14 10:56 GMT+02:00 Roman Prykhodchenko <me at romcheg.me>: > Fuelers, > > as you know a big effort has been put into making Fuel Client’s CLI better > and as a result we got a new fuel2 utility with a new set of commands and > options. Some folks still put great effort to move everything that’s left > in the old CLI to the new CLI. > > Every new thing added to the old CLI moves the point where we can finally > remove it to the future. My proposal is to do a hard code freeze for the > old CLI and only add new stuff to the new one. > > > - romcheg > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151014/43486e96/attachment.html>