Re: [openstack-dev] [qa] Tempest bug triage questions

On 06/22/2015 10:15 AM, Yaroslav Lobankov wrote: Hello everyone, I have some questions about the bug triage procedure for Tempest: 1. Some bugs in Tempest have status "Fix committed". Should we move statuses of these bugs to "Fix released"? Yes, tempest doesn't have the kind of releases where

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

+1 On 06/22/2015 04:23 PM, Matthew Treinish wrote: Hi Everyone, I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team. Jordan has been a steady contributor and reviewer on tempest over the past few cycles and he's been actively engaged in the Tempest community. Jordan ha

Re: [openstack-dev] [QA] Prototype of the script for Tempest auto-configuration

the patch on master and ran the script. The script was finished without any errors and the tempest.conf was generated! Of course, this patch needs a lot of work, but the idea looks very cool! Also I would like to thank David Kranz for his working on initial version of the

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 02/06/2015 07:49 AM, Sean Dague wrote: On 02/06/2015 07:39 AM, Alexandre Levine wrote: Rushi, We're adding new tempest tests into our stackforge-api/ec2-api. The review will appear in a couple of days. These tests will be good for running against both nova/ec2-api and stackforge/ec2-api. As

Re: [openstack-dev] [stable] juno is fubar in the gate

On 02/10/2015 10:35 AM, Matthew Treinish wrote: On Tue, Feb 10, 2015 at 11:19:20AM +0100, Thierry Carrez wrote: Joe, Matt & Matthew: I hear your frustration with broken stable branches. With my vulnerability management team member hat, responsible for landing patches there with a strict deadlin

Re: [openstack-dev] [stable] juno is fubar in the gate

On 02/10/2015 12:20 PM, Jeremy Stanley wrote: On 2015-02-10 11:50:28 -0500 (-0500), David Kranz wrote: [...] I would rather give up branchless tempest than the ability for real distributors/deployers/operators to collaborate on stable branches. [...] Keep in mind that branchless tempest came

[openstack-dev] [qa][swift] Signature of return values in tempest swift client

Almost all of the OpenStack REST apis return little of user value in the response headers, with json bodies containing the returned data. The tempest client methods had been returning two values with one always being ignored. To clean that up before moving the service clients to tempest-lib, we

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On 02/24/2015 09:37 AM, Chris Dent wrote: On Tue, 24 Feb 2015, Sean Dague wrote: That also provides a very concrete answer to "will people show up". Because if they do, and we get this horizontal refactoring happening, then we get to the point of being able to change release cadences faster. If

Re: [openstack-dev] [Nova][Tempest] Tempest will deny extra properties on Nova v2/v2.1 API

On 02/24/2015 06:55 AM, Ken'ichi Ohmichi wrote: Hi Ghanshyam, 2015-02-24 20:28 GMT+09:00 GHANSHYAM MANN : On Tue, Feb 24, 2015 at 6:48 PM, Ken'ichi Ohmichi wrote: Hi Nova team is developing Nova v2.1 API + microversions in this cycle, and the status of Nova v2.1 API has been changed to CURRE

Re: [openstack-dev] [QA] testing implementation-specific features not covered by OpenStack APIs

On 03/03/2015 11:28 AM, Radoslaw Zarzynski wrote: As we know Tempest provides many great tests for verification of conformance with OpenStack interfaces - the tempest/api directory is full of such useful stuff. However, regarding the #1422728 ticket [1] (dependency on private HTTP header of Swift

[openstack-dev] [heat][qa] Forward plan for heat scenario tests

Since test_server_cfn_init was recently moved from tempest to the heat functional tests, there are no subclasses of OrchestrationScenarioTest. If there is no plan to add any more heat scenario tests to tempest I would like to remove that class. So I want to confirm that future scenario tests wil

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

In the process of writing a unit test for this I discovered that it can call out to keystone for a token with some configurations through the call to get_configured_credentials. This surprised me since I thought it would just check for the necessary admin credentials in either tempest.conf or a

