[openstack-dev] [qa] resigning from Tempest core

Hi folks, as already mentioned during the current code sprint: I am currently lacking time for reviews and code contributions. I think it better to step back and let other’s in that are more active. Thanks for all the support and it was really fun the past 3 years working with you! Regards

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

l <https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/ironic-ml2-integration.html> [2]: https://wiki.openstack.org/wiki/Neutron/L2-GW [3]: https://wiki.openstack.org/wiki/Neutron/TrunkPort > On 09 Mar 2016, at 09:25, Koderer, Marc <m...@koderer.com> wrote: > >

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

g/#/c/284034/> > > -Sukhdev > > > On Tue, Mar 1, 2016 at 1:08 AM, Koderer, Marc <m...@koderer.com > <mailto:m...@koderer.com>> wrote: > >> On 01 Mar 2016, at 06:22, Kevin Benton <ke...@benton.pub >> <mailto:ke...@benton.pub>> wr

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

> On 01 Mar 2016, at 06:22, Kevin Benton wrote: > > >This seems gross and backwards. It makes sense as a short term hack but > >given that we have time to design this correctly I'd prefer to get this > >information in a more straighforward way. > > Well it depends on what

[openstack-dev] [Neuton][ml2][Manila] API to query segments used during port binding

Hi Neutron team, I am currently working on a feature for hierarchical port binding support in Manila [1] [2]. Just to give some context: In the current implementation Manila creates a neutron port but let it unbound (state DOWN). Therefore Manila uses the port create only retrieve an IP address

Re: [openstack-dev] [OpenStack-Dev][Manila] BP https://blueprints.launchpad.net/manila/+spec/access-groups

Hi Nidhi, It’s might also a good idea to have a short discussion during the manila meeting [1]. You can simply add your topic to the agenda. Regards Marc [1]: https://wiki.openstack.org/wiki/Manila/Meetings > On 26 Feb 2016, at 10:52,

Re: [openstack-dev] [QA] Proposed Changes to Tempest Core

+1 -Ursprüngliche Nachricht- Von: Matthew Treinish [mailto:mtrein...@kortar.org] Gesendet: Dienstag, 22. Juli 2014 00:34 An: openstack-dev@lists.openstack.org Betreff: [openstack-dev] [QA] Proposed Changes to Tempest Core Hi Everyone, I would like to propose 2 changes to the

Re: [openstack-dev] [QA][Infra] Mid-Cycle Meet-up

Hi all, just some general information for your trip: - Darmstadt is quite close to Frankfurt am Main: From Frankfurt Airport you can take a bus shuttle that takes you directly to the office campus (the trip takes around 25 minutes depending on your arrival gate):

Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta

Hi, 7:30pm at Ted's Montana Grill. I called them and they put us on the list. Again the location: https://plus.google.com/100773563660993493024/posts/P9YSgT8AVXh It's quite near to all the hotels. See you there! Marc From: Koderer, Marc [m.kode

Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta

mobile number.. Regards Marc From: Koderer, Marc [m.kode...@telekom.de] Sent: Monday, May 05, 2014 8:41 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta All right, let’s meet

Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta

arrive Sunday at 3:30pm. Either Sunday or Monday are fine with me. Lookging forward to it :-) On Wed, Apr 30, 2014 at 5:11 AM, Koderer, Marc m.kode...@telekom.demailto:m.kode...@telekom.de wrote: Hi folks, last time we met one day before the Summit started for a short meet-up. Should we do the same

[openstack-dev] [qa] QA Summit Meet-up Atlanta

Hi folks, last time we met one day before the Summit started for a short meet-up. Should we do the same this time? I will arrive Saturday to recover from the jet lag ;) So Sunday 11th would be fine for me. Regards, Marc ___ OpenStack-dev mailing

[openstack-dev] [qa] API schema location

Hi Chris, hi all, I just recognized that we have very similar interface definitions in tempest/api_schema and etc/schema: https://github.com/openstack/tempest/tree/master/etc/schemas https://github.com/openstack/tempest/tree/master/tempest/api_schema Any objections if I move them to a single

Re: [openstack-dev] [qa] API schema location

On Tue, 18 Marc 2014 12:00:00 +0100 Christopher Yeoh [mailto:cbky...@gmail.com] wrote: On Tue, 18 Mar 2014 10:39:19 +0100 Koderer, Marc m.kode...@telekom.de wrote: I just recognized that we have very similar interface definitions in tempest/api_schema and etc/schema: https://github.com

Re: [openstack-dev] [qa] API schema location

From: Matthew Treinish [mtrein...@kortar.org] Sent: Tuesday, March 18, 2014 7:08 PM On Tue, Mar 18, 2014 at 12:34:57PM +0100, Koderer, Marc wrote: On Tue, 18 Marc 2014 12:00:00 +0100 Christopher Yeoh [mailto:cbky...@gmail.com] wrote: On Tue, 18 Mar 2014 10:39:19 +0100 Koderer, Marc

