Jump to: navigation, search

Difference between revisions of "Nova"

m (People)
(People: Add link to Nova-Ironic wiki page)
Line 54: Line 54:
* [[Nova/APIWGLiaisons|API Working Group Liaisons]]
* [[Nova/APIWGLiaisons|API Working Group Liaisons]]
** Matthew Gilliard (mgilliard) and Alex Xu (alex_xu)
** Matthew Gilliard (mgilliard) and Alex Xu (alex_xu)
* Ironic Liaison
* [[Nova-Ironic|Ironic Liaison]]
** John Villalovos (jlvillal)
** John Villalovos (jlvillal)
** Michael Davies (mrda) (backup)
** Michael Davies (mrda) (backup)

Revision as of 22:33, 12 May 2015



Official name OpenStack Compute
Source code https://github.com/openstack/nova
Bug tracker https://bugs.launchpad.net/nova
Feature tracker https://blueprints.launchpad.net/nova
Developer doc http://docs.openstack.org/developer/nova/

Python Nova client

Source code https://github.com/openstack/python-novaclient
Bug tracker https://bugs.launchpad.net/python-novaclient
Feature tracker https://blueprints.launchpad.net/python-novaclient


  • PTL
    • John Garbutt (johnthetubaguy)
  • Feature Drivers
  • Code Reviewers
  • Blueprint Czar (responsible for maintenance of Nova's blueprint lists)
    • TBC
  • Bug Czar (responsible for organizing Nova's bug team that maintains Nova's bug list)
    • TBC
  • Security Czar (responsible for working with VMT and leading nova-coresec)
    • Michael Still (mikal)
  • Gate Czar (on top of the status of Nova in the CI gate)
    • Matt Riedemann (mriedem)
  • APAC/US Meeting Czar (runs the 2100 UTC Nova meeting)
    • Michael Still (mikal)
  • API Working Group Liaisons
    • Matthew Gilliard (mgilliard) and Alex Xu (alex_xu)
  • Ironic Liaison
    • John Villalovos (jlvillal)
    • Michael Davies (mrda) (backup)
  • python-novaclient Czar
    • TBC
  • Mentoring (and Answers) Czar
    • TBC
  • Release Czar and Stable Branch Czar
    • TBC
  • Docs Czar
    • TBC

For bug tag owners, please see: Nova Bug Triage

For other folks, please see: Cross Project Liaisons (CPLs)


  • Previous PTLs
    • Vish Ishaya (vishy), project beginning until Grizzly release
    • Russell Bryant (russellb), Havana and Icehouse releases
    • Michael Still (mikal), Juno and Kilo releases

General Resources


Release Process

  • Nova releases are now done by providing the Release Manager with a git SHA to tag
  • Client releases are done by following Nova/Client Release Process

Other resources

Resources for Contributors

Contributor Documentation

Nova subteams

The Nova team meets weekly: Meetings/Nova. In addition to a project-wide Nova gathering each week, there are some sub-teams. These sub-teams get together to discuss work going on in a focused area of Nova.

Notes on Sub-teams:
  • The linked wiki page should include:
    • The mission of the team
    • A regular meeting time
    • A coordinator / point of contact
    • Meeting Agenda
    • Links to logs from previous meetings
  • A sub-team representative should regularly attend the main Nova meeting to provide a sub-team status report.
  • A sub-team is *not* exclusively responsible for an area of code. Anyone is welcome to contribute anywhere. However, you are encouraged to communicate regularly with others working in the same area as you and sub-teams help encourage that.
  • A sub-team is about organizing development efforts, but not necessarily setting direction for the project in a given area. Review of patches is still done by the nova-core team and it is beneficial to publish designs to the openstack-dev mailing list for vetting in advance.
Active Sub-teams: