[openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

lient is removed from Tempest, it would still be available via the Heat Tempest plugin. As long as the plugin implements the service client interface, the Heat service client will register automatically in the service client manager and be available for use as today. Andrea Frittoli (andreaf) [0]

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Tue, Apr 18, 2017 at 10:07 AM Arx Cruz wrote: > On Tue, Apr 18, 2017 at 10:42 AM, Steven Hardy wrote: > >> On Mon, Apr 17, 2017 at 12:48:32PM -0400, Justin Kilpatrick wrote: >> > On Mon, Apr 17, 2017 at 12:28 PM, Ben Nemec >> wrote: >> > > Tempest isn't really either of those things. Accord

Re: [openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

On Mon, Apr 17, 2017 at 7:58 PM Ihar Hrachyshka wrote: > On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier > wrote: > > We don"t run slow tests because the QA team think that they don't bring > > enough value to be executed, every time and everywhere. The idea is that > if > > some specific slow t

Re: [openstack-dev] [qa][nova][defcore] Removal of Compute Baremetal GET nodes tests from Tempest

Thanks for raising this point! On Tue, Apr 11, 2017 at 5:34 AM Ghanshyam Mann wrote: > Hi All, > > There is tempest tests for compute baremetal GET nodes tests[1]. This > tests involve ironic and nova. Ironic to create baremetal nodes and > then GET nodes using nova APIs. > Nova only provides GE

[openstack-dev] [qa] No meeting next week 13/04

Hi, a few of us will be off next week, so I'm proposing to cancel the meeting on Thursday. Let me know if you have any concern. andrea __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

Re: [openstack-dev] [tripleo] pingtest vs tempest

I don't really have much context in what the decision is going to be based on here, so I'll just add some random comments here and there. On Thu, Apr 6, 2017 at 12:48 PM Arx Cruz wrote: > Having tempest running will allow these jobs to appear in openstack-health > system as well. > I agree that

Re: [openstack-dev] [QA][intel-nfv-ci-tests][octavia][tap-as-a-service][vmware-nsx][networking-sfc] Refactor of Tempest scenario base classes

andrea On Fri, Mar 24, 2017 at 2:55 PM Andrea Frittoli wrote: > Status update on the scenario manager base class: > > - 13 patches merged > - 6 patches ready (on master) > - 2 patches ready (on stable branches) > > Details: https://etherpad.openstack.org/p/tempest-manager-plug

Re: [openstack-dev] [devstack] experimenting with systemd for services

On Wed, Apr 5, 2017 at 9:14 PM Sean Dague wrote: > At the PTG clayg brought up an excellent question about what the > expected flow was to restart a bunch of services in devstack after a > code changes that impacts many of them (be it common code, or a > library). People had created a bunch of va

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On Fri, 24 Mar 2017, 5:06 p.m. Lauren Sell, wrote: > Hi everyone, > > We’ve been talking for some time about updating the project navigator, and > we have a draft ready to share for community feedback before we launch and > publicize it. One of the big goals coming out of the joint TC/UC/Board >

Re: [openstack-dev] [QA][blazar][intel-nfv-ci-tests][nova-lxd][octavia][tap-as-a-service][vmware-nsx][barbican] Refactor of Tempest scenario base classes

to this. thank you andrea On Sat, Mar 18, 2017 at 12:04 PM Andrea Frittoli wrote: > Status update. > > Thanks to all your work, we are getting close to finishing this work! > > - 12 patches merged > - 7 patches ready, pending approval > - 2 patches (on stable branches) with

Re: [openstack-dev] [qa][cinder] RFC: Cinder test on Tempest

On Wed, Mar 22, 2017 at 8:31 PM Sean McGinnis wrote: > On Wed, Mar 22, 2017 at 01:08:23PM -0700, Ken'ichi Ohmichi wrote: > > Hi, > > > > Now we need to update Tempest for following Cinder API status. > > I have an idea for restructuring and happy to see feedback about that. > > > > Now Cinder API

Re: [openstack-dev] [QA] [Patrole] Nominating Felipe Monteiro for patrole core

On Thu, Mar 16, 2017 at 6:32 PM BARTRA, RICK wrote: > Felipe has done a tremendous amount of work stabilizing, enabling gates, > contributing new tests, and extensively reviewing code in the Patrole > project. In fact, he is the number one contributor to Patrole in terms of > lines of code. He is

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

patches that need a review, any help would be much appreciated! Thank you andrea On Wed, Mar 15, 2017 at 3:56 PM Andrea Frittoli wrote: > On Wed, Mar 15, 2017 at 11:38 AM Dmitry Tantsur > wrote: > > On 02/27/2017 12:34 PM, Andrea Frittoli wrote: > > Hello folks, > >

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

nk you, much appreciated! > > > -Solio > > > > *From: *Andrea Frittoli > *Reply-To: *"OpenStack Development Mailing List (not for usage > questions)" > *Date: *Tuesday, March 7, 2017 at 3:28 PM > *To: *"OpenStack Development Mailing List (not for

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On Fri, Mar 17, 2017 at 1:03 PM Sean Dague wrote: > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > The patch that reduced the number of Tempest Scenarios we run in every > > job and also reduce the test run concurrency [0] was merged 13 days ago. > > Since, the situation (i.e the high number o

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

On Thu, 16 Mar 2017, 9:34 a.m. Thierry Carrez, wrote: > Kendall Nelson wrote: > > We have a very limited slots available for interested projects so it > > will be a first come first served process. Let me know if you are > > interested and I will reserve a slot for you if there are spots left. >

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

QA would love to have a slot for new contributors to QA projects and plugins. On Wed, 15 Mar 2017, 8:21 p.m. Rob Cresswell (rcresswe), wrote: > Horizon would love the opportunity to baffle newcomers. > This could also be useful for the many plugins that are managed by their > respective service

[openstack-dev] [QA] Forum Boston - Brainstorming

Hello folks, I set up an etherpad [0] for the QA team to track topic ideas / proposals for the Forum [1]. Please feel free to contribute ideas, we'll have a slot to discuss about this during our meetings starting tomorrow. Andrea [0] https://etherpad.openstack.org/p/BOS-QA-brainstorming [1] http

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

On Wed, Mar 15, 2017 at 11:38 AM Dmitry Tantsur wrote: > On 02/27/2017 12:34 PM, Andrea Frittoli wrote: > > Hello folks, > > > > TL;DR: if today you import manager,py from tempest.scenario please > maintain a > > copy of [0] in tree until further notice. > >

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 8, 2017 at 8:09 PM Monty Taylor wrote: > On 03/08/2017 10:31 AM, Daniel P. Berrange wrote: > > On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote: > >> Hey all, > >> > >> We have a set of old vanity redirect URLs from back when we made a URL > >> for each project: > >> > >>

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Mon, Mar 13, 2017 at 6:52 AM Ghanshyam Mann wrote: > On Sun, Mar 12, 2017 at 7:40 AM, Matt Riedemann > wrote: > > On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > > > We had a couple of sessions related to this topic at the PTG [0][1]. > > We agreed that we want to

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Sat, Mar 11, 2017 at 10:45 PM Matt Riedemann wrote: On 3/10/2017 3:02 PM, Andrea Frittoli wrote: > > We had a couple of sessions related to this topic at the PTG [0][1]. > > We agreed that we want to still maintain integration tests only in > Tempest, which means that API micr

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

On Fri, Mar 10, 2017 at 8:39 PM Ken'ichi Ohmichi wrote: > Hi John, > > Now Tempest is testing microversions only for Nova and contains some > testing framework for re-using for another projects. > On this framework, we can implement necessary microversions tests as > we want and actually many mic

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Fri, Mar 10, 2017 at 4:55 PM Sean McGinnis wrote: > > > > > As far as I can tell: > > - Cinder v1 if I'm not mistaken has been deprecated in Juno, so it's > > deprecated in all supported releases. > > - Glance v1 has been deprecated in Newton, so it's deprecated in all > > supported releases >

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Fri, Mar 10, 2017 at 1:59 AM Ghanshyam Mann wrote: On Fri, Mar 10, 2017 at 7:23 AM, Lance Bragstad wrote: On Thu, Mar 9, 2017 at 3:46 PM, Doug Hellmann wrote: Excerpts from Andrea Frittoli's message of 2017-03-09 20:53:54 +: > Hi folks, > > I'm trying to figure out what's the best ap

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Fri, Mar 10, 2017 at 3:12 PM Lance Bragstad wrote: > On Fri, Mar 10, 2017 at 8:49 AM, Andrea Frittoli < > andrea.fritt...@gmail.com> wrote: > > > > On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann > wrote: > > Excerpts from Ghanshyam Mann's message of 2017

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Fri, Mar 10, 2017 at 2:49 PM Andrea Frittoli wrote: > On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann > wrote: > > Excerpts from Ghanshyam Mann's message of 2017-03-10 10:55:25 +0900: > > On Fri, Mar 10, 2017 at 7:23 AM, Lance Bragstad > wrote: > > > >

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

#OpenStack_Block_Storage_.28Cinder.29 On Fri, Mar 10, 2017 at 2:49 PM Andrea Frittoli wrote: > On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann > wrote: > > Excerpts from Ghanshyam Mann's message of 2017-03-10 10:55:25 +0900: > > On Fri, Mar 10, 2017 at 7:23 AM,

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann wrote: > Excerpts from Ghanshyam Mann's message of 2017-03-10 10:55:25 +0900: > > On Fri, Mar 10, 2017 at 7:23 AM, Lance Bragstad > wrote: > > > > > > > > > > > On Thu, Mar 9, 2017 at 3:46 PM, Doug Hellmann > > > wrote: > > > > > >> Excerpts from An

[openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

Hi folks, I'm trying to figure out what's the best approach to fade out testing of deprecated API versions. We currently host in Tempest API tests for Glance API v1, Keystone API v2 and Cinder API v1. According to the guidelines for the "follow-standard-deprecation" tag [0], when projects that ha

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

your work on this! I would recommend to prune the imported module as much as possible as well. It would make it easier for the QA team to identify which interfaces on Tempest side should be migrated to stable. andrea On Wed, Mar 1, 2017 at 1:25 PM Andrea Frittoli wrote: > On Wed, Mar 1, 2017

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

://review.openstack.org/#/c/439291/1 > Cheers, > > Dr. Pavlo Shchelokovskyy > Senior Software Engineer > Mirantis Inc > www.mirantis.com > > On Mon, Feb 27, 2017 at 1:34 PM, Andrea Frittoli < > andrea.fritt...@gmail.com> wrote: > > Hello folks, > > TL;DR:

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

y > as well as on particular patch if we need to. > > -gmann > > On Fri, Mar 3, 2017 at 4:28 PM, Andrea Frittoli > wrote: > > Hello folks, > > we discussed a lot since the PTG about issues with gate stability; we need > a stable and reliable gate to ensure smooth progr

Re: [openstack-dev] Disabling glance v1 by default in devstack

On Fri, Mar 3, 2017 at 7:38 PM Matt Riedemann wrote: > I've got a change proposed to disable glance v1 by default in devstack > for Pike [1]. > > The glance v1 API has been deprecated for awhile now. Nova started > supporting glance v2 in Newton and removed the ability to use nova with > glance v

[openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

Hello folks, we discussed a lot since the PTG about issues with gate stability; we need a stable and reliable gate to ensure smooth progress in Pike. One of the issues that stands out is that most of the times during test runs our test VMs are under heavy load. This can be the common cause behind

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

On Wed, Mar 1, 2017 at 2:21 AM Takashi Yamamoto wrote: > hi, > > On Mon, Feb 27, 2017 at 8:34 PM, Andrea Frittoli > wrote: > > Hello folks, > > > > TL;DR: if today you import manager,py from tempest.scenario please > maintain > > a copy of [0] in tree unt

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

On Wed, Mar 1, 2017 at 12:54 PM Sean Dague wrote: > On 03/01/2017 07:35 AM, Jordan Pittier wrote: > > > > > > On Wed, Mar 1, 2017 at 3:57 AM, Ghanshyam Mann > > wrote: > > > > Doing gradual refactoring and fixing plugins time to time needs lot > > of wait

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

On Wed, Mar 1, 2017 at 12:39 PM Jordan Pittier wrote: > On Wed, Mar 1, 2017 at 3:57 AM, Ghanshyam Mann > wrote: > > Doing gradual refactoring and fixing plugins time to time needs lot of > wait and sync. > > That needs: > 1. Plugins to switch from current method usage. Plugins to have some other

[openstack-dev] [QA] Pike PTG Summary

Hi everyone, thanks to everyone who joined the QA track, hands-on session and discussions at the first PTG in Atlanta. I think it was a very productive week, it was great to meet so many of you in person. We also received a lot of feedback from the community [0]. The list of sessions is available

[openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octavia]

Hello folks, TL;DR: if today you import manager,py from tempest.scenario please maintain a copy of [0] in tree until further notice. Full message: -- One of the priorities for the QA team in the Pike cycle is to refactor scenario tests to a sane code base [1]. As they are now, c

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

by patch basis. It would slow us down too much and it would become an ongoing effort for other teams which is probably not sustainable. > -gmann > > On Mon, Feb 27, 2017 at 3:13 AM, Andrea Frittoli < > andrea.fritt...@gmail.com> wrote: > > > On Sun, Feb 26, 2017 a

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

On Sun, Feb 26, 2017 at 12:49 AM Masayuki Igawa wrote: > Hi, > > Thank you for bringing this up. > > Yeah, I understand your frustration. We already have the document about > our stable interface[1]. It says > -- > Stability > Any code that lives in tempest/lib will be treated as a stable int

Re: [openstack-dev] [QA]Removal of test runner wrapper scripts in Tempest

On Wed, Feb 22, 2017 at 10:40 AM Jordan Pittier wrote: > Hi, > I've proposed https://review.openstack.org/#/c/436983/ in Tempest which > says: > > *Remove deprecated test runner wrappers (.sh files) This patch removes > run_tempest.sh, run_tests.sh, tools/pretty_tox.sh > tools/pretty_tox_serial.s

Re: [openstack-dev] [QA] [ptg] Team photo

My bad, this link should be working: https://www.dropbox.com/sh/9svvv9cx51s1gzc/AAABHkfOTNtsUwi9Eb2GxPXLa?dl=0 The pictures are quite large so I'd rather not attach them directly. andrea On Wed, Feb 22, 2017 at 10:15 AM Yaroslav Lobankov wrote: > +1 > > Regards, > Yaroslav Lobankov. > > On Wed

[openstack-dev] [QA] [ptg] Team photo

Here are our team photos: https://www.dropbox.com/home/Public/PTG%20Atlanta%20QA%20Team andrea __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu

Re: [openstack-dev] [QA][ptg] QA Team social evening

we're meeting at the reception in 5min see you there andrea On Tue, 21 Feb 2017, 11:49 a.m. Andrea Frittoli, wrote: > Hello folks, > > I booked a table for tonight at 7:30 at Poor Calvin's [0]. It's a 15min > away from the Sheraton [1], for everyone who's answere

Re: [openstack-dev] [qa] Tempest Stable plugin interface change broke gate

Hi Graham, sorry about that, and good catch. You are right, that's a stable interface so that change should not have landed. andrea On Tue, Feb 21, 2017 at 2:51 PM Hayes, Graham wrote: > Hi. > > https://review.openstack.org/#/c/434304/ landed yesterday, which was a > change to the stable inter

Re: [openstack-dev] [QA][ptg] QA Team social evening

u later! Andrea [0] http://www.poorcalvins.com/Home [1] https://goo.gl/ADuVlX [2] http://doodle.com/poll/yxy8ts8s8te8rwwhsfrnft2i/admin On Mon, Feb 20, 2017 at 11:18 PM Andrea Frittoli wrote: Hi folks, thank you for your vote! It looks like the best option is tomorrow (Tuesday) night - there'

Re: [openstack-dev] [QA][ptg] QA Team social evening

ase let me know. Thanks! andrea On Sun, Feb 19, 2017 at 12:35 PM Andrea Frittoli wrote: > Hello, > > I'd like to propose a social evening for the folks in the QA sessions. > I prepared a doodle [0] so if you're interested please vote :) > > I added the link to the

[openstack-dev] [QA] No team meeting this week

Hello, Since most of us are at the PTG, we will not have a meeting this week (Feb 16th). Next meeting will be on March 2nd at 17:00 UTC [0]. andrea [0] https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_March_2nd_2017_.281700_UTC.29

[openstack-dev] [QA][ptg] QA Team social evening

Hello, I'd like to propose a social evening for the folks in the QA sessions. I prepared a doodle [0] so if you're interested please vote :) I added the link to the main QA etherpad [1] as well. If you know a good place to go for food or drinks please add it to the etherpad as well. Andrea [0]

Re: [openstack-dev] [QA] [all] Pike PTG QA Input / Feedback Session

[0], so we can discuss about it at the PTG and use it to improve ourselves :) On Tue, Feb 14, 2017 at 12:38 AM Andrea Frittoli wrote: > Hi folks, > > at the PTG in Atlanta we will schedule a session [0] to collect and > discuss feedback and > input from the community on existing Q

Re: [openstack-dev] [QA] Pike PTG Schedule

go, so I allocated 2 x 30min slots to most sessions. If you need a projector please book a room accordingly, and mark it on the schedule so that folks know where to go. Andrea On Wed, Feb 15, 2017 at 2:22 PM Andrea Frittoli wrote: > On Tue, Feb 14, 2017 at 3:00 PM Ken'ichi Ohmichi

Re: [openstack-dev] [QA] Pike PTG Schedule

On Tue, Feb 14, 2017 at 3:00 PM Ken'ichi Ohmichi wrote: > Hi Andrea, > > Thanks for organizing QA sessions for PTG. > > 2017-02-13 16:16 GMT-08:00 Andrea Frittoli : > > Hello team, > > > > I did some work on the etherpad [0] to organise the QA PTG schedul

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Some (new?) data on the oom kill issue in the gate. I filed a new bug / E-R query yet for the issue [1][2] since it looks to me like the issue is not specific to mysqld - oom-kill will just pick the best candidate, which in most cases happens to be mysqld. The next most likely candidate to show er

[openstack-dev] [QA] [all] Pike PTG QA Input / Feedback Session

Hi folks, at the PTG in Atlanta we will schedule a session [0] to collect and discuss feedback and input from the community on existing QA projects. We will use the resulting material in a later session to set priorities of the QA team for Pike. Note that for Tempest plugins specifically there wil

[openstack-dev] [QA] Quality Assurance logo files

-- Forwarded message - From: Heidi Joy Tretheway Date: Mon, Feb 13, 2017 at 10:09 PM Subject: Quality Assurance logo files To: , Hi Ken’ichi and Andrea, I’m excited to finally be able to share final project logo files with you. Inside this folder, you’ll find full-color and one

[openstack-dev] [QA] Pike PTG Schedule

Hello team, I did some work on the etherpad [0] to organise the QA PTG schedule based on the proposed sessions. I separated discussion sessions from hands-on type of actives. I thing the former will require a fixed schedule so folks may know when to pop-in to attend; the latter may happen more ad-

Re: [openstack-dev] [designate] Status of the project

On Thu, Feb 9, 2017 at 7:22 PM Hayes, Graham wrote: > The HTML version of this is here: > http://graham.hayes.ie/posts/openstack-designate-where-we-are/ > > I have been asked a few times recently "What is the state of the Designate > project?", "How is Designate getting on?", and by people who kn

Re: [openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

On Tue, Feb 7, 2017 at 1:55 AM Ghanshyam Mann wrote: > Hi Jordan, > > Thanks for bring it up. I know we had both side of argument on those > changes. > > IMO in general, its all QA team responsibility to verify the requirement > very strictly and make sure no changes break existing released versi

Re: [openstack-dev] gate jobs - papercuts

I actually ended-up proposing an update to the other bug, as the signature was much closed [0] andrea [0] https://bugs.launchpad.net/nova/+bug/1643911 [1] https://review.openstack.org/427754 On Wed, Feb 1, 2017 at 1:50 PM Andrea Frittoli wrote: > The first one is yet another flavour

Re: [openstack-dev] gate jobs - papercuts

The first one is yet another flavour of libvirtd crash [0]: >> *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x56108d7a7450 *** which adds to the list of three libvirt crash signatures listed by Jordan in [1]. I guess this new (?) signature could be incorporated in bug [2]

Re: [openstack-dev] [QA] Gate Jobs failing after patch for bug/1628016

On Mon, Jan 30, 2017 at 3:25 PM White, Joshua L wrote: > Hi Team, > > > > I would like to get your feedback on the gate jobs failing and how to > alleviate the issue. > > > > The gate jobs are failing once the prefix is actually added for these > tests jobs below: > > > > 1. *test_list_container_

Re: [openstack-dev] [qa] PTL non-candidacy

Thank you Ken for the great work and for your leadership! I'm really glad you'll stay in the team and keep contributing. On Fri, Jan 20, 2017 at 12:41 AM Ghanshyam Mann wrote: > Thanks Kenichi for all your hardwork and nice leadership. > > Its been very good and lot of things we finished under

[openstack-dev] [qa] PTL Candidacy for Pike

Andrea Frittoli (andreaf) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

The difficulty with integration testing is that the services under test run in processes separated from the test one(s). There is not obvious / existing mechanism to collect coverage data in this case. Several cycles back used to be a backdoor built into nova to enable coverage data collection dur

Re: [openstack-dev] tempest tests in Horizon GUI

Hi Ofer, Tempest tests try to cleanup after themselves, so in theory after a Tempest run you shouldn't see any test resource left around. If you run your tests using dynamic credentials, test accounts are created on the fly, and deleted after they're used. If you use preprovisioned credentials, y

[openstack-dev] [tempest][plugins] Service clients stable interface in tempest.lib

y if your currently using one of the unstable "Manager" interfaces today. Please reach out for help in the #openstack-qa room if you have questions on the new interfaces, trouble using them in your plugin, requests for features or feedback. Thanks for reading through. Andrea Frittoli (an

Re: [openstack-dev] [all][tc] Equal Chances for all projects (was Plugins for all)

On Mon, Jul 25, 2016 at 10:36 PM Hayes, Graham wrote: > Top posting - this is a recap of what has been said, and some > clarifications > > I realise that I was not very clear at the beginning of this process, so > here is my effort to clarify things, from the ML thread, and the review. > > > .

Re: [openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

rates, so it may be that the pass rate is already good enough. > > > Anyway we proposed the following fix to tempest [3] > > Thanks for fixing this, and sorry about the inconvenience. Even with the fix in, the Mellanox CI job failed, which if unfortunate. I issued a re-check. Andrea Fritto

[openstack-dev] [qa] Tempest pre-provisioned credentials in the gate

or [3] of the tool that pre-proprovisioned the accounts has fixed the issue: the past 8 runs of the periodic jobs have not encountered that race anymore [4][5]. Specifically I'd like to propose changing to start changing of the neutron jobs [6]. Andrea Frittoli [0] http://docs.openstack.org

Re: [openstack-dev] [qa] Tempest unstable interfaces in plugins

On Sun, Jun 12, 2016 at 2:25 PM Assaf Muller wrote: > On Sat, Jun 11, 2016 at 4:04 PM, Ken'ichi Ohmichi > wrote: > > 2016-06-10 17:01 GMT-07:00 Assaf Muller : > >> On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli > >> wrote: > >>> Dear all, >

[openstack-dev] [qa] Tempest unstable interfaces in plugins

Dear all, I'm working on making the client manager in Tempest a stable interface, so that in future it may be used safely by plugins to easily gain access service clients [0]. This work inevitably involves changing the current client manager (unstable) interface. Several tempest plugins in OpenSt

Re: [openstack-dev] StackViz is now enabled for all devstack-gate jobs

Great job, thanks! On Tue, 7 Jun 2016, 3:36 a.m. Masayuki Igawa, wrote: > Congrats! I'm looking forward to seeing an integration/collaboration > with openstack-heath :) > > On Tue, Jun 7, 2016 at 8:32 AM, Buckley, Tim Jason > wrote: > > Hello all, > > > > I'd like to announce that StackViz will

Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

On Mon, 30 May 2016, 6:25 p.m. Ken'ichi Ohmichi, wrote: > Hi, > > There are many patches which are not updated in Tempest review queue > even if having gotten negative feedback from reviewers or jenkins. > Nova team is abandoning such patches like [1]. > I feel it would be nice to abandone such p

Re: [openstack-dev] [openstack-health][QA] We need your feedbacks

I personally like Openstack Health UI/UX. I use it a lot a an initial source of information. Thanks to the OH team for all the great work on this! And +1 to the new "feedback" link on the top and bottom of every page :) A few thoughts on my experience with OH. It can take a few clicks in OH to g

Re: [openstack-dev] [QA][RFC] Skip this week meeting

I don't have anything urgent so fine with me. Andrea On Mon, 2 May 2016, 3:04 p.m. Masayuki Igawa, wrote: > Hi QA guys, > > We have very few topic this week to discuss. So I think we should skip > this week meeting. > Any thoughts? > > Best Regards, > -- Masayuki Igawa > > _

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

I look forward to the first (as far as I know) tempest plugin for a service in its own repo! :) On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham wrote: > On 04/04/2016 16:36, Jordan Pittier wrote: > > > > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham > > wrote: > > > >

Re: [openstack-dev] [neutron]: Neutron naming legal issues

LoL good one :) On Fri, Apr 1, 2016 at 6:47 AM Jimmy Akin wrote: > > Dear Neutrinos, > > We've been following the project for quite some time. > To our satisfaction the project seems to have done well; the base line of > features that were available to the networking component of OpenStack > (th

Re: [openstack-dev] How does tempest read in the variables defined in tempest.conf?

Hi, To run a multi-region scenario you need to have both regions deployed before a tempest run is started, so you would need a extra configuration items. But I'm not convinced that would be in scope for tempest - there's no single way to deploy multiple regions. To run the same scenario tests ag

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi wrote: > 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen : > > On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote: > >> Hi > >> > >> I have one proposal[1] related to negative tests in Tempest, and > >> hoping opinions before doing that. >

Re: [openstack-dev] [Neutron] [neutron-lib] adding a new flag to neutron-lib

packages from a single repo. On Mon, Mar 14, 2016 at 6:04 PM Andrea Frittoli wrote: > Hi Anil, > > Devstack will install neutron-lib from the configured pypi mirror by > default. > > To pickup the change in neutron-lib (or in a library in general) before a > release is made

Re: [openstack-dev] [Neutron] [neutron-lib] adding a new flag to neutron-lib

Hi Anil, Devstack will install neutron-lib from the configured pypi mirror by default. To pickup the change in neutron-lib (or in a library in general) before a release is made you'll need to use a -src job for that library [0], where the library is installed from source. andrea [0] http://git.

Re: [openstack-dev] [QA] Not running for PTL

Thanks Matt for the great work as PTL in the past 4 cycles! You had the fun of serving through the change in governance model, which is especially though on horizontal teams like QA - and I think you set strong foundations for QA to be successful in the big tent. andreaf On Mon, Mar 14, 2016 at

Re: [openstack-dev] [qa] openstack health accounting problem

Thanks Sean for bringing this up. It's a known pain point that we discussed back in Tokyo [0]. Failures in class level fixtures are difficult to handle consistently, because there is no concept of success / failure at class level in the data model. If a failure happens during setup, no test is a

Re: [openstack-dev] [Octavia] [Tempest] Tempest tests using tempest-plugin

All the code that is in tempest-lib is stable interface that can be consumed safely. The code in tempest instead does not provide a guaranteed stable interface, as it was not originally meant for external consumption. So while you can import it, it may change without warning (i.e. with no new tempe

Re: [openstack-dev] Gerrit Upgrade to ver 2.11 completed.

nice, thank you! On Thu, Dec 17, 2015 at 4:05 PM Zaro wrote: > forgot this one as well: https://review.openstack.org/241278 > > On Thu, Dec 17, 2015 at 7:02 AM, Zaro wrote: > > On Thu, Dec 17, 2015 at 12:31 AM, Andrea Frittoli > > wrote: > >> Thanks for the upgra

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

Thanks for the upgrade, and for all the effort you folks put into keeping our gerrit close to upstream! One thing that I find inconvenient in the new UI is the size of the middle (test results) column: it's too narrow, no matter how large my browser window is, or what browser I use - which causes

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

Looking at the tool, it seems to me that is servers a combination of functions: - provision test resources - support for distribution specific / cloud specific overrides to default - support for configuration override via CLI - discovery of configuration Test resource provisioning is something tha

Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI

>> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >

Re: [openstack-dev] [Tempest] Can we add testcase for Unshelving volume backed instance?

Hi, Yes please do. Could you file a lp bug for it? It seems to me to be a good candidate for a scenario test. Thank you Andrea On Mon, 20 Jul 2015 1:45 pm Deore, Pranali11 wrote: > Hi, > > > > Unshelving a volume backed instance was not working before merging the > patch [1]. > > > > In case

Re: [openstack-dev] [qa] Status of account creds in the [identity] section of tempest.conf

On Fri, Jun 19, 2015 at 10:30 AM Matthew Treinish wrote: > On Thu, Jun 18, 2015 at 02:13:56PM -0400, David Kranz wrote: > > We had a discussion about this at the qa meeting today around the > following > > proposal: > > > > tl;dr The test accounts feature provides the same functionality as the >

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

I'm late in my reply, but I can still give my +1 and say welcome to the team Jordan! On Mon, Jun 29, 2015 at 4:26 PM Jordan Pittier wrote: > Thanks a lot ! > I just want to say that I am happy about this and I look forward to > continue working on Tempest with you all. > > Cheers, > Jordan > > O

Re: [openstack-dev] [qa] identity v3 issue causing non-admin job to fail

Hi David, admin_domain_name is used at the moment to fill in the domain when missing in a few cases. The get_credentials method is one of them. Another two are setting the default domain for the users in tempest.conf [0], and setting the domain for credentials loaded from a YAML file [1]. [0] htt

Re: [openstack-dev] [qa] [tempest] Question on time precision in auth providers

Hi Daryl, the original reason for having a strict check in there was that the auth provider a specialised to the identity provider in use (KeystoneV2AuthProvider, KeystoneV3AuthProvider), and the timestamp format embedded in there is what's provided by keystone's identity v2 and identity v3 token

Re: [openstack-dev] [qa] [devstack] Confusion about member roles in tempest/devstack

On 6 April 2015 at 21:27, David Kranz wrote: > On 04/06/2015 03:14 PM, Matthew Treinish wrote: > > On Mon, Apr 06, 2015 at 02:25:14PM -0400, David Kranz wrote: > > There have been a number of changes in tempest recently that seem to > coordinate with devstack that are a bit unclear. > > Well, the

Re: [openstack-dev] [qa] Question about is_admin_available()

Preventing the token request could be an improvement, as the token request might not be expected to happen in that method. If the token cannot be obtained because credentials are wrong, an exception will be triggered. If we removed the token request from is_admin_available, this scenario would be

Re: [openstack-dev] [tempest] tearDownClass usage in scenario tests

Hello Rich, in the latest tempest we made two significant changes compared to the version you're using. We dropped the use of official clients from scenario tests (and OfficialClientTest has been replaced by ScenarioTest). And we introduced resource_setup and resource_cleanup in the test base cla

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

Hello Danny, I think so. Any special concern with a VM using more than one port on a subnet? andrea On 2 December 2014 at 02:04, Danny Choi (dannchoi) wrote: > Hi, > > When I attach 2 interfaces from the same subnet to a VM, there is no error > returned and > both interfaces come up. > > lab@tm

Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core

+1 On 21 Nov 2014 18:25, "Ken1 Ohmichi" wrote: > +1 :-) > > Sent from my iPod > > On 2014/11/22, at 7:56, Christopher Yeoh wrote: > > > +1 > > > > Sent from my iPad > > > >> On 22 Nov 2014, at 4:56 am, Matthew Treinish > wrote: > >> > >> > >> Hi Everyone, > >> > >> I'd like to propose we add Gh

<    1   2   3   >