Re: [openstack-dev] [QA] [rally] How will Tempest discover/run tests migrated to specific projects?

On 03/30/2015 10:44 AM, Matthew Treinish wrote: On Mon, Mar 30, 2015 at 12:21:18PM +0530, Rohan Kanade wrote: Since tests can now be removed from Tempest < https://wiki.openstack.org/wiki/QA/Tempest-test-removal> and migrated to their specific projects. Does Tempest plan to discover/run these t

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

There have been a number of changes in tempest recently that seem to coordinate with devstack that are a bit unclear. The following values are defined in tempest config as defaults: [auth] # Roles to assign to all users created by tempest (list value) #tempest_roles = [object-storage] # Role t

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

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 issue was that before tempest was making all sorts of

[openstack-dev] [qa] official clients and tempest

Since tempest no longer uses the official clients as a literal code dependency, except for the cli tests which are being removed, the clients have been dropping from requirements.txt. But when debugging issues uncovered by tempest, or when debugging tempest itself, it is useful to use the cli t

Re: [openstack-dev] [qa] official clients and tempest

On 04/08/2015 02:36 PM, Matthew Treinish wrote: On Wed, Apr 08, 2015 at 01:08:03PM -0400, David Kranz wrote: Since tempest no longer uses the official clients as a literal code dependency, except for the cli tests which are being removed, the clients have been dropping from requirements.txt

Re: [openstack-dev] [api] Minor changes to API

On 04/20/2015 08:07 PM, Ian Wells wrote: On 20 April 2015 at 15:23, Matthew Treinish > wrote: On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: > It would be nice to have a consistent policy here; it would make future > decision making easier

Re: [openstack-dev] [all] Question for the TC candidates

On 04/24/2015 10:42 AM, Chris Dent wrote: On Fri, 24 Apr 2015, Ed Leafe wrote: I read "the downstream" to mean what you refer to as "people who deploy workloads on them". In this context, I saw the operators as the end-users of the work the devs do. If that gave the impression that I don't care

Re: [openstack-dev] [qa] trimming down Tempest smoke tag

On 04/28/2015 06:38 AM, Sean Dague wrote: The Tempest Smoke tag was originally introduced to provide a quick view of your OpenStack environment to ensure that a few basic things were working. It was intended to be fast. However, during Icehouse the smoke tag was repurposed as a way to let neutro

Re: [openstack-dev] [swift] Go! Swift!

On 04/30/2015 12:52 PM, Jay Pipes wrote: On 04/30/2015 12:40 PM, John Dickinson wrote: Swift is a scalable and durable storage engine for storing unstructured data. It's been proven time and time again in production in clusters all over the world. We in the Swift developer community are constan

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On 05/06/2015 02:07 PM, Jay Pipes wrote: Adding [api] topic. API WG members, please do comment. On 05/06/2015 08:01 AM, Sean Dague wrote: On 05/06/2015 07:11 AM, Chris Dent wrote: On Wed, 6 May 2015, Sean Dague wrote: All other client errors, just be a 400. And use the emerging error reporti

Re: [openstack-dev] [new][cloudpulse] Announcing a project to HealthCheck OpenStack deployments

On 05/13/2015 09:06 AM, Simon Pasquier wrote: Hello, Like many others commented before, I don't quite understand how unique are the Cloudpulse use cases. For operators, I got the feeling that existing solutions fit well: - Traditional monitoring tools (Nagios, Zabbix, ) are necessary any

Re: [openstack-dev] [new][cloudpulse] Announcing a project to HealthCheck OpenStack deployments

On 05/13/2015 09:51 AM, Simon Pasquier wrote: On Wed, May 13, 2015 at 3:27 PM, David Kranz <mailto:dkr...@redhat.com>> wrote: On 05/13/2015 09:06 AM, Simon Pasquier wrote: Hello, Like many others commented before, I don't quite understand how unique are the

<    1   2   3