[openstack-dev] [qa] [Infra] pep8 issues in tempest gate / testscenarios lib

Hi folks, I can't make it to the QA meeting for today so I wanted to summarize the issue that we have with the pep8 and tempest gate. An example for the issue you can find here: https://review.openstack.org/#/c/79256/

Re: [openstack-dev] [Tempest - Stress Test][qa] : implement a full SSH connection on ssh_floating.py and improve it

Von: LELOUP Julien [mailto:julien.lel...@3ds.com] Gesendet: Montag, 3. März 2014 11:21 An: OpenStack Development Mailing List (not for usage questions); Koderer, Marc Betreff: [Tempest - Stress Test][qa] : implement a full SSH connection on ssh_floating.py and improve it Hello, It tourns

Re: [openstack-dev] Cleaning OpenStack resources

Hi Forent, thanks for the link. Our current implementation of for the cleanup is a bit buggy. I will give your script a try. Maybe we could use it an replace the existing module. Regards Marc From: Florent Flament [florent.flament-...@cloudwatt.com]

Re: [openstack-dev] [qa] [Tempest - Stress Test] : some improvements / issues on the stress test framework

Hi Julien, please don't forget the [qa] tag - otherwise your lost in the ML noise ;) Ok thanks for the bug reports. I confirmed 1273245 and 1273254 but I am not totally sure with 1273186. Could you give some more details how the CLI interface will look like? Or simply propose a patch. It could

Re: [openstack-dev] [qa] [Tempest - Stress Test] : implement a full SSH connection on ssh_floating.py and improve it

/tempest/stress/etc/sample-unit-test.json With that you can launch them with the parameters you already described. Regards, Marc From: LELOUP Julien [julien.lel...@3ds.com] Sent: Friday, January 17, 2014 3:49 PM To: Koderer, Marc Cc: openstack-dev

[openstack-dev] [qa] RE: [Tempest - Stress Test] : implement a full SSH connection on ssh_floating.py and improve it

Hello Juilen, I forwarded your mail to the correct mailing list. Please do not use the qa list any longer. I am happy that you are interested in stress tests. All the tests in tempest/stress/actions are more or less deprecated. So what you should use instead is the stress decorator (e.g.

[openstack-dev] [qa] negative test framework: ready for review

Hi all, first part of the negative test framework is ready for review: https://review.openstack.org/#/c/64733/ Please have a look. Regards Marc and David DEUTSCHE TELEKOM AG Digital Business Unit, Cloud Services (PI) Marc Koderer Cloud Technology Software Developer T-Online-Allee 1, 64211

Re: [openstack-dev] [qa] RE: [Tempest - Stress Test] : implement a full SSH connection on ssh_floating.py and improve it

To: Koderer, Marc Cc: openstack-dev@lists.openstack.org Subject: RE: [qa] RE: [Tempest - Stress Test] : implement a full SSH connection on ssh_floating.py and improve it Hello Marc, Thanks for your answer. At the moment I'm willing to spend some time on this kind of scenario so I will see how

Re: [openstack-dev] [qa] negative test generation and testscenarios

Hi Robert, https://review.openstack.org/#/c/64733 is updated and is using testscenarios now. I was wondering if it would make sense to use a decorator instead of a class attribute to mark a test case for a certain test scenario, like: @TestCaseWithScenario(_scenarios1) def

Re: [openstack-dev] [nova] [qa] api schema validation pattern changes

Von: David Kranz [mailto:dkr...@redhat.com] Gesendet: Montag, 13. Januar 2014 05:04 An: openstack-dev@lists.openstack.org Betreff: Re: [openstack-dev] [nova] [qa] api schema validation pattern changes On 01/12/2014 10:14 PM, Matthew Treinish wrote: snip Last, is a question, is it

Re: [openstack-dev] [qa] Moving the QA meeting time

Hi all! -Ursprüngliche Nachricht- Von: Kenichi Oomichi [mailto:oomi...@mxs.nes.nec.co.jp] Gesendet: Donnerstag, 5. Dezember 2013 01:37 An: OpenStack Development Mailing List (not for usage questions) Betreff: Re: [openstack-dev] [qa] Moving the QA meeting time Hi Matthew,

Re: [openstack-dev] [qa] Proposals for Tempest core

+1 for both! From: Sean Dague [s...@dague.net] Sent: Friday, November 15, 2013 2:38 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [qa] Proposals for Tempest core It's post summit time, so time to evaluate our

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

Hi, see below. Regards Marc From: Kenichi Oomichi [oomi...@mxs.nes.nec.co.jp] Sent: Wednesday, November 13, 2013 7:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [qa] moratorium on new negative tests in

[openstack-dev] [qa] fuzzy testing of client functions

Hello folks, I remember that we had a quick chat about fuzzy testing in a QA meeting. IMHO we have much too many negative tests in tempest that aren't really complex. So I tried to build up a little tool that discovers the parameters of a client functions and randomizes the input for it. It