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

Hi, I agree with Jordan. We don't have to use the tool as part of the gate. It's target audience is people and not CI systems. More specifically - new users. However, we could add a gate (or a few) for the tool that makes sure a proper conf file is generated. It doesn't have to run the tests, just

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

On Tue, Oct 20, 2015 at 2:06 PM, Behzad Dastur wrote: > I have a contrail/OpenStack cloud deployed on which I am trying to run > some rally benchmarks. But I am having trouble getting the rally boot tests > to run. It throws the "Error Forbidden: It is not allowed to

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

}, > > "context": { > "network": {"networks_per_tenant": 1}, > "users": { > > "tenants": 3, > > "users_per_tenant": 2 > >

Re: [openstack-dev] [Rally] Improve review process

+1 - Original Message - From: Boris Pavlovic bpavlo...@mirantis.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, May 5, 2015 6:09:43 PM Subject: Re: [openstack-dev] [Rally] Improve review process Roman, Well done!

Re: [openstack-dev] [rally] Weekly meeting

Thank you for moving it to a more reasonable time for me. - Original Message - From: Boris Pavlovic bo...@pavlovic.me To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, carlos torres carlos.tor...@rackspace.com, yfr...@redhat.com, yingjun

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

- Original Message - From: Aleksandr Maretskiy amarets...@mirantis.com To: Andrey Kurilin akuri...@mirantis.com Cc: Boris Pavlovic bo...@pavlovic.me, OpenStack Development Mailing List openstack-dev@lists.openstack.org, yfr...@redhat.com, yingjun li yingjun...@kylin-cloud.com,

Re: [openstack-dev] [qa] Lack of consistency in returning response from tempest clients

Hi, I'd rather not subclass dict directly. for various reasons adding extra attributes to normal python dict seems prone to errors since people will be expecting regular dicts, and on the other hand if we want to expand it in the future we might run into problems playing with dict methods (such

Re: [openstack-dev] [Neutron] [LBaaS] LBaaS v2 API syntax additions/changes

I would like to add a question to John's list - Original Message - From: John Schwarz jschw...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, August 26, 2014 2:22:33 PM Subject: Re: [openstack-dev]

Re: [openstack-dev] [qa] The role of an abstract client in tempest

- Original Message - From: David Kranz dkr...@redhat.com To: OpenStack Development Mailing List openstack-dev@lists.openstack.org Sent: Friday, July 25, 2014 4:54:22 PM Subject: [openstack-dev] [qa] The role of an abstract client in tempest Even as a core contributor for several

Re: [openstack-dev] [QA] Questions about test policy for scenario test

- Original Message - From: Fei Long Wang feil...@catalyst.net.nz To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Cc: br...@catalyst.net.nz Sent: Tuesday, June 24, 2014 8:29:03 AM Subject: [openstack-dev] [QA] Questions about test

Re: [openstack-dev] [QA] Tempest Release Naming

- Original Message - From: Sean Dague s...@dague.net To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Friday, May 23, 2014 3:40:16 AM Subject: Re: [openstack-dev] [QA] Tempest Release Naming On 05/22/2014 08:33 PM, Jeremy

Re: [openstack-dev] [Neutron][QA]Request for input for Juno Design Summit, Atlanta

Hi, For everyone's convenience, I've added to the pad short descriptions of Network Scenarios that are currently in tree (or under review) that I am familiar with. Feel free to add/edit Regards Yair - Original Message - From: Miguel Lavalle mig...@mlavalle.com To: OpenStack

Re: [openstack-dev] [Tempest][qa] : backporting Test Security Groups Basic Ops in stable/havana ?

Hi Julien I've tried to backport it in the past, and it was rejected, as it needs quite a lot of work. If you are able to convince everyone otherwise, I will gladly help you with the code. However, I think the better solution would be to somehow create a gate that runs the scenarios in the

Re: [openstack-dev] [QA] The future of nosetests with Tempest

- Original Message - From: Alexei Kornienko alexei.kornie...@gmail.com To: openstack-dev@lists.openstack.org Sent: Friday, February 28, 2014 12:43:13 PM Subject: Re: [openstack-dev] [QA] The future of nosetests with Tempest Hi, Let me express my concerns on this topic: With

[openstack-dev] [Neutron] port forwarding from gateway to internal hosts

Hi, What's the status of this BP? - https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding will it be ready for I3? The BP is approved but the patch is abandoned Regards Yair ___ OpenStack-dev mailing list

[openstack-dev] [Neutron] port forwarding from gateway to internal hosts

Hi, What's the status of this BP? - https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding will it be ready for I3? The BP is approved but the patch is abandoned Regards Yair ___ OpenStack-dev mailing list

Re: [openstack-dev] [qa][Neutron][Tempest][Network] Break down NetworkBasicOps to smaller test cases

On 20 January 2014 09:23, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-01-19 at 07:17 -0500, Yair Fried wrote: OK, but considering my pending patch (#3 and #4) what about: #1 - #2 #1 - #3 #1 - #4 instead of #1 - #2 - #3 - #4 a failure in #2 will prevent #3 and #4

Re: [openstack-dev] [qa][Neutron][Tempest][Network] Break down NetworkBasicOps to smaller test cases

NetworkBasicOps to smaller test cases On 01/19/2014 02:06 AM, Yair Fried wrote: MT:Is your issue here that it's just called basic ops and you don't think that's reflective of what is being tested in that file anymore No. My issue is, that the current scenario is, in fact, at least 2 separate

Re: [openstack-dev] [qa][Neutron][Tempest][Network] Break down NetworkBasicOps to smaller test cases

Sent: Friday, January 17, 2014 6:17:55 AM Subject: Re: [openstack-dev] [qa][Neutron][Tempest][Network] Break down NetworkBasicOps to smaller test cases On Wed, Jan 15, 2014 at 11:20:22AM -0500, Yair Fried wrote: Hi Guys As Maru pointed out - NetworkBasicOps scenario has grown out of proportion

[openstack-dev] [qa][Neutron][Tempest][Network] Break down NetworkBasicOps to smaller test cases

Hi Guys As Maru pointed out - NetworkBasicOps scenario has grown out of proportion and is no longer basic ops. So, I started breaking it down to smaller test cases that can fail independently. Those test cases share the same setup and tear-down code: 1. create network resources (and verify

[openstack-dev] [qa][FWaaS][Neutron]Firewall service disabled on gate

Hi, I'm trying to push a firewall api test [1] and I see it cannot run on the current gate. I was FWaaS is disabled since it broke the gate. Does anyone knows if this is still an issue? If so - how do we overcome this? I would like to do some work on this service (scenarios) and don't want to

Re: [openstack-dev] [QA][Neutron] About paramiko's SSHException: Error reading SSH protocol banner

This might be completely off, in isolated creds, a private network is created for each tenant, while the test already creates its own private tenant network, thereby changing the behavior from how it was intended to, and how it is in simple mode. Could this be related? I have this patch

Re: [openstack-dev] [OpenStack-Infra][qa][Tempest][Network] [Infra]Test for external connectivity

Yair - Original Message - From: Yair Fried yfr...@redhat.com To: openstack-in...@lists.openstack.org Sent: Monday, December 23, 2013 5:57:44 PM Subject: [OpenStack-Infra] Fwd: [openstack-dev] [Openstack][qa][Tempest][Network] [Infra]Test for external connectivity - Forwarded

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

- Original Message - From: Brent Eagles beag...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Monday, December 23, 2013 10:48:50 PM Subject: Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the

[openstack-dev] [Tempest][qa] Adding tags to commit messages

Hi, Suggestion: Please consider tagging your Tempest commit messages the same way you do your mails in the mailing list Explanation: Since tempest is a single project testing multiple Openstack project we have a very diverse collection of patches as well as reviewers. Tagging our commit

Re: [openstack-dev] [Openstack][qa][Tempest][Network] [Infra]Test for external connectivity

would really like your input in this matter, as I am in the final stretch of this patch and cannot move any farther by myself Regards Yair Fried - Original Message - From: Jeremy Stanley fu...@yuggoth.org To: openstack-dev@lists.openstack.org Sent: Thursday, November 21, 2013 12:17:52 AM

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

Hi Guys, I run into this issue trying to incorporate this test into cross_tenant_connectivity scenario: launching 2 VMs in different tenants What I saw, is that in the gate it fails half the time (the original test passes without issues) and ONLY on the 2nd VM (the first FLIP propagates

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

questions) openstack-dev@lists.openstack.org Sent: Thursday, December 19, 2013 12:42:56 PM Subject: Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point On 12/19/2013 03:31 AM, Yair Fried wrote: Hi Guys, I run into this issue trying to incorporate

Re: [openstack-dev] [Openstack][qa][Tempest][Network] Test for external connectivity

-0800 (-0800), Sean Dague wrote: On 11/18/2013 02:41 AM, Yair Fried wrote: [...] 2. add fields in tempest.conf for * external connectivity = False/True * external ip to test against (ie 8.8.8.8) +1 for #2. In the gate we'll need to think about what that address can / should

[openstack-dev] [Openstack][qa][Tempest][Network] Test for external connectivity

configured 2. activly configure dns on subnet creation (based on tempest.conf Comments/suggestions will be much appriciated Regards Yair Fried ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman