Re: [Openstack] [openstack-dev] Common client version to communicate with various OpenStack releases

2017-04-10 Thread Dean Troyer
On Mon, Apr 10, 2017 at 6:46 AM, Bharat Kumar Kobagana wrote: > Which are the non-end-of-life releases, till Kilo? Everything older than Mitaka is already EOL, Mitaka happens soon. The releases page[0] shows 10 Apr 2017 (today!?) as the EOL date for Mitaka, but I don't think

Re: [Openstack] [openstack-dev] Common client version to communicate with various OpenStack releases

2017-04-10 Thread Bharat Kumar Kobagana
Hello Troyer, Thank you very much for your quick response and great help. Which are the non-end-of-life releases, till Kilo? On Apr 10, 2017 6:28 AM, "Dean Troyer" wrote: On Sat, Apr 8, 2017 at 1:57 AM, Bharat Kumar Kobagana wrote: > Is it possible use

Re: [Openstack] [openstack-dev] Common client version to communicate with various OpenStack releases

2017-04-09 Thread Dean Troyer
On Sat, Apr 8, 2017 at 1:57 AM, Bharat Kumar Kobagana wrote: > Is it possible use same Python client version to communicate with all > releases? Yes, with one recent exception. If you use the current clients you will be backward-compatible for all non-end-of-life releases,

[Openstack] [openstack-dev] Common client version to communicate with various OpenStack releases

2017-04-09 Thread Bharat Kumar Kobagana
Hello all, I have a workstation machine which communicates with various OpenStack releases (Newton, Mitaka, Liberty and Kilo) through Python clients (python-keystoneclient, python-novaclient, python-glanceclient, python-cinderclient). Is it possible use same Python client version to