Difference between revisions of "Nova"
John Garbutt (talk | contribs) m (→Contributor Documentation) |
(→People) |
||
| Line 47: | Line 47: | ||
** TBC | ** TBC | ||
* Gate Czar (on top of the status of Nova in the CI gate) | * Gate Czar (on top of the status of Nova in the CI gate) | ||
| − | ** | + | ** Matt Riedemann (mriedem) |
* [[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) | ||
Revision as of 21:32, 7 May 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/ |
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
- Gate Czar (on top of the status of Nova in the CI gate)
- Matt Riedemann (mriedem)
- API Working Group Liaisons
- Matthew Gilliard (mgilliard) and Alex Xu (alex_xu)
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
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
