OpenStack - User contributions [en]

Governance/Foundation/5Nov2017BoardMeeting

2017-10-26T15:25:44Z

Flaper87: /* Leadership Meeting Agenda */

The OpenStack Board and joint leadership meeting will be held November 5th, Sydney Australia in the Sydney ICC

The OpenStack Board will meet from 9am to 11am. The joint leadership meeting will be held from 11am to 5pm.

To join the session:
# Go to https://openstack.webex.com/openstack/k2/j.php?MTID=t53950a00f714e0e71a4e2aabd8ac9e68
# Enter your name and email address.
# Enter the session password: This session does not require a password.
# Click "Join Now".
# Follow the instructions that appear on your screen.
#: Session number: 927 178 747
#: Session password: This session does not require a password.

== Board Meeting Agenda - Tenative ==
: Chair: Alan Clark, Vice Chair: Lew Tucker
: Executive Director: Jonathan Bryce
: Minutes: Mark Radcliffe
:
:: Non official meeting discussion Channels:
::* webex chat
::* IRC: #openstack-board
::* Etherpad: https://etherpad.openstack.org/p/UnofficialBoardNotes-Nov5-2017
:
'''(9:00) Call To Order, Open Session'''
# Role Call
# Welcome to the board Tristan Goode, Aptira. Thank you Jessica for your time and contribution to the OpenStack Board
#Approve the minutes from the 10 October 2017 board meeting

''' (10:00) Strategic Discussions'''
# New Projects Under The OpenStack Umbrella - Jonathan
## Proposed structure / process

'''(11:00) Committee Actions and Updates'''
# (11:00) Membership Committee - Rob, Anni
* New member application
'''(11:30) Board Executive Meeting'''


'''(12:00) Close of meeting'''
''' (12:00) Break for Lunch '''

== Leadership Meeting Agenda ==
: Chair: Alan Clark, Vice Chair: Lew Tucker
: Chair: Thierry Carrez
: Chair: Edgar Magana
: Executive Director: Jonathan Bryce
'''(13:00) Call To Order, Open Session'''
# Agenda Items TBD
# Top-5 "help wanted" list review (Thierry, Doug)
# Developer satisfaction: a look back at the results of the questions around satisfaction in the PTG survey (Chris D.)
# Revisit "New Projects Under The OpenStack Umbrella" while the UC and TC are in session (if not otherwise there earlier)
# Heads up on upcoming research on improving inclusiveness in our community: Request for feedback on previous works, if any (flaper87, cmurphy, TheJulia)

'''(16:30) Leadership Photo'''
:
'''(17:00) Close of meeting'''

''' Evening Event '''

Meetings/TechnicalCommittee

2017-08-25T09:55:39Z

Flaper87: /* Current proposals */

__NOTOC__

