OpenStack Kilo Design Summit has ended
This is the schedule for the Kilo Design Summit, where OpenStack contributors discuss the future of OpenStack development.
Click here for the main OpenStack Summit conference schedule.

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

Wednesday, November 5

09:00 CET

Gap analysis for using Tempest in production
Tempest should be able to run against any OpenStack cloud as README says. However, it's difficult to run against production (not devstack) OpenStack cloud now. In this session, we will talk about the gap that we should resolve. For example, UX(there are hundreds configs..), stability, performance etc.. Topic for which we already have bp done/in progress/todo, e.g. Cleanup of resources, run with pre-provisioned accounts (no overall admin required for parallel run)

Some subtopics which may be discussed as part of this session are:

Tempest UX Improvements, revisiting a GUI/service, tempest/rally integration

Wednesday November 5, 2014 09:00 - 09:40 CET

11:00 CET

Tempest scope in the brave new world
As part of the discussions during the Juno cycle about the gate scaling limits we've been encroaching on, one of the solutions was to switch a large portion of the functional testing burden back into the individual projects. So where does this leave tempest? This session will be concerned with defining exactly what the scope of tempest should be moving forward, and how it fits in the greater testing scheme within OpenStack.

Wednesday November 5, 2014 11:00 - 11:40 CET

14:40 CET

QA/Infra: Gating relationships
Discuss evolving needs of project gates. Criteria on what project interfaces need what kind of testing or gating. How to ensure that is kept up to date over time. What can be automated? How to document the result so that developers understand what is being tested, how, and when.

Wednesday November 5, 2014 14:40 - 15:20 CET

15:30 CET

QA and CI after merge
Moving forward there is a desire to reduce the scope of the gate to a stable and reliable "gold standard" and move the testing of special cloud configurations and scenarios to post merge. [0] This is to help reduce the complexity of the gate to make it more reliable and easier to debug for everyone. But, first we need to define what kind of scenarios are outside of the gold standard and should be tested post merge. There is also a gap in the tooling for this effort, we need a dashboard and other tools to advertise the test results properly and to simplify troubleshooting.

Discussion on test after code merge:
- Which features to verify after merge
- Which kind of tests (flacky, long running, multinode)
- How to track results trends
- How to save features and tests verified after merge from bit rot

[0] http://lists.openstack.org/pipermail/openstack-dev/2014-July/041057.html

17:20 CET

Tempest-lib moving forward
During the juno release the tempest-lib project was started. The goal of tempest-lib is to take some of the common glue in tempest and create an externally consumable library that will enable creating additional test suites easily using similar mechanisms to tempest. This session aims to be a discussion on how tempest-lib should evolve and what functionality should be in it as opposed to tempest.

Wednesday November 5, 2014 17:20 - 18:00 CET
Thursday, November 6

11:50 CET

Future Auth interface design for Tempest
As part of the work to stabilize the interfaces which should be externally consumable one of particular note is the auth layer in tempest. Currently it's designed to be fairly modular and has 2 implementations for either keystone v2 or v3, but it is still has some underlying assumptions about how the auth is setup. However, as part of the migration to tempest-lib this interface arguably should be created in a way which doesn't assume keystone is the auth mechanism being used. The in-tree implemenations of the interface will still be keystone specific, but it will allow external consumers to use whatever auth system they need.(for example swift auth) This session will discuss how we should implement the to-be auth interface in tempest-lib (by considering some use cases) to make it work for most use cases.

Thursday November 6, 2014 11:50 - 12:30 CET

14:30 CET

Discussion of the direction that should be taken for devstack and grenade during the kilo cycle.

Thursday November 6, 2014 14:30 - 15:10 CET
Friday, November 7

09:00 CET

Infra / QA / RelMgt contributors meetup
The contributors meetup is a informal gathering of the project contributors, with an open agenda.

Friday November 7, 2014 09:00 - 12:30 CET

13:40 CET

Infra / QA / RelMgt contributors meetup
The contributors meetup is a informal gathering of the project contributors, with an open agenda.

Friday November 7, 2014 13:40 - 17:10 CET