Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Design Summit [clear filter]
Tuesday, April 16

11:00am PDT

Tempest Scope
Tempest has grown from smoke tests for Nova, to incorporating most of the core projects, to including CLI testing.

purpose of summit session:
* get a clear definition of Tempest scope that we are good with for Havana (we can revisit at each future summit)
* figure out what other kinds of tests we'd welcome
* if we are increasing scope in a single project, do we have guidelines for reviewing / contributing to get people into core (make sure people are reviewing past just one subdir to ensure we don't have culture framentation)

(Session proposed by Sean Dague)

Tuesday April 16, 2013 11:00am - 11:40am PDT

11:50am PDT

Strategies for Gating in a growing project
Tempest reached an important milestone recently when the whole suite became a gating job for all projects. This is good, but as

1. more tests pour in to projects
2. more projects have multiple API versions
3. more projects become Integrated
4. Tempest moves towards a real acceptance test for OpenStack

it is unlikely that "gate all projects on the full test suite of every other project" is sustainable. We should be able to come up with a better strategy to decide which parts of Tempest should be gating and make gating test coverage more modular while minimizing the risk of regression.

(Session proposed by David Kranz)

Tuesday April 16, 2013 11:50am - 12:30pm PDT

1:50pm PDT

Multi-node Openstack Testing
This session will include the following subject(s):

OpenStack in OpenStack:

In this presentation, we discuss how to deploy a multi-node OpenStack environment inside a typical openstack environment, where you usually get a VM with an internal IP and optionally a public floating IP via NAT. Such a virtual deployment option is desirable for developing and testing new features that require multiple node setup, such as networking, high availability, live upgrade, etc.

We demonstrate a few key enabling technologies:

* nested server virtualization;
* software-defined networking and policy routing for virtual private and public layer-2 networks;
* chef for automatic configuration and deployment.

(Session proposed by Yun Mao)

multi-node openstack testing:

Discuss how the CI system and the Gate can deploy and test multi-node setuips.

Specifically, the TripleO team has been working on a heat-based installation of OpenStack that is also hopefully going to be referenced/used as part of the refstack work. This work allows us to do multi-node deploys without needing to pull in non-OpenStack deployment technology that may be contentious such as puppet, chef, juju or maas. Additionally, work has already started on integrating this work with OpenStack CI.

Talk about the approach in general, and what the status of CI integration is.

(Session proposed by Monty Taylor)

Tuesday April 16, 2013 1:50pm - 2:30pm PDT

2:40pm PDT

FITS testing of public clouds
We run tempest against our code on commit - but it's been suggested/requested that we configure something to be able to run tempest against existing public clouds. There are some logistical issues to consder - such as when to run (every commit to tempest?) and what to do with the results (publish them? tweet about them? carrier pigeon?)

(Session proposed by Monty Taylor)

Tuesday April 16, 2013 2:40pm - 3:20pm PDT

3:40pm PDT

Gating/Validation of OpenStack Deployments
Even though projects are being gated with Tempest, we've found that there are a number defects of that do not appear until OpenStack components are deployed in a larger, more realistic test environment. We'd like to discuss the level of rigor we've defined to gate our deployments and see how we can push that work upstream.

(Session proposed by Daryl Walleck)

Tuesday April 16, 2013 3:40pm - 4:20pm PDT

4:30pm PDT

Upgrade testing and Grenade
Grenade is now running in a non-voting mode for some projects. It is time to firm up the plans for how to use it for gating and the process for tracking failures.

(Session proposed by Dean Troyer)

Tuesday April 16, 2013 4:30pm - 5:10pm PDT

5:20pm PDT

Beyond the API - End to End Testing of OpenStack
While we've done a good job of testing of the APIs with Tempest project, the major of the defects have to do with the actual artifacts generated by API requests (the servers, their networking, etc). I'd like to discuss what a reasonable and achievable goal of extending our test coverage beyond the API would look like.

(Session proposed by Daryl Walleck)

Tuesday April 16, 2013 5:20pm - 6:00pm PDT
Wednesday, April 17

11:00am PDT

Adding new integrated projects to Tempest
The Ceilometer and Heat projects are now integrated projects, and need to be included in the Tempest test suite. We need guidance on how to approach that (what it means, what has to happen, how to avoid pitfalls, whatever). Share your wisdom with us!


(Session proposed by Doug Hellmann)

Wednesday April 17, 2013 11:00am - 11:40am PDT

11:50am PDT

testr / testtools feedback/next-steps
A number of projects have adopted testrepository / testtools at this point. ODS seems like a good point to take stock, gather pain points and plan how to address them.

(Session proposed by Robert Collins)

Wednesday April 17, 2013 11:50am - 12:30pm PDT

1:50pm PDT

Tempest Best Practice Guide
* we seem to have conflicting reviewer opinions on what a good patch is. We should try to consolidate on a single culture for good contributions, as it will confuse new contributors less.
* personally would like to formalize that we're starting from the Nova guidelines and moving on from there.

purpose of summit session:
* get aggrement on HACKING rules that we want to enforce
* figure out what additional rules / collateral / documentation we need to help new contributors onboard
* come up with guidelines on what an ideal test looks like
* what refactorings we should do early in Havana to get closer to ideal
* what good changesets look like (agreement on scope and patch series)

(Session proposed by Sean Dague)

Wednesday April 17, 2013 1:50pm - 2:30pm PDT

2:40pm PDT

Rackspace testing engine Case Study/Overview
RAX is open sourcing it's internal testing framework used to test our deployed OpenStack instances. We would like to have a session to demo and discuss our approach, how it could be used in the community, etc..

(Session proposed by Sam Danes)

Wednesday April 17, 2013 2:40pm - 3:20pm PDT

3:40pm PDT

Tempest - Gap Analysis - Identify new testsdevelop

1.Identify test gaps for all core services Swift,Nova, Keystone, Cinder and Quantum projects .
2.From gaps, identify new tests to be written to have coverage.
3.Discuss as part of design session that leads to new blueprints and blueprint ownership for Havana release

Etherpad: https://etherpad.openstack.org/havana-gap-analysis

(Session proposed by Ravikumar Venkatesan)

Wednesday April 17, 2013 3:40pm - 4:20pm PDT