Difference between revisions of "Meetings/Libvirt"
(→Libvirt Meetings) |
(→Libvirt Meetings) |
||
(11 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
= Libvirt Meetings = | = Libvirt Meetings = | ||
− | + | === As of at least May 2015 [1] the weekly libvirt sub-team meeting has been disbanded due to lack of interest/attendance. === | |
− | + | [1] http://eavesdrop.openstack.org/meetings/nova/2015/nova.2015-05-28-14.02.log.html | |
== Who are we ? == | == Who are we ? == | ||
Line 33: | Line 33: | ||
=== Contact info === | === Contact info === | ||
− | Email: openstack-dev@lists.openstack.org (tag with [nova][libvirt]) | + | Email: <code><nowiki>openstack-dev@lists.openstack.org</nowiki></code> (tag with [nova][libvirt]) |
− | IRC: #openstack-dev on freenode (OpenStack specific) or #virt on oftc.net (Libvirt upstream developers) | + | IRC: <code><nowiki>#openstack-dev</nowiki></code> on freenode (OpenStack specific) or #virt on oftc.net (Libvirt upstream developers) |
== Meetings == | == Meetings == | ||
+ | |||
+ | === As of at least May 2015 [1] the weekly libvirt sub-team meeting has been disbanded due to lack of interest/attendance. === | ||
+ | |||
+ | [1] http://eavesdrop.openstack.org/meetings/nova/2015/nova.2015-05-28-14.02.log.html | ||
=== Agenda === | === Agenda === | ||
Line 49: | Line 53: | ||
=== Schedule === | === Schedule === | ||
− | * Tuesday, May 20th. 1500 UTC ([[ | + | * Tuesday, August 19th, 1500 UTC ([[Meetings/Libvirt/Minutes/20140819 |Minutes]], [http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-08-19-15.00.html IRC logs]]] |
+ | * Tuesday, June 10th. 1500 UTC ([[Meetings/Libvirt/Minutes/20140610 |Minutes]], [http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-10-15.00.html IRC logs]]] | ||
+ | * Tuesday, June 3rd. 1500 UTC ([[Meetings/Libvirt/Minutes/20140603 |Minutes]], [http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-03-15.00.html IRC logs]]] | ||
+ | * Tuesday, May 27th. 1500 UTC ([[Meetings/Libvirt/Minutes/20140527 |Minutes]], [http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-05-27-15.01.html IRC logs]]] | ||
+ | * Tuesday, May 20th. 1500 UTC ([[Meetings/Libvirt/Minutes/20140520 |Minutes]], [http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-05-20-15.00.html IRC logs]]] | ||
+ | |||
+ | [[Category: Nova]] | ||
+ | [[Category: meetings]] |
Latest revision as of 14:46, 3 September 2015
Contents
Libvirt Meetings
As of at least May 2015 [1] the weekly libvirt sub-team meeting has been disbanded due to lack of interest/attendance.
[1] http://eavesdrop.openstack.org/meetings/nova/2015/nova.2015-05-28-14.02.log.html
Who are we ?
The group is a subset of the Nova developers interested in the Libvirt driver in Nova, for any hypervisor (including but not limited to KVM, QEMU, Xen (libxl) and LXC), and welcomes contribution from interested parties representing any other OpenStack projects that utilize / integrate with Libvirt.
Mission
The mission of the team is
- To ensure Libvirt continues to be the leading virtualization driver in Nova for any hypervisor it supports"
Tasks
The areas the team works in are many and varied
- Triage incoming bug reports
- Review of blueprints / nova-specs
- Tracking of progress / resolving roadblocks in development / reviews
- Respond to gate stability issues impacting libvirt CI
- Planning / assistence for bringing new libvirt hypervisor/container drivers into Nova
Leadership
Meeting facilitator
- Daniel Berrange (IRC: danpb, Red Hat)
Contact info
Email: openstack-dev@lists.openstack.org
(tag with [nova][libvirt])
IRC: #openstack-dev
on freenode (OpenStack specific) or #virt on oftc.net (Libvirt upstream developers)
Meetings
As of at least May 2015 [1] the weekly libvirt sub-team meeting has been disbanded due to lack of interest/attendance.
[1] http://eavesdrop.openstack.org/meetings/nova/2015/nova.2015-05-28-14.02.log.html
Agenda
Add items for discussion to the team meeting etherpad
Etherpad to be copied to a wiki page 'Meeting/Libvirt/Mintues/YEARMONTHDAY' after the meeting completes