The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode. See the [https://governance.openstack.org/tc/#how-to-propose-governance-changes governance website] for details on how to propose governance changes.

=== Current proposals ===
''Status last updated: August 25th, 2017''

'''Leadership'''
* ''Adding infra to the top 5 help wanted list (fungi)''
** ''Next step: fungi to raise discussion / submit a proposal''

'''New project teams'''
* Add Stackube project team [https://review.openstack.org/462460]
** Status: Project was set up, ready for review again. Dims mentoring.
* Add Glare project team [https://review.openstack.org/479285]
** Status: Ready for review again. Team will meet with TC at the PTG.
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
* Add Blazar project team [https://review.openstack.org/482860]
** Status: Ready for review again. Team will meet with TC at the PTG.
* Add Gluon project team [https://review.openstack.org/463069]
** Status: Frozen while Gluon discusses further integration opportunities with Neutron
** Next step: Meet with the TC at the PTG to discuss recent progress in Neutron integration

'''Inclusion & Diversity'''
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
** Status: Discussion in progress on latest revision. Is likely to be transformed into guidance in the Project Team Guide
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
** Status: Voting in progress
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
** ''Status: ML created, "meta" SIG set up, first workgroups to be migrated''
** ''Next step: Migrate volunteer WGs''

'''Other'''
* Amend leaderless program resolution timeframe [https://review.openstack.org/492578] (persia)
** Status: Majority reached on Aug 17, to be approved early next week
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87)
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
** Status: Voting in progress
* Appoint Kota TSUYUZAKI as Storlets PTL for Queens [https://review.openstack.org/493846] (ttx)
** Status: Majority reached on Aug 21st, to be approved early next week
* Be explicit about supported database versions [https://review.openstack.org/493932] (mordred)
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html
** Status: Open discussion
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
** Status: Frozen while thingee works on driver discoverability
* networking-cisco project team addition [https://review.openstack.org/363709] (thingee)
** Status: Blocked until driver teams are a thing
** Next step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue
* ''How to deal with confusion around "hosted" projects (ttx)''
** ''Initial ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118368.html''
** ''Subsequent ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119043.html''
** ''Status: Brainstorming''

=== Next Meeting ===

* Date: tbd
* Chair: tbd

==== Agenda ====

* tbd

==== Apologies for Absence ====

* tbd

=== Past meetings logs ===

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc

[[Category: meetings]]

Forum/Boston2017

2017-05-11T13:08:09Z

Flaper87: /* Thursday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - https://etherpad.openstack.org/p/doc-future
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* 12:05 etcd as a base service - https://etherpad.openstack.org/p/BOS-etcd-base-service
* [12:45pm-2:00pm] - Zaqar Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-zaqar-project-onboarding
* [2:00pm-3:30pm] - Hierarchical Quotas - https://etherpad.openstack.org/p/BOS-forum-quotas
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:00pm-3:30pm] - Zun Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-zun-project-onboarding
* [2:00pm-2:40pm] - Ironic Feedback Session - https://etherpad.openstack.org/p/BOS-forum-ironic-feedback
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - neutron multi-site https://etherpad.openstack.org/p/pike-neutron-multi-site
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [3:40pm-4:20pm] - Deprecating Postgresql https://etherpad.openstack.org/p/BOS-postgresql
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [4:40pm-5:20pm] - CellsV2 Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-cellsv2-developer-community-coordination
* [4:40pm-6:10pm] - QA onboarding at the forum - https://etherpad.openstack.org/p/BOS-QA-onboarding
* [5:30pm-6:10pm] - How do you use Glance? - https://etherpad.openstack.org/p/BOS-forum-how-do-you-use-glance
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances
* [5:30pm-6:10pm] - https://etherpad.openstack.org/p/BOS-k8s-SIG-PM

= Tuesday =
* [11:15am-11:55am] Distributed SNAT with DVR - https://etherpad.openstack.org/p/boston-dvr
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:00pm-3:30pm] OpenStack User API Improvements - https://etherpad.openstack.org/p/BOS-forum-openstack-user-api-improvements
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [2:50pm-3:30pm] Openstack on The Edge - Fog Edge Massively Distributed clouds - birds-of-a-feather - https://etherpad.openstack.org/p/BOS-Fog-Edge-MassivelyDistributed-BoF
* [2:50pm-3:30pm] Container Sharding - https://etherpad.openstack.org/p/BOS-swift-container-sharding
* [3:40pm-4:20pm] OpenStack-Ansible Operator Feedback - https://etherpad.openstack.org/p/BOS-osa-ops-feedback
* [3:40pm-4:20pm] Swift lots of small files (losf) optimisation - https://etherpad.openstack.org/p/swift-losf-base
* [3:40pm-4:20pm] https://etherpad.openstack.org/p/BOS-financial-WG
* [3:40pm-4:20pm] API Microversion Discussion Hour - https://etherpad.openstack.org/p/BOS-api-microversions
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [4:40pm-5:20pm] Exposing Deployer Differences Without Death https://etherpad.openstack.org/p/BOS-forum-exposing-deployer-differences
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds
* [5:30pm-6:10pm] https://etherpad.openstack.org/p/BOS-forum-future-of-hypervisor-tuning

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [9:50am-10:30am] Advanced Instance Scheduling: Reservations and Preemption - https://etherpad.openstack.org/p/BOS-forum-advanced-instance-scheduling
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:00am-11:40am] - Large Deployment Team (1/2) https://etherpad.openstack.org/p/BOS-forum-large-deployment-team
* [11:00am-11:40am] - The Future of VPN as a Service (VPNaaS) https://etherpad.openstack.org/p/boston-vpnaas
* [11:50am-12.30pm] - OpenStack Operators Ops Meetup Team Catch-Up - https://etherpad.openstack.org/p/BOS-forum-ops-catch-up
* [11:50am-12:30pm] Comparing OpenStack and Kubernetes Resource Tracking - https://etherpad.openstack.org/p/BOS-forum-openstack-k8s-resource-tracking
* [11:50am-12:20pm] Making Neutron Easy for people who want basic Networking - https://etherpad.openstack.org/p/pike-neutron-making-it-easy
* [11:50am-12:30pm] App Developer Enablement Working Group - https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org
* [12:30pm-1:50pm] - OpenStack Karbor project onboarding - https://etherpad.openstack.org/p/BOS-Karbor-onboarding
* [1:50pm-2:30pm] Neutron pain points - https://etherpad.openstack.org/p/neutron-boston-painpoints
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [2:40pm-3:20pm] Scientific OpenStack BoF - https://etherpad.openstack.org/p/Scientific-WG-boston
* [2:40pm-3:20pm] Methods and Projects for Deploying OpenStack with Containers - https://etherpad.openstack.org/p/boston-deploying-openstack-on-k8s
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [3:30pm-4:10pm] Neutron Diagnostics Tools - https://etherpad.openstack.org/p/pike-neutron-diagnostics
* [3:30pm-4:10pm] LCOO Main Working Group-Continue Roadmap Dicussion: https://etherpad.openstack.org/p/BOS-forum-LCOOWG
* [3:30pm-4:10pm] API-WG BoF https://etherpad.openstack.org/p/BOS-API-WG-BOF
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [4:30pm-5:10pm] Ops Tags WG session - https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session
* [4:30pm-5:10pm] Horizon operator / plugin feedback - https://etherpad.openstack.org/p/horizon-pike-feedback
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks
* [5:20pm-6:00pm] Fog/Edge/Massively Distributed Clouds (working group session) - https://etherpad.openstack.org/p/Massively_distributed_wg_boston_summit
* [5:20pm-6:00pm] Cloud-Native Design/Refactoring Across OpenStack https://etherpad.openstack.org/p/cloud-native-forum

= Thursday =
* [9:00am-9:40am] Containers lifecycle management: https://etherpad.openstack.org/p/BOS-forum-containers-lifecycle-management
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [9:50am-10:30am] - Strategy for Unanswered Requirements - https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:00am - 11:40] Zun Developer/Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-zun-developer-operator-feedback
* [11:00am - 11:40] High Availability in OpenStack - https://etherpad.openstack.org/p/BOS-forum-HA-in-openstack
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [11:50am-12:30pm] LCOO Get to know us at the Boston Summit - https://etherpad.openstack.org/p/BOS-forum-LCOOGetToKnow
* [1:30pm-2:10pm] User Committee Session - https://etherpad.openstack.org/p/BOS-forum-user-committee-session
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications
* [5:00pm-5:40pm] UC Governance and Support of WGs - https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - Continuing the discussion from container deployment session https://etherpad.openstack.org/p/boston-deploying-openstack-on-k8s
* 2:20-3:00 MR102 - Swift Rebalance Optimizations https://etherpad.openstack.org/p/swift-rebalance
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - Discussion of use cases for alternate messaging technology with oslo.messaging https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Forum/Boston2017

2017-05-10T21:44:51Z

Flaper87: /* Wednesday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - https://etherpad.openstack.org/p/doc-future
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* 12:05 etcd as a base service - https://etherpad.openstack.org/p/BOS-etcd-base-service
* [2:00pm-3:30pm] - Hierarchical Quotas - https://etherpad.openstack.org/p/BOS-forum-quotas
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:00pm-3:30pm] - Zun Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-zun-project-onboarding
* [2:00pm-2:40pm] - Ironic Feedback Session - https://etherpad.openstack.org/p/BOS-forum-ironic-feedback
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - neutron multi-site https://etherpad.openstack.org/p/pike-neutron-multi-site
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [3:40pm-4:20pm] - Deprecating Postgresql https://etherpad.openstack.org/p/BOS-postgresql
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [4:40pm-5:20pm] - CellsV2 Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-cellsv2-developer-community-coordination
* [4:40pm-6:10pm] - QA onboarding at the forum - https://etherpad.openstack.org/p/BOS-QA-onboarding
* [5:30pm-6:10pm] - How do you use Glance? - https://etherpad.openstack.org/p/BOS-forum-how-do-you-use-glance
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances
* [5:30pm-6:10pm] - https://etherpad.openstack.org/p/BOS-k8s-SIG-PM

= Tuesday =
* [11:15am-11:55am] Distributed SNAT with DVR - https://etherpad.openstack.org/p/boston-dvr
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:00pm-3:30pm] OpenStack User API Improvements - https://etherpad.openstack.org/p/BOS-forum-openstack-user-api-improvements
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [2:50pm-3:30pm] Openstack on The Edge - Fog Edge Massively Distributed clouds - birds-of-a-feather - https://etherpad.openstack.org/p/BOS-Fog-Edge-MassivelyDistributed-BoF
* [2:50pm-3:30pm] Container Sharding - https://etherpad.openstack.org/p/BOS-swift-container-sharding
* [3:40pm-4:20pm] OpenStack-Ansible Operator Feedback - https://etherpad.openstack.org/p/BOS-osa-ops-feedback
* [3:40pm-4:20pm] Swift lots of small files (losf) optimisation - https://etherpad.openstack.org/p/swift-losf-base
* [3:40pm-4:20pm] https://etherpad.openstack.org/p/BOS-financial-WG
* [3:40pm-4:20pm] API Microversion Discussion Hour - https://etherpad.openstack.org/p/BOS-api-microversions
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [4:40pm-5:20pm] Exposing Deployer Differences Without Death https://etherpad.openstack.org/p/BOS-forum-exposing-deployer-differences
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds
* [5:30pm-6:10pm] https://etherpad.openstack.org/p/BOS-forum-future-of-hypervisor-tuning

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [9:50am-10:30am] Advanced Instance Scheduling: Reservations and Preemption - https://etherpad.openstack.org/p/BOS-forum-advanced-instance-scheduling
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:00am-11:40am] - Large Deployment Team (1/2) https://etherpad.openstack.org/p/BOS-forum-large-deployment-team
* [11:00am-11:40am] - The Future of VPN as a Service (VPNaaS) https://etherpad.openstack.org/p/boston-vpnaas
* [11:50am-12.30pm] - OpenStack Operators Ops Meetup Team Catch-Up - https://etherpad.openstack.org/p/BOS-forum-ops-catch-up
* [11:50am-12:30pm] Comparing OpenStack and Kubernetes Resource Tracking - https://etherpad.openstack.org/p/BOS-forum-openstack-k8s-resource-tracking
* [11:50am-12:20pm] Making Neutron Easy for people who want basic Networking - https://etherpad.openstack.org/p/pike-neutron-making-it-easy
* [11:50am-12:30pm] App Developer Enablement Working Group - https://etherpad.openstack.org/p/BOS-forum-developer-openstack-org
* [12:30pm-1:50pm] - OpenStack Karbor project onboarding - https://etherpad.openstack.org/p/BOS-Karbor-onboarding
* [1:50pm-2:30pm] Neutron pain points - https://etherpad.openstack.org/p/neutron-boston-painpoints
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [2:40pm-3:20pm] Scientific OpenStack BoF - https://etherpad.openstack.org/p/Scientific-WG-boston
* [2:40pm-3:20pm] Methods and Projects for Deploying OpenStack with Containers - https://etherpad.openstack.org/p/boston-deploying-openstack-on-k8s
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [3:30pm-4:10pm] Neutron Diagnostics Tools - https://etherpad.openstack.org/p/pike-neutron-diagnostics
* [3:30pm-4:10pm] LCOO Main Working Group-Continue Roadmap Dicussion: https://etherpad.openstack.org/p/BOS-forum-LCOOWG
* [3:30pm-4:10pm] API-WG BoF https://etherpad.openstack.org/p/BOS-API-WG-BOF
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [4:30pm-5:10pm] Ops Tags WG session - https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session
* [4:30pm-5:10pm] Horizon operator / plugin feedback - https://etherpad.openstack.org/p/horizon-pike-feedback
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks
* [5:20pm-6:00pm] Fog/Edge/Massively Distributed Clouds (working group session) - https://etherpad.openstack.org/p/Massively_distributed_wg_boston_summit
* [5:20pm-6:00pm] Cloud-Native Design/Refactoring Across OpenStack https://etherpad.openstack.org/p/cloud-native-forum

= Thursday =
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [9:50am-10:30am] - Strategy for Unanswered Requirements - https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:00am - 11:40] Zun Developer/Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-zun-developer-operator-feedback
* [11:00am - 11:40] High Availability in OpenStack - https://etherpad.openstack.org/p/BOS-forum-HA-in-openstack
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [11:50am-12:30pm] LCOO Get to know us at the Boston Summit - https://etherpad.openstack.org/p/BOS-forum-LCOOGetToKnow
* [1:30pm-2:10pm] User Committee Session - https://etherpad.openstack.org/p/BOS-forum-user-committee-session
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications
* [5:00pm-5:40pm] UC Governance and Support of WGs - https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - Continuing the discussion from container deployment session https://etherpad.openstack.org/p/boston-deploying-openstack-on-k8s
* 2:20-3:00 MR102 - Swift Rebalance Optimizations https://etherpad.openstack.org/p/swift-rebalance
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - Discussion of use cases for alternate messaging technology with oslo.messaging https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Meetings/TechnicalCommittee

2017-02-10T12:59:50Z

Flaper87: /* Agenda */

__NOTOC__

The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.

=== Next Meeting ===

* February 14th, 20:00 UTC
* Chair: Thierry Carrez (ttx)

==== Agenda ====

* Update projects.yaml with results of the PTL elections [https://review.openstack.org/430481]
* PTG organization
* Document current base services [https://review.openstack.org/430965]
* Glance: Changing response status code. What's the best path forward? [https://review.openstack.org/#/c/420038/] [https://review.openstack.org/#/c/425487/] (flaper87, rosmaita)
* Deprecate postgresql in OpenStack [https://review.openstack.org/427880]
* More tbd
* Open discussion

==== Backlog ====
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:

* Add Golang CTI (WIP) [https://review.openstack.org/410355] (needs more prep work)
* Introduce assert:supports-api-compatibility [https://review.openstack.org/418010] (needs more discussion)
* Driver teams decision [https://review.openstack.org/403829] [https://review.openstack.org/403836] (Feb 7? paused for a couple of weeks to get discovery work started first)
* Add networking-cisco back into the Big Tent [https://review.openstack.org/363709] (deferred until we get to a decision on driver teams)
* Add Pike goal split out tempest plugins [https://review.openstack.org/369749] (to be deferred to Queens)

==== Apologies for Absence ====

* tbd

=== Proposing discussion topics, motions or other governance changes before the TC ===

Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.

Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.

Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.

=== Past meetings logs ===

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc

[[Category: meetings]]

Meetings/InfraTeamMeeting

2016-10-17T18:58:14Z

Flaper87: /* Agenda for next meeting */

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html Docs Publishing via AFS]
* [https://etherpad.openstack.org/p/infra-ocata-summit-planning Ocata Summit Planning] (pleia2, c/o fungi)
** http://lists.openstack.org/pipermail/openstack-infra/2016-October/004768.html
* Replacement of cacti node (rcarrillocruz)
** https://review.openstack.org/#/c/378996/
** https://review.openstack.org/#/c/383761/
* Host http://shields.io/ for generating badges to show on repos (flaper87)
** http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html
* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)

[https://review.openstack.org/#/c/381332/ rsc -> valence]

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/InfraTeamMeeting

2016-10-17T18:57:51Z

Flaper87: /* Agenda for next meeting */

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html Docs Publishing via AFS]
* [https://etherpad.openstack.org/p/infra-ocata-summit-planning Ocata Summit Planning] (pleia2, c/o fungi)
** http://lists.openstack.org/pipermail/openstack-infra/2016-October/004768.html
* Replacement of cacti node (rcarrillocruz)
** https://review.openstack.org/#/c/378996/
** https://review.openstack.org/#/c/383761/
* Host http://shields.io/ for generating badges to show on repos (flaper87)
- http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html
* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)

[https://review.openstack.org/#/c/381332/ rsc -> valence]

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/TechnicalCommittee

2016-08-08T07:51:38Z

Flaper87: /* Agenda */

__NOTOC__

The [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]] is one of the [[Governance|governing bodies]] of the OpenStack project. You can find more information about it, such as the list of its [http://governance.openstack.org current members] or its [http://governance.openstack.org/reference/charter.html governance charter], on the OpenStack governance website at http://governance.openstack.org . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.

=== Next Meeting ===

* August 9th, 20:00 UTC
* Chair: Flavio Percoco (flaper87)

==== Agenda ====

* Clarify that cycle-trailing projects follow the milestone deadlines [https://review.openstack.org/348501]
* Refresh I18n ATC list [https://review.openstack.org/351480]
* Replacing Morgan's seat [http://lists.openstack.org/pipermail/openstack-tc/2016-August/001233.html], including various proposals [https://review.openstack.org/351104] [https://review.openstack.org/351295] [https://review.openstack.org/351427]
* Community-wide goals [https://review.openstack.org/349068] [https://review.openstack.org/349069] [https://review.openstack.org/349070]
* Open discussion
** Agree to at least temporarily abandon stalled items [https://review.openstack.org/338796] [https://review.openstack.org/314691] [https://review.openstack.org/295971] [https://review.openstack.org/295528]

==== Backlog ====
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:

* Equal Integration Chances for all Projects [https://review.openstack.org/342366] (round 2) (WIP)
* Split out the requirements repo into its own team [https://review.openstack.org/348462] (WIP)
* Clarify what an active (core) reviewer is [https://review.openstack.org/342225] (WIP)
* Add project Tricircle to OpenStack big-tent [https://review.openstack.org/338796] (deferred, mordred to drive)
* Add Cross Project Liason imformation to projects.yaml [https://review.openstack.org/336395] (WIP)
* Trim tc-approved-release tag to just base IaaS projects [https://review.openstack.org/314691] (pending update)
* type:packaging [https://review.openstack.org/295971] and type:deployment [https://review.openstack.org/295528] tags (pending iterations on the reviews)

==== Apologies for Absence ====

* tbd

=== Proposing discussion topics, motions or other governance changes before the TC ===

Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.

Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.

Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.

=== Past meetings logs ===

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc

[[Category: meetings]]

CrossProjectLiaisons

2016-05-23T14:55:33Z

Flaper87: /* Release management */

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || Lin Tan || lintan
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachyshka
|-
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Huichun Lu, Ethan Gafford || huichun, egafford
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || Flavio Percoco || nikhil
|-
| Heat || Thomas Herve || therve
|-
| Horizon || David Lyle || david-lyle
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Steve Martinelli || stevemar
|-
| Magnum || Hongbin lu || hongbin
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Sylvain Bauza || bauzas
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Searchlight || Travis Tripp || TravT
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Steve Heyman || hockeynut
|-
| Ceilometer || Chris Dent || cdent
|-
| Cinder || ||
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Nikhil Komawar || nikhil
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Timur Sufiev || tsufiev
|-
| Ironic || John Villalovos || jlvillal
|-
| Keystone || David Stanek || dstanek
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || ||
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || Fei Long Wang || flwang
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Cinder || Sean Mcginnis || smcginnis
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || ||
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Randall Burt || randallburt
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || ||
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Edgar Magana || emagana
|-
| Nova || Joe Gordon or Michael Still || Jog0 or mikal
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || ||
|-
| Sahara || Chad Roberts, Michael Ionkin || crobertsrh mionkin
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || ||
|-
| Tripleo || ||
|-
| Trove || Laurel Michaels || laurelm
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Pierre Mathieu || slashme
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== Vulnerability management ==

The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Congress || Masahito Muroi || masahito
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Lin Hua Cheng || lhcheng
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Dolph Mathews || dolphm
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Michael Still || mikal
|-
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Erno Kuvaja || jokke_
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Nikolay Starodubtsev || Nikolay_St
|-
| Sahara || Ethan Gafford || egafford
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil

|-
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Sahara || Sergey Lukjanov || SergeyLukjanov

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|}

== Product Working Group ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Glance || Nate Ziemann || nate_zman
|-
| Horizon || Carol Barrett || barrett1
|-
| Keystone || ||
|-
| Kolla || Carol Barrett || barrett1
|-
| Magnum || Steve Gordon || sgordon
|-
| Manilla ||Pete Chadwick ||
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| Sahara || Ethan Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
|}

== I18n ==
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages.

If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.

* The liaison should be a core reviewer for the project and understand i18n status of the project.
* The liaison should understand project release schedule very well.
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Nikita Konovalov || NikitaKonovalov
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean M. Collins || sc68cal || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova
|-
| || Michael Davies || mrda || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Sahara / Trove || || ||
|-
| || Ethan Gafford || egafford || Sahara liaison for Trove
|-
| || Amrith Kumar || amrith || Trove liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

== Cross-Project Spec Liaisons ==

The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Astara|| Ryan Petrello || ryanpetrello
|-
| Barbican || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || Graham hayes || mugsie
|-
| Dragonflow || Gal Sagie || gsagie
|-
| Freezer || Pierre Mahieu || slashme
|-
| Fuel || Andrew Woodward || xarses
|-
| Glance || Nikhil Komawar || nikhil
|-
| Heat || Rico Lin || ricolin
|-
| Horizon || David Lyle || david-lyle
|-
| Infrastructure || Matthew Wagoner || olaph
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Kolla || Steven Dake || sdake
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Hongbin Lu || hongbin
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Chris Dent || cdent
|-
| OpenStack-Ansible || Travis Truman || automagically
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev
|-
| Searchlight || Travis Tripp || TravT
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Tacker || Sridhar Ramaswamy || sridhar_ram
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang

|}

Magnum/NativeAPI

2016-04-04T15:21:07Z

Flaper87: /* Use Cases for Magnum's "container" Resource */

NOTICE: This is a work-in-progress draft. Our community is working on refining this draft here: https://etherpad.openstack.org/p/magnum-native-api

=Magnum's Native Container APIs=
Magnum bays support native API access as well as a more limited form of wrapped access to that same functionality through a <code>/container</code> resource in the Magnum API. This means that, depending on which bay type you select: Docker Swarm, Kubernetes, or Apache Mesos, you get the API that comes with that container orchestration engine. For example, if I create a Bay in Magnum using the Docker Swarm bay type, I will have an endpoint for the Docker API that I can interact with using the native <code>docker</code> CLI tools.

==Project Position on Native APIs==
Magnum's contributors recognize the native API approach is preferred, as it offers users a more complete set of features and capabilities, and those can be updated without waiting for Magnum to re-implement them. It also allows for use of native tooling, which is the preferred user experience.

==Use Cases for Magnum's "container" Resource==
We are seeking production use cases for the <code>/container</code> resource offered in the Magnum API. If you have one, please identify it here:
* Deploy containers from other OpenStack services. Expecting services to abstract every possible supported bay type is not scalable. A more precise example, I'd like trove to deploy DBs on containers and to do that, I'd like it to use Magnum's containers API. (flaper87)

CrossProjectLiaisons

2016-01-19T02:07:49Z

Flaper87: /* Cross-Project Spec Liaisons */

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || Lin Tan || lintan
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachyshka
|-
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Sergey Reshetnyak || sreshetnyak
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Sergey Kraynev || skraynev
|-
| Horizon || David Lyle || david-lyle
|-
| Ironic || Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) || jroll (dtantsur)
|-
| Keystone || Steve Martinelli || stevemar
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || lane_kong
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kyle Mestery || mestery
|-
| Nova || Sylvain Bauza || bauzas
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Searchlight || Travis Tripp || TravT
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || John Dickinson || notmyname
|-
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik
|-
| Zaqar || ||
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Steve Heyman || hockeynut
|-
| Ceilometer || Chris Dent || cdent
|-
| Cinder || ||
|-
| Glance || Nikhil Komawar || nikhil_k
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || ||
|-
| Ironic || John Villalovos || jlvillal
|-
| Keystone || David Stanek || dstanek
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano and Sergey Lukjanov || tosky and SergeyLukjanov
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || ||
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || ||
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Constanze Kratel || constanze
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Cinder || Mike Perez || thingee
|-
| Congress || ||
|-
| Designate || ||
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Randall Burt || randallburt
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Mitsuhiro SHIGEMATSU || pshige
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Magnum || ||
|-
| Manila || ||
|-
| Mistral || ||
|-
| Murano || Ekaterina Chernova || katyafervent
|-
| Neutron || Edgar Magana || emagana
|-
| Nova || Joe Gordon or Michael Still || Jog0 or mikal
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Rally || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || ||
|-
| Tripleo || ||
|-
| Trove || Laurel Michaels || laurelm
|-
| Zaqar || ||
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Adam Gandelman || adam_g
|-
| Keystone || Dolph Mathews || dolphm
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar || amrith
|-
|}

== Vulnerability management ==

The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Lin Hua Cheng || lhcheng
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Dolph Mathews || dolphm
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Michael Still || mikal
|-
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Craig Vyvial or Nikhil Manchanda || cp16net or SlickNik
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Erno Kuvaja || jokke_
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Nikolay Starodubtsev || Nikolay_St
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k

|-
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Nikhil Manchanda || SlickNik
|}

== Product Working Group ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Glance || Nate Ziemann || nate_zman
|-
| Horizon || Carol Barrett || barrett1
|-
| Keystone || Sheena Gregson ||
|-
| Kolla || Carol Barrett || barrett1
|-
| Magnum || Steve Gordon || sgordon
|-
| Manilla ||Pete Chadwick ||
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockyg
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Willains || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean M. Collins || sc68cal || Neutron liaison for Nova
|-
| || Brent Eagles || beagles || Nova liaison for Neutron
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova
|-
| || Michael Davies || mrda || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

== Cross-Project Spec Liaisons ==

The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || ||
|-
| Ceilometer || ||
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || ||
|-
| Designate || ||
|-
| Glance || Nikhil Komawar || nikhil
|-
| Heat || ||
|-
| Horizon || ||
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || ||
|-
| Murano || ||
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || ||
|-
| Oslo || ||
|-
| Sahara || ||
|-
| Searchlight || ||
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || ||
|-
| Zaqar || ||
|}

Design Summit/Mitaka/Etherpads

2015-10-16T07:02:41Z

Flaper87: /* Glance */

[[Category:Summit]]
[[Category:Liberty]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>
== Event intro/closure ==
* Tue 11:15: Design Summit 101 [https://etherpad.openstack.org/p/mitaka-design-summit-101]
* Fri 12:30: Design Summit feedback [https://etherpad.openstack.org/p/mitaka-design-summit-feedback]

== Cinder ==
* Wed 14.00: Why fight it, Cinder could/should be the next ViPR [https://etherpad.openstack.org/p/mitaka-cinder-direction]
* Wed 14.50: Availability zones in Cinder [https://etherpad.openstack.org/p/mitaka-cinder-az]
* Thur 9.00: Experimental APIs and Microversions [https://etherpad.openstack.org/p/mitaka-cinder-experimental-apis]
* Thur 9.50: Cinder Nova Interaction [https://etherpad.openstack.org/p/mitaka-cinder-nova-interaction]
* Thur 13.50: Cinder driver interface [https://etherpad.openstack.org/p/mitaka-cinder-driver-interface]
* Thur 14.40: API Microversions [https://etherpad.openstack.org/p/mitaka-cinder-api-microversions]
* Thur 15.30: ABC work [https://etherpad.openstack.org/p/mitaka-cinder-abc-work]
* Thur 15.30: Driver deadlines [https://etherpad.openstack.org/p/mitaka-cinder-driver-deadlines]
* Thur 16.30: C-Vol Active/Active HA [https://etherpad.openstack.org/p/mitaka-cinder-cvol-aa]
* Thur 17.20: Volume manager locks [https://etherpad.openstack.org/p/mitaka-cinder-volmgr-locks]
* Fri: Contributor Meetup [https://etherpad.openstack.org/p/mitaka-cinder-contributor-meetup]

== Congress ==
* Wed 2:00: [https://etherpad.openstack.org/p/congress-mitaka-arch Distributed architecture and additional features for Mitaka]
* Wed 2:50: [https://etherpad.openstack.org/p/congress-mitaka-integrations Integration with other projects: congress gating (murano, nova, neutron, etc.), keystone]
* Wed 3:40: [https://etherpad.openstack.org/p/congress-mitaka-external Discussions with external teams: OPNFV, Monasca]

== Cross-Project workshops ==

All sessions are on Tuesday 2015-10-27

* 11:15
** Cycle themes [https://etherpad.openstack.org/p/mitaka-crossproject-themes]
* 12:05
** Supporting DefCore and Interoperability Testing [https://etherpad.openstack.org/p/mitaka-crossproject-defcore]
** Tags today and tomorrow [https://etherpad.openstack.org/p/mitaka-crossproject-next-tags]
* 14:50
** Role Assignments for Service users [https://etherpad.openstack.org/p/mitaka-cross-project-role-assignment-service-user]
* 15:40
** Documenting the OpenStack way [https://etherpad.openstack.org/p/mitaka-crossproject-doc-the-way]
* 16:40
** Troubleshooting cross-project comms [https://etherpad.openstack.org/p/mitaka-crossproject-comms]
* 17:30
** Serving extreme use cases [https://etherpad.openstack.org/p/mitaka-crossproject-extreme-usecases]

== Ceilometer ==
* Wednesday, 2015-08-28
** 11:15 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms alams]
** 12:05 - [https://etherpad.openstack.org/p/mitaka-telemetry-ui visualising data]
** 14:50 - [https://etherpad.openstack.org/p/mitaka-telemetry-upgrades rolling upgrades]
** 15:40 - [https://etherpad.openstack.org/p/mitaka-telemetry-split componentisation]

* Thursday, 2015-08-29
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-testing functional and integration testing]
** 09ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-bi business intelligence]
** 11ː00 - [https://etherpad.openstack.org/p/mitaka-telemetry-polling refined polling]
** 11ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-cross-project project data ownership]
** 13ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms event alarms]

* Friday, 2015-08-30
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-contributors-meetup contributors meetup]

== Designate ==

* Wed 11:15: Roadmap https://etherpad.openstack.org/p/mitaka-designate-summit-roadmap
* Wed 12:05: Alias Records https://etherpad.openstack.org/p/mitaka-designate-summit-alias
* Wed 14:00: Batch API Actions https://etherpad.openstack.org/p/mitaka-designate-summit-batch-api
* Wed 14:50: Embedable Services https://etherpad.openstack.org/p/mitaka-designate-summit-embeddable-services
* Wed 16:40: Incremental Zone Transfer (IFXR) https://etherpad.openstack.org/p/mitaka-designate-summit-ifxr
* Fri 14:00: Contributors Meetup https://etherpad.openstack.org/p/mitaka-designate-summit-meetup

== Glance ==

* Wed:
** 14:00 - 14:40: Trusts implementation (mfedosin) https://etherpad.openstack.org/p/mitaka-glance-trusts
* Thur:
** 09:00 - 09:40 (fishbowl): Cross-project image protection (rosmaita) https://etherpad.openstack.org/p/mitaka-glance-xp-property-protections-support
** 09:50 - 10:30: Image Signature Verification Improvements (bpoulos) https://etherpad.openstack.org/p/mitaka-glance-image-signing-and-encryption
** 11:50 - 12:30: Defcore Updates and joint effort (flaper87) https://etherpad.openstack.org/p/mitaka-glance-defcore
** 14:40 - 15:20 (fishbowl): Glance image import reloaded (rosmaita, mclaren) https://etherpad.openstack.org/p/Mitaka-glance-image-import-reloaded
** 15:30 - 16:10 (fisbowl): Artifacts Review (ativelkov) https://etherpad.openstack.org/p/mitaka-glance-artifacts-review
** 16:30 - 17:10: Glance image import (follow-up working session) (flaper87) https://etherpad.openstack.org/p/Mitaka-glance-image-import-reloaded
** 17:20 - 18:00: Finalize Glance priorities (flaper87)

== Nova ==

* Wed 11:15: REST API https://etherpad.openstack.org/p/mitaka-nova-api
* Wed 12:05: Upgrade https://etherpad.openstack.org/p/mitaka-nova-upgrade

* Wed 14:00: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Wed 14:50: OS VIF lib https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib
* Wed 15:40: Resources and Flavors https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 16:40: Resources and Flavors (continued) https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 17:30: SR-IOV https://etherpad.openstack.org/p/mitaka-nova-sr-iov

* Thurs 09:00: Cells v2 https://etherpad.openstack.org/p/mitaka-nova-cells
* Thurs 9:50: see Cinder track
* Thurs 11:00: Scheduler https://etherpad.openstack.org/p/mitaka-nova-scheduler
* Thurs 11:50: see Ironic track

* Thurs 13:50: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Thurs 14:40: Error handling https://etherpad.openstack.org/p/mitaka-nova-error-handling
* Thurs 15:30: Cross Service issues: Server locking, token refresh, Instance users https://etherpad.openstack.org/p/mitaka-nova-service-users
* Thurs 16:30: Mitaka Priorities https://etherpad.openstack.org/p/mitaka-nova-priorities
* Thurs 17:20: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference

* Fri: 09:00 and 14:00: Nova contributors meetup https://etherpad.openstack.org/p/mitaka-nova-summit-meetup

== Manila ==
* Wed 11:15 - 11:55: (WS) Migration Improvements https://etherpad.openstack.org/p/mitaka-manila-migration-improvements
* Wed 12:05 - 12:45: (WS) Access Allow/Deny Driver Interface https://etherpad.openstack.org/p/mitaka-manila-allow-deny
* Thu 11:00 - 11:40: (FB) Share Replication https://etherpad.openstack.org/p/mitaka-manila-replication
* Thu 11:50 - 12:30: (FB) Alternative Snapshot Semantics https://etherpad.openstack.org/p/mitaka-manila-snapshot-semantics
* Thu 14:40 - 15:20: (WS) Export Location Metadata https://etherpad.openstack.org/p/mitaka-manila-export-location-metadata
* Thu 15:30 - 16:10: (WS) Interactions Between New Features https://etherpad.openstack.org/p/mitaka-manila-feature-interactions
* Fri 09:00 - 12:30: (CM) Contributor Meetup https://etherpad.openstack.org/p/mitaka-manila-contributor-meetup

== Release management ==
* Thu 15:30: Mitaka process changes [https://etherpad.openstack.org/p/mitaka-relmgt-process-changes]
* Thu 16:30: Work session: the Mitaka plan [https://etherpad.openstack.org/p/mitaka-relmgt-plan]

== Puppet OpenStack ==
* General etherpadː https://etherpad.openstack.org/p/HND-puppet
* Wed 2 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Wed 2.50 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Thu 1.50 pm: Community feedbackː https://etherpad.openstack.org/p/HND-puppet-community
* Thu 2.40 pm: CI and documentationː https://etherpad.openstack.org/p/HND-puppet-ci and https://etherpad.openstack.org/p/HND-puppet-doc
* Thu 4.30 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code

== Ironic ==
* The everything etherpad: https://etherpad.openstack.org/p/summit-mitaka-ironic
* Wednesday fishbowl DS3 2:00-2:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-third-party-ci
* Wednesday fishbowl DS3 2:50-3:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-group-management
* Thursday workroom DS10 9:00-9:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-notifications-bus
* Thursday workroom DS10 9:50-10:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-composition
* Thursday fishbowl DS3 11:00-11:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-api
* Thursday fishbowl DS3 11:50-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-nova-driver (joint session with Nova)
* Thursday workroom DS11 4:30-5:10 https://etherpad.openstack.org/p/summit-mitaka-ironic-lock-manager
* Thursday workroom DS11 5:20-6:00 https://etherpad.openstack.org/p/summit-mitaka-ironic-gate-improvements
* Friday workroom DS15 9:00-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-contributors-meetup (shared space with Infra)

== Heat ==
* The everything etherpad: https://etherpad.openstack.org/p/mitaka-heat-sessions
'''Wed'''
* 11:15 - 11:55: [https://etherpad.openstack.org/p/mitaka-heat-documentation (W) Documentation improvements]
* 12:05 - 12:45: [https://etherpad.openstack.org/p/mitaka-heat-tests (W) Heat tests]
* 14:00 - 14:40: [https://etherpad.openstack.org/p/mitaka-heat-convergence-migration (W) Tool to migrate stacks to/from convergence]
* 14:50 - 15:30: [https://etherpad.openstack.org/p/mitaka-heat-large-stacks (F) Issues from deploying very large stacks]
* 15:40 - 16:20: [https://etherpad.openstack.org/p/mitaka-heat-user-ops (F) User/ops session for summit ]
'''Thu'''
* 09:00 - 09:40: [https://etherpad.openstack.org/p/mitaka-heat-autoscaling (W) AutoScaling/Group architecture/roadmap]
* 09:50 - 10:30: [https://etherpad.openstack.org/p/mitaka-heat-break-stack-barrier (W) Breaking the stack barrier]
* 11:00 - 11:40: [https://etherpad.openstack.org/p/mitaka-heat-composition-improvements (F) Composition improvements ]
* 11:50 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-openstackclient (F) Complete heat support in python-openstackclient ]
* 13:50 - 14:30: [https://etherpad.openstack.org/p/mitaka-heat-hooks-notifications (W) Hooks & Notifications ]
* 14:40 - 15:20: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph1 (W) Convergence Phase 1 results]
* 15:30 - 16:10: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph2 (W) Convergence Phase 2 start]
'''Fri'''
* 09:00 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-summit-meetup Contributor Meetup]

== OpenStack Chef ==
* general discussion: https://etherpad.openstack.org/p/mitaka-openstack-chef-general
* defining the refactoring process: https://etherpad.openstack.org/p/mitaka-openstack-chef-refactoring

== OpenStackClient ==
* Wed 16:40 - 17:20: [https://etherpad.openstack.org/p/tokyo-osc-session Near-term Roadmap]
* Fri 09:00 - 12:30: [https://etherpad.openstack.org/p/tokyo-osc-meetup Meetup]

Design Summit/Mitaka/Etherpads

2015-10-16T06:59:20Z

Flaper87:

[[Category:Summit]]
[[Category:Liberty]]
[[Category:Etherpad]]

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>
== Event intro/closure ==
* Tue 11:15: Design Summit 101 [https://etherpad.openstack.org/p/mitaka-design-summit-101]
* Fri 12:30: Design Summit feedback [https://etherpad.openstack.org/p/mitaka-design-summit-feedback]

== Cinder ==
* Wed 14.00: Why fight it, Cinder could/should be the next ViPR [https://etherpad.openstack.org/p/mitaka-cinder-direction]
* Wed 14.50: Availability zones in Cinder [https://etherpad.openstack.org/p/mitaka-cinder-az]
* Thur 9.00: Experimental APIs and Microversions [https://etherpad.openstack.org/p/mitaka-cinder-experimental-apis]
* Thur 9.50: Cinder Nova Interaction [https://etherpad.openstack.org/p/mitaka-cinder-nova-interaction]
* Thur 13.50: Cinder driver interface [https://etherpad.openstack.org/p/mitaka-cinder-driver-interface]
* Thur 14.40: API Microversions [https://etherpad.openstack.org/p/mitaka-cinder-api-microversions]
* Thur 15.30: ABC work [https://etherpad.openstack.org/p/mitaka-cinder-abc-work]
* Thur 15.30: Driver deadlines [https://etherpad.openstack.org/p/mitaka-cinder-driver-deadlines]
* Thur 16.30: C-Vol Active/Active HA [https://etherpad.openstack.org/p/mitaka-cinder-cvol-aa]
* Thur 17.20: Volume manager locks [https://etherpad.openstack.org/p/mitaka-cinder-volmgr-locks]
* Fri: Contributor Meetup [https://etherpad.openstack.org/p/mitaka-cinder-contributor-meetup]

== Congress ==
* Wed 2:00: [https://etherpad.openstack.org/p/congress-mitaka-arch Distributed architecture and additional features for Mitaka]
* Wed 2:50: [https://etherpad.openstack.org/p/congress-mitaka-integrations Integration with other projects: congress gating (murano, nova, neutron, etc.), keystone]
* Wed 3:40: [https://etherpad.openstack.org/p/congress-mitaka-external Discussions with external teams: OPNFV, Monasca]

== Cross-Project workshops ==

All sessions are on Tuesday 2015-10-27

* 11:15
** Cycle themes [https://etherpad.openstack.org/p/mitaka-crossproject-themes]
* 12:05
** Supporting DefCore and Interoperability Testing [https://etherpad.openstack.org/p/mitaka-crossproject-defcore]
** Tags today and tomorrow [https://etherpad.openstack.org/p/mitaka-crossproject-next-tags]
* 14:50
** Role Assignments for Service users [https://etherpad.openstack.org/p/mitaka-cross-project-role-assignment-service-user]
* 15:40
** Documenting the OpenStack way [https://etherpad.openstack.org/p/mitaka-crossproject-doc-the-way]
* 16:40
** Troubleshooting cross-project comms [https://etherpad.openstack.org/p/mitaka-crossproject-comms]
* 17:30
** Serving extreme use cases [https://etherpad.openstack.org/p/mitaka-crossproject-extreme-usecases]

== Ceilometer ==
* Wednesday, 2015-08-28
** 11:15 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms alams]
** 12:05 - [https://etherpad.openstack.org/p/mitaka-telemetry-ui visualising data]
** 14:50 - [https://etherpad.openstack.org/p/mitaka-telemetry-upgrades rolling upgrades]
** 15:40 - [https://etherpad.openstack.org/p/mitaka-telemetry-split componentisation]

* Thursday, 2015-08-29
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-testing functional and integration testing]
** 09ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-bi business intelligence]
** 11ː00 - [https://etherpad.openstack.org/p/mitaka-telemetry-polling refined polling]
** 11ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-cross-project project data ownership]
** 13ː50 - [https://etherpad.openstack.org/p/mitaka-telemetry-alarms event alarms]

* Friday, 2015-08-30
** 09:00 - [https://etherpad.openstack.org/p/mitaka-telemetry-contributors-meetup contributors meetup]

== Designate ==

* Wed 11:15: Roadmap https://etherpad.openstack.org/p/mitaka-designate-summit-roadmap
* Wed 12:05: Alias Records https://etherpad.openstack.org/p/mitaka-designate-summit-alias
* Wed 14:00: Batch API Actions https://etherpad.openstack.org/p/mitaka-designate-summit-batch-api
* Wed 14:50: Embedable Services https://etherpad.openstack.org/p/mitaka-designate-summit-embeddable-services
* Wed 16:40: Incremental Zone Transfer (IFXR) https://etherpad.openstack.org/p/mitaka-designate-summit-ifxr
* Fri 14:00: Contributors Meetup https://etherpad.openstack.org/p/mitaka-designate-summit-meetup

== Glance ==

* Wed:
** 14:00 - 14:40: Trusts implementation (mfedosin) https://etherpad.openstack.org/p/mitaka-glance-trusts
* Thur:
** 09:00 - 09:40 (fishbowl): Cross-project image protection (rosmaita) https://etherpad.openstack.org/p/mitaka-glance-xp-property-protections-support
** 09:50 - 10:30: Image Signature Verification Improvements (bpoulos) https://etherpad.openstack.org/p/mitaka-glance-image-signing-and-encryption
** 11:50 - 12:30:
** 14:40 - 15:20 (fishbowl): Glance image import reloaded (rosmaita, mclaren) https://etherpad.openstack.org/p/Mitaka-glance-image-import-reloaded
** 15:30 - 16:10 (fisbowl): Artifacts Review (ativelkov) https://etherpad.openstack.org/p/mitaka-glance-artifacts-review
** 16:30 - 17:10: Glance image import (follow-up working session) (flaper87) https://etherpad.openstack.org/p/Mitaka-glance-image-import-reloaded
** 17:20 - 18:00: Finalize Glance priorities (flaper87)

== Nova ==

* Wed 11:15: REST API https://etherpad.openstack.org/p/mitaka-nova-api
* Wed 12:05: Upgrade https://etherpad.openstack.org/p/mitaka-nova-upgrade

* Wed 14:00: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Wed 14:50: OS VIF lib https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib
* Wed 15:40: Resources and Flavors https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 16:40: Resources and Flavors (continued) https://etherpad.openstack.org/p/mitaka-nova-resource-modeling
* Wed 17:30: SR-IOV https://etherpad.openstack.org/p/mitaka-nova-sr-iov

* Thurs 09:00: Cells v2 https://etherpad.openstack.org/p/mitaka-nova-cells
* Thurs 9:50: see Cinder track
* Thurs 11:00: Scheduler https://etherpad.openstack.org/p/mitaka-nova-scheduler
* Thurs 11:50: see Ironic track

* Thurs 13:50: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference
* Thurs 14:40: Error handling https://etherpad.openstack.org/p/mitaka-nova-error-handling
* Thurs 15:30: Cross Service issues: Server locking, token refresh, Instance users https://etherpad.openstack.org/p/mitaka-nova-service-users
* Thurs 16:30: Mitaka Priorities https://etherpad.openstack.org/p/mitaka-nova-priorities
* Thurs 17:20: Unconference https://etherpad.openstack.org/p/mitaka-nova-unconference

* Fri: 09:00 and 14:00: Nova contributors meetup https://etherpad.openstack.org/p/mitaka-nova-summit-meetup

== Manila ==
* Wed 11:15 - 11:55: (WS) Migration Improvements https://etherpad.openstack.org/p/mitaka-manila-migration-improvements
* Wed 12:05 - 12:45: (WS) Access Allow/Deny Driver Interface https://etherpad.openstack.org/p/mitaka-manila-allow-deny
* Thu 11:00 - 11:40: (FB) Share Replication https://etherpad.openstack.org/p/mitaka-manila-replication
* Thu 11:50 - 12:30: (FB) Alternative Snapshot Semantics https://etherpad.openstack.org/p/mitaka-manila-snapshot-semantics
* Thu 14:40 - 15:20: (WS) Export Location Metadata https://etherpad.openstack.org/p/mitaka-manila-export-location-metadata
* Thu 15:30 - 16:10: (WS) Interactions Between New Features https://etherpad.openstack.org/p/mitaka-manila-feature-interactions
* Fri 09:00 - 12:30: (CM) Contributor Meetup https://etherpad.openstack.org/p/mitaka-manila-contributor-meetup

== Release management ==
* Thu 15:30: Mitaka process changes [https://etherpad.openstack.org/p/mitaka-relmgt-process-changes]
* Thu 16:30: Work session: the Mitaka plan [https://etherpad.openstack.org/p/mitaka-relmgt-plan]

== Puppet OpenStack ==
* General etherpadː https://etherpad.openstack.org/p/HND-puppet
* Wed 2 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Wed 2.50 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code
* Thu 1.50 pm: Community feedbackː https://etherpad.openstack.org/p/HND-puppet-community
* Thu 2.40 pm: CI and documentationː https://etherpad.openstack.org/p/HND-puppet-ci and https://etherpad.openstack.org/p/HND-puppet-doc
* Thu 4.30 pm: Code design sessionː https://etherpad.openstack.org/p/HND-puppet-code

== Ironic ==
* The everything etherpad: https://etherpad.openstack.org/p/summit-mitaka-ironic
* Wednesday fishbowl DS3 2:00-2:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-third-party-ci
* Wednesday fishbowl DS3 2:50-3:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-group-management
* Thursday workroom DS10 9:00-9:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-notifications-bus
* Thursday workroom DS10 9:50-10:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-composition
* Thursday fishbowl DS3 11:00-11:40 https://etherpad.openstack.org/p/summit-mitaka-ironic-driver-api
* Thursday fishbowl DS3 11:50-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-nova-driver (joint session with Nova)
* Thursday workroom DS11 4:30-5:10 https://etherpad.openstack.org/p/summit-mitaka-ironic-lock-manager
* Thursday workroom DS11 5:20-6:00 https://etherpad.openstack.org/p/summit-mitaka-ironic-gate-improvements
* Friday workroom DS15 9:00-12:30 https://etherpad.openstack.org/p/summit-mitaka-ironic-contributors-meetup (shared space with Infra)

== Heat ==
* The everything etherpad: https://etherpad.openstack.org/p/mitaka-heat-sessions
'''Wed'''
* 11:15 - 11:55: [https://etherpad.openstack.org/p/mitaka-heat-documentation (W) Documentation improvements]
* 12:05 - 12:45: [https://etherpad.openstack.org/p/mitaka-heat-tests (W) Heat tests]
* 14:00 - 14:40: [https://etherpad.openstack.org/p/mitaka-heat-convergence-migration (W) Tool to migrate stacks to/from convergence]
* 14:50 - 15:30: [https://etherpad.openstack.org/p/mitaka-heat-large-stacks (F) Issues from deploying very large stacks]
* 15:40 - 16:20: [https://etherpad.openstack.org/p/mitaka-heat-user-ops (F) User/ops session for summit ]
'''Thu'''
* 09:00 - 09:40: [https://etherpad.openstack.org/p/mitaka-heat-autoscaling (W) AutoScaling/Group architecture/roadmap]
* 09:50 - 10:30: [https://etherpad.openstack.org/p/mitaka-heat-break-stack-barrier (W) Breaking the stack barrier]
* 11:00 - 11:40: [https://etherpad.openstack.org/p/mitaka-heat-composition-improvements (F) Composition improvements ]
* 11:50 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-openstackclient (F) Complete heat support in python-openstackclient ]
* 13:50 - 14:30: [https://etherpad.openstack.org/p/mitaka-heat-hooks-notifications (W) Hooks & Notifications ]
* 14:40 - 15:20: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph1 (W) Convergence Phase 1 results]
* 15:30 - 16:10: [https://etherpad.openstack.org/p/mitaka-heat-convergence-ph2 (W) Convergence Phase 2 start]
'''Fri'''
* 09:00 - 12:30: [https://etherpad.openstack.org/p/mitaka-heat-summit-meetup Contributor Meetup]

== OpenStack Chef ==
* general discussion: https://etherpad.openstack.org/p/mitaka-openstack-chef-general
* defining the refactoring process: https://etherpad.openstack.org/p/mitaka-openstack-chef-refactoring

== OpenStackClient ==
* Wed 16:40 - 17:20: [https://etherpad.openstack.org/p/tokyo-osc-session Near-term Roadmap]
* Fri 09:00 - 12:30: [https://etherpad.openstack.org/p/tokyo-osc-meetup Meetup]

CrossProjectLiaisons

2015-10-16T06:32:20Z

Flaper87: /* Inter-project Liaisons */

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || ||
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || Lin Tan || lintan
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachyshka
|-
| Nova || Victor Stinner|| haypo
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Sergey Reshetnyak || sreshetnyak
|-
| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Swift || John Dickinson || notmyname
|-
| Neutron || Kyle Mestery || mestery
|-
| Keystone || Morgan Fainberg || morganfainberg
|-
| Horizon || David Lyle || david-lyle
|-
| Glance || Flavio Percoco || flaper87
|-
| Ceilometer || gordon chung || gordc
|-
| Heat || Angus Salkeld || asalkeld
|-
| Oslo || Davanum Srinivas || dims
|-
| Trove || Nikhil Manchanda || SlickNik
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Zaqar || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Manila || Ben Swartzlander || bswartz
|-
| Murano || Serg Melikyan || sergmelikyan
|-
| Congress || Tim Hinrichs || thinrichs
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Matt Riedemann || mriedem
|-
| Cinder || ||
|-
| Swift || ||
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Keystone || David Stanek || dstanek
|-
| Horizon || ||
|-
| Glance || Nikhil Komawar || nikhil_k
|-
| Ceilometer || Chris Dent || cdent
|-
| Heat || Steve Baker || stevebaker
|-
| Oslo || Davanum Srinivas || dims
|-
| Trove || Nikhil Manchanda and Peter Stachowski || SlickNik and peterstac
|-
| Sahara || Luigi Toscano and Sergey Lukjanov || tosky and SergeyLukjanov
|-
| Ironic || John Villalovos || jlvillal
|-
| Zaqar || ||
|-
| Barbican || Steve Heyman || hockeynut
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Joe Gordon or Michael Still || Jog0 or mikal
|-
| Cinder || Mike Perez || thingee
|-
| Swift || ||
|-
| Neutron || Edgar Magana || emagana
|-
| Keystone || Steve Martinelli || stevemar
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Heat || Randall Burt || randallburt
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Trove || Laurel Michaels, Matt Griffin || laurelm mattgriffin
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Ironic || Mitsuhiro SHIGEMATSU || pshige
|-
| Zaqar || ||
|-
| Barbican || Constanze Kratel || constanze
|-
| Murano || Ekaterina Chernova || katyafervent
|-
| Manila || ||
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Adam Gandelman || adam_g
|-
| Keystone || Dolph Mathews || dolphm
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || ||
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Amrith Kumar || amrith
|-
|}

== Vulnerability management ==

The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Lin Hua Cheng || lhcheng
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Dolph Mathews || dolphm
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Michael Still || mikal
|-
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Nikhil Manchanda || SlickNik
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-api on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Erno Kuvaja || jokke_
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Nikolay Starodubtsev || Nikolay_St
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k

|-
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig
|-
| Documentation || Andreas Jaeger|| AJaeger
|}

== Product Working Group ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Manilla ||Pete Chadwick ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Horizon || Carol Barrett || barrett
|-
| Keystone || Sheena Gregson ||
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| Swift || Phil Willains || philipw
|-
| Glance || Nate Ziemann || nate_zman
|-
|OSClient || Megan Rossetti ||
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean M. Collins || sc68cal || Neutron liaison for Nova
|-
| || Brent Eagles || beagles || Nova liaison for Neutron
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova
|-
| || Michael Davies || mrda || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

CrossProjectLiaisons

2015-10-16T06:31:32Z

Flaper87: /* Infra */

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || ||
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || Lin Tan || lintan
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachyshka
|-
| Nova || Victor Stinner|| haypo
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Sergey Reshetnyak || sreshetnyak
|-
| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Swift || John Dickinson || notmyname
|-
| Neutron || Kyle Mestery || mestery
|-
| Keystone || Morgan Fainberg || morganfainberg
|-
| Horizon || David Lyle || david-lyle
|-
| Glance || Flavio Percoco || flaper87
|-
| Ceilometer || gordon chung || gordc
|-
| Heat || Angus Salkeld || asalkeld
|-
| Oslo || Davanum Srinivas || dims
|-
| Trove || Nikhil Manchanda || SlickNik
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Zaqar || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Manila || Ben Swartzlander || bswartz
|-
| Murano || Serg Melikyan || sergmelikyan
|-
| Congress || Tim Hinrichs || thinrichs
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Matt Riedemann || mriedem
|-
| Cinder || ||
|-
| Swift || ||
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Keystone || David Stanek || dstanek
|-
| Horizon || ||
|-
| Glance || Nikhil Komawar || nikhil_k
|-
| Ceilometer || Chris Dent || cdent
|-
| Heat || Steve Baker || stevebaker
|-
| Oslo || Davanum Srinivas || dims
|-
| Trove || Nikhil Manchanda and Peter Stachowski || SlickNik and peterstac
|-
| Sahara || Luigi Toscano and Sergey Lukjanov || tosky and SergeyLukjanov
|-
| Ironic || John Villalovos || jlvillal
|-
| Zaqar || ||
|-
| Barbican || Steve Heyman || hockeynut
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Nova || Joe Gordon or Michael Still || Jog0 or mikal
|-
| Cinder || Mike Perez || thingee
|-
| Swift || ||
|-
| Neutron || Edgar Magana || emagana
|-
| Keystone || Steve Martinelli || stevemar
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Heat || Randall Burt || randallburt
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Trove || Laurel Michaels, Matt Griffin || laurelm mattgriffin
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Ironic || Mitsuhiro SHIGEMATSU || pshige
|-
| Zaqar || ||
|-
| Barbican || Constanze Kratel || constanze
|-
| Murano || Ekaterina Chernova || katyafervent
|-
| Manila || ||
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Adam Gandelman || adam_g
|-
| Keystone || Dolph Mathews || dolphm
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || ||
|-
| Sahara || Sergey Lukjanov || SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Amrith Kumar || amrith
|-
|}

== Vulnerability management ==

The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Glance || Stuart McLaren or Nikhil Komawar || mclaren or nikhil_k
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Lin Hua Cheng || lhcheng
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Dolph Mathews || dolphm
|-
| Neutron || Salvatore Orlando || salv-orlando
|-
| Nova || Michael Still || mikal
|-
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov
|-
| Swift || ||
|-
| Trove || Nikhil Manchanda || SlickNik
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-api on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Erno Kuvaja || jokke_
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Nikolay Starodubtsev || Nikolay_St
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil_k

|-
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig
|-
| Documentation || Andreas Jaeger|| AJaeger
|}

== Product Working Group ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Manilla ||Pete Chadwick ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Horizon || Carol Barrett || barrett
|-
| Keystone || Sheena Gregson ||
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| Swift || Phil Willains || philipw
|-
| Glance || Nate Ziemann || nate_zman
|-
|OSClient || Megan Rossetti ||
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean M. Collins || sc68cal || Neutron liaison for Nova
|-
| || Brent Eagles || beagles || Nova liaison for Neutron
|-
| Nova / Glance || || ||
|-
| || Fei Long Wang || flwang || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova
|-
| || Michael Davies || mrda || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Mitsuhiro SHIGEMATSU and Jim Rollenhagen || pshige and jroll || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

CrossProjectLiaisons

2015-10-16T06:29:57Z

Flaper87: /* QA */

CrossProjectLiaisons

2015-10-16T06:29:22Z

Flaper87: /* Oslo */

2014-11-12T15:27:41Z

Flaper87: Created page with "== Storage Backends == * http://voltdb.com/ * https://foundationdb.com * http://www.orientechnologies.com/ * http://www.rethinkdb.com/ Note: Cassandra has known problems with..."

== Storage Backends ==
* http://voltdb.com/
* https://foundationdb.com
* http://www.orientechnologies.com/
* http://www.rethinkdb.com/

Note: Cassandra has known problems with high data churn, and doesn't solve the issue of atomic marker generation, but if we want to try building workarounds for all that, we can prototype this as
a backend as well.

Zaqar

2014-11-12T15:26:51Z

Flaper87: /* Community */

== Overview ==

Zaqar is a multi-tenant cloud messaging service for web developers. It combines the ideas pioneered by Amazon's SQS product with additional semantics to support event broadcasting.

The service features a fully RESTful API, which developers can use to send messages between various components of their SaaS and mobile applications, by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind.

Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the "over-cloud" layer. Cloud operators can leverage Zaqar to provide equivalents of SQS and SNS to their customers.

=== Key features ===

Zaqar provides the following key features:

* Firewall-friendly, HTTP-based API with Keystone support
* Multi-tenant queues based on Keystone project IDs
* Support for [[Zaqar/Use_Cases|several common patterns]] including event broadcasting, task distribution, and point-to-point messaging
* Component-based architecture with support for custom backends and message filters
* Efficient reference implementation with an eye toward low latency and high throughput (dependent on backend)
* Highly-available and horizontally scalable

=== Project scope ===

The Zaqar API is data-oriented. That is, it does not provision message brokers and expose those directly to clients. Instead, the API acts as a bridge between the client and one or more backends. A provisioning service for message brokers—however useful—serves a somewhat different market from what Zaqar is targeting today. With that in mind, if users are interested in a broker provisioning service, the community should consider starting a new project to address that need.

=== Design principles ===

Zaqar, as with all OpenStack projects, is designed with the following guidelines in mind:

* '''Component-based architecture.''' Quickly add new behaviors
* '''Highly available and scalable.''' Scale to very serious workloads
* '''Fault tolerant.''' Isolated processes avoid cascading failures
* '''Recoverable.''' Failures should be easy to diagnose, debug, and rectify
* '''Open standards.''' Be a reference implementation for a community-driven

== The API ==

At first glance, Zaqar's RESTful API may seem a bit out of the ordinary. Message brokers typically rely on a custom binary protocol and long-lived connections. However, many of today's developers prefer a more web-friendly HTTP API. They value the simplicity and transparency of the protocol, its firewall-friendly nature, and its huge ecosystem of tools, load balancers and proxies. In addition, cloud operators appreciate the scalability aspects of the REST architectural style.

[[Zaqar/specs/api/v1|Version 1.0]] of the API has been stable for some time. We are working on a [[Zaqar/specs/api/v1.1|1.1 version]] with minor changes to remove some of the rough edges in 1.0, and we welcome community feedback. Note that some proposals by the community, such as '''removing random access to individual messages by ID''', will be taken care of in version 2.0 when we will have more freedom to make major changes.

== Status ==

With the close of the Icehouse cycle, the program has achieved a number of important milestones:

* Zaqar's first official, production-ready "1.0" release is now [http://tarballs.openstack.org/marconi/ available for download]. This first release includes a battle-tested MongoDB driver, and production-ready drivers for additional backends are in the works.
* Zaqar's v1.0 API is stable and ready to code against.
* Basic user and operator docs are [http://docs.openstack.org/developer/marconi/ now available], and we will be adding tons of new content during Juno.
* A reference client library (written in Python) is now [https://pypi.python.org/pypi/python-marconiclient/ available on PyPI] which supports the entire v1.0 API. Support for other languages is available through [http://developer.rackspace.com/#home-sdks Rackspace-supported SDKs].

The program has attracted a growing community of contributors from all over the world. We are particularly proud of our interns:

* 10+ organizations represented
* 5 core reviewers
* 6 interns for Juno (representing GSoC, GNOME OPW, Rackspace and Red Hat)

== Resources ==

The Zaqar team hangs out in '''#openstack-zaqar''' on Freenode. Feel free to stop in anytime to chat with us; the crew is always happy to hear your ideas and answer questions. If you run into a bug, please report it using our [https://bugs.launchpad.net/marconi issue tracker].

==== Docs ====

* [http://docs.openstack.org/developer/marconi/ Zaqar User Guide]
* [https://ask.openstack.org/en/questions/ Ask OpenStack (Community Q&A)]
* [[Zaqar/docs/about|About the program]]

==== Releases ====


* 2014.1 ([http://tarballs.openstack.org/marconi/marconi-2014.1.tar.gz download] | [[Marconi/releases/icehouse|notes]])

==== Talks ====

* Alejandro Cabrera. Rackspace Atlanta. Introducing Openstack Marconi. July 17, 2013. [http://www.youtube.com/watch?v=b-IWDG7kKGQ Youtube] [https://speakerdeck.com/cabrera/introducing-openstack-marconi Speaker Deck]
* Flavio Percoco. EuroPython 2013. Marconi: Queuing and Notification Service for Openstack. July 2, 2013. [http://www.youtube.com/watch?v=iNOd7-_TdDo YouTube]
* Kurt Griffiths, Allan Metts. Openstack Summit April 2013. Project Overview: OpenStack Queuing and Notification Service ("Marconi"). April 2013. [http://www.youtube.com/watch?feature=player_embedded&v=henTTZWtt2k YouTube]
* Kurt Griffiths, Flavio Percoco, Allan Metts. Openstack Summit November 2013. Openstack Queuing and Notification Service. November 2013. [http://www.youtube.com/watch?v=IgE3Jskqtek YouTube]
* Yeela Kaplan. EuroPython 2014. OpenStack Queuing and Notification Service ("Marconi"). July 22, 2014. [https://www.youtube.com/watch?v=d65TtqGp-9Q YouTube]

==== Articles ====

* Oz Akan. Rackspace Devops Blog. July 25, 2013. [http://developer.rackspace.com/blog/openstack-marconi-api.html Openstack Marconi API].
* Flavio Percoco. Developer's Black Hole. March 2014. [http://blog.flaper87.com/post/531cd585d987d24e83f082a5 People don't like to queue up].

== Contributor Guide ==

''Note: The Marconi team is reworking this section of the wiki with tons of updated content, so some pages are missing or incomplete at the moment. If you can't find the information you are looking for, please drop us a line in IRC (#openstack-zaqar) and we'll be happy to help.''

==== Getting Started ====

* [[Zaqar/Welcome_new_contributors|Welcome new contributors]]
* [[Zaqar/Give_Zaqar_a_try|Give Zaqar a try]]
* [[Zaqar/Your first patch|Your first patch]]
* [[Zaqar/Your_first_review|Your first review]]
* [[Zaqar/Write the tests!|Write the tests!]]
* [[Zaqar/Write the docs!|Write the docs!]]


==== API Specs ====

* [[Marconi/specs/api/v1|API v1.0]] ('''released in 2014.1''')
* [[Marconi/specs/api/v1.1|API v1.1]]
* [[Marconi/specs/api/v2.0|API v2.0]]

==== Design ====

* [[Zaqar/Use_Cases|Zaqar Use Cases]]
* [[Server Architecture (Marconi)|Server Architecture]]
* Reference Clients
** [[Python Client Library (Marconi)|Python Library & CLI]]
** [https://github.com/abettadapur/marconiclient C# Library]
* Summit Notes
** [[Juno/Notes/Marconi|Juno Easel Pad]]

==== Quality Engineering ====

* [[Application Security (Marconi)|Application Security]]
* [[Performance Testing (Marconi)|Performance Testing]]
* [[Functional Testing (Marconi)|Functional Testing]]
* [[Integration Testing (Marconi)|Integration Testing]]


==== Resources ====

* [[Zaqar/About|About the program]]
* [[Zaqar/Frequently asked questions|Frequently asked questions]]
* [[Zaqar/Development process|Development process]]
* [[Zaqar/Blueprinting process|Blueprinting process]]
* [[Zaqar/Programming style guide|Programming style guide]]
* [[Zaqar/Reviewer guide|Reviewer guide]]
* [[Zaqar/Getting help|Getting help]]

==== Community ====

* [https://webchat.freenode.net/?channels=openstack-marconi #openstack-zaqar] (IRC)
* [[Meetings/Zaqar|Meetings]]
* [https://launchpad.net/marconi/+milestones Milestones]
* [https://blueprints.launchpad.net/marconi Blueprints]
* [https://bugs.launchpad.net/marconi Bugs]
* [https://github.com/openstack/marconi Server Code]
* [https://github.com/openstack/python-marconiclient Client Code]
* [[Zaqar/Feedback|Feedback]]

== Third party ==

* [[Driver development guide (Marconi)|Driver development guide]]

== Administrivia ==

* [[Roadmap (Marconi)|Roadmap]]
* [https://etherpad.openstack.org/p/naav-graduation Incubation Status]
* [[How to Release (Marconi)|How to Release]]
* [[Security/Juno/Marconi|OSSG Q&A for Marconi (Juno)]]

Meetings/Zaqar

2014-11-12T12:55:43Z

Flaper87: /* Next meeting */

= Weekly Zaqar (queuing) Team Meeting =

The [https://launchpad.net/zaqar Zaqar] project team holds a weekly team meeting in <code><nowiki>#openstack-meeting-3</nowiki></code>. We meet at alternating times, so two calendar reminders are required:

* Every other Monday [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 15:00 UTC], starting '''Monday, 28 July 2014'''
* Every other Monday at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=21&min=0&sec=0 21:00 UTC], starting '''Monday, 4 August 2014'''

== Next meeting ==

* Monday, 17 November 2014 (15:00 UTC)

==== Agenda ====

* Review Specs: https://review.openstack.org/#/q/status:open+project:openstack/zaqar-specs,n,z

===== Usual Stuff =====

* Review actions from last time
* Updates on blueprints
* Updates on bugs
* Open discussion (time permitting)

==== Discuss Later ====

* Decide if/when/how to take advantage of MongoDB 2.6 (index intersection, other features?) (kgriffs)
* Proposal to support claim delay to posted messages in v1.1 (kgriffs)
** Makes [[Use_Cases_(Marconi)#Auditing|the auditing use case]] easier to implement
** Reduces feature parity gap with SQS
* [https://etherpad.openstack.org/p/naav-scratch Proposal] to add per-project and per-queue defaults in v1.1 (kgriffs)
** Gives users more control over lazy queue creation
** Would reduce wire traffic, at expense of having to look up default values server-side (caching is a must!)
* Several asks for a Kafka driver lately; a prototype would be cool, but we are short on people and could use a new contributor to take this on... (kgriffs)
* Renaming the program: https://etherpad.openstack.org/p/marconi-scratch
* Notifications for MagnetoDB (malini, kgriffs)
** See https://wiki.openstack.org/wiki/MagnetoDB/notification & http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg25038.html
* Preflight Checklist for releases, including milestones (kgriffs)
* Blueprint review process (kgriffs)
* Concurrency strategy for client (flaper87)
* Push-based interaction model in the client? (kgriffs)

== Previous meetings ==

* Meeting #67 | v1.1 freeze, Pre-release test day, documenting drivers capabilities, design sessions, RC2 | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-10-06-15.01.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-10-06-15.01.log.html log]
* Meeting #66 | Suggestions for a couple additional queue stats, heat integration, swift integration | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-29-21.07.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-29-21.07.log.html log]
* Meeting #65 | Benchmarks on Redis, API checks docs, Dox early adoption, Client API v1.1, final graduation meeting | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-08-15.00.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-08-15.00.log.html log]
* Meeting #64 | Redis patch has landed!, Checks API/storage layer, Summit sessions proposals, API v2, Graduation | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-01-21.00.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-01-21.00.log.html log]
* Meeting #63 | Get rid of config samples, Juno status, Graduation | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-25-15.10.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-25-15.10.log.html log]
* Meeting #62 | Docs status, Health blueprint | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-18-21.11.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-18-21.11.log.html log]
* Meeting #61 | Docs status, Benchmark results, Redis driver status, Heat feedback | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-11-15.02.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-11-15.02.log.html log]
* Meeting #60 | '''First Zaqar meeting!''', Graduation status, Project rename, Blueprints for Juno, Keywords in commit messages, Transport limit options location | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-04-21.00.html summary] | [http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-08-04-21.00.log.html log]
* Meeting #59 | '''Weekly meeting changed to 19UTC (to be confirmed)''', API test, Tempest Integration, Benchmark, API v1.1 Homedoc, Redis | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-15-15.02.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-15-15.02.log.html log]
* Meeting #58 | '''Weekly meeting changed to 21UTC (to be confirmed)''', ID or name for queue flavors, Benchmark and Notifications | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-08-15.02.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-08-15.02.log.html log]
* Meeting #57 | Benchmark environment and tool plan, TC checkpoint, Redis and AMQP status | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-01-15.03.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-07-01-15.03.log.html log]
* Meeting #56 | Plan to Implement renaming (NaaV), Review Queue, C# Client | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-17-15.05.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-17-15.05.log.html log]
* Meeting #55 | Marconi Renamed to Naav, Specs Implementation, Unified API model | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-10-15.01.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-10-15.01.log.html log]
* Meeting #54 | Specs, AMQP, Code of Conduct | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-03-15.02.html summary] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-06-03-15.02.log.html log]
* Meeting #53 | Remove get message by id endpoints, blueprints for J1 | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-27-15.02.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-27-15.02.html summary]
* Meeting #52 | Summit Retro, AMQP Driver | [http://eavesdrop.openstack.org/meetings/marconi_team_meeting/2014/marconi_team_meeting.2014-05-20-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_team_meeting/2014/marconi_team_meeting.2014-05-20-15.01.html summary]
* Meeting #51 | Summit Planning, OSSG, Write the Docs! | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-06-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-05-06-15.01.html summary]
* Meeting #50 | Summit: Planning, Prizes, Events | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-29-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-29-15.01.html summary]
* Meeting #49 | New Interns, Summit -Sessions & Planning, POP Vote | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-22-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-22-15.01.html summary]
* Meeting #48 | Blocking Issues, Gate Fixing, Summit Planning | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-15-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-15-15.00.html summary]
* Meeting #47 | Pop Semantics, Deprecating Queue Metadata | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-08-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-08-15.01.html summary]
* Meeting #46 | Oslo Liaison, Unified Guest Agent + Marconi | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-01-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-01-15.01.html summary]
* Meeting #45 | Graduation Reflections, Pop Semantics | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-25-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-25-15.00.html summary]
* Meeting #44 | Pecan Evaluation | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-18-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-18-15.01.html summary]
* Meeting #43 | Queues -> Topics, v1.1/v2.0 Plans | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-11-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-11-15.00.html summary]
* Meeting #42 | SqlAlchemy is Done, Pecan Evaluation Objectives | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-04-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-03-04-15.00.html summary]
* Meeting #41 | SqlAlchemy is Near, Pecan Evaluation Pt. 1 | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-18-15.04.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-18-15.04.html summary]
* Meeting #40 | Summit Planning, SQL, API v1.1 | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-11-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-11-15.01.html summary]
* Meeting #39 | SQL Driver, Towards Icehouse | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-04-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-02-04-15.00.html summary]
* Meeting #38 | Actions for Everyone | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-28-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-28-15.00.html summary]
* Meeting #37 | Preparing to Cut Icehouse-2 Release | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-21-15.03.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-21-15.03.html summary]
* Meeting #36 | Push-based Messaging and Updates | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-14-15.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-14-15.01.html summary]
* Meeting #35 | Graduation Catchup | [http://eavesdrop.openstack.org/meetings/marconi_team/2014/marconi_team.2014-01-07-15.11.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_team/2014/marconi_team.2014-01-07-15.11.html summary]
* Meeting #34 | Towards Graduation | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-17-15.11.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-17-15.11.html summary]
* Meeting #33 | Setting Priorities | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-10-15.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-10-15.05.html summary]
* Meeting #32 | Marconi Notifications: Goals, Features, Payloads, Elephants, Workers | [http://eavesdrop.openstack.org/meetings/marconi_notifications_brainstorm/2013/marconi_notifications_brainstorm.2013-12-03-15.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_notifications_brainstorm/2013/marconi_notifications_brainstorm.2013-12-03-15.05.html summary] | [https://etherpad.openstack.org/p/marconi-notifications-brainstorm etherpad]
* Meeting #31 | JSON-Homedoc and Documentation | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-02-15.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-12-02-15.05.html summary]
* Meeting #30 | Summit Retro, Sharding | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-11-18-16.09.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-11-18-16.09.html summary]
* Meeting #29 | Sharding, Triage, and API Next | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-28-16.04.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-28-16.04.html summary]
* Meeting #28 | Sharding and Versioning! | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-21-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-21-16.03.html summary]
* Meeting #27 | v1 API is now frozen! | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-07-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-07-16.03.html summary]
* Meeting #26 | API reviews: marconi-proxy, marconi-queues | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-30-16.04.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-30-16.04.html summary]
* Meeting #25 | Finishing up marconi-proxy, status of Pecan/Falcon discussion | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-23-16.19.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-23-16.19.html summary]
* Meeting #24 | Proxy progress, bug triage | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-16-16.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-16-16.05.html summary]
* Meeting #23 | SQL driver, tsung, performance | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-09-16.06.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-09-09-16.06.html summary]
* Meeting #22 | Core team organization, performance | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-26-16.07.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-26-16.07.html summary]
* Meeting #21 | Deleting claimed messages, incubation, client reboot | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-19-16.03.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-19-16.03.html summary]
* Meeting #20 | Trello no more, bp and bug triage for H3 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-12-16.04.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-12-16.04.html summary]
* Meeting #19 | Testing refactoring | 2 August 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-02-16.02.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-08-02-16.02.html summary]
* Meeting #18 | Queue metadata | 18 July 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-18-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-18-19.05.html summary]
* Meeting #17 | Rebooting python-marconiclient, perf testing results | 11 July 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-11-19.03.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-11-19.03.html summary]
* Meeting #16 | Stats, limits, incubation; oh my! | 27 June 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-27-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-27-19.05.html summary]
* Meeting #15 | Incubation application, memcache and haproxy, client integration with Swift | 20 June 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-20-19.06.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-20-19.06.html summary]
* Meeting #14 | Community feedback, incubation prep, salty tests | 13 June 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-13-19.06.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-13-19.06.html summary]
* Meeting #13 | Handling storage connection errors, python-marconiclient, milestones | 6 June 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-06-19.14.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-06-19.14.html summary]
* Meeting #12 | Bug triage, QA/ref cluster progress and hardening | 23 May 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-23-19.10.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-23-19.10.html summary]
* Meeting #11 | Blueprint target, test update, apiclient, zmq | 16 May 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-16-19.00.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-16-19.00.txt summary]
* Meeting #10 | System and perf testing, blueprint triage | 9 May 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-09-19.07.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-09-19.07.html summary]
* Meeting #9 | Alignment with Havana milestones, FIFO, saved by grace | 2 May 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-02-19.20.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-02-19.20.html summary]
* Meeting #8 | Portland Demo, Auth, Claims, Routing | 4 April 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-04-04-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-04-04-19.05.html summary]
* Meeting #7 | State of the project, claiming messages | 21 Mar 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-03-21-19.04.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-03-21-19.04.html summary]
* Meeting #6 | Posting messages, queue metadata | 7 Mar 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-03-07-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-03-07-19.05.html summary]
* Meeting #5 | Claiming messages, dev kickoff | 21 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-21-19.06.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-21-19.06.html summary]
* Meeting #4 | GET and POST messages | 14 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.html summary]
* Meeting #3 | PUT vs. PATCH, JSON vs. XML, and other discussions re the API draft. | 7 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-07-19.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-07-19.01.html summary]
* Meeting #2 | Concrete queues, no tags, locking semantics, unified queue types or ? | 24 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-01-24-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-01-24-19.05.html summary]
* Meeting #1 | Kickoff |17 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.html summary]

== Meeting organizers ==

* Groom the agenda 24h in advance
* Use http://meetbot.debian.net/Manual.html to get an automatic summary, and remember to record minutes on this page (see above).
* Record decisions and commitments; review in the next meeting