Open Stack

hi,

On Sat, Oct 17, 2015 at 12:50 AM, Eichberger, German
<german.eichberger at hpe.com> wrote:
> Hi,
>
> Just moving the tests is not sufficient since the gate jobs also need
> adjustment.

yea.
do yo have any advice how it should be done?
i submitted an experimental job [2] so that the movement can be tested at least.
how do you think?

[2] https://review.openstack.org/#/c/236762/

>
> German
>
> On 10/16/15, 1:50 AM, "Takashi Yamamoto" <yamamoto at midokura.com> wrote:
>
>>hi,
>>
>>On Thu, Oct 15, 2015 at 11:17 PM, Matthew Treinish <mtreinish at kortar.org>
>>wrote:
>>> On Thu, Oct 15, 2015 at 08:25:40PM +0900, Takashi Yamamoto wrote:
>>>> hi,
>>>>
>>>> i'm looking in fwaas tempest tests and have a question about code
>>>>location.
>>>>
>>>> currently,
>>>>
>>>> - fwaas api tests and its rest client are in neutron repo
>>>
>>> This is a bad situation because it means that we're directly coupling
>>>fwaas to
>>> the neutron repo. Everything that depends on fwaas should be separate
>>>and self
>>> contained outside of the neutron repo. The longer that things are like
>>>this it
>>> will just lead to more headaches down the road.
>>>
>>>> - there are no fwaas scenario tests
>>>>
>>>> eventually,
>>>>
>>>> - 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, [1]
>>is there easy way to run them together with the rest of neutron api tests
>>for gate-neutron-dsvm-api job?
>>
>>[1] https://review.openstack.org/#/c/235790/
>>
>>>
>>>> - the rest client will be in tempest-lib
>>>
>>> The discussion on which clients are in scope for tempest-lib hasn't
>>>fully
>>> happened yet. For right now we're taking a conservative approach and
>>>the clients
>>> can live in tempest-lib if there are tests in the tempest tree using
>>>them.
>>> (which is not fwaas) This might change eventually, (there will be a
>>>summit
>>> session on it) but for right now I'd say the fwaas clients should live
>>>in the
>>> fwaas repo. (they can and likely should still be based on the
>>>tempest-lib rest
>>> client)
>>>
>>> -Matt Treinish
>>>
>>>
>>>_________________________________________________________________________
>>>_
>>> 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
>>>
>>
>>__________________________________________________________________________
>>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
>
>
> __________________________________________________________________________
> 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