Hi, QA folks!

As ironic-inspector is joining the openstack/* crows, we're faces with integration testing question. At the summit we discussed with Devananda that it makes sense for inspector + ironic integration test to live in tempest with other bare metal tests.

However, judging by https://etherpad.openstack.org/p/YVR-QA-in-the-big-tent even Ironic integration tests will no longer be welcome in Tempest itself, to say nothing about pretty new Inspector.

Are there any hints now on where we can start with our integration tests? After a quick look at devstack-gate I got an impression that it's expecting tests as part of tempest:
https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L600

Our final goal is to have devstack gate test for Ironic and Inspector projects working together.

Cheers,
Dmitry

On 06/10/2015 08:07 AM, Yuiko Takada wrote:
Hi, Dmitry,

    I guess the whole idea of new release models is NOT to tie projects
    to each other any more except for The Big Release twice a year :) So
    I think no, we don't need to. We still can do it, if we have
    something to release by the time Ironic releases, but I suggest
    deciding it on case-by-case basis.

OK, I see.

One more concern, about Tempest integration test which I will implement
in V2.1.0,
it seems like that we cannot add Ironic-inspector's tests into Tempest
even if integration tests.
Please see:
https://etherpad.openstack.org/p/YVR-QA-in-the-big-tent

Good catch. I guess the answer depends on where Ironic integration tests are going to live - we're going to live with them. Let me retarget this thread to a wider audience.


But I heard from you that Devananda thinks we need this in tempest
itself. [3]
Do you know something like current situation?


Best Regards,
Yuiko Takada

2015-06-09 15:59 GMT+09:00 Dmitry Tantsur <[email protected]
<mailto:[email protected]>>:

    On 06/09/2015 03:49 AM, Yuiko Takada wrote:

        Hi, Dmitry,

        Thank you for notifying.

             I've updated our summit etherpad [3] with whatever priorities I
             remembered, please have a look. I've also untargeted a few
        things in
             launchpad [4] (and will probably untarget more later on).
        Please
             assign yourself, if you want something done in this release
        time frame.

        I've assigned one item to myself in [3], and also I added one BP
        to [4],
        so please take a look.
        https://blueprints.launchpad.net/ironic-inspector/+spec/delete-db-api


    Looks good, though I don't think it's a big priority for 2.0.0.
    Definitely worth doing for 2.1.0.

    Thanks for assigning for tempest work, that's definitely a priority
    right now.


        BTW, how do you think about Ironic-inspector's release model?
        You wrote "Version released with Ironic Liberty" as
        Ironic-inspector Version 2.1.0 in etherpad [3],
        but as you know, Ironic's release model has changed to feature
        releases.(right?)
        Should we make our release model same as Ironic?


    I guess the whole idea of new release models is NOT to tie projects
    to each other any more except for The Big Release twice a year :) So
    I think no, we don't need to. We still can do it, if we have
    something to release by the time Ironic releases, but I suggest
    deciding it on case-by-case basis.



        Best Regards,
        Yuiko Takada(Inspector team member)

        2015-06-08 20:38 GMT+09:00 Dmitry Tantsur <[email protected]
        <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>>:


             Hello, Inspector team!

             The renaming process is going pretty well, the last thing
        we need to
             do is to get Infra approval and actual rename [1][2].

             I'd like to allow people (e.g. myself) to start packaging
        inspector
             under it's new name, so I'd like to make 2.0.0 release as
        soon as
             possible (as opposed to scheduling it to particular date). All
             breaking changes should land by this release - I don't
        expect 3.0.0
             soon :)

             I've updated our summit etherpad [3] with whatever priorities I
             remembered, please have a look. I've also untargeted a few
        things in
             launchpad [4] (and will probably untarget more later on).
        Please
             assign yourself, if you want something done in this release
        time frame.

             I would like 2.1.0 to be released with Ironic Liberty and be
             properly supported.

             Let me know what you think.

             Cheers,
             Dmitry

             [1] https://review.openstack.org/#/c/188030/
             [2] https://review.openstack.org/#/c/188798/
             [3] https://etherpad.openstack.org/p/liberty-ironic-discoverd
             [4]
        https://bugs.launchpad.net/ironic-inspector/+milestone/2.0.0


        
__________________________________________________________________________
             OpenStack Development Mailing List (not for usage questions)
             Unsubscribe:
        [email protected]?subject:unsubscribe
        <http://[email protected]?subject:unsubscribe>

        <http://[email protected]?subject:unsubscribe>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




        
__________________________________________________________________________
        OpenStack Development Mailing List (not for usage questions)
        Unsubscribe:
        [email protected]?subject:unsubscribe
        <http://[email protected]?subject:unsubscribe>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:
    [email protected]?subject:unsubscribe
    <http://[email protected]?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to