Re: [openstack-dev] [mistral][tempest][congress] import or retain mistral tempest service client

2018-03-28 Thread Eric K
Thank you, Dougal and Ghanshyam for the responses! What I can gather is: service client registration > import service client > retaining copy. So the best thing for Congress to do now is to import the service client. On 3/17/18, 9:00 PM, "Ghanshyam Mann" wrote: >Hi

Re: [openstack-dev] [mistral][tempest][congress] import or retain mistral tempest service client

2018-03-17 Thread Ghanshyam Mann
Hi All, Sorry for late response, i kept this mail unread but forgot to respond. reply inline. On Fri, Mar 16, 2018 at 8:08 PM, Dougal Matthews wrote: > > > On 13 March 2018 at 18:51, Eric K wrote: >> >> Hi Mistral folks and others, >> >> I'm working

Re: [openstack-dev] [mistral][tempest][congress] import or retain mistral tempest service client

2018-03-16 Thread Dougal Matthews
On 13 March 2018 at 18:51, Eric K wrote: > Hi Mistral folks and others, > > I'm working on Congress tempest tests [1] for integration with Mistral. In > the tests, we use a Mistral service client to call Mistral APIs and > compare results against those obtained by

[openstack-dev] [mistral][tempest][congress] import or retain mistral tempest service client

2018-03-13 Thread Eric K
Hi Mistral folks and others, I'm working on Congress tempest tests [1] for integration with Mistral. In the tests, we use a Mistral service client to call Mistral APIs and compare results against those obtained by Mistral driver for Congress. Regarding the service client, Congress can either