OpenStack - User contributions [en]

CrossProjectLiaisons

2020-06-22T22:44:03Z

Lingxian:

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Bernard Cafarelli || bcafarel
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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 || Lingxian Kong || lxkong
|-
| 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

The liaisons list is now being maintained in the [https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml release's repo here]. If you want to add/update liaison info, please submit a patch to the releases repository.

== 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
|-
| Cyborg || Chenke || chenker
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Ghanshyam Mann || gmann
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| Trove || Lingxian Kong || lxkong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Lingxian Kong || lxkong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || ||
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Lee Yarwood || lyarwood
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== 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 unless explicitly listed.
* 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's core security review team in Launchpad or StoryBoard (reviewers who will be given access to embargoed vulnerabilities by the VMT)
* If the project has multiple core security review teams for different deliverables they should be listed together in the appropriate column.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle !! Security Team
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill ||
|-
| Cinder || || || [https://launchpad.net/~cinder-coresec/+members all deliverables]
|-
| Glance || Brian Rosmaita || rosmaita || [https://launchpad.net/~glance-coresec/+members all deliverables]
|-
| Heat || Steve Hardy || shardy ||
|-
| Horizon || Ivan Kolodyazhny || e0ne || [https://launchpad.net/~horizon-coresec/+members all deliverables]
|-
| Keystone || Gage Hugo || gagehugo || [https://launchpad.net/~keystone-coresec/+members all deliverables]
|-
| Neutron || Miguel Lavalle || mlavalle || [https://launchpad.net/~neutron-coresec/+members all deliverables]
|-
| Nova || Michael Still || mikal || [https://launchpad.net/~nova-coresec/+members all deliverables]
|-
| Oslo || || || [https://launchpad.net/~oslo-coresec/+members all deliverables]
|-
| Sahara || Telles Nobrega || tellesnobrega ||
|-
| Swift || || || [https://launchpad.net/~swift-coresec/+members all deliverables]
|-
| Trove || Lingxian Kong || lxkong ||
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Lingxian Kong || lxkong

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

|-
| Airship || Matt McEuen || mattmceuen
|}

== 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 || Abhishek Kekane || akekane
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| 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 || ||
|-
| Trove || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project.

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Luka Peschke
| peschk_l
| luka.peschke@objectif-libre.com
| CEST (UTC+2)
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Kristi Nikolla
| knikolla
|
|
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Stefano Canepa
| sc
| sc@linux.it
| UTC
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| skaplons@redhat.com
| UTC+1
| [[Neutron|Neutron]]
|-
| Eric Fried
| efried
| openstack@fried.cc
| UTC-6
| Nova
|-
| Alex Xu
| alex_xu
| hejie.xu@intel.com
| UTC+8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Canwei Li
| licanwei
| li.canwei2@zte.com.cn
| UTC+8
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

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

CrossProjectLiaisons

2020-06-22T22:34:54Z

Lingxian: /* Vulnerability management */

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

== Oslo ==

There are far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Bernard Cafarelli || bcafarel
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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

The liaisons list is now being maintained in the [https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml release's repo here]. If you want to add/update liaison info, please submit a patch to the releases repository.

== 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
|-
| Cyborg || Chenke || chenker
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Ghanshyam Mann || gmann
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || ||
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Lee Yarwood || lyarwood
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== 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 unless explicitly listed.
* 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's core security review team in Launchpad or StoryBoard (reviewers who will be given access to embargoed vulnerabilities by the VMT)
* If the project has multiple core security review teams for different deliverables they should be listed together in the appropriate column.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle !! Security Team
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill ||
|-
| Cinder || || || [https://launchpad.net/~cinder-coresec/+members all deliverables]
|-
| Glance || Brian Rosmaita || rosmaita || [https://launchpad.net/~glance-coresec/+members all deliverables]
|-
| Heat || Steve Hardy || shardy ||
|-
| Horizon || Ivan Kolodyazhny || e0ne || [https://launchpad.net/~horizon-coresec/+members all deliverables]
|-
| Keystone || Gage Hugo || gagehugo || [https://launchpad.net/~keystone-coresec/+members all deliverables]
|-
| Neutron || Miguel Lavalle || mlavalle || [https://launchpad.net/~neutron-coresec/+members all deliverables]
|-
| Nova || Michael Still || mikal || [https://launchpad.net/~nova-coresec/+members all deliverables]
|-
| Oslo || || || [https://launchpad.net/~oslo-coresec/+members all deliverables]
|-
| Sahara || Telles Nobrega || tellesnobrega ||
|-
| Swift || || || [https://launchpad.net/~swift-coresec/+members all deliverables]
|-
| Trove || Lingxian Kong || lxkong ||
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

|-
| Airship || Matt McEuen || mattmceuen
|}

== 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 || Abhishek Kekane || akekane
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| 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 || ||
|-
| Trove || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project.

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Luka Peschke
| peschk_l
| luka.peschke@objectif-libre.com
| CEST (UTC+2)
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Kristi Nikolla
| knikolla
|
|
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Stefano Canepa
| sc
| sc@linux.it
| UTC
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| skaplons@redhat.com
| UTC+1
| [[Neutron|Neutron]]
|-
| Eric Fried
| efried
| openstack@fried.cc
| UTC-6
| Nova
|-
| Alex Xu
| alex_xu
| hejie.xu@intel.com
| UTC+8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Canwei Li
| licanwei
| li.canwei2@zte.com.cn
| UTC+8
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

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

First Contact SIG

2019-04-24T02:27:40Z

Lingxian: /* Project Liaisons */

==First Contact SIG==

'''Our Mission'''

To provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community.

'''Chairs'''
* Kendall Nelson (diablo_rojo) UTC -7

'''Members'''
* Zhipeng Huang (zhipeng) UTC+8
* Amy Marrich (spotz) UTC-6
* Colleen Murphy (cmurphy) UTC+1
* Ildikó Váncsa (ildikov) UTC+1 (UTC+2 with daylight saving)
* Jay Bryant (jungleboyj) UTC-6
* Ghanshyam Mann (gmann) UTC+9
* Matt Oliver (mattolverau) UTC+10 (UTC+11 with daylight saving)
* Gergely Csatari (csatari) UTC+1 (UTC+2 with daylight saving)
* Surya Prakash Singh (spsurya) UTC+9

===Helpful Resources===
* [https://www.openstack.org/community/ Contributor Portal]
* [[Mentoring]]
* [[Outreachy]]

===Project Liaisons===

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Christophe Sauthier
| huats
| christophe.sauthier@objectif-libre.com
|
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Colleen Murphy
| cmurphy
| colleen@gazlene.net
| UTC+1
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Cristiano Bellucci
| cbellucci
| Cristiano.bellucci@est.fujitsu.com
| UTC+1
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| slawek@kaplonski.pl
| UTC+1
| [[Neutron|Neutron]]
|-
| Melanie Witt
| melwitt
| melwitt@gmail.com
| UTC-8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Julien Danjou
| jd
| julien@danjou.info
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Aditi Sharma
| adisky
| adi.sky17@gmail.com
| UTC+5:30
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

===Meeting Agenda===
The First Contact SIG team holds public weekly meeting:

* Channel: <code><nowiki>#openstack-upstream-institute</nowiki></code>
* Time: biweekly-odd on Wednesday at 0100 UTC.
* For Chair person: Start this meeting using: #startmeeting fc_sig
* The meeting minutes of previous meetings can be found here: [http://eavesdrop.openstack.org/meetings/fc_sig/ meeting minutes on eavesdrop]

'''Ping list:''' gmann, mattoliverau, cmurphy, tonyb, spotz

Standing Items:
* Announcements
** Update UTC offsets
* New Contributor Patches
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22+is:open+-project:+openstack-dev/sandbox+AND+-project:openstack-dev/ci-sandbox Unmerged Patches Not in the sandbox or ci-sandbox]
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22 All Changes]
** https://etherpad.openstack.org/p/FC_SIG_patch_checkup
** New Contributor the Month
* Ask.openstack.org Contribution Questions
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contribution/page:1/ 'Contribution' Tag]
**[https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contributor/page:1/ 'Contributor' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:community/page:1/ 'Community' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:developer/page:1/ 'Developer' Tag']
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:development/page:1/ 'Development' Tag]
** [https://ask.openstack.org/en/questions/tags:gettingstarted/ 'Getting Started' Tag]
** [https://ask.openstack.org/en/questions/tags:basics/ 'basics' Tag]
** [https://ask.openstack.org/en/questions/tags:beginner/ 'beginner' Tag]
** [https://ask.openstack.org/en/questions/tags:newbie/ 'newbie' Tag]
** [https://ask.openstack.org/en/questions/tags:noob/ 'noob' Tag]
** [https://ask.openstack.org/en/questions/tags:training/ 'training' Tag]
** [https://etherpad.openstack.org/p/ask.o.o-contribution Etherpad for Seeding Ask.O.O]

Other Items:
* Sandbox Bot
** http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002291.html
** https://review.openstack.org/#/c/636466/1
* Summit + Forum Planning
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23740/first-contact-sig-meet-and-greet FC SIG Meet and Greet]
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23659/welcoming-new-contributors-state-of-the-union-and-deduplication-of-efforts Deduplication of Efforts]
* Project Liaisons
** Need to email openstack-discuss list to make sure the list is up to date with new PTLs
* People to Reach Out To
** [https://ethercalc.openstack.org/fc-sig-contact-list Pretty Ethercalc]

First Contact SIG

2019-04-24T02:27:10Z

Lingxian: /* Project Liaisons */

==First Contact SIG==

'''Our Mission'''

To provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community.

'''Chairs'''
* Kendall Nelson (diablo_rojo) UTC -7

'''Members'''
* Zhipeng Huang (zhipeng) UTC+8
* Amy Marrich (spotz) UTC-6
* Colleen Murphy (cmurphy) UTC+1
* Ildikó Váncsa (ildikov) UTC+1 (UTC+2 with daylight saving)
* Jay Bryant (jungleboyj) UTC-6
* Ghanshyam Mann (gmann) UTC+9
* Matt Oliver (mattolverau) UTC+10 (UTC+11 with daylight saving)
* Gergely Csatari (csatari) UTC+1 (UTC+2 with daylight saving)
* Surya Prakash Singh (spsurya) UTC+9

===Helpful Resources===
* [https://www.openstack.org/community/ Contributor Portal]
* [[Mentoring]]
* [[Outreachy]]

===Project Liaisons===

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Christophe Sauthier
| huats
| christophe.sauthier@objectif-libre.com
|
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Colleen Murphy
| cmurphy
| colleen@gazlene.net
| UTC+1
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Cristiano Bellucci
| cbellucci
| Cristiano.bellucci@est.fujitsu.com
| UTC+1
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| slawek@kaplonski.pl
| UTC+1
| [[Neutron|Neutron]]
|-
| Melanie Witt
| melwitt
| melwitt@gmail.com
| UTC-8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Julien Danjou
| jd
| julien@danjou.info
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
|
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Aditi Sharma
| adisky
| adi.sky17@gmail.com
| UTC+5:30
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

===Meeting Agenda===
The First Contact SIG team holds public weekly meeting:

* Channel: <code><nowiki>#openstack-upstream-institute</nowiki></code>
* Time: biweekly-odd on Wednesday at 0100 UTC.
* For Chair person: Start this meeting using: #startmeeting fc_sig
* The meeting minutes of previous meetings can be found here: [http://eavesdrop.openstack.org/meetings/fc_sig/ meeting minutes on eavesdrop]

'''Ping list:''' gmann, mattoliverau, cmurphy, tonyb, spotz

Standing Items:
* Announcements
** Update UTC offsets
* New Contributor Patches
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22+is:open+-project:+openstack-dev/sandbox+AND+-project:openstack-dev/ci-sandbox Unmerged Patches Not in the sandbox or ci-sandbox]
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22 All Changes]
** https://etherpad.openstack.org/p/FC_SIG_patch_checkup
** New Contributor the Month
* Ask.openstack.org Contribution Questions
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contribution/page:1/ 'Contribution' Tag]
**[https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contributor/page:1/ 'Contributor' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:community/page:1/ 'Community' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:developer/page:1/ 'Developer' Tag']
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:development/page:1/ 'Development' Tag]
** [https://ask.openstack.org/en/questions/tags:gettingstarted/ 'Getting Started' Tag]
** [https://ask.openstack.org/en/questions/tags:basics/ 'basics' Tag]
** [https://ask.openstack.org/en/questions/tags:beginner/ 'beginner' Tag]
** [https://ask.openstack.org/en/questions/tags:newbie/ 'newbie' Tag]
** [https://ask.openstack.org/en/questions/tags:noob/ 'noob' Tag]
** [https://ask.openstack.org/en/questions/tags:training/ 'training' Tag]
** [https://etherpad.openstack.org/p/ask.o.o-contribution Etherpad for Seeding Ask.O.O]

Other Items:
* Sandbox Bot
** http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002291.html
** https://review.openstack.org/#/c/636466/1
* Summit + Forum Planning
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23740/first-contact-sig-meet-and-greet FC SIG Meet and Greet]
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23659/welcoming-new-contributors-state-of-the-union-and-deduplication-of-efforts Deduplication of Efforts]
* Project Liaisons
** Need to email openstack-discuss list to make sure the list is up to date with new PTLs
* People to Reach Out To
** [https://ethercalc.openstack.org/fc-sig-contact-list Pretty Ethercalc]

CrossProjectLiaisons

2019-04-19T10:42:06Z

Lingxian: /* Release management */

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

== Oslo ==

There are far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Nate Johnston || njohnston
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Stephen Finucane || stephenfin
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Akihiro Motoki || amotoki
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Felipe Monteiro || felipemonteiro
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza, Matt Riedemann || bauzas, mriedem
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| OpenStackAnsible || Jean-Philippe Evrard || evrardjp
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Placement || Chris Dent || cdent
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || Canwei Li || licanwei
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Boden Russel || boden
|-
| Nova || Stephen Finucane || stephenfin
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Matt Riedemann || mriedem
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Mark Goddard || mgoddard
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

== 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 || Abhishek Kekane || akekane
|-
| 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 || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project. The list of project liaisons are in [https://wiki.openstack.org/wiki/First_Contact_SIG First Contact SIG Wiki page].

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

IRC

2018-08-23T12:51:56Z

Lingxian: /* OpenStack IRC channels (chat.freenode.net) */

IRC, or Internet Relay Chat, is often used as a real-time communication capability with open source projects. We're pretty proud of the friendly vibe in the OpenStack channels and invite anyone wanting to ask questions or talk about all things OpenStack to the channels.

IRC software can be found for all operating systems. The [https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients#Operating_system_support IRC clients comparison chart on Wikipedia] can help you pick one for your operating system.

You don't have to have a complex setup to use IRC. You can use the web client for Freenode, which doesn't require any download or setup. Just pick a nickname and join #openstack: http://webchat.freenode.net/?channels=openstack,openstack-dev.

=== How to read messages exchanged when you're offline ===

IRC, unlike other chat systems, doesn't keep when you're offline. In order to be notified of relevant communications you can either look at the [http://eavesdrop.openstack.org/irclogs/ channel logs] or setup an IRC proxy.

The most common IRC proxies are [http://wiki.znc.in/ZNC znc] and [https://bip.milkypond.org/ bip]. See the following guides to configure them:

* [https://kashyapc.fedorapeople.org/notes-bip-IRC-proxy/README Installation notes for Fedora/RH-like] and [https://kashyapc.fedorapeople.org/notes-bip-IRC-proxy/bip.conf example bip.conf] contributed by Kashyap Chamarthy
* ZNC [https://dague.net/2014/09/13/my-irc-proxy-setup/ configuration notes] contributed by Sean Dague
* [https://weechat.org/ WeeChat] IRC client combines proxy and client, and allows you to run the client in a shell and access that client additionally from a web client or Android app.

=== IRC meetings ===

The OpenStack project holds its various public meetings on IRC. See [[Meetings]] for details.

== OpenStack IRC channels (chat.freenode.net) ==

If you want to start a new IRC channel, please consult with the InfrastructureTeam in #openstack-infra or at openstack-infra@lists.openstack.org to ensure it gets registered appropriately.

'''Many IRC channels are logged and [http://eavesdrop.openstack.org/irclogs/ recordings are publicly accessible]'''. If you're concerned about privacy consider using a [https://freenode.net/kb/answer/cloaks cloak], [https://freenode.net/kb/answer/chat tor], hide your real name and be mindful not to write sensitive data in these channels.

{| class="wikitable sortable" border="1"
|-
! IRC Channel !! Description
|-
|'''#openstack''' || general discussion, support
|-
|'''#openstack-ansible''' || [http://docs.openstack.org/developer/openstack-ansible/ OpenStack-Ansible] discussions
|-
|'''#openstack-anvil''' || [http://anvil.readthedocs.org/ Anvil] discussion channel
|-
|'''#openstack-app-catalog''' || [http://apps.openstack.org Community App Catalog] discussions
|-
|'''#openstack-barbican''' || Barbican-related team discussions
|-
|'''#openstack-blazar''' || blazar (formerly climate) team discussions
|-
|'''#openstack-board''' || OpenStack Foundation Board Meeting Back channel (mainly quiet except during meetings)
|-
|'''#openstack-telemetry''' || Telemetry team (ceilometer, aodh, gnocchi) discussions
|-
|'''#openstack-chef''' || deployment and operating OpenStack with Chef
|-
| '''#openstack-chinese''' || general discussion, support in Chinese
|-
| '''#openstack-cinder''' || cinder team discussions
|-
| '''#openstack-community''' || coordination of community activity
|-
| '''#openstack-containers''' || Magnum team discussion
|-
| '''#openstack-cue''' || Cue team discussion
|-
|'''#openstack-defcore''' || Defcore discussion channel
|-
|'''#openstack-dev''' || general and cross-project development discussion
|-
|'''#openstack-dib''' || Discussion around diskimage-builder
|-
|'''#openstack-dns''' || Designate DNS team discussions
|-
|'''#openstack-doc''' || documentation team discussion
|-
|'''#openstack-dragonflow''' || [https://docs.openstack.org/dragonflow/ Dragonflow] team discussion
|-
|'''#openstack-ec2api''' || EC2 API discussion channel
|-
|'''#openstack-fr''' || general discussion, support in French
|-
|'''#openstack-fwaas''' || Firewall as a Service discussions
|-
|'''#openstack-gbp''' || Group Based Policy discussions
|-
|'''#openstack-glance''' || glance team discussions
|-
|'''#openstack-glare''' || glare team discussions
|-
|'''#openstack-freezer''' || freezer team discussions
|-
|'''#openstack-gsoc''' || google summer of code discussions
|-
|'''#openstack-ha''' || High Availability discussions
|-
|'''#openstack-heat-translator''' || Heat-Translator and TOSCA-Parser team discussions
|-
|'''#openstack-horizon''' || horizon team discussions
|-
|'''#openstack-hyper-v''' || Microsoft Windows guests and hypervisor discussion
|-
| '''#openstack-i18n''' || I18N team discussions
|-
|'''#openstack-infra''' || developer community infrastructure, continuous integration testing
|-
|'''#openstack-ironic''' || ironic & bare metal discussions
|-
|'''#openstack-jjb''' || Jenkins Job Builder discussions
|-
|'''#openstack-karbor''' || karbor team discussions
|-
|'''#openstack-keystone''' || keystone team discussions
|-
|'''#openstack-ko''' || general discussion, support in Korean
|-
|'''#openstack-kolla''' || Kolla team discussion channel
|-
|'''#openstack-kuryr''' || Kuryr team discussion channel
|-
|'''#openstack-latinamerica''' || OpenStack Latin America (Spanish)
|-
|'''#openstack-lbaas''' || Neutron LBaaS and Project Octavia discussions
|-
|'''#openstack-manila''' || shared / distributed file system service team discussions
|-
|'''#openstack-marconi''' || queue/messaging marconi team discussions
|-
|'''#openstack-meeting''' || team meetings
|-
|'''#openstack-meeting-alt''' || team meetings, alternate channel
|-
|'''#openstack-meeting-cp''' || cross-project meetings
|-
|'''#openstack-meeting-3''' || team meetings, another alternate channel
|-
|'''#openstack-meeting-4''' || team meetings, another alternate channel
|-
|'''#openstack-mistral''' || Mistral Workflow Service for OpenStack
|-
|'''#openstack-monasca''' || Monasca Monitoring and Logging as-a-Service for OpenStack
|-
|'''#openstack-neutron''' || neutron team discussions
|-
|'''#openstack-nfv''' || [[Teams/NFV|NFV]] team discussions
|-
|'''#openstack-nova''' || nova team discussions
|-
|'''#openstack-operators''' || OpenStack Operators discussion channel
|-
|'''#openstack-opw''' || GNOME OPW mentor, intern and supporter discussions
|-
|'''#openstack-oslo''' || [https://wiki.openstack.org/wiki/Oslo Oslo] development discussion
|-
|'''#openstack-performance''' || All OpenStack performance related discussions
|-
|'''#openstack-pkg''' || Debian packaging discussions
|-
|'''#openstack-pl''' || OpenStack discussions in Polish
|-
|'''#openstack-powervm''' || PowerVM OpenStack drivers discussion channel
|-
| '''#openstack-qa''' || QA team discussion
|-
| '''#openstack-qinling''' || Function as a Service discussion channel
|-
|'''#openstack-rally''' || [https://wiki.openstack.org/wiki/Rally Rally] measure performance of your cloud
|-
|'''#openstack-rating''' || Rating team discussions
|-
|'''#openstack-release''' || Release managers channel
|-
|'''#openstack-requirements''' || Requirements discussion channel
|-
|'''#openstack-rpm-packaging''' || RPM packaging discussions
|-
|'''#openstack-sahara''' || [https://wiki.openstack.org/wiki/Sahara Sahara] team discussions
|-
|'''#openstack-sdks''' || Development of SDKs to work with OpenStack and the unified OpenStack command line tool
|-
|'''#openstack-security''' || General discussion about OpenStack security and open channel for the OpenStack Security Group (OSSG)
|-
|'''#openstack-searchlight''' || [wiki.openstack.org/wiki/Searchlight] - Search your OpenStack resources
|-
|'''#openstack-stable''' || stable branch management discussions
|-
|'''#openstack-state-management''' || [https://wiki.openstack.org/wiki/TaskFlow TaskFlow] and state-management development discussion
|-
|'''#openstack-swift''' || swift team discussions
|-
|'''#openstack-third-party-ci''' || OpenStack third-party CI operators
|-
|'''#openstack-trove''' || trove database team discussions
|-
|'''#openstack-tw''' || general discussion, support in Taiwan
|-
|'''#openstack-upstream-institute''' || OpenStack Upstream Institute team discussions and a forum to discuss questions and best practices about on-boarding new contributors
|-
| '''#openstack-ux''' || discussion channel for user experience
|-
|'''#openstack-vmware''' || The VMwareAPI team discussion channel
|-
|'''#openstack-watcher''' || [https://wiki.openstack.org/wiki/Watcher Watcher] discussion channel
|-
|'''#openstack-zun''' || [https://wiki.openstack.org/wiki/Zun Zun] discussion channel
|-
|'''#airshipit''' || OpenStack [https://www.airshipit.org/ Airship] discussion channel - declarative automated cloud provisioning and management
|-
|'''#congress''' || Congress policy developer discussion channel
|-
|'''#fuel''' || Fuel users&developers discussion channel
|-
|'''#heat''' || Heat developer discussion channel
|-
|'''#magnetodb''' || Key-Value storage for OpenStack
|-
|'''#murano''' || Murano team discussions
|-
|'''#nova-docker''' || Nova Docker team discussions
|-
|'''#refstack''' || RefStack
|-
|'''#senlin''' || [https://wiki.openstack.org/wiki/Senlin Senlin] team discussions
|-
|'''#storyboard''' || StoryBoard team discussions
|-
|'''#tacker''' || [https://wiki.openstack.org/wiki/Tacker Tacker] NFV Orchestrator team discussions
|-
|'''#tripleo''' || TripleO team discussions
|-
|'''#puppet-openstack''' || Openstack Puppet modules discussions
|-}

[[Category:Connect]]

IRC

2018-08-23T12:51:31Z

Lingxian: /* OpenStack IRC channels (chat.freenode.net) */

IRC, or Internet Relay Chat, is often used as a real-time communication capability with open source projects. We're pretty proud of the friendly vibe in the OpenStack channels and invite anyone wanting to ask questions or talk about all things OpenStack to the channels.

IRC software can be found for all operating systems. The [https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients#Operating_system_support IRC clients comparison chart on Wikipedia] can help you pick one for your operating system.

You don't have to have a complex setup to use IRC. You can use the web client for Freenode, which doesn't require any download or setup. Just pick a nickname and join #openstack: http://webchat.freenode.net/?channels=openstack,openstack-dev.

=== How to read messages exchanged when you're offline ===

IRC, unlike other chat systems, doesn't keep when you're offline. In order to be notified of relevant communications you can either look at the [http://eavesdrop.openstack.org/irclogs/ channel logs] or setup an IRC proxy.

The most common IRC proxies are [http://wiki.znc.in/ZNC znc] and [https://bip.milkypond.org/ bip]. See the following guides to configure them:

* [https://kashyapc.fedorapeople.org/notes-bip-IRC-proxy/README Installation notes for Fedora/RH-like] and [https://kashyapc.fedorapeople.org/notes-bip-IRC-proxy/bip.conf example bip.conf] contributed by Kashyap Chamarthy
* ZNC [https://dague.net/2014/09/13/my-irc-proxy-setup/ configuration notes] contributed by Sean Dague
* [https://weechat.org/ WeeChat] IRC client combines proxy and client, and allows you to run the client in a shell and access that client additionally from a web client or Android app.

=== IRC meetings ===

The OpenStack project holds its various public meetings on IRC. See [[Meetings]] for details.

== OpenStack IRC channels (chat.freenode.net) ==

If you want to start a new IRC channel, please consult with the InfrastructureTeam in #openstack-infra or at openstack-infra@lists.openstack.org to ensure it gets registered appropriately.

'''Many IRC channels are logged and [http://eavesdrop.openstack.org/irclogs/ recordings are publicly accessible]'''. If you're concerned about privacy consider using a [https://freenode.net/kb/answer/cloaks cloak], [https://freenode.net/kb/answer/chat tor], hide your real name and be mindful not to write sensitive data in these channels.

{| class="wikitable sortable" border="1"
|-
! IRC Channel !! Description
|-
|'''#openstack''' || general discussion, support
|-
|'''#openstack-ansible''' || [http://docs.openstack.org/developer/openstack-ansible/ OpenStack-Ansible] discussions
|-
|'''#openstack-anvil''' || [http://anvil.readthedocs.org/ Anvil] discussion channel
|-
|'''#openstack-app-catalog''' || [http://apps.openstack.org Community App Catalog] discussions
|-
|'''#openstack-barbican''' || Barbican-related team discussions
|-
|'''#openstack-blazar''' || blazar (formerly climate) team discussions
|-
|'''#openstack-board''' || OpenStack Foundation Board Meeting Back channel (mainly quiet except during meetings)
|-
|'''#openstack-telemetry''' || Telemetry team (ceilometer, aodh, gnocchi) discussions
|-
|'''#openstack-chef''' || deployment and operating OpenStack with Chef
|-
| '''#openstack-chinese''' || general discussion, support in Chinese
|-
| '''#openstack-cinder''' || cinder team discussions
|-
| '''#openstack-community''' || coordination of community activity
|-
| '''#openstack-containers''' || Magnum team discussion
|-
| '''#openstack-cue''' || Cue team discussion
|-
|'''#openstack-defcore''' || Defcore discussion channel
|-
|'''#openstack-dev''' || general and cross-project development discussion
|-
|'''#openstack-dib''' || Discussion around diskimage-builder
|-
|'''#openstack-dns''' || Designate DNS team discussions
|-
|'''#openstack-doc''' || documentation team discussion
|-
|'''#openstack-dragonflow''' || [https://docs.openstack.org/dragonflow/ Dragonflow] team discussion
|-
|'''#openstack-ec2api''' || EC2 API discussion channel
|-
|'''#openstack-fr''' || general discussion, support in French
|-
|'''#openstack-fwaas''' || Firewall as a Service discussions
|-
|'''#openstack-gbp''' || Group Based Policy discussions
|-
|'''#openstack-glance''' || glance team discussions
|-
|'''#openstack-glare''' || glare team discussions
|-
|'''#openstack-freezer''' || freezer team discussions
|-
|'''#openstack-gsoc''' || google summer of code discussions
|-
|'''#openstack-ha''' || High Availability discussions
|-
|'''#openstack-heat-translator''' || Heat-Translator and TOSCA-Parser team discussions
|-
|'''#openstack-horizon''' || horizon team discussions
|-
|'''#openstack-hyper-v''' || Microsoft Windows guests and hypervisor discussion
|-
| '''#openstack-i18n''' || I18N team discussions
|-
|'''#openstack-infra''' || developer community infrastructure, continuous integration testing
|-
|'''#openstack-ironic''' || ironic & bare metal discussions
|-
|'''#openstack-jjb''' || Jenkins Job Builder discussions
|-
|'''#openstack-karbor''' || karbor team discussions
|-
|'''#openstack-keystone''' || keystone team discussions
|-
|'''#openstack-ko''' || general discussion, support in Korean
|-
|'''#openstack-kolla''' || Kolla team discussion channel
|-
|'''#openstack-kuryr''' || Kuryr team discussion channel
|-
|'''#openstack-latinamerica''' || OpenStack Latin America (Spanish)
|-
|'''#openstack-lbaas''' || Neutron LBaaS and Project Octavia discussions
|-
|'''#openstack-manila''' || shared / distributed file system service team discussions
|-
|'''#openstack-marconi''' || queue/messaging marconi team discussions
|-
|'''#openstack-meeting''' || team meetings
|-
|'''#openstack-meeting-alt''' || team meetings, alternate channel
|-
|'''#openstack-meeting-cp''' || cross-project meetings
|-
|'''#openstack-meeting-3''' || team meetings, another alternate channel
|-
|'''#openstack-meeting-4''' || team meetings, another alternate channel
|-
|'''#openstack-mistral''' || Mistral Workflow Service for OpenStack
|-
|'''#openstack-monasca''' || Monasca Monitoring and Logging as-a-Service for OpenStack
|-
|'''#openstack-neutron''' || neutron team discussions
|-
|'''#openstack-nfv''' || [[Teams/NFV|NFV]] team discussions
|-
|'''#openstack-nova''' || nova team discussions
|-
|'''#openstack-operators''' || OpenStack Operators discussion channel
|-
|'''#openstack-opw''' || GNOME OPW mentor, intern and supporter discussions
|-
|'''#openstack-oslo''' || [https://wiki.openstack.org/wiki/Oslo Oslo] development discussion
|-
|'''#openstack-performance''' || All OpenStack performance related discussions
|-
|'''#openstack-pkg''' || Debian packaging discussions
|-
|'''#openstack-pl''' || OpenStack discussions in Polish
|-
|'''#openstack-powervm''' || PowerVM OpenStack drivers discussion channel
|-
| '''#openstack-qa''' || QA team discussion
|-
| '''#openstack-qingling''' || Function as a Service discussion channel
|-
|'''#openstack-rally''' || [https://wiki.openstack.org/wiki/Rally Rally] measure performance of your cloud
|-
|'''#openstack-rating''' || Rating team discussions
|-
|'''#openstack-release''' || Release managers channel
|-
|'''#openstack-requirements''' || Requirements discussion channel
|-
|'''#openstack-rpm-packaging''' || RPM packaging discussions
|-
|'''#openstack-sahara''' || [https://wiki.openstack.org/wiki/Sahara Sahara] team discussions
|-
|'''#openstack-sdks''' || Development of SDKs to work with OpenStack and the unified OpenStack command line tool
|-
|'''#openstack-security''' || General discussion about OpenStack security and open channel for the OpenStack Security Group (OSSG)
|-
|'''#openstack-searchlight''' || [wiki.openstack.org/wiki/Searchlight] - Search your OpenStack resources
|-
|'''#openstack-stable''' || stable branch management discussions
|-
|'''#openstack-state-management''' || [https://wiki.openstack.org/wiki/TaskFlow TaskFlow] and state-management development discussion
|-
|'''#openstack-swift''' || swift team discussions
|-
|'''#openstack-third-party-ci''' || OpenStack third-party CI operators
|-
|'''#openstack-trove''' || trove database team discussions
|-
|'''#openstack-tw''' || general discussion, support in Taiwan
|-
|'''#openstack-upstream-institute''' || OpenStack Upstream Institute team discussions and a forum to discuss questions and best practices about on-boarding new contributors
|-
| '''#openstack-ux''' || discussion channel for user experience
|-
|'''#openstack-vmware''' || The VMwareAPI team discussion channel
|-
|'''#openstack-watcher''' || [https://wiki.openstack.org/wiki/Watcher Watcher] discussion channel
|-
|'''#openstack-zun''' || [https://wiki.openstack.org/wiki/Zun Zun] discussion channel
|-
|'''#airshipit''' || OpenStack [https://www.airshipit.org/ Airship] discussion channel - declarative automated cloud provisioning and management
|-
|'''#congress''' || Congress policy developer discussion channel
|-
|'''#fuel''' || Fuel users&developers discussion channel
|-
|'''#heat''' || Heat developer discussion channel
|-
|'''#magnetodb''' || Key-Value storage for OpenStack
|-
|'''#murano''' || Murano team discussions
|-
|'''#nova-docker''' || Nova Docker team discussions
|-
|'''#refstack''' || RefStack
|-
|'''#senlin''' || [https://wiki.openstack.org/wiki/Senlin Senlin] team discussions
|-
|'''#storyboard''' || StoryBoard team discussions
|-
|'''#tacker''' || [https://wiki.openstack.org/wiki/Tacker Tacker] NFV Orchestrator team discussions
|-
|'''#tripleo''' || TripleO team discussions
|-
|'''#puppet-openstack''' || Openstack Puppet modules discussions
|-}

[[Category:Connect]]

Qinling

2018-07-07T00:57:01Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling could support different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: https://docs.openstack.org/qinling/latest/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://storyboard.openstack.org/#!/project/927
* Bug Track: https://storyboard.openstack.org/#!/project/927
* IRC channel on Freenode: #openstack-qinling

==Videos==
* [https://www.youtube.com/watch?v=K2SiMZllN_A Qinling Demo]，A quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
* [https://www.youtube.com/watch?v=NmCmOfRBlIU Sydney Summit presentation]

First Contact SIG

2018-06-06T22:38:21Z

Lingxian: /* Project Liaisons */

CrossProjectLiaisons

2018-04-20T02:30:49Z

Lingxian: /* Release management */

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

== Oslo ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Bhagyashri Shewale|| bhagyashris
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Petr Kovar || pkovar
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || ||
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, 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 || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

== 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 || Brian Rosmaita || rosmaita
|-
| 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 || ||
|-
| 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 / 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
|-
| 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

CrossProjectLiaisons

2018-03-16T11:42:59Z

Lingxian:

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 || Bhagyashri Shewale|| bhagyashris
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Qinling || Lingxian Kong || kong
|-
| 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 || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ying Zuo || ying_zuo
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| 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 || Abhishek Kekane || abhishekk
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| 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 || Tom Barron || tbarron
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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 || Colleen Murphy || cmurphy
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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 || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || ||
|-
| 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 || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

== 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 || Brian Rosmaita || rosmaita
|-
| 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 || ||
|-
| 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 / 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
|-
| 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 || ||
|-
| 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 || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| 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
|-
| Qinling || Lingxian Kong || kong
|-
| 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 || Maciej Jozefczyk || mjozefcz
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

Qinling

2018-01-15T22:20:22Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling could support different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

==Videos==
* [https://www.youtube.com/watch?v=K2SiMZllN_A Qinling Demo]，A quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
* [https://www.youtube.com/watch?v=NmCmOfRBlIU Sydney Summit presentation]

Qinling

2018-01-15T22:19:45Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling could support different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

Videos:
* [https://www.youtube.com/watch?v=K2SiMZllN_A Qinling Demo]，A quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
* [https://www.youtube.com/watch?v=NmCmOfRBlIU Sydney Summit presentation]

Qinling

2018-01-15T22:19:30Z

Lingxian: Created page with "= Qinling(Function as a Service in OpenStack) = Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like..."

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling could support different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

Videos:
* [https://www.youtube.com/watch?v=K2SiMZllN_A Qinling Demo]
A quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
* [https://www.youtube.com/watch?v=NmCmOfRBlIU Sydney Summit presentation]

Faas

2017-10-15T11:27:04Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling supports different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

Here is a quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
https://www.youtube.com/watch?v=K2SiMZllN_A

Faas

2017-10-15T11:25:44Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling supports different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

Here is a quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
https://www.youtube.com/watch?v=K2SiMZllN_A

Faas

2017-10-15T11:25:08Z

Lingxian: /* Qinling(Function as a Service in OpenStack) */

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling supports different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

Here is a quick demo of how to use Qinling to automatically resize photos uploaded to Swift:
<iframe width="560" height="315" src="https://www.youtube.com/embed/K2SiMZllN_A" frameborder="0" allowfullscreen></iframe>

Faas

2017-09-04T20:11:52Z

= Qinling(Function as a Service in OpenStack) =

Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling supports different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.

* Free software: Apache license
* Documentation: http://qinling.readthedocs.io/
* Source: http://git.openstack.org/cgit/openstack/qinling
* Features: https://blueprints.launchpad.net/qinling
* Bug Track: http://bugs.launchpad.net/qinling
* IRC channel on Freenode: #openstack-qinling

CrossProjectLiaisons

2016-03-26T00:13:07Z

Lingxian: /* Release management */

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

== Oslo ==

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

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

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

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

== Release management ==

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

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

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

== QA ==

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

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

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

== Documentation ==

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

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

== Stable Branch ==

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

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

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

== Vulnerability management ==

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

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

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

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

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

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

|-
| Trove || Nikhil Manchanda || SlickNik

|-
| Sahara || Sergey Lukjanov || SergeyLukjanov

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

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

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

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

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

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

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Glance || ||
|-
| Keystone || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Cinder || ||
|-
| Swift || ||
|-
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki
|-
| Telemetry || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Heat || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Sahara || Chad Roberts || crobertsrh
|-
|}

== Inter-project Liaisons ==

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

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

=== 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|| Adam Gandelman || adam_g
|-
| Barbican || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Tim Hinrichs || thinrichs
|-
| Designate || Graham hayes || mugsie
|-
| Glance || Nikhil Komawar || nikhil
|-
| Heat || Rico Lin || ricolin
|-
| Horizon || Tyr Johanson || tyr
|-
| Infrastructure || Matthew Wagoner || olaph
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Magnum || Adrian Otto || adria̠n_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Serg Melikyan || smelikyan
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Chris Dent || cdent
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Michael McCune or Sergey Lukjanov || elmiko or SergeyLukjanov
|-
| Searchlight || Travis Tripp || TravT
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || John Dickinson || notmyname
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|}

CrossProjectLiaisons

2016-01-09T07:57:13Z

Lingxian: /* Release management */

CrossProjectLiaisons

2015-10-22T09:17:02Z

Lingxian: /* Release management */

Stackforge Namespace Retirement

2015-08-28T02:29:24Z

Lingxian: /* Active Projects to Move */

=== Background ===

The stackforge/ git namespace is being retired, and active projects are being moved to the openstack/ namespace. See this mailing list post for [http://lists.openstack.org/pipermail/openstack-dev/2015-August/071816.html full background]. These changes are scheduled to occur on October 17, 2015.

There are two lists below, one for active projects that should be moved, and a second for inactive projects that should become read-only. Please update them to add your project to the correct list.

=== Active Projects to Move ===
Active stackforge projects that wish to move into the openstack/ namespace should be added to this list. Projects in this list will be automatically moved by the Infrastructure team to openstack/ on October 17. Please note that no other renames can happen during this move -- projects will strictly be moved from stackforge/ to openstack/ with their existing names.

* aeromancer
* cloud-init
* python-openstacksdk
* networking-hyperv
* networking-zvm
* compute-hyperv
* nova-zvm-virt-driver
* telcowg-usecases
* anvil
* doc8
* vmtp
* wsme
* tacker
* tacker-specs
* tacker-horizon
* python-tackerclient
* third-party-ci-tools
* terracotta

=== Inactive Projects to Retire ===
Inactive projects that should be retired should be added to this list. These projects will have a commit merged removing their content and replacing it with a message indicating the project is no longer maintained and will become read-only in Gerrit.

* MRaaS
* openstackdroid

Mistral/Team

2015-07-09T11:42:38Z

Lingxian: /* Mistral Team */

== Mistral Team ==

=== Renat Akhmerov===

'''IRC: rakhmerov'''

Senior Software Engineer at Mirantis. His primary expertise is distributed computing and HPC, Concurrent Programming, Java, Spring and In-Memory Data Grids (GridGain, GemFire, Coherence) as well as significant experience in framework development. Since the very beginning of the project he’s been actively contributing in both architecture design and implementation. He’s also been working as a community lead and presenting the project publicly.

=== Nikolay Makhotkin ===

'''IRC: nmakhotkin'''

Software Engineer at Mirantis. He has expertise in Hadoop and its components: MapReduce, Oozie, Hive and also in Java and building web-applications. He has worked on Mistral since its inception and implemented a lot of essential parts of Mistral.

=== Dmitri Zimine ===

'''IRC: dzimine'''

Dmitri is a Chief Stormer at StackStorm, responsible for building operation automation. He has over a decade of experience in cloud management and datacenter automation, including VMware vSphere and Opalis Integration Server (now Microsoft System Center Orchestrator). Dmitri contributes his vision and experience in workflow and run-book automation to drive the project.

=== Anastasia Kuznetsova ===

'''IRC: akuznetsova'''

Quality Assurance Engineer at Mirantis. Anastasia is now fully responsible for QA activities on Mistral including integration and pre-release testing.

=== Timur Nurlygayanov ===

'''IRC: tnurlygayanov'''

Senior Quality Assurance Engineer at Mirantis. Timur made major contribution to automated tests for Mistral.

=== Winson Chan ===

'''IRC: m4dcoder'''

Solution Architect at StackStorm. He has experience developing, deploying, and operating distributed automation and management solutions for enterprise scale private clouds. He has studied and worked with OpenStack since Essex and has development experience with Heat and contributed to a number of bugs and blueprints.

=== Lingxian Kong===

'''IRC: xylan_kong'''

Senior Software Engineer at Huawei, leader of Huawei OpenStack community dev team. He was the earliest/first OpenStack community contributor in Huawei from Folsom release, who has in-depth knowledge (architecture&implementation) of OpenStack core projects, including Nova, Cinder, Neutron, Heat, Ceilometer, etc.

Meetings/MistralAgenda

2015-06-29T12:40:28Z

Lingxian: /* Agenda */

We have IRC meetings on #openstack-meeting weekly on Mondays at 16:00 UTC.

== Next meetings ==

June 29

== Agenda ==

* Review action items
* Current status (progress, issues, roadblocks, further plans)
* Duplicating messages on executors
* Liberty-2 planning
* Open discussion

+ remove utils.wf_trace module, make use of the capability provided by oslo.log, http://rst.ninjs.org/?n=8103f392cf12595a549ac8c3329a331a&theme=nature

== Checklist for the meeting organizer ==

* Publish the agenda 24h in advance.
* Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action.
* Use http://meetbot.debian.net/Manual.html to get an automatic summary.
* Prepare an outline for the meeting to speed things up.
* Record decisions and commitments; review in the next meeting.

== Previous meetings ==
http://eavesdrop.openstack.org/meetings/mistral/

PRC Kilo Hackaton

2015-06-24T06:36:04Z

Lingxian:

Huawei and Intel successfully launched 1st PRC OpenStack Hackathon at April. During the 1st hackathon, there are 16 OpenStackers from Huawei, Intel and AWCloud, totally fixed 29 bugs. This hackathon also get media's eye ball to report China technical contribution to OpenStack community. Huawei and Intel show the commitment of OpenStack Stability to enterprise customer.

Now Huawei and Intel will be pleased to host 2nd PRC OpenStack hackathon !
Come to join other OpenStackers to make Liberty a grand success!
Come to build your personal network. Learn tips and tricks and gain a better understanding by working closely with others.
Cores and PTLs will be on standby to review patches and vote for merges.

= Liberty Bug Fix Fest =

* Focus: Nova Neutron Heat Horizon Ceilometer
* Location: Xi'An, Close to HuaWei Office (Final venue will update later)
* Dates: August 26-28, 2015
* Hosts: Huawei and Intel
* Capacity: 20-50

SIGN UP on the [https://etherpad.openstack.org/p/2015_8_Prc_Hackthon]!

== Directions == 


Nova, Neutron, Horizon, Ceilometer, Heat, etc. projects in OpenStack

== Agenda ==

* Day1

** 9:00~9:15 Kick-off and Announce the game rule (Game Rule: Standup Style / Bug Fix Wall Paper)

** 9:15~9:30 Self-Introduction

** 9:30~11:50 Bug Fix

** 11:50~12:00 Exciting Moment : Summary the achievement

** 12:00~13:00 Lunch

** 13:00~16:50 Bug Fix

** 16:50~17:00 Exciting Moment : Summary the achievement

** 17:00~18:00 Networking

* Day 2

** 9:00~11:50 Bug Fix

** 11:50~12:00 Exciting Moment : Summary the achievement

** 12:00~13:00 Lunch

** 13:00~16:50 Bug Fix

** 16:50~17:00 Exciting Moment : Summary the achievement

** 17:00~20:00 Hackathon Night (Happy Hour, Hack Award )

* Day 3

** 9:00~11:50 Bug Fix

** 11:50~12:00 Exciting Moment : Summary the achievement and kick off 3rd PRC Hackathon

** 12:00~13:00 Lunch

** 13:00~18:00 OpenStackers Team Building (outing at some top attractions)

== Local Attractions ==

- http://www.chinatourguide.com/xian/

- http://www.chinahighlights.com/xian/tours.htm

More can be found at Google.com: https://www.google.de/?gfe_rd=cr&ei=m0keVZyEGIGh8weJuIDwCg&gws_rd=ssl#q=xi'an+attractions

== Meals plans ==

Lunch will be provided

Dinner: Participants to pay for own dinner for the 1st day. Dining venue suggestions will be provided.

Add your name to the [https://etherpad.openstack.org/p/2015_8_Prc_Hackthon]!

== Team Building Event ==

On August 27 we're planning a success/celebration event. Sign-up adding your name to the [https://etherpad.openstack.org/p/2015_8_Prc_Hackthon]!
On August 28 we're planning a outing. Sign-up adding your name to the [https://etherpad.openstack.org/p/2015_8_Prc_Hackthon]!

= Resources for developers =

List of Release Candidate bugs are most likely to appear on liberty

pages: https://launchpad.net/nova/liberty

- Etc

ReleaseNotes/Juno

2014-10-16T11:45:38Z

Lingxian: Fix a typo

{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0; background-color:#FFFFFF;font-size:95%; vertical-align:middle;"
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]
| '''Release Under Development'''
This release of OpenStack is under development and has yet to be completed.

The information on this page may not accurately reflect the state of release at the current point in time.
|}

= OpenStack 2014.2 (Juno) Release Notes =

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

== General Upgrade Notes ==

* The simplejson package is an optional requirement in most projects, therefore it's not listed in all project's requirements.txt file. However, if you're using it, e.g. better performance with python 2.6 on RHEL 6, then you will need simplejson >= 2.2.0. See https://bugs.launchpad.net/oslo-incubator/+bug/1361230 for details.

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

The Juno integrated release includes three releases of OpenStack Swift: 2.0.0, 2.1.0, and 2.2.0. The changelog for these releases is available at https://github.com/openstack/swift/blob/2.2.0.rc1/CHANGELOG#L1-L173. Please refer to that document for release details.

Important new features are highlighted below. Please read the CHANGELOG and associated documentation.

* Storage policies
* Keystone v3 support
* Server-side account-to-account copy
* Better partition placement when adding a new server, zone, or region.
* Zero-copy GET responses using splice()
* Parallel object auditor

=== Known Issues ===

* None at this time

=== Upgrade Notes ===

As always, you can upgrade your Swift cluster with no downtime for end-users. Please refer to sample config files and documentation before every release.

* There have been some logging changes that need to be called out. In all cases, well-behaved log processors will not be affected.
** Storage node (account, container, object) logs now have the PID logged at the end of the log line.
** Object daemons now send a user-agent string with their full name (e.g. "obj" is now "object").
* Once an additional storage policy has been enabled, downgrading to Swift pre-2.0.0 will cause any additional storage policies to become unavailable.
* As part of an effort to eventually update the default port to swift to an non-IANA-assigned range, bind_port is now a required setting. Anyone currently explicitly setting the ports will not be affected. However, if you do not currently set the ports, please ensure that your *_server.conf has bind_port set to match your ring as part of your upgrade.
* Note that storage policies include a new daemon, the container-reconciler.
* TempURL default allowed methods config setting now also allows POST and DELETE. This means tempurls can be created for these verbs. It does not affect any existing tempurls.
* A list of all updated, deprecated or removed options in swift can be found at: http://docs.openstack.org/trunk/config-reference/content/swift-conf-changes-master.html

== OpenStack Compute (Nova) ==

===Instance features===

* Allow users to specify an image to use for rescue instead of the original base image. [https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/allow-image-to-be-specified-during-rescue specification]
* Allow images to specify if a config drive should be used. [https://blueprints.launchpad.net/nova/+spec/config-drive-image-property launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/config-drive-image-property specification]
* Give users and administrators the ability to control the vCPU topology exposed to guests via flavors. [https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-vcpu-topology specification]
* Attach All Local Disks During Rescue. [https://blueprints.launchpad.net/nova/+spec/rescue-attach-all-disks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rescue-attach-all-disks specification]

===Networking===

* Improve the nova-network code to allow per-network settings. [https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/better-support-for-multiple-networks specification]
* Allow deployers to add hooks which are informed as soon as networking information for an instance is changed. [https://blueprints.launchpad.net/nova/+spec/instance-network-info-hook launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/instance-network-info-hook specification]
* Enable nova instances to be booted up with SR-IOV neutron ports. [https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/pci-passthrough-sriov specification]
* Permit VMs to attach multiple interfaces to one network. [https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/nfv-multiple-if-1-net specification]

===Scheduling===

* Extensible Resource Tracking. The set of resources tracked by nova is hard coded, this change makes that extensible, which will allow plug-ins to track new types of resources for scheduling. [https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/extensible-resource-tracking specification]
* Allow a host to be evacuated, but with the scheduler selecting destination hosts for the instances moved. [https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/find-host-and-evacuate-instance specification]
* Add support for host aggregates to scheduler filters. launchpad: [https://blueprints.launchpad.net/nova/+spec/per-aggregate-disk-allocation-ratio disk]; [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-instances-per-host instances]; and [https://blueprints.launchpad.net/nova/+spec/per-aggregate-max-io-ops-per-host IO ops] [http://specs.openstack.org/openstack/nova-specs/specs/juno/per-aggregate-filters specification]

===Other===

* i18n Enablement for Nova, turn on the lazy translation support from Oslo i18n and updating Nova to adhere to the restrictions this adds to translatable strings. [https://blueprints.launchpad.net/nova/+spec/i18n-enablement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/i18n-enablement specification]
* Offload periodic task sql query load to a slave sql server if one is configured. [https://blueprints.launchpad.net/nova/+spec/juno-slaveification launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/juno-slaveification specification]
* Only update the status of a host in the sql database when the status changes, instead of every 60 seconds. [https://blueprints.launchpad.net/nova/+spec/on-demand-compute-update launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/on-demand-compute-update specification]
* Include status information in API listings of hypervisor hosts. [https://blueprints.launchpad.net/nova/+spec/return-status-for-hypervisor-node launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/return-status-for-hypervisor-node specification]
* Allow API callers to specify more than one status to filter by when listing services. [https://blueprints.launchpad.net/nova/+spec/servers-list-support-multi-status launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/servers-list-support-multi-status specification]
* Add quota values to constrain the number and size of server groups a users can create. [https://blueprints.launchpad.net/nova/+spec/server-group-quotas launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/server-group-quotas specification]

===Hypervisor driver specific===

====Hyper-V====

* Support for differencing vhdx images. [https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-differencing-vhdx-resize-support specification]
* Support for console serial logs. [https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-console-log specification]
* Support soft reboot. [https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/hyper-v-soft-reboot specification]

====Ironic====

* Add a virt driver for Ironic. [https://blueprints.launchpad.net/nova/+spec/add-ironic-driver launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/add-ironic-driver specification]

====libvirt====

* Performance improvements to listing instances on modern libvirts. [https://blueprints.launchpad.net/nova/+spec/libvirt-domain-listing-speedup launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-domain-listing-speedup specification]
* Allow snapshots of network backed disks. [https://blueprints.launchpad.net/nova/+spec/libvirt-volume-snap-network-disk launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-volume-snap-network-disk specification]
* Enable qemu memory balloon statistics for ceilometer reporting. [https://blueprints.launchpad.net/nova/+spec/enabled-qemu-memballoon-stats launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/enabled-qemu-memballoon-stats specification]
* Add support for handing back unused disk blocks to the underlying storage system. [https://blueprints.launchpad.net/nova/+spec/libvirt-disk-discard-option launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-disk-discard-option specification]
* Meta-data about an instance is now recorded in the libvirt domain XML. This is intended to help administrators while debugging problems. [https://blueprints.launchpad.net/nova/+spec/libvirt-driver-domain-metadata launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-driver-domain-metadata specification]
* Support namespaces for LXC containers. [https://blueprints.launchpad.net/nova/+spec/libvirt-lxc-user-namespaces launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/libvirt-lxc-user-namespaces specification]
* Copy-on-write cloning for RBD-backed disks. [https://blueprints.launchpad.net/nova/+spec/rbd-clone-image-handler launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/rbd-clone-image-handler specification]
* Expose interactive serial consoles. [https://blueprints.launchpad.net/nova/+spec/serial-ports launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/serial-ports specification]
* Allow controlled shutdown of guest operating systems during VM power off. [https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/user-defined-shutdown specification]
* Intelligent NUMA node placement for guests. [https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/virt-driver-numa-placement specification]

====vmware====

* Move the vmware driver to using the oslo vmware helper library. [https://blueprints.launchpad.net/nova/+spec/use-oslo-vmware launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/use-oslo-vmware specification]
* Add support for network interface hot plugging to vmware. [https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-hot-plug specification]
* Refactor the vmware driver's spawn functionality to be more maintainable. This work was internal, but is mentioned here because it significantly improves the supportability of the VMWare driver. [https://blueprints.launchpad.net/nova/+spec/vmware-spawn-refactor launchpad] [http://specs.openstack.org/openstack/nova-specs/specs/juno/vmware-spawn-refactor specification]

=== Known Issues ===

* None at this time

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Nova can be found at: http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html
* The nova-manage flavor subcommand is deprecated in Juno and will be removed in the 2015.1 (K) release: https://review.openstack.org/#/c/86122/
* https://review.openstack.org/#/c/102212/
* Minimum required libvirt version is now 0.9.11: https://review.openstack.org/#/c/58494/
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.
* Debug log output in python-novaclient has [https://review.openstack.org/#/c/98443/ changed slightly] to improve readability. The sha1 hash of the keystone token is now printed instead of the token itself - greatly shortening the amount of content being printed while still retaining the ability to determine token mismatch scenarios. In addition, some extra '\n' characters that were being added are removed. ''Double-check any log parsers!''
* libvirt.volume_drivers config param for nova.conf is deprecated, to be removed in the Lxxxx release. In general, this should affect only a small number of developers working on drivers. If this is you, the recommended approach is to continue your work inside a nova tree.

== OpenStack Image Service (Glance) ==
=== Key New Features ===
* Asynchronous Processing
* Pull of glance.store into its own library
* [http://docs.openstack.org/developer/glance/metadefs-concepts.html Metadata Definitions Catalog]
* Restricted policy for downloading images.
* Enhanced Scrubber service allows single instance services multiple glance-api servers cross nodes.

=== Known Issues ===

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Glance can be found at: http://docs.openstack.org/trunk/config-reference/content/glance-conf-changes-master.html
* The ability to upload a public image is now admin-only by default. To continue to use the previous behaviour, edit the publicize_image flag in etc/policy.json to remove the role restriction.
* The requirement and check on UTF-8 charset for DB tables is enforced, operator need to migration tables and existing data to UTF-8 manually if glance-manage complains it during the sync.

== OpenStack Dashboard (Horizon) ==

=== Key New Features ===

==== Sahara ====
The OpenStack Data Processing project (Sahara) was formally included into the integrated release in Juno and Horizon includes broad support for managing your data processing. You can specify and build clusters to utilize several data types with user specified jobs while tracking the progress of those jobs.

==== Neutron Features ====
Neutron added several new features in Juno, including:
* DVR (Distributed Virtual Routing)
* L3 HA support
* IPv6 subnet modes

Horizon provides support for these new features with the Juno release. These features provide much greater flexibility in specifying software defined networks.

An existing feature in Neutron that Horizon now supports is the MAC learning extension.

==== Glance Features ====
In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

==== Cinder Features ====
In a continued effort to provide fuller API support, several features supported by Cinder are now supported in Horizon in the Juno release. Users can now utilize swift to store volume backups from Horizon as well as restore volumes from these backups.

Other features of the Cinder API not previously supported by Horizon added in Juno include:
* Enabling resetting the state of a snapshot
* Enabling resetting the state of a volume
* Supporting upload-to-image
* Volume retype
* QoS (quality of service) support

==== Trove ====
Trove supports potentially using numerous different datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

Another addition is support for utilizing and restoring from incremental database backups.

To improve support for Neutron based clouds, when creating a database instance, the user can now specify the NIC for the database instance on creation allowing direct access to the instance by the user.

==== Nova ====
The new nova instance actions panel provides a list of all actions taken on all instances in the current project allowing users to view resulting errors or actions taken by other users on those instances.

Administrators now have the ability to evacuate hosts off hypervisors which can aid in system maintenance by providing a mechanism to migrate all instances to other hosts.

==== Improved Plugin Support ====
The plugin system in Horizon continued to improve in the Juno release.
Some of those improvements:
* Support for adding plugin specific AngularJS modules
* Support for adding static files, e.g., CSS, JS, images
* Ability to add exceptions
* Fixing ordering issues
* Numerous other bug fixes

==== Enhanced RBAC support ====
In an ongoing effort to support richer role based access control (RBAC) in Horizon, the views for several more services were enhanced with RBAC checks to determine user access to actions. The newly supported services are compute, network and orchestration. These changes allow operators to implement finer grained access control than just "member" and "admin".

The identity panels (domains, projects, users, roles, groups) have also been converted to support RBAC at the view level. The identity panels have been moved from the admin dashboard into their own 'Identity' dashboard and accessibility is determined by policies alone. This is the first step toward consolidating the near duplicate content of the project and admin dashboards into single views supporting a wide range of roles.

==== UX Changes ====
In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Havana release.

==== JavaScript Libraries Extracted ====
As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.

==== Conversion from LESS to SCSS ====
The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.

=== Known Issues ===

==== Rendering issues in extensions ====
The conversion to utilizing Bootstrap v3 can cause content extensions written on top of Horizon to have rendering issues. Most of these are fixed by a simple CSS class name substitutions. These issues are primarily seen with buttons and panel content widths.

==== Online Compression ====
With the move to SCSS, there may be issues with utilizing online compression in non-DEBUG mode in Horizon. Offline compression continues to work as in previous releases.

==== Neutron L3 HA ====
The HA property is updateable in the UI, however, the migration itself fails on the agent.

=== Upgrade Notes ===
* FLAVOR_EXTRA_KEYS setting deprecated. The use of this key has been replaced with direct calls to the nova and [http://docs.openstack.org/developer/glance/metadefs-concepts.html glance api] as appropriate.

== OpenStack Identity (Keystone) ==

=== Key New Features ===

* Keystone now has experimental support for [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone federation], where one instance acts as an Identity Provider, and the other a Service Provider.
* PKIZ is a new token provider available for users of PKI tokens, which simply adds zlib-based compression to traditional PKI tokens.
* The hashing algorithm used for PKI tokens has been made configurable (the default is still MD5, but the Keystone team recommends that deployments migrate to SHA256).
* Identity-driver-configuration-per-domain now supports Internet domain names of arbitrary hierarchical complexity (for example, <code>customer.cloud.example.com</code>).
* The LDAP identity backend now supports <code>description</code> as an attribute of users.
* Identity API v3 requests are now validated via JSON Schema.
* In the case of multiple identity backends, Keystone can now map arbitrary resource IDs to arbitrary backends.
* <code>keystoneclient.middleware.auth_token</code> has been moved into it's own repository, <code>keystonemiddleware.auth_token</code>.
* Identity API v3 now supports a discrete call to retrieve a service catalog, <code>GET /v3/auth/catalog</code>.
* Federated authentication events and local role assignment operations now result in CADF (audit) notifications.
* Keystone can now associate a given policy blob with one or more endpoints.
* Keystone now provides JSON Home documents on the root API endpoints in response to <code>Accept: application/json-home</code> headers.
* Hiding endpoints from client's service catalogs is now more easily manageable via <code>OS-EP-FILTER</code>.
* The credentials collection API is now filterable per associated user (<code>GET /v3/credentials?user_id={user_id}</code>).
* New, generic API endpoints are available for retrieving authentication-related data, such as a service catalog, available project scopes, and available domain scopes.
* Keystone now supports mapping the user <code>enabled</code> attribute to the <code>lock</code> attribute in LDAP (and inverting the corresponding boolean value accordingly).
* A CA certificate file is now configurable for LDAPS connections.
* The templated catalog backend now supports generating service catalogs for Identity API v3.
* Service names were added to the v3 service catalog.
* Services can now be filtered by name (<code> GET /v3/services?name={service_name}</code>).

=== Known Issues ===
==== LDAP paged search results don't work with python-ldap 2.4 ====
When using an LDAP backend with paged search results enabled, AttributeErrors will be encountered if python-ldap 2.4 is being used. This is due to a backwards incompatible API change in python-ldap. The issue can be worked around in a few ways:
* Disabling paging of search results by setting ''page_size'' to ''0'' in the ''[ldap]'' section of keystone.conf.
* Downgrade python-ldap to version 2.3.x.

A fix for this issue has been proposed, which is expected to be made available in a stable update for Juno. For more details see https://bugs.launchpad.net/keystone/+bug/1381768

=== Upgrade Notes ===

* Due to the simpler out-of-the-box experience, the default token provider is now UUID instead of PKI.
* Database migrations for releases prior to Havana have been dropped, meaning that you must upgrade to the Juno release from either a Havana or Icehouse deployment.
* A comprehensive list of all updated, deprecated or removed options in Keystone can be found at: http://docs.openstack.org/trunk/config-reference/content/keystone-conf-changes-master.html
** All <code>token_api</code> methods are now deprecated.
** LDAP configuration options that previously contained the deprecated <code>tenant</code> terminology have been superseded by options using the term <code>project</code>.
** Proxy methods from the identity backend to the assignment backend (created to provide backwards compatibility as a result of the split of the Assignment backend from the Identity backend), have been removed. This should only affect custom, out-of-tree API extensions.
** Loading authentication plugins solely by class name in <code>keystone.conf</code> is now deprecated in favor of loading them by <code>custom-method-name = custom_package.CustomClass</code> pairs, and then defining the sequence of authentication methods as a list (<code>methods = custom-method-name, password</code>).
** In-tree token drivers (<code>keystone.token.backends</code>) have been moved to <code>keystone.token.persistence.backends</code>. Proxy objects exist to maintain compatibility. If a non-default value is used, it is recommended the value of the <code>driver</code> option in the <code>[token]</code> section of <code>keystone.conf</code> is updated to use the new location.
* All KVS backends besides the <code>token</code> driver have been formally deprecated.
* LDAP/AD configuration: All configuration options containing the term "tenant" have been deprecated in favor of similarly named configuration options using the term "project" (for example, <code>tenant_id_attribute</code> has been replaced by <code>project_id_attribute</code>).

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DB migration refactor and new timeline
* Distributed Virtual Router Support (DVR)
* Full IPV6 support for tenant networks
* High Availability for the L3 Agent
* ipset support for security groups in place of iptables (this option is configurable)
* L3 agent performance improvements
* Migration to oslo.messaging library for RPC communication.
* Security group rules for devices RPC call refactoring (a huge performance improvement)
* New Plugins supported in Juno include the following:
** A10 Networks LBaaS driver for the LBaaS V1 API
** Arista L3 routing plugin
** Big Switch L3 routing plugin
** Brocade L3 routing plugin
** Cisco APIC ML2 Driver (including a L3 routing plugin).
** Cisco CSR L3 routing plugin
** Freescale SDN ML2 Mechanism Driver
** Nuage Networks ML2 Mechanism Driver
** SR-IOV capable NIC ML2 Mechanism Driver

=== Known Issues ===
* This is the first release for DVR and HA L3. The Neutron team desires to designate these features as production ready in Kilo and requests that deployers test on non-critical workloads and report any issues.
* FWaaS is still labeled as experimental, as it does not allow you to have more than one FW per tenant.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in neutron can be found at: http://docs.openstack.org/trunk/config-reference/content/neutron-conf-changes-master.html
* Attribute level policies dependent on resources are not enforced anymore. Meaning that some older policies from Icehouse are not needed. (e.g. "get_port:binding:vnic_type": "rule:admin_or_owner").
* The following plugins are deprecated in Juno:
** Cisco Nexus Sub-Plugin (The Nexus 1000V Sub-Plugin is still retained and supported in Juno).
** Mellanox Plugin
** Ryu Plugin
*XML support in the API is deprecated. Users and deployers should migrate to JSON for API interactions as soon as possible since the XML support will be removed in the Kilo (2015.1) release.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* Support for Volume Replication.
* Support for Consistency Groups and Snapshots of Consistency Groups.
* Support for Volume Pools.
* Completion of i18n-enablement
* Honor Glance protected properties in Image Upload
* Enable ability to restrict bandwidth usage on volume-copy operations
* Add Volume Num Weigher Scheduling

=== New Drivers/Plugins ===
* Datera
* Fujitsu Eternus
* Fusion IO
* Hitachi HBSD
* Huawei
* Nimble
* Prophetstor
* Pure
* XtremIO
* Oracle ZFS

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in Cinder can be found at: http://docs.openstack.org/trunk/config-reference/content/cinder-conf-changes-master.html
* Nova is now supporting the [https://review.openstack.org/#/c/43986/ Cinder V2 API]. The Cinder V1 API is deprecated in Juno and Nova will switch over to Cinder V2 by default in the "L" release.

== OpenStack Telemetry (Ceilometer) ==
=== Key New Features ===
* Support for partitioning metric collection load across horizontally scaled-out central agents
* New method of partitioning alarm evaluation load using [https://github.com/stackforge/tooz tooz] coordination, as opposed to a hand-crafted protocol
* Much improved SQLAlchemy storage performance & scalability, so that MySQL or PostgreSQL can be used as the metering store for PoCs or small deployments
* Support for hardware-oriented monitoring of IPMI sensors via notifications from either Ironic or a new standalone agent
* More flexible & efficient SNMP monitoring:
** batching queries for multiple SNMP metrics into a single call to each daemon
** dynamic discovery of nodes deployed by TripleO for SNMP polling
** the ability to more easily extend the range of SNMP metrics that ceilometer gathers
** the ability to derive new metrics from arithmetic transformations applied to multiple primary metrics
* Metering of Neutron networking services: LBaaS, FWaaS & VPNaaS
* New XenAPI compute inspector
* Support for persisting events via the MongoDB & Hbase storage drivers (previously limited to SQLAlchemy)
* Support for per-device metering of instance disks
* Use of ceilometer as a collector for os-profiler data
* New Telemetry section of the [http://docs.openstack.org/admin-guide-cloud/content/ch_admin-openstack-telemetry.html Cloud Administrator Guide]

=== Known Issues ===
* [https://bugs.launchpad.net/ceilometer/+bug/1381600 1381600] The new <code>ceilometer-agent-ipmi</code> fails to emit any samples when it encounters unparseable data from <code>ipmitool</code>.

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in ceilometer can be found at: http://docs.openstack.org/trunk/config-reference/content/ceilometer-conf-changes-master.html

== OpenStack Orchestration (Heat) ==
=== Key New Features ===

* Recovery from failures during stack updates
* API to cancel and roll back an in-progress stack update
* Implementation of new resource types:
** OS::Glance::Image
** OS::Heat::SwiftSignal
*** Provides the option to store Wait Condition (and Software Deployment) data in Swift
** OS::Heat::StructuredDeployments
*** Groups code for multiple lifecycle events into a single deployment resource
** OS::Heat::SoftwareDeployments
*** Provides a way of avoiding circular dependencies when deploying an interdependent cluster of servers
** OS::Heat::SoftwareComponent
** OS::Nova::ServerGroup
** OS::Sahara::NodeGroupTemplate
** OS::Sahara::ClusterTemplate
* Remember the previously-supplied parameters when updating a stack
* Improved scalability
* Improved visibility into trees of nested stacks

=== Known Issues ===
None yet

=== Upgrade Notes ===
* A list of all updated, deprecated or removed options in heat can be found at: http://docs.openstack.org/trunk/config-reference/content/heat-conf-changes-master.html

== OpenStack Database service (Trove) ==
=== Key New Features ===
* Support for Asynchronous Replication (master-slave replicas) between provisioned mysql instances.
* Introduction of a new Clustering API with initial support for MongoDB clusters.
* Support for deploying Trove on an OpenStack solution that is using Neutron for networking. Prior to this, only nova-network was supported.
* Support for provisioning PostgreSQL datastore instances.
* Backup and Restore support for Couchbase.
* Support to optionally restrict the Cinder backend used for Trove volumes.
* Support for defining custom datastore configuration parameters in the Trove database (using mgmt API).
* The ability to list all datastore types and versions in a single call

=== Other Incremental Improvements===
* Logging audit to improve log levels throughout the trove components.
* The extensions loading mechanism was improved by adding support for stevedore.
* The ability to support volumes for data is now on a per datastore bases.
* Created and updated timestamps and instance count were added to configuration groups list and details calls.

=== Known Issues ===
* [https://bugs.launchpad.net/trove/+bug/1333852 1333852]: Trove does not support flavor UUIDs -- the Trove flavors API requires flavors with a numerical ID in order to be consistent with the API response for icehouse Trove.

=== Upgrade Notes ===
None yet

== OpenStack Data Processing (Sahara) ==
=== New Key Features ===

* Data processing UI was fully merged into OpenStack Dashboard (horizon).
* Support of CDH 5.x was added.
* Support of Apache Spark was added. Supported versions are 0.9.1 and 1.0.0. Elastic data processing (EDP) engine was refactored a lot to support non-Oozie workflow engines.
* Support of Apache Hadoop 2.4.1 was added in addition to existing 1.2.1 and 2.3.0. Version 2.3.0 is deprecated in Juno.
* Support of multi region deployments.
* Hadoop Swift authentication using [http://docs.openstack.org/developer/sahara/userdoc/advanced.configuration.guide.html#domain-usage-for-swift-proxy-users keystone trust mechanism]. Now Hadoop can access data in Swift without storing credentials in config files.
* [http://docs.openstack.org/developer/sahara/userdoc/configuration.guide.html#sahara-notifications-configuration Ceilometer integration] was added. Now Sahara notifies Ceilometer about all cluster state changes.
* Cluster provisioning error handling was improved. If something goes wrong during scaling, cluster will rollback to original state.
* Added ability to [http://docs.openstack.org/developer/sahara/userdoc/features.html#security-group-management specify security groups for a node group]. Also Sahara could automatically create security group with only required ports open.
* Implemented [http://docs.openstack.org/developer/sahara/userdoc/features.html#running-sahara-in-distributed-mode distributed mode] for Sahara: sahara-all process is decoupled into sahara-api and sahara-engine. You can run several instances of sahara-api and sahara-engine on different hosts. Note that the feature implementation is considered to be in alpha-state.

=== Known Issues ===

* [https://bugs.launchpad.net/sahara/+bug/1271349 Bug 1271349]: Sahara requires root privileges to access VMs via namespaces.

=== Upgrade Notes ===

==== Main binary renamed to sahara-all ====

Please, note that you should use `sahara-all` instead of `sahara-api` to start
the All-In-One Sahara.

==== sahara.conf upgrade ====

We've migrated from custom auth_token middleware config options to the common
config options. To update your config file you should replace the following
old config opts with the new ones.

* "os_auth_protocol", "os_auth_host", "os_auth_port" -> "[keystone_authtoken]/auth_uri" and "[keystone_authtoken]/identity_uri"
* "os_admin_username" -> "[keystone_authtoken]/admin_user"
* "os_admin_password" -> "[keystone_authtoken]/admin_password"
* "os_admin_tenant_name" -> "[keystone_authtoken]/admin_tenant_name"

We've replaced oslo code from sahara.openstack.common.db by usage of oslo.db library.

Also sqlite database is not supported anymore. Please use MySQL or PostgreSQL
db backends for Sahara. Sqlite support was dropped because it doesn't support
(and not going to support, see http://www.sqlite.org/omitted.html) ALTER
COLUMN and DROP COLUMN commands required for DB migrations between versions.

You can find more info about config file options in Sahara repository in file
"etc/sahara/sahara.conf.sample".

==== Sahara Dashboard was merged into OpenStack Dashboard ====

The Sahara Dashboard is not available in Juno release. Instead it's
functionality is provided by OpenStack Dashboard out of the box.
The Sahara UI is available in OpenStack Dashboard in
"Project" -> "Data Processing" tab.

Note that you have to properly register Sahara in Keystone in
order for Sahara UI in the Dashboard to work.

==== VM user name changed for HEAT infrastructure engine ====

We've updated HEAT infrastructure engine ("infrastructure_engine=heat") to
use the same rules for instance user name as in direct engine. Before the
change user name for VMs created by Sahara using HEAT engine was always
'ec2-user'. Now user name is taken from the image registry as it is described
in the documentation.

Note, this change breaks Sahara backward compatibility for clusters created
using HEAT infrastructure engine before the change. Clusters will continue to
operate, but it is not recommended to perform scale operation over them.

==== Anti affinity implementation changed ====

Starting with Juno release anti affinity feature is implemented using server
groups. There should not be much difference in Sahara behavior from user
perspective, but there are internal changes:

* Server group object will be created if anti affinity feature is enabled.
* New implementation doesn't allow several affected instances on the same host even if they don't have common processes. So, if anti affinity enabled for 'datanode' and 'tasktracker' processes, previous implementation allowed to have instance with 'datanode' process and other instance with 'tasktracker' process on one host. New implementation guarantees that instances will be on different hosts.

Note, new implementation will be applied for new clusters only. Old implementation will be applied if user scales cluster created in Icehouse.

== OpenStack Documentation ==

* This release, the OpenStack Foundation funded a five-day book sprint to write the new [http://docs.openstack.org/arch-design/content/arch-guide-how-this-book-is-organized.html OpenStack Architecture Design Guide]. It offers architectures for general purpose, compute-focused, storage-focused, network-focused, multi-site, hybrid, massively scalable, and specialized clouds.
* The Install Guides have had a lot of clean up and standardization: uses common message queue (RabbitMQ), replaces openstack-config (crudini) commands with config file editing for improved learning opportunities and consistency, references a generic SQL database so that MariaDB or MySQL can be substituted, and replaces auth_port and auth_protocol with identity_uri, and auth_host with auth_uri throughout. The Install Guides are thoroughly tested on each distribution and continuously published until the official release packages are available to everyone.
* The [http://docs.openstack.org/high-availability-guide/content/index.html High Availability Guide] now has a separate review team and has moved into a separate repository.
* The [http://docs.openstack.org/security-guide/content/ Security Guide] now has a specialized review team and has moved into a separate repository.
* The long-form API reference documents have been re-purposed to focus on the [http://developer.openstack.org/api-ref.html API Complete Reference].
* The User Guide now contains Database Service for OpenStack information.
* The Command-Line Reference has been updated with new client releases and now contains additional chapters for the common OpenStack client, the trove-manage client, and the Data processing client (sahara).
* The [http://docs.openstack.org/admin-guide-cloud/content/ OpenStack Cloud Administrator Guide] now contains information about Telemetry (ceilometer).