[openstack-dev] [QA] Liberty End-of-cycle Code Sprint

/wiki/QA/CodeSprintLibertyFortCollins Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [Tempest]No way to skip S3 related tests

On Fri, Jul 31, 2015 at 12:47:55PM +0200, Jordan Pittier wrote: Hi, With the commit [1] minimize the default services that happened in April, nova-objectstore is not run by default. Which means that by default, Devstack doesnt provide any S3 compatible API (because swift3 is not enabled by

Re: [openstack-dev] [tempest] Mellanox CI request to comment

On Mon, Aug 10, 2015 at 10:56:00AM +, Lenny Verkhovsky wrote: Hi all, Lately we discovered a bug[1] in tempest after the code was merged. To minimize such things in the future we are asking permission for our CI to comment as non-voting CI to tempest commits. As long as it's not leaving

Re: [openstack-dev] [QA] Doodle poll for New Alternating Week QA Meeting time

On Tue, Jul 07, 2015 at 11:06:41AM -0400, Matthew Treinish wrote: Hi everyone, As a follow-up from the QA meeting from 2 weeks ago I'm starting a poll to reschedule the 22:00 UTC QA meeting: http://doodle.com/eykyptgi3ca3r9mk I used the yaml2ical repo (which is awesome and makes

Re: [openstack-dev] [Cinder] python-cinderclient functional tests

On Mon, Jul 13, 2015 at 12:04:05PM -0700, Mike Perez wrote: On 16:28 Jul 10, Ivan Kolodyazhny wrote: Hi Mike, Unfortunately, we don't get a lot of stats [1] because we don't run it often. I've added 'check experimental' comment to latest python-cinderclient review request to get more

Re: [openstack-dev] [puppet] running tempest on beaker jobs

On Mon, Jul 13, 2015 at 07:50:59AM -0400, Emilien Macchi wrote: On 07/12/2015 11:29 PM, Matt Fischer wrote: We used Tempest for a time against our production environment. It was a pain to clean up but ephemeral test jobs solves that for you. A few questions: What version of

Re: [openstack-dev] [puppet] running tempest on beaker jobs

On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote: We used Tempest for a time against our production environment. It was a pain to clean up but ephemeral test jobs solves that for you. A few questions Just curious how long ago was this? Because resource leaks have always been

[openstack-dev] [QA] No Meeting until Nov. 12th

Hi everyone, Just realized I never sent out the reminder that we won't be holding our weekly meetings until after summit. Since people are travelling this week we won't be having the meeting today either. Our normal weekly meeting schedule will resume on Nov 12th. The time for the meeting that

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Tue, Nov 10, 2015 at 10:13:09AM +0100, Thierry Carrez wrote: > Matthew Treinish wrote: > > [...] > > The discussion here is about the cross project effort around stable > > branches, > > which by design is a more limited scope now. Right now the cross project &

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 05:41:53PM +0100, Thierry Carrez wrote: > Hi everyone, > > A few cycles ago we set up the Release Cycle Management team which was a > bit of a frankenteam of the things I happened to be leading: release > management, stable branch maintenance and vulnerability management.

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On Mon, Nov 09, 2015 at 05:05:36PM +1100, Tony Breeds wrote: > On Fri, Nov 06, 2015 at 10:12:21AM -0800, Clint Byrum wrote: > > > The argument in the original post, I think, is that we should not > > stand in the way of the vendors continuing to collaborate on stable > > maintenance in the

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: > > On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: > > > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > > > > > > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > > > > Hi everyone, > > > > >

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > A few cycles ago we set up the Release Cycle Management team which was a > > >

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

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

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote: > On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto > wrote: > > > hi, > > > > i'm looking in fwaas tempest tests and have a question about code location. > > > > currently, > > > > - fwaas api tests and its

[openstack-dev] [QA] Design Summit Schedule

Hi Everyone, I just pushed up the QA schedule for design summit: https://mitakadesignsummit.sched.org/overview/type/qa Let me know if there are any big schedule conflicts or other issues, so we can work through the problem. Thanks, Matt Treinish signature.asc Description: PGP signature

Re: [openstack-dev] [QA] Design Summit Schedule

On Fri, Oct 16, 2015 at 01:21:04PM +0200, Dmitry Tantsur wrote: > On 10/15/2015 06:42 PM, Matthew Treinish wrote: > > > >Hi Everyone, > > > >I just pushed up the QA schedule for design summit: > > > >https://mitakadesignsummit.sched.org/overview/type/qa

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

On Tue, Oct 20, 2015 at 11:16:38AM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2015-10-20 13:41:05 +: > > On 2015-10-20 09:31:52 -0400 (-0400), Doug Hellmann wrote: > > > Excerpts from Ben Swartzlander's message of 2015-10-19 21:02:46 -0400: > > > > I would like the

[openstack-dev] [QA][ec2-api][nova] Future of Tempest ec2 tests

ter we get things working. What I have up on github should be a good starting point that's easy to take over. Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [testing] moving testrepository *outside* the tox venv

On Sat, Jul 11, 2015 at 11:35:16AM +1200, Robert Collins wrote: On 9 July 2015 at 10:52, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote: So - I'm looking to: A) have a discussion and identify any issues with moving testr out of the

Re: [openstack-dev] [testing] moving testrepository *outside* the tox venv

On Thu, Jul 09, 2015 at 06:59:44AM -0700, Morgan Fainberg wrote: Or a database per python major version (or at least gracefully handle the incompatibility). --Morgan Sent via mobile On Jul 9, 2015, at 06:43, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Robert Collins's

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

On Tue, Nov 17, 2015 at 01:39:34AM +, Masayuki Igawa wrote: > Hi tempest CLI users and developers, > > Now, we are improving Tempest CLI as we discussed at the summit[1] and > migrating legacy commands to tempest cli[2]. > > In this situation, my concern is 'CLI compatibility'. > If we'll

[openstack-dev] subunit2html location on images changing

thing. Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [tempest] Is there a sandbox project how to use tempest test plugin interface?

On Thu, Sep 10, 2015 at 02:56:31PM +0200, Lajos Katona wrote: > Hi, > > I just noticed that from tag 6, the test plugin interface considered ready, > and I am eager to start to use it. > I have some questions: > > If I understand well in the future the plugin interface will be moved to >

[openstack-dev] [QA] Mitaka Summit Session Planning

Hi Everyone, I started an etherpad to track ideas for summit sessions: https://etherpad.openstack.org/p/mitaka-qa-summit-topics If you have an idea for a session feel free to add it to the etherpad. As we get closer to summit we'll dedicate a QA meeting to selecting which topics we'll have

Re: [openstack-dev] repairing so many OpenStack components writing configuration files in /usr/etc

On Thu, Sep 24, 2015 at 04:25:31PM +0200, Thomas Goirand wrote: > Hi, > > It's about the 3rd time just this week, that I'm repairing an OpenStack > component which is trying to write config files in /usr/etc. Could this > non-sense stop please? So I'm almost 100% that the intent for everyone

Re: [openstack-dev] repairing so many OpenStack components writing configuration files in /usr/etc

On Thu, Sep 24, 2015 at 10:57:48AM -0400, Steve Martinelli wrote: > > just a general FYI - so for pyCADF (and I'm guessing others), it was a very > subtle error: > > https://github.com/openstack/pycadf/commit/4e70ff2e6204f74767c5cab13f118d72c2594760 > > Essentially the entry points in setup.cfg

Re: [openstack-dev] [neutron] Stumped...need help with neutronclient job failure

On Thu, Sep 24, 2015 at 10:52:45AM -0700, Kevin Benton wrote: > Can you look to see what process tempest_lib is trying to execute? > > On Wed, Sep 23, 2015 at 4:02 AM, Paul Michali wrote: > > > Hi, > > > > I created a pair of experimental jobs for python-neutronclient that

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

On Tue, Dec 08, 2015 at 07:25:50PM +, Flavio Percoco wrote: > Greetings, > > I just reviewed a patch in tempest that proposed adding new tests for > the Glance's task API. While I believe it's awesome that folks in the > tempest team keep adding missing tests for projects, I think it'd be >

[openstack-dev] Announcing the OpenStack Health Dashboard

in improving it. Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Mon, Dec 07, 2015 at 06:18:04PM -0500, Steve Martinelli wrote: > > ... re-adding the operators mailing list. > > sounds like we should document how to do this, with the assertion that it > is not tested with our CI. > > with that said, we should try to have a job that sets up keystone with >

[openstack-dev] Cleaning Up Deprecation Warnings in the Gate

services with deprecated options. But, a big part is also going to be going through the logs to find out where we're using deprecated options. Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack

Re: [openstack-dev] [stable] meeting time proposal

On Wed, Dec 16, 2015 at 01:12:13PM -0600, Matt Riedemann wrote: > I'm not entirely sure what the geo distribution is for everyone that works > on stable, but I know we have people in Europe and some people in Australia. > So I was thinking alternating weekly meetings: > > Mondays at 2100 UTC > >

[openstack-dev] [QA] No meetings for the next 2 weeks

Hi Everyone, As we discussed during today's QA meeting we'll not be holding the weekly QA meeting for the next 2 weeks. Most people will be on vacation anyway, so this likely isn't a big surprise. The next meeting will be on Jan. 7th at 0900 UTC. Thanks, Matt Treinish signature.asc

Re: [openstack-dev] Cleaning Up Deprecation Warnings in the Gate

On Thu, Dec 10, 2015 at 03:03:01PM -0500, gord chung wrote: > > > On 10/12/15 12:04 PM, Matthew Treinish wrote: > >Using this query to see how many deprecation warning we emit on jobs running > >on > >master in the past 7 days: > > > >http://logstash.open

Re: [openstack-dev] [QA][Tempest] Drop javelin off tempest

On Thu, Dec 10, 2015 at 11:15:06AM +0100, Daniel Mellado wrote: > Hi All, > > In today's QA meeting we were discussing about dropping Javelin off > tempest if it's not being used anymore in grenade, as sdague pointed > out. We were thinking about this as a part of the work for [1], where we > hit

Re: [openstack-dev] [QA] No meetings for the next 2 weeks

On Thu, Dec 17, 2015 at 04:06:38PM -0500, Matthew Treinish wrote: > > Hi Everyone, > > As we discussed during today's QA meeting we'll not be holding the weekly QA > meeting for the next 2 weeks. Most people will be on vacation anyway, so this > likely isn't a big surpri

[openstack-dev] [QA] Mitaka Code Sprint

sign up using the wiki page: https://wiki.openstack.org/wiki/QA/CodeSprintMitakaBoston Thanks, Matthew Treinish signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

On Fri, Jun 03, 2016 at 01:53:16PM -0600, Matt Fischer wrote: > On Fri, Jun 3, 2016 at 1:35 PM, Lance Bragstad wrote: > > > Hey all, > > > > I have been curious about impact of providing performance feedback as part > > of the review process. From what I understand, keystone

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: > Last year, in response to Nova micro-versioning and extension updates[1], > the QA team added strict API schema checking to Tempest to ensure that > no additional properties were added to Nova API responses[2][3]. In the > last year, at

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: > > > Last year, in response to Nova micro-versioning and extension updates[1], > > > the QA team

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

On Fri, May 27, 2016 at 05:52:51PM +0300, Vasyl Saienko wrote: > Lucas, Andrew > > Thanks for fast response. > > On Fri, May 27, 2016 at 4:53 PM, Andrew Laski wrote: > > > > > > > On Fri, May 27, 2016, at 09:25 AM, Lucas Alvares Gomes wrote: > > > Hi, > > > > > > Thanks for

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Tue, Jun 14, 2016 at 12:19:54PM -0700, Chris Hoge wrote: > > > On Jun 14, 2016, at 11:21 AM, Matthew Treinish <mtrein...@kortar.org> wrote: > > > > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: > >> Last year, in response to Nova micr

Re: [openstack-dev] [tempest] the project specific config option not generated together with tempest.conf.sample

Just a note, please don't start a new thread as a reply to an existing thread. (well unless you remove the In-Reply-To header from the message) There is more details on this here: https://wiki.openstack.org/wiki/MailingListEtiquette#Threading I almost missed this because it was part of a

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Tue, Jun 14, 2016 at 05:42:16PM -0400, Doug Hellmann wrote: > Excerpts from Matthew Treinish's message of 2016-06-14 15:12:45 -0400: > > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > > > On Tue,

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Fri, Jun 17, 2016 at 04:26:49PM -0700, Mike Perez wrote: > On 15:12 Jun 14, Matthew Treinish wrote: > > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > > > On Tue, Ju

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

devs. > > > > I posted a link to this thread to the DefCore mailing list to make > > that working group aware of the outstanding issues. > > > > > On Jun 14, 2016, at 3:50 PM, Matthew Treinish <mtrein...@kortar.org> > > > wrote: > > &

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

I posted a link to this thread to the DefCore mailing list to make > > > > that working group aware of the outstanding issues. > > > > > > > > > On Jun 14, 2016, at 3:50 PM, Matthew Treinish <mtrein...@kortar.org> > > > > > wrote: > > > > > >

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

and not that of the working group > > > > > > itself, which may independently reject the idea outside of the > > > > > > response from the upstream devs. > > > > > > > > > > > > I posted a link to this thread to the De

Re: [openstack-dev] [nova][cinder] How will nova advertise that volume multi-attach is supported?

On Wed, Jan 13, 2016 at 04:52:37PM -0600, Matt Riedemann wrote: > tl;dr - do we need a REST API microversion for multi-attach support in nova? Yes, I think so > > The details: > > The volume multi-attach series in nova, starting here [1], has run into an > upgrade problem. > > Basically,

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On Wed, Jan 13, 2016 at 10:47:21PM +, Sean M. Collins wrote: > On Wed, Jan 13, 2016 at 03:57:37PM CST, Mooney, Sean K wrote: > > One of the ideas that I have been thinking about over the last month or two > > is do we > > Want to create a dedicated library file in devstack to support

Re: [openstack-dev] [tempest] BadAltAuth / Test Isolation same tenant

On Mon, Feb 08, 2016 at 06:04:15PM +0100, Vincent Gatignol wrote: > Hi there, > > I know that it's not the default configuration for openstack nor tempest but > I need to make a script that test user isolation _inside_ the same tenant. > > Some of our users are in the same tenant but they

Re: [openstack-dev] All hail the new per-region pypi, wheel and apt mirrors

On Wed, Feb 10, 2016 at 06:45:25PM -0600, Monty Taylor wrote: > Hey everybody, > > tl;dr - We have new AFS-based consistent per-region mirrors of PyPI and APT > repos with additional wheel repos containing pre-built wheels for all the > modules in global-requirements > > We've just rolled out a

Re: [openstack-dev] [stable] Kilo gate doesn't like testtools 2.0.0

On February 6, 2016 4:29:34 PM GMT+11:00, Matt Riedemann wrote: > > >On 2/4/2016 11:23 PM, Tony Breeds wrote: >> Hi All, >> Just a quick heads up that the kilo gate (and therefore anything >that >> relies on kilo)[1] is a little busted. >> >> This was

Re: [openstack-dev] [QA][Neutron] IPv6 related intermittent test failures

On Tue, Feb 02, 2016 at 05:09:47PM -0800, Armando M. wrote: > Folks, > > We have some IPv6 related bugs [1,2,3] that have been lingering for some > time now. They have been hurting the gate (e.g. [4] the most recent > offending failure) and since it looks like they have been without owners > nor

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On Thu, Jan 21, 2016 at 08:18:14AM -0500, Davanum Srinivas wrote: > Hi, > > Failures for this job has been trending up and is causing the large > gate queue as well. I've logged a bug: > https://bugs.launchpad.net/openstack-gate/+bug/1536622 > > and am requesting switching the voting to off for

Re: [openstack-dev] [gate] large-ops failure spike

On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: > The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in > the last 24 hours. > > http://tinyurl.com/j5u4nf5 > > There isn't an obvious culprit at this point. I spent some time this There is a very obvious culprit, pip 8

Re: [openstack-dev] [Neutron][[Infra] Gate failure

On Tue, Jan 19, 2016 at 05:28:46PM -0800, Armando M. wrote: > Hi neutrinos, > > New week, new gate failure. This time this might be infra related [1]. This > one fails with [2]. If you know what's going on, spread the word! Pip 8 was just released and made trying to uninstall distutils installed

Re: [openstack-dev] [nova][testing] How to run a subset of py34 unit tests

On Fri, Jan 22, 2016 at 06:46:48PM -0800, melanie witt wrote: > Hi everyone, > > I noticed because of the way we run the py34 tests in tox.ini, I'm not able > to specify a filter regex the way I normally do as a positional arg, for > example: 'tox -epy34 nova.tests.unit.network' doesn't filter

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

On Tue, Feb 16, 2016 at 10:07:19AM +0100, Jordan Pittier wrote: > Hi list, > I understood we need to limit the number of tests and jobs that are run for > each Tempest patch because our resources are not unlimited. > > In Tempest, we have 5 multinode experimental jobs: > >

Re: [openstack-dev] [qa] deprecating Tempest stress framework

On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote: > I know that there are folks around that are using it. > +1 to move it to a separate repo. That sounds fine to me, let's mark the stress runner as deprecated and before we remove it someone can spin up a separate repo that owns the

[openstack-dev] [QA] End of the openstack-qa mailing list

Hi everyone, I just wanted to send an announcement to the ML that we've officially shutdown the openstack-qa ML. We had basically stopped using this completely 2-3 years ago but kept the list alive because of the periodic job results needing a place to be sent. However, with the introduction of

Re: [openstack-dev] [qa] Tempest removal of tempest.api.compute.test_authorization

On Tue, Feb 09, 2016 at 07:41:18PM -0500, Sean Dague wrote: > As proposed in this patch - https://review.openstack.org/#/c/271467/ > > These tests do some manipulation of the request URI to attempt to > request Nova resources owned by a different project_id. However they all > basically test the

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

Hi everyone, I'm writing this to announce that I am not running for QA PTL this cycle. I've been the QA PTL for the past 4 cycles and I think it's time for another person to take over the role. I think during the past 4 cycles the QA community has grown greatly and become a much larger and

Re: [openstack-dev] [nova] API priorities in Newton

On Wed, Mar 30, 2016 at 03:26:13PM -0400, Sean Dague wrote: > During the Nova API meeting we had some conversations about priorities, > but this feels like the thing where a mailing list conversation is more > inclusive to get agreement on things. I think we need to remain focused > on what API

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

On Tue, Apr 05, 2016 at 01:37:21PM +0100, Kiall Mac Innes wrote: > Agreed on a separate repo. > > I'm honestly a little unsure how in-service-repo would ever work long > term, given that tempest's requirements will match master, and may > not be compatible with N releases ago's $service

Re: [openstack-dev] [all] Maintaining httplib2 python library

On Mon, Mar 14, 2016 at 10:37:52AM -0400, Sean Dague wrote: > On 03/14/2016 10:24 AM, Ian Cordasco wrote: > > > > > > -Original Message- > > From: Davanum Srinivas > > Reply: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] [nova] config options help text improvement: current status

On Thu, Mar 03, 2016 at 10:24:28AM +1100, Tony Breeds wrote: > On Wed, Mar 02, 2016 at 06:11:47PM +, Tim Bell wrote: > > > Great. Does this additional improved text also get into the configuration > > guide documentation somehow ? > > It's certainly part of tox -egenconfig, I don't know

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

On Thu, Mar 31, 2016 at 11:38:55AM -0400, Minying Lu wrote: > Hi all, > > I'm working on resource federation at the Massachusetts Open Cloud. We want > to implement functional test on the k2k federation, which requires > authentication with both a local keystone and a remote keystone (in a >

[openstack-dev] [tc][election] TC Candidacy

messaging about what OpenStack is much clearer. It would be my honor and privilege to serve the community if I'm lucky enough to be elected to the TC. Thanks, Matthew Treinish IRC: mtreinish Review history: https://review.openstack.org/#/q/reviewer:mtreinish%2540kortar.org Commit history

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: > Hi, > > Current OpenStack Infra Periodic jobs do not send e-mails (only > periodic-stable do), so I propose to create periodic-ci-reports > mailing list [1] and to use it when our periodic jobs fail [2]. > If accepted, people who

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

On Wed, Apr 13, 2016 at 06:22:50PM +0200, Ihar Hrachyshka wrote: > Matthew Treinish <mtrein...@kortar.org> wrote: > > > On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: > > > Hi, > > > > > > Current OpenStack Infra Periodic jobs do no

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

On Fri, May 06, 2016 at 04:40:28PM -0400, Davanum Srinivas wrote: > Thanks Jeremy, > > Since the following folks volunteered to help with requirements: > Dirk Mueller (SUSE) > Haïkel Guémar (RDO/CentOS) > Igor Yozhikov (MOS) > Alan Pevec (RDO) > Tony Breeds (Rackspace) > Ghe Rivero (HPE) > > So

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

On Wed, Apr 13, 2016 at 05:22:28PM +, Jeremy Stanley wrote: > On 2016-04-13 12:58:47 -0400 (-0400), Matthew Treinish wrote: > > So, sure I understand the attraction of an active notification. > [...] > > Instead, of pretending the ML work for doing this I think it'll b

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

On Wed, Apr 13, 2016 at 05:12:08PM -0500, Dolph Mathews wrote: > On Wed, Apr 13, 2016 at 2:37 PM, Emilien Macchi <emil...@redhat.com> wrote: > > > On Wed, Apr 13, 2016 at 12:13 PM, Matthew Treinish <mtrein...@kortar.org> > > wrote: > > > On Wed, Apr 13, 2

Re: [openstack-dev] [nova] Next steps for proxy API deprecation

On Tue, Jul 26, 2016 at 01:21:53PM -0400, Sean Dague wrote: > On 07/26/2016 01:14 PM, Matt Riedemann wrote: > > On 7/26/2016 11:59 AM, Matt Riedemann wrote: > >> Now that the 2.36 microversion change has merged [1], we can work on the > >> python-novaclient changes for this microversion. > >> > >>

Re: [openstack-dev] [nova] Next steps for proxy API deprecation

On Tue, Jul 26, 2016 at 12:14:03PM -0500, Matt Riedemann wrote: > On 7/26/2016 11:59 AM, Matt Riedemann wrote: > > Now that the 2.36 microversion change has merged [1], we can work on the > > python-novaclient changes for this microversion. > > > > At the midcycle we agreed [2] to also return a

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 09:56:09AM -0700, Clay Gerrard wrote: > On Mon, Aug 8, 2016 at 8:31 AM, Matthew Treinish <mtrein...@kortar.org> > wrote: > > > When we EOL a branch all of the infrastructure for running any ci against > > it goes away. > > > But...

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 09:52:55AM -0700, Clay Gerrard wrote: > On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander > wrote: > > > > > A big source of problems IMO is that tempest doesn't have stable branches. > > We use the master branch of tempest to test stable branches

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith wrote: > On Tue, Aug 9, 2016 at 4:53 PM, Sean McGinnis wrote: > > > . > > > > > > Mike, you must have left the midcycle by the time this topic came > > > up. On the issue of out-of-tree drivers, I specifically offered

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 01:39:55AM +, Jeremy Stanley wrote: > On 2016-08-09 15:56:57 -0700 (-0700), Mike Perez wrote: > > As others have said and as being a Cinder stable core myself, the status-quo > > and this proposal itself are terrible practices because there is no testing > > behind it,

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Tue, Aug 09, 2016 at 09:16:02PM -0700, John Griffith wrote: > On Tue, Aug 9, 2016 at 7:21 PM, Matthew Treinish <mtrein...@kortar.org> > wrote: > > > On Tue, Aug 09, 2016 at 05:28:52PM -0700, John Griffith wrote: > > > On Tue, Aug 9, 2016 at 4:53 PM, Sean M

Re: [openstack-dev] [nova][qa] When do we need tests for microversions in Tempest?

On Wed, Jul 13, 2016 at 09:55:33PM -0500, Matt Riedemann wrote: > There are several changes in Tempest right now trying to add response schema > validation for the 2.26 microversion which added server tags to the server > GET response. This is needed for anything testing a microversion >=2.26, >

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Wed, Jul 06, 2016 at 06:20:30PM +0200, Thierry Carrez wrote: > Matthew Treinish wrote: > > > [...] > > > Am I missing something else here? > > > > Well, for better or worse rootwrap filters are put in /etc and treated like > > a > >

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Wed, Jul 06, 2016 at 11:41:56AM -0500, Matt Riedemann wrote: > On 7/6/2016 10:55 AM, Matthew Treinish wrote: > > > > Well, for better or worse rootwrap filters are put in /etc and treated like > > a > > config file. What you're essentially saying is

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Wed, Jul 06, 2016 at 10:34:49AM -0500, Matt Riedemann wrote: > On 6/27/2016 6:24 AM, Sean Dague wrote: > > On 06/26/2016 10:02 PM, Angus Lees wrote: > > > On Fri, 24 Jun 2016 at 20:48 Sean Dague > > > wrote: > > > > > > On 06/24/2016 05:12 AM,

Re: [openstack-dev] [neutron][grafana][infra] how to read grafana

On Mon, Aug 08, 2016 at 02:40:31PM +0200, Ihar Hrachyshka wrote: > Hi, > > I was looking at grafana today, and spotted another weirdness. > > See the periodic jobs dashboard: > > http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=4 > > Currently it shows for me 100% failure

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Mon, Aug 08, 2016 at 07:40:56PM +0300, Duncan Thomas wrote: > On 8 August 2016 at 18:31, Matthew Treinish <mtrein...@kortar.org> wrote: > > > > > This argument comes up at least once a cycle and there is a reason we > > don't do > > this. When we EO

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Mon, Aug 08, 2016 at 09:47:53AM -0500, Sean McGinnis wrote: > > > > Unless you manage to get it approved for the global policy, I think > > you will effectively make your stable:follows-policy tag obsolete, > > and then it should be removed from your project. Read the > > requirements: > > >

Re: [openstack-dev] gate jobs - papercuts

On Tue, Jan 31, 2017 at 12:49:13PM -0500, Davanum Srinivas wrote: > Folks, > > Here's the list of job failures that failed in the gate queue. > captured with my script[1][2] since around 10:00 AM today. All jobs > failed with just one bad test. > >

Re: [openstack-dev] [elastic-recheck] Miscellaneous questions of potential Neutron interest

On Tue, Jan 31, 2017 at 10:38:58AM -0800, Ihar Hrachyshka wrote: > Hi all, > > we were looking at expanding usage of elastic-recheck in Neutron, and > several questions popped up that we would like to ask. > > 1. Are all jobs eligible for coverage with queries? The reason we ask > is that there

Re: [openstack-dev] gate jobs - papercuts

On Tue, Jan 31, 2017 at 01:19:41PM -0500, Steve Martinelli wrote: > On Tue, Jan 31, 2017 at 12:49 PM, Davanum Srinivas > wrote: > > > Folks, > > > > Here's the list of job failures that failed in the gate queue. > > captured with my script[1][2] since around 10:00 AM today.

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

On Thu, Feb 02, 2017 at 04:27:51AM +, Dolph Mathews wrote: > What made most services jump +20% between mitaka and newton? Maybe there is > a common cause that we can tackle. Yeah, I'm curious about this too, there seems to be a big jump in Newton for most of the project. It might not a be a

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

On Wed, Feb 01, 2017 at 04:24:54PM -0800, Armando M. wrote: > Hi, > > [TL;DR]: OpenStack services have steadily increased their memory > footprints. We need a concerted way to address the oom-kills experienced in > the openstack gate, as we may have reached a ceiling. > > Now the longer version:

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

On Thu, Feb 02, 2017 at 11:10:22AM -0500, Matthew Treinish wrote: > On Wed, Feb 01, 2017 at 04:24:54PM -0800, Armando M. wrote: > > Hi, > > > > [TL;DR]: OpenStack services have steadily increased their memory > > footprints. We need a concerted way to addres

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/tempest failed

On Sun, Feb 19, 2017 at 07:25:39AM +, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - periodic-tempest-dsvm-full-ubuntu-trusty-mitaka > http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-ubuntu-trusty-mitaka/27fe759/ > : SUCCESS

[openstack-dev] [QA][all] Pike PTG Tempest Plugin Cross Project Session

Hi Everyone, I just wanted to advertise that we will be hosting a 1 hr cross project session at the PTG next week. We have the Macon discussion room at the PTG reserved [1] on Tuesday between 9:30a to 10:30a. The intent of this session is for anyone who is producing or consuming tempest plugins

Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

On Tue, Aug 16, 2016 at 10:40:07PM +, Elancheran Subramanian wrote: > Hello There, > I’m currently playing with using Tempest as our integration tests for our > internal and external clouds, facing some issues with api which are not > supported in our cloud. For ex, listing domains isn’t

Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

On Wed, Aug 17, 2016 at 12:27:29AM +, Elancheran Subramanian wrote: > Hello Punal, > We do support both V2 and V3, that’s just a example I’ve stated BTW. We do > have our own integration tests which are pretty much covers all our > integration points with openstack. But we would like to

Re: [openstack-dev] Let's drop the postgresql gate job

On Thu, Aug 18, 2016 at 11:33:59AM -0500, Matthew Thode wrote: > On 08/18/2016 10:00 AM, Matt Riedemann wrote: > > It's that time of year again to talk about killing this job, at least > > from the integrated gate (move it to experimental for people that care > > about postgresql, or make it

<    1   2   3   4   >