Difference between revisions of "Nova"
John Garbutt (talk | contribs) m (→Nova) |
John Garbutt (talk | contribs) m (→Nova) |
||
Line 22: | Line 22: | ||
|} | |} | ||
− | We align with what was the integrated release schedule, with three milestones. For liberty this means: [Liberty_Release_Schedule] | + | We align with what was the integrated release schedule, with three milestones. For liberty this means: [[Liberty_Release_Schedule]] |
=== Python Nova client === | === Python Nova client === |
Revision as of 11:28, 4 June 2015
Contents
Projects
Nova
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/ |
We align with what was the integrated release schedule, with three milestones. For liberty this means: Liberty_Release_Schedule
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 |
People
- 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
- Stable Branch Czar (works with stable maintenance team around Nova things)
- Matt Riedemann (mriedem)
- 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 (gilliard) and Alex Xu (alex_xu)
- Ironic Liaison
- John Villalovos (jlvillal)
- Michael Davies (mrda) (backup)
- python-novaclient Czar
- TBC
- Mentoring Czar
- John Garbutt (johnthetubaguy)
- Answers Czar
- Release Czar
- TBC
- Docs Czar
- TBC
For bug tag owners, please see: Nova Bug Triage
For other folks, please see: Cross Project Liaisons (CPLs)
General Resources
Documentation
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
- Details about the hypervisor support matrix
Resources for Contributors
Contributor Documentation
- General Developer's Guide
- Nova Architecture and long term plan Docs
- When you need a spec vs a blueprint
- nova-spec process
- Bug Triage Process and Bug tag owners
- Nova/ReleaseChecklist
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:
- EC2 API
- Hyper-V
- Nova Bugs
- Gantt (ex-Scheduler) (Meetings)
- VMwareAPI
- XenAPI
- Libvirt
- Containers
- Docker
- Cellsv2
History
- Previous PTLs
- Vish Ishaya (vishy), project beginning until Grizzly release
- Russell Bryant (russellb), Havana and Icehouse releases
- Michael Still (mikal), Juno and Kilo releases
- Previous or current core reviewers:
- Andrew Laski
- Brian D. Elliott
- Brian Lamar
- Brian Waldon
- Chris Behrens
- Chris Yeoh
- Dan Prince
- Dan Smith
- Daniel Berrange
- Devananda van der Veen
- Jay Pipes
- Joe Gordon
- Johannes Erdfelt
- John Garbutt
- Ken'ichi Ohmichi
- Kevin L. Mitchell
- Lorin Hochstein
- Mark McLoughlin
- Matt Dietz
- Matt Riedemann
- Melanie Witt
- Michael Still
- Nikola Dipanov
- Pádraig Brady
- Paul Voccio
- Rick Harris
- Russell Bryant
- Sandy Walsh
- Sean Dague
- Soren Hansen
- Trey Morris
- Vishvananda Ishaya
- Yun Mao
Developer Contacts
Work In Progress The following is a list of major subsystems within Nova and people that you can approach on IRC or email if you have questions about that particular subsystem. IRC nicks are in parentheses.
Nova Objects Framework
- Dan Smith (dansmith) - Jay Pipes (jaypipes)
libvirt virt driver
- Dan Berrange (danpb)
Hyper-V virt driver
- Claudiu Belu (claudiub)
VMWare/vCenter virt driver
- Gary Kotton (garyk) - Radoslav Gerganov (rgerganov)
XenAPI virt driver
- John Garbutt (johnthetubaguy)
Ironic/bare metal
- Devananda van der Veen (devananda)
Scheduling and resource tracking
- Sylvain Bauza (bauzas) - Jay Pipes (jaypipes)
Block device mapping and volume attachments
- Nikola Dipanov (ndipanov)
REST API
- Sean Dague (sdague) - Alex Xu (alex_xu)
Database
- Andrew Laski (alaski)
Cells (v1 and v2)
- Andrew Laski (alaski) - Melanie Witt (melwitt)
nova-network
- ?
Neutron
- Brent Eagles (beagles)
RPC and notification system
- Dan Smith (dansmith)
So, you want to learn more about Nova?
To learn more about Nova, please read out about Nova Mentoring