Oleg, The backend part of the client was not changed dramatically due to requirements for backwards compatibility issues. ATM we do have plans to support multiple versions of the Fuel API but the work is only being scoped now. The major technical issue is that Nailgun does not provide any versioning for it’s API so on the client side it’s only possible to support multiple versions of Fuel API on the very basic level when a version of the API is directly mapped to the version of Fuel. I am not sure we will be able to support older versions of the API in the new Fuel Client due to lack of time. However, the structure of the client will allow to add that support in a pretty easy way. - romcheg > 19 трав. 2015 о 16:01 Oleg Gelbukh <ogelbukh at mirantis.com> написав(ла): > > Roman, > > This is awesome news! Thank you for this huge improvement for developers who consume Fuel API. > > Could you please elaborate on backwards compatibility between the new client and older versions of Fuel API? For example, is it possible to use the new client to work with Fuel 4.x? 5.x? > > -- > Best regards, > Oleg Gelbukh > > On Fri, May 15, 2015 at 5:39 PM, Roman Prykhodchenko <me at romcheg.me <mailto:me at romcheg.me>> wrote: > Hi folks! > > I’m glad to announce that the first independent release of Fuel Client was published to PyPi: https://pypi.python.org/pypi/python-fuelclient <https://pypi.python.org/pypi/python-fuelclient> > You can either download it from the web page or install with pip install python-fuelclient. > > What’s new: > > - Fuel client is now able to run most of it’s features remotely from Fuel’s master node. > - Old CLI was deprecated, new fuel2 utility is a preview of the new Fuel client which will be available in the next major release > - Versioning scheme of the Fuel Client is not tightly bound to Fuel’s version scheme anymore. > - Other improvements and bug-fixes > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > __________________________________________________________________________ > 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/20150525/6ccb2481/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150525/6ccb2481/attachment.pgp>