[openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?
yamamoto at midokura.com
Mon Oct 19 03:10:23 UTC 2015
On Sat, Oct 17, 2015 at 12:50 AM, Eichberger, German
<german.eichberger at hpe.com> wrote:
> Just moving the tests is not sufficient since the gate jobs also need
do yo have any advice how it should be done?
i submitted an experimental job  so that the movement can be tested at least.
how do you think?
> On 10/16/15, 1:50 AM, "Takashi Yamamoto" <yamamoto at midokura.com> wrote:
>>On Thu, Oct 15, 2015 at 11:17 PM, Matthew Treinish <mtreinish at kortar.org>
>>> On Thu, Oct 15, 2015 at 08:25:40PM +0900, Takashi Yamamoto wrote:
>>>> i'm looking in fwaas tempest tests and have a question about code
>>>> - fwaas api tests and its rest client are in neutron repo
>>> This is a bad situation because it means that we're directly coupling
>>> the neutron repo. Everything that depends on fwaas should be separate
>>> contained outside of the neutron repo. The longer that things are like
>>> will just lead to more headaches down the road.
>>>> - there are no fwaas scenario tests
>>>> - fwaas api tests should be moved into neutron-fwaas repo
>>>> - fwaaa scenario tests should be in neutron-fwaas repo too.
>>> This is definitely the right direction.
>>if i move fwaas tests from neutron to neutron-fwaas, 
>>is there easy way to run them together with the rest of neutron api tests
>>for gate-neutron-dsvm-api job?
>>>> - the rest client will be in tempest-lib
>>> The discussion on which clients are in scope for tempest-lib hasn't
>>> happened yet. For right now we're taking a conservative approach and
>>> can live in tempest-lib if there are tests in the tempest tree using
>>> (which is not fwaas) This might change eventually, (there will be a
>>> session on it) but for right now I'd say the fwaas clients should live
>>> fwaas repo. (they can and likely should still be based on the
>>> -Matt Treinish
>>> OpenStack Development Mailing List (not for usage questions)
>>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>OpenStack Development Mailing List (not for usage questions)
>>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev