OpenStack - User contributions [en]

Meetings/Ironic

2018-06-25T15:03:53Z

Rloo: /* Next Meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1500 UTC on Mondays (as of March 26, 2018), are held in the <code><nowiki>#openstack-ironic</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Julia Kreger (TheJulia) or Dmitry Tantsur (dtantsur).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

Meetings are held weekly. If one is cancelled, it will either be mentioned in the previous meeting or an email will be sent out to the openstack-dev mailing list.

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2018/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** (TheJulia) L3 deployment driver/framework IPA configuration passing
*** Nokia is proposing this driver and functionality under a single spec https://review.openstack.org/#/c/543936/13/specs/approved/L3-based-deployment.rst
*** Their vmedia does not support dual virtual device attachment. The spec proposes two options. Does anyone see any issues with Option-2?
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

<none>

Meetings/Ironic

2018-05-04T19:39:18Z

Rloo: /* Agenda for next meeting */

Ironic

2018-03-28T21:43:20Z

Rloo: /* Projects */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [https://docs.openstack.org/ironic/latest/user/index.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Documentation
| https://docs.openstack.org/ironic/latest/
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/943
|-
| Feature tracker
| https://storyboard.openstack.org/#!/project/943
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/959
|-
| Feature tracker
| https://storyboard.openstack.org/#!/project/959
|-
| Documentation
| https://docs.openstack.org/python-ironicclient/latest/
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/947
|-
| Documentation
| https://docs.openstack.org/ironic-python-agent/latest/
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://storyboard.openstack.org/#!/project/944
|-
| Feature tracker
| https://storyboard.openstack.org/#!/project/944
|-
| Documentation
| https://docs.openstack.org/ironic-inspector/latest/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/941
|-
| Documentation
| https://docs.openstack.org/bifrost/latest/
|}

== networking-baremetal ==

'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/networking-baremetal
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/955
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://storyboard.openstack.org/#!/project/946
|-
| Documentation
| https://docs.openstack.org/ironic-lib/latest/
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://storyboard.openstack.org/#!/project/952
|-
| Documentation
| https://docs.openstack.org/ironic-ui/latest/
|}

= People =

'''PTL''': Julia Kreger (TheJulia)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2018-03-26T13:43:06Z

Rloo: /* Weekly Ironic Project Team Meeting */

CrossProjectLiaisons

2018-02-27T14:06:52Z

Rloo: /* 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
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Dharini Chandrasekar || dharinic
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Flavio Percoco || flaper87
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Petr Kovar || pkovar
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ying Zuo || ying_zuo
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Jay Bryant || jungleboyj
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || ||
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Boden Russel || boden
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Rob Cresswell || robcresswell
|-
| 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 || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| 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 [https://security.openstack.org/vmt-process.html 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
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| 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_
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Elise 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
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov
|-
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me
|-
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha

|-
| TripleO || 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
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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 (or a person who is not a core reviewer but agreed & approved by PTL) 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
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || ||
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| 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 K. Mooney || sean-k-mooney || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Mike Fedosin || mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat 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
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== 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 || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Eric Kao || ekcs
|-
| 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 || ||
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Kolla || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Tacker || Sridhar Ramaswamy || sridhar_ram
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

CrossProjectLiaisons

2018-02-27T14:06:07Z

Rloo: /* QA */

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
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Dharini Chandrasekar || dharinic
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Flavio Percoco || flaper87
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Petr Kovar || pkovar
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ying Zuo || ying_zuo
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Jay Bryant || jungleboyj
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || ||
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Boden Russel || boden
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Rob Cresswell || robcresswell
|-
| 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 || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| 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 [https://security.openstack.org/vmt-process.html 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
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| 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_
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Elise 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
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur, Vasyl Saienko || dtantsur, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov
|-
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me
|-
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha

|-
| TripleO || 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
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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 (or a person who is not a core reviewer but agreed & approved by PTL) 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
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || ||
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| 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 K. Mooney || sean-k-mooney || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Mike Fedosin || mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat 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
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== 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 || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Eric Kao || ekcs
|-
| 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 || ||
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Kolla || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Tacker || Sridhar Ramaswamy || sridhar_ram
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

CrossProjectLiaisons

2018-02-27T14:05:32Z

Rloo: /* Oslo */

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
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Dharini Chandrasekar || dharinic
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Flavio Percoco || flaper87
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Petr Kovar || pkovar
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ying Zuo || ying_zuo
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || John Villalovos || jlvillal
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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 || Jay Bryant || jungleboyj
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || ||
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Boden Russel || boden
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== 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
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Rob Cresswell || robcresswell
|-
| 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 || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| 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 [https://security.openstack.org/vmt-process.html 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
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| 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_
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Elise 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
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur, Vasyl Saienko || dtantsur, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov
|-
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me
|-
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha

|-
| TripleO || 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
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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 (or a person who is not a core reviewer but agreed & approved by PTL) 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
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || ||
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| 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 K. Mooney || sean-k-mooney || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Mike Fedosin || mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat 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
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== 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 || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Eric Kao || ekcs
|-
| 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 || ||
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Kolla || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Tacker || Sridhar Ramaswamy || sridhar_ram
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

Meetings/Ironic

2018-02-12T16:58:25Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-ironic</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on February 12, 2018 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180212T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** PTG Topics https://etherpad.openstack.org/p/ironic-rocky-ptg
*** Please provide feedback to interested topics, provide +1 if the topic is relevant to yourself.
*** The Etherpad will be broken into many etherpads this coming Friday, February 16th along with a basic schedule created for Wednesday/Thursday.
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2018/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** What do we do with grenade
*** We are stuck in that we can't restart nova-compute and nova-conductor on the primary node.
*** We could consider completing the upgrade and just testing that the pin works as expected in a mixed environment as RPC/Data errors should shake out in the final tempest run.
* RFE review
** (rloo) Decide whether to approve or needs spec:
*** [RFE] support healthcheck middleware: https://bugs.launchpad.net/ironic/+bug/1748515
*** [RFE] Stop special handling of mime extensions in the API: https://bugs.launchpad.net/ironic/+bug/1748224
*** [RFE] Support alternative tempurl algorithms for swift: https://bugs.launchpad.net/ironic/+bug/1747466
*** [RFE] Fujitsu iRMC BIOS configuration: https://bugs.launchpad.net/ironic/+bug/1743674
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-12-04T15:48:28Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on December 4, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171204T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** (TheJulia) Due to lack of interest at present, the ironic-ui meeting will be cancelled for the time being. Please contact TheJulia if interested in contributing.
** (TheJulia) TheJulia is unavailable on Monday/Tuesday of this week.
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Decide next steps (e.g. approve, need more info, need spec) for these proposed RFEs:
*** [RFE] Ironic doesn't support zmq with oslo.messaging: https://bugs.launchpad.net/ironic/+bug/1669243
*** [RFE] serial console through shellinabox is not multi-tenant and has no token/password protection: https://bugs.launchpad.net/ironic/+bug/1660351
*** [RFE] Change VIF list endpoint to output additional information: https://bugs.launchpad.net/ironic/+bug/1657170
*** [RFE] complete SSL support for https image references: https://bugs.launchpad.net/ironic/+bug/1719582
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-21T15:41:08Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The virtual mid-cycle will be on November 27, 2017 from 1500 UTC to 1900 UTC.

The next meeting will be on December 4, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171204T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Decide next steps (e.g. approve, need more info, need spec) for these proposed RFEs:
*** [RFE] Ironic doesn't support zmq with oslo.messaging: https://bugs.launchpad.net/ironic/+bug/1669243
*** [RFE] serial console through shellinabox is not multi-tenant and has no token/password protection: https://bugs.launchpad.net/ironic/+bug/1660351
*** [RFE] Change VIF list endpoint to output additional information: https://bugs.launchpad.net/ironic/+bug/1657170
*** [RFE] complete SSL support for https image references: https://bugs.launchpad.net/ironic/+bug/1719582
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-21T15:22:14Z

Rloo: /* Next Meeting */

Meetings/Ironic

2017-11-20T16:56:39Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** (TheJulia) Summary of Ironic sessions from Sydney: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124520.html
** (dtantsur) Midcycle information: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124724.html
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-20T15:53:08Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** (TheJulia) Summary of Ironic sessions from Sydney: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124520.html
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
*** [RFE] Add Redfish Inspect Interface to Ironic: https://bugs.launchpad.net/ironic/+bug/1668487
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-14T22:10:44Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** (TheJulia) Summary of Ironic sessions from Sydney: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124520.html
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** (TheJulia) Hardware Vendor questions from forum action items.
*** Does the BMC your hardware you driver supports, support asserting keys into the TPM module?
*** Operators are asking about standardized firmware update mechanisms, specifically to help enable automation and automatic updates across a large diverse fleet of machines.
**** How might we go ahead and get the discussion started with each vendor's firmware teams as to the present packaging/installation options?
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
*** [RFE] Add Redfish Inspect Interface to Ironic: https://bugs.launchpad.net/ironic/+bug/1668487
* Open discussion
** (rloo) revisit adding a new 'supported_power_states' field to Node responses: https://review.openstack.org/#/c/382194

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-14T01:17:18Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
*** [RFE] Add Redfish Inspect Interface to Ironic: https://bugs.launchpad.net/ironic/+bug/1668487
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-14T01:16:49Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
*** [RFE] Add Redfish Inspect Interface to Ironic
* Open discussion: https://bugs.launchpad.net/ironic/+bug/1668487

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-14T01:16:32Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** (rloo) Do these need more information or a spec, or can they be approved?
*** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
*** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
*** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
*** [RFE] Add Redfish Inspect Interface to Ironic* Open discussion: https://bugs.launchpad.net/ironic/+bug/1668487

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-11-13T23:23:23Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on November 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171120T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** [RFE] deprecate "hash_distribution_replicas" config option: https://bugs.launchpad.net/ironic/+bug/1680160
** [RFE] SNMP driver does not implement security features: https://bugs.launchpad.net/ironic/+bug/1710850
** [RFE] for rolling upgrades, pin the API version: https://bugs.launchpad.net/ironic/+bug/1708549
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-10-30T16:53:07Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on October 30, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20171030T1700).

== Agenda for next meeting ==
* Announcements / Reminder
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/
** rloo submitted patch to "Add the supports-rolling-upgrade tag to Ironic": https://review.openstack.org/#/c/514448/
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Appointing a bug triaging lead for the coming week
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-08-28T15:28:12Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on August 28, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170828T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** (rloo) we have OSC baremetal documentation: https://docs.openstack.org/python-ironicclient/latest/cli/osc_plugin_cli.html#command-reference
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** Team photo on the PTG: https://docs.google.com/spreadsheets/d/18DmI9ydq6dKr4hAcoAN83vYXWn8TV1NEvy09Ll02_Y0/edit#gid=0
** Team dinner/beers at the PTG? https://doodle.com/poll/nvavg9ab9ebq2e4v
** Finalizing the PTG plans: https://etherpad.openstack.org/p/ironic-queens-ptg
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Ironic/CoreTeam

2017-08-17T18:47:03Z

Rloo: /* Teams */

[[Category:Ironic]]

= Teams =

The [https://review.openstack.org/#/admin/groups/165,members ironic-core] team is responsible for reviewing all changes proposed to repositories (in 'master' branch) that are under the [https://governance.openstack.org/tc/reference/projects/ironic.html governance of ironic]. That includes the following repositories (this list is not exhaustive):
* openstack/ironic -- the primary services which comprise the OpenStack Ironic project
* openstack/python-ironicclient -- our Python client library and CLI
* openstack/ironic-python-agent -- the in-ramdisk Agent which we utilize for inband provisioning of hardware
* bifrost -- Ansible play books for running Ironic standalone
* ironic-lib -- common library of functions used by other Ironic projects

Similar to the ironic-core team, the [https://review.openstack.org/#/admin/groups/950,members ironic-stable-maint] team is responsible for reviewing all changes proposed to the repositories, in any stable (not 'master') branches. There are more restrictive [https://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines review guidelines] for stable branches.

The [https://review.openstack.org/#/admin/groups/307,members ironic-python-agent-core] team is an additional team which leads the review effort on the below projects. Members of this team may or may not be members of ironic-core.
* openstack/ironic-python-agent

The [https://review.openstack.org/#/admin/groups/352,members ironic-specs-core] team is responsible for reviewing design specifications. Not all ironic-core members have the time to dedicate to design reviews (and some would just rather focus on code). Furthermore, some operators routinely contribute to the design process, but don't have the time to regularly review code, and as such they are not members of ironic-core.
* openstack/ironic-specs

The [https://review.openstack.org/#/admin/groups/481,members ironic-inspector-core] team is responsible for the following projects:
* openstack/ironic-inspector

The [https://review.openstack.org/#/admin/groups/703,members bifrost-core] team is an additional team which leads the review effort on the below projects. Members of this team may or may not be members of ironic-core.
* openstack/bifrost

All of the teams are not mentioned here. You can find other ironic-related teams (some of them) at:
* https://review.openstack.org/#/admin/groups/?filter=ironic

Note that everyone is encouraged to help review changes, even if you are not a member of one of these teams. All reviews are very useful and are taken into account by the core team members. Participating in the review process is the most critical task on the road to joining any of the teams.

= Adding or Removing Members =

Each review group above should reflect active participation in the respective team. The ironic-core and ironic-specs-core teams are led by the project PTL, whereas ironic-python-agent-core and ironic-inspector-core are delegated to JayF and dtantsur, respectively.

The addition of new members, or removal of existing members, should be discussed amongst existing cores periodically, and any changes should be paired with an email to the openstack-dev mailing list. Such a discussion may be initiated by any core at any time. A member of the team may be removed at any time by the PTL. This is typically due to a drop off of involvement by the member such that they are no longer meeting expectations to maintain team membership. There is no need for a vote either when adding or removing members, though it is customary to get input from the existing team when making any changes to the team structure.

Note that discussing concerns about a nominee openly can have negative ramifications for the nominee. The effects of being nominated and then publicly -1'd are unpleasant at best and harmful at worst. Therefor, it is preferable to have an initial informal round of discussion amongst the existing core team to ensure that there is enough consensus and desire to work with the nominee, prior to a public vote.

It is also customary to reach out to the nominee privately to confirm their willingness to accept the position prior to any public discussion, though, as one can infer from the review activity an existing level of commitment to the project, this is not necessary.

= Membership Expectations =

Membership in the core review team is a significant commitment and should not be taken lightly. Maintaining membership on this team takes a lot of time. Further, it is important that the time invested is ''consistent''. It is harmful to the team and the project overall for the core team members' participation to be inconsistent.

Team members are expected to participate in code reviews on a regular (near daily) basis. Members are also expected to stay on top of discussions happening within the project, primarily on the openstack-dev mailing list and IRC. Note that IRC is used quite heavily, so members should be in <tt>#openstack-ironic</tt> as much as they can. These activities are critical to be able to provide high quality reviews based on the current state of the project that are consistent with the reviews being done by others on the team and consistent with the [http://docs.openstack.org/infra/manual/developers.html#peer-review documented review guidelines].

One metric used to determine the level of participation in reviews is just the number of reviews being done. While there is no hard line for an expectation on the number of reviews you are doing, members are generally expected to be in the same ballpark as the majority of the rest of the team. You can find stats on that here:

* [http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt Last 30 Days]
* [http://russellbryant.net/openstack-stats/ironic-reviewers-90.txt Last 90 days]
* [http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt Last 180 Days]

The number of reviews is certainly not the only important thing. It is also important that reviews are high quality, such that you gain respect from the other core team members over time. This is done by regularly providing high quality constructive criticism. Your well thought out recommendations for changes are what build credibility for your +1 of a patch.

All of these things are important, but the most important thing of all is to gain trust from the majority of the core team. There's not a well defined list of things you must do to gain this trust, but all of the expectations described here are a starting point.

= Review Prioritization =

Not all reviews are created equal. Team members should take care in prioritizing where they invest their review time. In general, priority should be based on the priority of the bug or blueprint the patch is associated with. Beyond that, older reviews should get priority. Take a look at the [[ReviewWorkflowTips]] page for tips on how to work prioritization into your workflow.

= Other notes =

* A -2 is not overridable by any other core, so be very sparing with them. It's a way to signal "this is so bad, I'm going to unilaterally veto it"
* Avoid the "perception of impropriety"
** a patch should not be reviewed and approved solely by core team members from the company that proposed the patch (particularly true of large features)
* Do not approve your own patches
* Approving a patch requires at least two +2
** Risky patches should get left up a little longer, so more cores have a chance to review
** except for trivial patches which can be approved with just one +2. You can use common sense to decide. Since common sense isn't always common, here are some areas where it is OK:
*** fix-ups to address review feedback
*** grammatical/clarification fixes to docstrings and inline comments[1]
*** global requirement (from OpenStack Proposal Bot) updates (depends on the change, but most would probably qualify)
*** translation patches
*** updates to 'development' config files like .gitignore
* Try to review at least 1 patch per day (on average)
** and let the team know if you're taking an extended vacation, so they don't wonder why you're not reviewing anything :)

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-February/057794.html

Ironic

2017-07-26T19:09:42Z

Rloo: /* Projects */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [https://docs.openstack.org/ironic/latest/user/index.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Documentation
| https://docs.openstack.org/ironic/latest/
|-
| Bug tracker
| https://bugs.launchpad.net/ironic
|-
| Feature tracker
| https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-ironicclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-ironicclient
|-
| Documentation
| https://docs.openstack.org/python-ironicclient/latest/
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-python-agent
|-
| Documentation
| https://docs.openstack.org/ironic-python-agent/latest/
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-inspector/
|-
| Feature tracker
| https://bugs.launchpad.net/ironic-inspector/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Documentation
| https://docs.openstack.org/ironic-inspector/latest/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://bugs.launchpad.net/bifrost
|-
| Documentation
| https://docs.openstack.org/bifrost/latest/
|}

== networking-baremetal ==

'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/networking-baremetal
|-
| Bug tracker
| https://bugs.launchpad.net/networking-baremetal
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-lib
|-
| Documentation
| https://docs.openstack.org/ironic-lib/latest/
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-ui/
|-
| Documentation
| https://docs.openstack.org/ironic-ui/latest/
|}

= People =

'''PTL''': Dmitry Tantsur (dtantsur)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Ironic

2017-07-26T19:04:16Z

Rloo: /* ironic */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [https://docs.openstack.org/ironic/latest/user/index.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Documentation
| https://docs.openstack.org/ironic/latest/
|-
| Bug tracker
| https://bugs.launchpad.net/ironic
|-
| Feature tracker
| https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-ironicclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-ironicclient
|-
| Developer doc
| http://docs.openstack.org/developer/python-ironicclient
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-python-agent
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-python-agent
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-inspector/
|-
| Feature tracker
| https://bugs.launchpad.net/ironic-inspector/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-inspector/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://bugs.launchpad.net/bifrost
|}

== networking-baremetal ==

'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/networking-baremetal
|-
| Bug tracker
| https://bugs.launchpad.net/networking-baremetal
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-lib
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-ui/
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-ui/
|}

= People =

'''PTL''': Dmitry Tantsur (dtantsur)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Ironic

2017-07-26T19:01:59Z

Rloo: /* OpenStack Bare Metal Provisioning Program */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [https://docs.openstack.org/ironic/latest/user/index.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Developer doc
| http://docs.openstack.org/developer/ironic/
|-
| Bug tracker
| https://bugs.launchpad.net/ironic
|-
| Feature tracker
| https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-ironicclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-ironicclient
|-
| Developer doc
| http://docs.openstack.org/developer/python-ironicclient
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-python-agent
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-python-agent
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-inspector/
|-
| Feature tracker
| https://bugs.launchpad.net/ironic-inspector/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-inspector/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://bugs.launchpad.net/bifrost
|}

== networking-baremetal ==

'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/networking-baremetal
|-
| Bug tracker
| https://bugs.launchpad.net/networking-baremetal
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-lib
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-ui/
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-ui/
|}

= People =

'''PTL''': Dmitry Tantsur (dtantsur)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2017-07-17T20:16:42Z

Rloo: /* Agenda for next meeting */

Meetings/Ironic

2017-07-13T17:55:25Z

Rloo: /* Agenda for next meeting */

Meetings/Ironic

2017-07-11T12:50:45Z

Rloo: /* Agenda for next meeting */

Meetings/Ironic

2017-07-10T16:02:58Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur) or Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on July 10, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170710T1700).

== Agenda for next meeting ==
* Announcements / Reminder
** Non-client libraries deadline next week. This affects ironic-lib and sushy.
** Release request for ironicclient 1.14 with BFV API submitted (thanks TheJulia)
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** (rloo) REST API to list volume connectors & volume targets returns node_uuid, but port & portgroup doesn't. Are we OK with inconsistency?
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Ironic

2017-06-05T18:00:04Z

Rloo: /* Projects */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [http://docs.openstack.org/developer/ironic/deploy/user-guide.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Developer doc
| http://docs.openstack.org/developer/ironic/
|-
| Bug tracker
| https://bugs.launchpad.net/ironic
|-
| Feature tracker
| https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-ironicclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-ironicclient
|-
| Developer doc
| http://docs.openstack.org/developer/python-ironicclient
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-python-agent
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-python-agent
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-inspector/
|-
| Feature tracker
| https://bugs.launchpad.net/ironic-inspector/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-inspector/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://bugs.launchpad.net/bifrost
|}

== networking-baremetal ==

'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/networking-baremetal
|-
| Bug tracker
| https://bugs.launchpad.net/networking-baremetal
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-lib
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-ui/
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-ui/
|}

= People =

'''PTL''': Dmitry Tantsur (dtantsur)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2017-04-19T17:43:02Z

Rloo: /* Agenda for next meeting */

Meetings/Ironic

2017-04-04T13:45:26Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on April 10, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170410T1700).

== Agenda for next meeting ==
* Announcements / Reminders
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** trello. (rloo) To use or not to use, that is the question. Unless someone wants to update it for Pike and maintain it, we should remove all trello links and capture info in another way (if people want that info...)
* RFE review

* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

CrossProjectLiaisons

2017-03-20T18:53:37Z

Rloo: /* Logging Working Group */

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 || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Rushil Chugh || crushil
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| 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. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Tim Simmons || timsim
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| 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 || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || - || -
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Timur Sufiev || tsufiev
|-
| Ironic || John Villalovos || jlvillal
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| 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 || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| 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
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| 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 || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || David Tardivel || dtardivel
|-
| 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 [https://security.openstack.org/vmt-process.html 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
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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_
|-
| Ironic || Solio Sarabia || soliosg
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Elise 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
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco|| flaper87
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

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

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

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

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

|-
| TripleO || 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
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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 (or a person who is not a core reviewer but agreed & approved by PTL) 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 || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| 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 || || ||
|-
| || Kevin Benton || kevinbenton || 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 || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat 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
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== 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 || Eric Kao || ekcs
|-
| 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 || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| OpenStack-Ansible || Travis Truman || automagically
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| 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

|}

CrossProjectLiaisons

2017-03-20T18:49:25Z

Rloo: /* Oslo */

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 || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Rushil Chugh || crushil
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| 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. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Tim Simmons || timsim
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| 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 || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || - || -
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Timur Sufiev || tsufiev
|-
| Ironic || John Villalovos || jlvillal
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Valeriy Ponomaryov || vponomaryov
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| 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 || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| 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
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| 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 || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || David Tardivel || dtardivel
|-
| 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 [https://security.openstack.org/vmt-process.html 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
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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 || ||
|-
| Sahara || Elise 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
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco|| flaper87
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

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

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

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

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

|-
| TripleO || 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
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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 (or a person who is not a core reviewer but agreed & approved by PTL) 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 || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| 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 || || ||
|-
| || Kevin Benton || kevinbenton || 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 || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat 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
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== 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 || Eric Kao || ekcs
|-
| 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 || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| OpenStack-Ansible || Travis Truman || automagically
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| 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

|}

Forum/Boston2017

2017-03-20T18:38:57Z

Rloo: /* Project Teams */

__NOTOC__
The grand list of all of the Boston Forum etherpads. Please include the name of the team that started the pad.

==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

===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/Ironic

2017-03-20T17:01:28Z

Rloo:

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on March 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170320T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** ironic-{core, release} groups were added to sushy-{core, release} groups respectively now that we decided to have it under the ironic umbrella! Happy hacking :D
** rloo is retiring from subteam-status-report duty; rama_y (Ramamani Yeleswarapu) has kindly agreed to take over. Thanks rama_y!
** thanks to the new ironic liaisons, JayF for i18n; Rushil Chugh for oslo; soliosg (Solio Sarabia) for logging working group.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
** Stuck specs for current and potential priorities
** Appointing a bug liaison for the next week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
* Open discussion
** Some interesting information https://bugs.launchpad.net/ironic/+bug/1672457 (mjturek)
** Having one or two config properties for SSL cert verification in the redfish driver: https://review.openstack.org/#/c/438982/11/ironic/drivers/modules/redfish/utils.py ; see comment at L48 (lucasagomes)

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-03-13T19:29:53Z

Rloo: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2017-03-09T15:10:10Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on March 13, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170313T1700).

== Agenda for next meeting ==
* Announcements / Reminders
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
** Stuck specs for current and potential priorities
** Appointing a bug liaison for the next week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** (rloo) Boston summit/forum brainstorming: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: TBD, poll at http://doodle.com/poll/qwhnpqazmf7fn5ik
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-03-09T15:09:52Z

Rloo: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

The next meeting will be on March 13, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170313T1700).

== Agenda for next meeting ==
* Announcements / Reminders
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Deciding on priorities for the coming week
** Stuck specs for current and potential priorities
** Appointing a bug liaison for the next week
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* (rloo) Boston summit/forum brainstorming: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* Boot From Volume meeting: TBD, poll at http://doodle.com/poll/qwhnpqazmf7fn5ik
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui

Meetings/Ironic

2017-03-06T20:14:14Z

Rloo: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2017-02-27T21:15:37Z

Rloo: /* Weekly Ironic Project Team Meeting */

Ironic

2017-02-27T20:54:42Z

Rloo: /* People */

= OpenStack Bare Metal Provisioning Program =

OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [http://docs.openstack.org/developer/ironic/deploy/user-guide.html Introduction to Ironic].

= Projects =

Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].

Some of the deliverables (or projects) are described below.

== ironic ==

The '''ironic''' project includes the ironic-api and ironic-conductor processes.

{| border="1" cellpadding="2"
| Official name
| '''OpenStack Bare Metal Provisioning'''
|-
| Source code
| https://git.openstack.org/cgit/openstack/ironic
|-
| Developer doc
| http://docs.openstack.org/developer/ironic/
|-
| Bug tracker
| https://bugs.launchpad.net/ironic
|-
| Feature tracker
| https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Specifications
| http://specs.openstack.org/openstack/ironic-specs
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

== python-ironicclient ==

'''python-ironicclient''' is a package that includes the python client and CLI.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/python-ironicclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-ironicclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-ironicclient
|-
| Developer doc
| http://docs.openstack.org/developer/python-ironicclient
|}

== ironic-python-agent ==

'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-python-agent"
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-python-agent
|-
| Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

== pyghmi ==

'''pyghmi''' is a python IPMI library; it is an alternative to IPMItool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/pyghmi
|}

== ironic-inspector ==

'''ironic-inspector''' is a hardware introspection tool.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-inspector
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-inspector/
|-
| Feature tracker
| https://bugs.launchpad.net/ironic-inspector/+bugs?field.tag=rfe+rfe-approved+&field.tags_combinator=ANY
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-inspector/
|}

== bifrost ==

'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/bifrost
|-
| Bug tracker
| https://bugs.launchpad.net/bifrost
|}

== ironic-lib ==

'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-lib
|-
| Bug tracker
| https://bugs.launchpad.net/ironic-lib
|}

== ironic-ui ==

'''ironic-ui''' is a horizon plugin for ironic.

{| border="1" cellpadding="2"
| Source code
| https://git.openstack.org/cgit/openstack/ironic-ui
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-ui/
|-
| Developer doc
| http://docs.openstack.org/developer/ironic-ui/
|}

= People =

'''PTL''': Dmitry Tantsur (dtantsur)

'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam

'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons

= Status =

Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.

Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.

Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.

For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].

= Etherpads =

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

= IRC =

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!

= Developers =

Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

= Pixie Boots, the Ironic drummer bear =

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
bear metal.svg|Icon
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/

= Misc. =

* [[Ironic/IPv6|Ironic + IPv6]]

= Outside the OpenStack Bare Metal Provisioning Program =

== Out-of-tree Ironic drivers ==

Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.
== Vendor-specific tools ==

Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.

{| border="1" cellpadding="2"
| Developer doc
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc
|-
| List of third party vendor tools
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList
|}

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2017-02-13T20:31:18Z

Rloo: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2017-02-13T20:30:08Z

Rloo: /* Next Meeting */

Meetings/Ironic

2017-02-06T19:30:06Z

Rloo: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2017-01-30T22:17:04Z

Rloo: /* Next Meeting */

Meetings/Ironic

2017-01-23T20:06:10Z

Rloo: /* Agenda for next meeting */

Meetings/Ironic

2017-01-23T20:05:33Z

Rloo: /* Next Meeting */

Meetings/Ironic

2017-01-16T19:26:05Z

Rloo: /* Next Meeting */

Meetings/Ironic

2017-01-09T18:04:08Z

Rloo: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2016-12-19T20:16:08Z

Rloo: /* Weekly Ironic Project Team Meeting */