Jump to: navigation, search

Design Summit

Revision as of 09:34, 28 March 2012 by ThierryCarrez (talk)

At OpenStack Design Summits the developers community gathers to discuss the requirements for the next release and connect with other community members.

Next Summit

Folsom Design Summit, Apr 16-18 in San Francisco: see details at Summit/Folsom

How does the summit work ?

The design summit is not a classic conference with speakers and presentations. Developers submit session ideas to discuss upcoming features for the next release cycle, which get reviewed and scheduled by the track leads. Those sessions can include formal presentations but are usually an open brainstorming discussion on a given subject or feature. If you care about a particular subject, please join. Due to the nature of the event, the schedule is a bit dynamic, so check out the summit schedule pages often.

Each session is moderated by a session lead, usually the person that proposed the session in the first place.

The OpenStack Design Summit is not the right place to get started or learn the basics of OpenStack. For that it's better to check the various OpenStack meetups organized by user groups around the world or one of the OpenStack conferences, which to date have happened the same week as the Design Summits.

Session types

The sessions come in three different flavors:

  • Brainstorm sessions are used to discuss and come up with a solution for complex issues
  • Presentation sessions are formal talks (with slides) presenting a given plan
  • Workshop sessions are hands-on workshops or tutorials around a given task or part of code

Those sessions can last 25min, 55min or 85min.

Tracks

The summit sessions fall into the following pre-defined tracks (and track leads):

  • Common development: Development processes and tools, release schedule, openstack-common (ttx)
  • Swift: OpenStack Object Storage (notmyname)
  • Nova core: OpenStack Compute core features, APIs, message queue... (vishy)
  • Nova hypervisors: Compute API, supported hypervisors and feature parity (soren)
  • Nova scaling: Scaling OpenStack Compute: cells, datastore, threading... (comstud)
  • Nova volumes: Future improvements in OpenStack Compute volumes (john-griffith)
  • Nova other: Other Nova stuff that doesn't fit in the previous categories (vishy)
  • Keystone: OpenStack Identity (heckj)
  • Glance: OpenStack Image service (bcwaldon)
  • Horizon: OpenStack Dashboard (devcamcar)
  • Quantum/Networking: Quantum project, Nova networking, Melange (danwent)
  • Documentation: Future efforts on documentation (annegentle)
  • QA: Quality assurance, unit tests, integration tests, Tempest... (jaypipes)
  • Deployment/Ops: OpenStack-wide packaging, integration issues, operational needs and challenges, admin tools... (anotherjesse)
  • Ecosystem & Open Space: peripheral projects, topics, and technical communities supporting OpenStack, and space to continue discussions that overflow sessions or come about from hall conversations. Time slots will be kept open for unconferencing -- proposals made and decided upon live in real-time by the participants. (lloydde)

Finally we also propose a set of 5min-long Lightning talks every day after lunch (first come first serve).

Before the summit

Propose sessions

  • Go to http://summit.openstack.org to propose sessions. You'll be authenticated through Launchpad SSO.
  • Click on Propose session on the sessions list screen to submit your own session topic
  • See information above to choose the right session type and appropriate track
  • For sessions about features, you should create a Launchpad blueprint to track its design and implementation, and add a link to it on the session proposal (example: nova/better-api to link to the better-api Nova blueprint).
  • Your proposal will initially be in Unreviewed status. It can then go to the following statuses:
    • Accepted: Your session was accepted and will be scheduled
    • WaitingList: Your session is accepted in a secondary list and will be scheduled if room is left in the schedule
    • NeedsFixing: Your proposal needs to be fixed before it can be accepted, please address reviewers comments
    • Refused: Your proposal has been rejected, see reviewers comments for an explanation

At the summit

  • The schedule will be available online. Refer to it early, refer to it often
  • The session should start on time, be there or be square
  • The session lead starts by introducing clearly what the session is about (and what it is not about) to set expectations
  • It is the responsibility of the session lead to keep the discussion live and on-topic
  • Make the best use of the available time !
  • Collaborative note taking during the session should be done through http://etherpad.openstack.org, please participate and make sure your points are reported there
  • In brainstorm sessions, 10 minutes before the end of the session, the session lead should start making sure he gets clear outcomes, work items and actions from the session
  • End on time, to give participants the time to switch rooms to the next session if needed