Difference between revisions of "Meetings/DBTeamMeeting"
< Meetings
(minor edits. add note "not dbaas") |
|||
| Line 14: | Line 14: | ||
** db-archiving | ** db-archiving | ||
** backportable-db-migrations | ** backportable-db-migrations | ||
| + | ** preventing sqlalchemy objects from being returned by nova.db.api | ||
| + | ** change nova/db/api to assume no more than one nova-compute per host (https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L380) | ||
| + | ** how to shrink nova/db/api | ||
| + | ** discussing any known performance issues | ||
* Open discussion | * Open discussion | ||
== Previous meetings == | == Previous meetings == | ||
Previous meetings, with their notes and logs, can be found in under [[Meetings/DBMeetingLogs]]. | Previous meetings, with their notes and logs, can be found in under [[Meetings/DBMeetingLogs]]. | ||
Revision as of 17:46, 1 November 2012
Weekly team meeting
There is a public weekly meeting held in #openstack-meeting, Fridays at 00:00 UTC, to discuss database usage within Openstack. This is not the DBaaS meeting. Historically, this was the NovaDB team meeting, but other projects share the same concerns, and with Grizzly there is ongoing work to create a shared db-common (oslo) project. Everyone interested in database-related topics (consistency, performance, HA, etc) is encouraged to attend.
Agenda for next meeting
- Discuss ongoing projects
- db-common (oslo)
- no-db-compute
- db-consistency
- db-archiving
- backportable-db-migrations
- preventing sqlalchemy objects from being returned by nova.db.api
- change nova/db/api to assume no more than one nova-compute per host (https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L380)
- how to shrink nova/db/api
- discussing any known performance issues
- Open discussion
Previous meetings
Previous meetings, with their notes and logs, can be found in under Meetings/DBMeetingLogs.
