e: Monday, January 23, 2017 at 7:55 AM
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [congress] ocata client causes feature
regression with pre-ocata server
> At some point the client somet
At some point the client sometimes made multiple API calls. I think (c)
seems right too.
Tim
On Sun, Jan 22, 2017 at 1:15 AM Monty Taylor wrote:
> On 01/21/2017 04:07 AM, Eric K wrote:
> > Hi all,
> >
> > I was getting ready to request release of congress client, but I
>
On 01/21/2017 04:07 AM, Eric K wrote:
> Hi all,
>
> I was getting ready to request release of congress client, but I
> remembered that the new client causes feature regression if used with
> older versions of congress. Specifically, new client with pre-Ocata
> congress cannot refer to datasource
Hi Tim,
I thought something like that would work. But actually python-congressclient
is not a listed requirement of congress server, no vice versa. Which is
correct in the sense that installing and running one does not require
installing the other on the same machine.
From: Tim Hinrichs
How about we go into the preocata server and change requirements.txt to
ensure it only supports the older clients. Something like...
Python-congressclient>2.3<2.5
Or whatever the versions are.
Tim
On Fri, Jan 20, 2017 at 7:07 PM Eric K wrote:
> Hi all,
>
> I was
Hi all,
I was getting ready to request release of congress client, but I
remembered that the new client causes feature regression if used with
older versions of congress. Specifically, new client with pre-Ocata
congress cannot refer to datasource by name, something that could be done
with