OpenStack - User contributions [en]

OpenStack health tracker

2018-08-09T15:38:41Z

Pabelanger: /* Loci */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Barbican ===

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update 2018-07-30 by cdent

* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Last updated 2018-07-23 by cdent

* Low number of reviews, commits, and contributors but it is somewhat steady.
* A significant amount of the code activity is related to aligning with infra/testing/qa related goals and not feature development. "most of our work at the moment is based around fixing the gate / not breaking future versions"
* ML list use is light, but that's always been the case.
* IRC channel is not busy but is responsive.
* Lurking difficulties:
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)
** Low number of reviews means meeting community goals difficult and distracting.
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.

Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Glance ===

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Infrastructure ===

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Ironic ===

=== Karbor ===

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-30, TheJulia
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc
* PTL felt that the team was in a good state, that goals had been progressing.
* Slight increase in review activity/commits, overall seems fairly healthy.

Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]
** Sam Yaple has agreed to run as PTL again

Update: 2018-08-09, pabelanger
* PTL missed original email, reason for delay.
* LOCI is now a single-repo project. Retired other repos.
* Is stable, but have not agreed and implemented a versioning system.
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.
* LOCI has 3 independent efforts right now from a few people that are encouraging.
** aarch64 support though we haven't setup gates yet
** opensuse 15 support
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.
* core of LOCI is stable and solid throughout all of this. Most/all of this work is about integrations with other OpenStack projects with the long term goals of sharing the "deploy" gates with OSH/Kolla/Triple-O, testing LOCI images.
* Email send to PTL to initiate communication

=== Magnum ===

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Mistral ===

=== Monasca ===

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

Update 6 Aug 2018, dhellmann

* Rong Zhu responded with some hopeful comments about the ZTE situation improving (and it seems to have) and meaning that team members will be more active on IRC again

=== Nova ===

Update 5 July 2018, dhellmann

* melwitt reports "I can't think of any issues we need help with"

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== OpenStackAnsible ===

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Powervmstackers ===

=== Puppet Openstack ===
Update: 2018-08-06 (cmurphy)
* Good progress on important features
** Puppet 5 support
** Debian support
* Some frustration with spam changes (compounded over multiple modules)
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators
* Overall seems to be growing traction and staying healthy

=== Qinling ===

=== Quality Assurance ===

Discussion with gmann, 2018-08-07:
* overall healthy with most repos receiving attention from a diversity of contributors
* grenade is one repo which is of concern, largely due to sdague's departure
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting
* help from individuals usually associated with other projects important aspect of QA health

Outside of that discussion, there are [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-08-02.log.html#t2018-08-02T16:13:21 concerns expressed] about QA being too focused on tempest, and tempest being too focused on Nova.

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Scientific ===
Update: July 17, pabelanger

=== Senlin ===

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===

Update: August 9, ttx

* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews
* Kota is pretty active though, and maintains the project well. He ran a project update session in Vancouver, and tries to recruit more contributors (including in local meetups).
* The team currently being one person, there are no IRC meetings or ML threads. Best way to join the team is the IRC channel (#openstack-storlets)

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: 2018-07-25, cdent
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* Lowish number of commits and reviews, but about what one would expect for a small and stable project
* Effectively in maintenance mode
* Some potential for greater engagement with Monasca
* The features in ceilometer are being shrunk to meet the needs of the people who are making contributions and there is concern that lack of engagement by others will lead to something breaking.

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews
* Claudiu missed the deadline for being PTL but would like to continue
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder
* Increased release velocity by Microsoft means greater change in Hyper-V
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html

Meetings/InfraTeamMeeting

2018-07-24T18:02:30Z

Pabelanger: /* Agenda for next meeting */

OpenStack health tracker

2018-07-18T17:18:29Z

Pabelanger: /* Documentation */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===

Update in progress (ttx)

* Currently single-vendor (all cores from ObjectifLibre)
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack
* IRC meetings do not appear on eavesdrop.openstack.org
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update in progress (cdent)

* Email sent to PTL to start conversation
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Puppet Openstack ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===
Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Scientific ===
Update: July 17, pabelanger

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

WIP: dhellmann (email sent 2018-07-17)

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening

OpenStack health tracker

2018-07-17T18:43:20Z

Pabelanger: /* Status updates */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===

Update in progress (ttx)

* Currently single-vendor (all cores from ObjectifLibre)
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack
* IRC meetings do not appear on eavesdrop.openstack.org
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

== Loci ==
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Puppet Openstack ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===
Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Scientific ===
Update: July 17, pabelanger

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===
Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening

OpenStack health tracker

2018-07-17T18:38:36Z

Pabelanger: /* Status updates */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===

Update in progress (ttx)

* Currently single-vendor (all cores from ObjectifLibre)
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack
* IRC meetings do not appear on eavesdrop.openstack.org
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===
Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Scientific ===
Update: July 17, pabelanger

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===
Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening

OpenStack health tracker

2018-06-12T16:08:13Z

Pabelanger: /* Project Teams */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
||
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
||
|-
| Chef Openstack
|| pabelanger
|-
| Cinder
|| smcginnis
|-
| Cloudkitty
|| ttx
|-
| Congress
||
|-
| Cyborg
|| ttx
|-
| Designate
||
|-
| Documentation
|| dhellmann
|-
| Dragonflow
||
|-
| Ec2-Api
||
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb
|-
| Horizon
|| cmurphy
|-
| I18n
||
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie
|-
| Karbor
|| ttx
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
||
|-
| Kuryr
||
|-
| Loci
|| pabelanger
|-
| Magnum
|| mnaser
|-
| Manila
|| smcginnis
|-
| Masakari
||
|-
| Mistral
|| zaneb
|-
| Monasca
||
|-
| Murano
||
|-
| Neutron
|| mugsie
|-
| Nova
|| mnaser
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx
|-
| Openstack-Helm
|| ttx
|-
| Openstackansible
|| mnaser
|-
| Openstackclient
|| dhellmann
|-
| Openstacksdk
|| pabelanger
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy
|-
| Powervmstackers
||
|-
| Puppet Openstack
|| cmurphy
|-
| Qinling
|| zaneb
|-
| Quality Assurance
|| cdent
|-
| Rally
|| pabelanger
|-
| Refstack
|| fungi
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
||
|-
| Searchlight
|| mugsie
|-
| Security
|| fungi
|-
| Senlin
|| zaneb
|-
| Solum
||
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
||
|-
| Telemetry
|| cdent
|-
| Tricircle
||
|-
| Tripleo
||
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
||
|-
| Watcher
||
|-
| Winstackers
|| pabelanger
|-
| Zaqar
|| zaneb
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==
=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]

=== Trove ===
Reported issues
* No project update in Vancouver
* Missed rocky-2 milestone
* Questions from some public cloud providers on whether they can count on it

Update: June 12, ttx
* The team changed leadership in Rocky
* The new team is small, but pretty alive and active
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

OpenStack health tracker

2018-06-12T16:07:32Z

Pabelanger: /* Project Teams */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
||
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
||
|-
| Chef Openstack
|| pabelanger
|-
| Cinder
|| smcginnis
|-
| Cloudkitty
|| ttx
|-
| Congress
||
|-
| Cyborg
|| ttx
|-
| Designate
||
|-
| Documentation
|| dhellmann
|-
| Dragonflow
||
|-
| Ec2-Api
||
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb
|-
| Horizon
|| cmurphy
|-
| I18n
||
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie
|-
| Karbor
|| ttx
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
||
|-
| Kuryr
||
|-
| Loci
|| pabelanger
|-
| Magnum
|| mnaser
|-
| Manila
|| smcginnis
|-
| Masakari
||
|-
| Mistral
|| zaneb
|-
| Monasca
||
|-
| Murano
||
|-
| Neutron
|| mugsie
|-
| Nova
|| mnaser
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx
|-
| Openstack-Helm
|| ttx
|-
| Openstackansible
|| mnaser
|-
| Openstackclient
|| dhellmann
|-
| Openstacksdk
|| pabelanger
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy
|-
| Powervmstackers
||
|-
| Puppet Openstack
|| cmurphy
|-
| Qinling
|| zaneb
|-
| Quality Assurance
|| cdent
|-
| Rally
||
|-
| Refstack
|| fungi
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
||
|-
| Searchlight
|| mugsie
|-
| Security
|| fungi
|-
| Senlin
|| zaneb
|-
| Solum
||
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
||
|-
| Telemetry
|| cdent
|-
| Tricircle
||
|-
| Tripleo
||
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
||
|-
| Watcher
||
|-
| Winstackers
||
|-
| Zaqar
|| zaneb
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==
=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]

=== Trove ===
Reported issues
* No project update in Vancouver
* Missed rocky-2 milestone
* Questions from some public cloud providers on whether they can count on it

Update: June 12, ttx
* The team changed leadership in Rocky
* The new team is small, but pretty alive and active
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

OpenStack health tracker

2018-06-12T16:06:54Z

Pabelanger: /* Working Groups */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
||
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
||
|-
| Chef Openstack
||
|-
| Cinder
|| smcginnis
|-
| Cloudkitty
|| ttx
|-
| Congress
||
|-
| Cyborg
|| ttx
|-
| Designate
||
|-
| Documentation
|| dhellmann
|-
| Dragonflow
||
|-
| Ec2-Api
||
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb
|-
| Horizon
|| cmurphy
|-
| I18n
||
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie
|-
| Karbor
|| ttx
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
||
|-
| Kuryr
||
|-
| Loci
||
|-
| Magnum
|| mnaser
|-
| Manila
|| smcginnis
|-
| Masakari
||
|-
| Mistral
|| zaneb
|-
| Monasca
||
|-
| Murano
||
|-
| Neutron
|| mugsie
|-
| Nova
|| mnaser
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx
|-
| Openstack-Helm
|| ttx
|-
| Openstackansible
|| mnaser
|-
| Openstackclient
|| dhellmann
|-
| Openstacksdk
||
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy
|-
| Powervmstackers
||
|-
| Puppet Openstack
|| cmurphy
|-
| Qinling
|| zaneb
|-
| Quality Assurance
|| cdent
|-
| Rally
||
|-
| Refstack
|| fungi
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
||
|-
| Searchlight
|| mugsie
|-
| Security
|| fungi
|-
| Senlin
|| zaneb
|-
| Solum
||
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
||
|-
| Telemetry
|| cdent
|-
| Tricircle
||
|-
| Tripleo
||
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
||
|-
| Watcher
||
|-
| Winstackers
||
|-
| Zaqar
|| zaneb
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==
=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]

=== Trove ===
Reported issues
* No project update in Vancouver
* Missed rocky-2 milestone
* Questions from some public cloud providers on whether they can count on it

Update: June 12, ttx
* The team changed leadership in Rocky
* The new team is small, but pretty alive and active
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

OpenStack health tracker

2018-06-12T16:06:22Z

Pabelanger: /* SIGs */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
||
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
||
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
||
|-
| Chef Openstack
||
|-
| Cinder
|| smcginnis
|-
| Cloudkitty
|| ttx
|-
| Congress
||
|-
| Cyborg
|| ttx
|-
| Designate
||
|-
| Documentation
|| dhellmann
|-
| Dragonflow
||
|-
| Ec2-Api
||
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb
|-
| Horizon
|| cmurphy
|-
| I18n
||
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie
|-
| Karbor
|| ttx
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
||
|-
| Kuryr
||
|-
| Loci
||
|-
| Magnum
|| mnaser
|-
| Manila
|| smcginnis
|-
| Masakari
||
|-
| Mistral
|| zaneb
|-
| Monasca
||
|-
| Murano
||
|-
| Neutron
|| mugsie
|-
| Nova
|| mnaser
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx
|-
| Openstack-Helm
|| ttx
|-
| Openstackansible
|| mnaser
|-
| Openstackclient
|| dhellmann
|-
| Openstacksdk
||
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy
|-
| Powervmstackers
||
|-
| Puppet Openstack
|| cmurphy
|-
| Qinling
|| zaneb
|-
| Quality Assurance
|| cdent
|-
| Rally
||
|-
| Refstack
|| fungi
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
||
|-
| Searchlight
|| mugsie
|-
| Security
|| fungi
|-
| Senlin
|| zaneb
|-
| Solum
||
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
||
|-
| Telemetry
|| cdent
|-
| Tricircle
||
|-
| Tripleo
||
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
||
|-
| Watcher
||
|-
| Winstackers
||
|-
| Zaqar
|| zaneb
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==
=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]

=== Trove ===
Reported issues
* No project update in Vancouver
* Missed rocky-2 milestone
* Questions from some public cloud providers on whether they can count on it

Update: June 12, ttx
* The team changed leadership in Rocky
* The new team is small, but pretty alive and active
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

Meetings/InfraTeamMeeting

2018-05-04T18:11:08Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2018-05-01T16:33:25Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2018-04-02T21:24:42Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2018-04-02T20:59:52Z

Pabelanger: /* Agenda for next meeting */

Release Naming/S Proposals

2018-02-20T16:13:49Z

Pabelanger: /* Proposed Names */

== S Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the S release of OpenStack. We will accept nominations until 2018-03-05 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the S release will come is [https://en.wikipedia.org/wiki/Berlin Berlin]

=== Proposed Names ===
[https://en.wikipedia.org/wiki/Spree Spree] (a river that flows through the Saxony, Brandenburg and Berlin states of Germany)

=== Proposed Names that do not meet the criteria ===

Release Naming/S Proposals

2018-02-20T16:10:56Z

Pabelanger: /* Exact Geographic Region */

== S Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the S release of OpenStack. We will accept nominations until 2018-03-05 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the S release will come is [https://en.wikipedia.org/wiki/Berlin Berlin]

=== Proposed Names ===

=== Proposed Names that do not meet the criteria ===

Release Naming/S Proposals

2018-02-15T16:08:52Z

Pabelanger: /* S Release Naming */

== S Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the S release of OpenStack. We will accept nominations until 2018-03-05 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the S release will come is [https://en.wikipedia.org/wiki/Germany Germany]

=== Proposed Names ===

=== Proposed Names that do not meet the criteria ===

Release Naming/S Proposals

2018-02-15T16:01:19Z

Pabelanger:

== S Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the S release of OpenStack. We will accept nominations until 2018-03-01 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the S release will come is [https://en.wikipedia.org/wiki/Germany Germany]

=== Proposed Names ===

=== Proposed Names that do not meet the criteria ===

Release Naming/S Proposals

2018-02-15T15:50:48Z

Pabelanger: Created page with "== S Release Naming == According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated nam..."

== S Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the S release of OpenStack. We will accept nominations until 2018-04-01 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the S release will come is [https://en.wikipedia.org/wiki/Germany Germany]

=== Proposed Names ===

=== Proposed Names that do not meet the criteria ===

Meetings/Zuul

2017-11-20T18:30:25Z

Pabelanger: /* Agenda for next meeting */

= Weekly Zuul meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings about Zuul and Nodepool development in <code><nowiki>#openstack-meeting-alt</nowiki></code>, Mondays at 2200 UTC. Everyone interested in Zuul, Nodepool, and related development is encouraged to attend.

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

== Agenda for next meeting ==
* General topics
** Add support for shared ansible_host in inventory (pabelanger)
*** https://review.openstack.org/521324/
** Allow run to be list of playbooks (pabelanger)
*** https://review.openstack.org/519596/
* Open Discussion

== Previous meetings ==

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/zuul/

Meetings/InfraTeamMeeting

2017-10-31T17:46:23Z

Pabelanger: /* Weekly Project Infrastructure team meeting */

Meetings/InfraTeamMeeting

2017-10-31T15:59:53Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-10-31T15:57:46Z

Pabelanger: /* Weekly Project Infrastructure team meeting */

Meetings/InfraTeamMeeting

2017-10-31T15:57:04Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-05-30T14:31:40Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-05-02T17:52:29Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-05-02T14:09:54Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-04-29T15:56:25Z

Pabelanger: /* Weekly Project Infrastructure team meeting */

Meetings/InfraTeamMeeting

2017-04-29T15:55:55Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-04-29T15:55:28Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-04-29T15:52:06Z

Pabelanger: /* Agenda for next meeting */

Meetings/Zuul

2017-04-26T16:23:32Z

Pabelanger: /* Agenda for next meeting */

= Weekly Zuul meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings about Zuul and Nodepool development in <code><nowiki>#openstack-meeting-alt</nowiki></code>, Mondays at 2200 UTC. Everyone interested in Zuul, Nodepool, and related development is encouraged to attend.

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

== Agenda for next meeting ==
* Announcements
* Actions from last meeting
* Status updates
** Zuul test enablement
** Zuul sample jobs
* Progress summary
* Announcements of areas of interest
* General topics (add agenda items here)
** Github patches (jeblair)
** Bubblewrap (jeblair)
** nodepool image testing spec (pabelanger)
*** https://review.openstack.org/139598
* Open Discussion

== Previous meetings ==

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/zuul/

Meetings/InfraTeamMeeting

2017-04-04T17:07:14Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2017-04-03T21:02:19Z

Pabelanger: /* Agenda for next meeting */

Meetings/Zuul

2017-03-13T15:47:40Z

Pabelanger: /* Agenda for next meeting */

= Weekly Zuul meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings about Zuul and Nodepool development in <code><nowiki>#openstack-meeting-alt</nowiki></code>, Mondays at 2200 UTC. Everyone interested in Zuul, Nodepool, and related development is encouraged to attend.

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

== Agenda for next meeting ==
* Announcements
* Actions from last meeting
* Status updates
** Nodepool
** Devstack-gate roles refactoring
** Zuul test enablement
** Zuul sample jobs
* Progress summary
* Announcements of areas of interest
* General topics (add agenda items here)
** Renaming zuul-launcher? (pabelanger)
*** 'launcher' could refer to zuul-launcher or nodepool-launcher, potentially confusing
*** zuul-runner, zuul-executor, zuul-agent, etc
* Open Discussion

== Previous meetings ==

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/zuul/

Meetings/InfraTeamMeeting

2017-03-07T15:08:46Z

Pabelanger:

Meetings/InfraTeamMeeting

2017-02-28T16:27:14Z

Pabelanger: /* Agenda for next meeting */

Meetings/Zuul

2017-01-30T18:33:02Z

Pabelanger: /* Agenda for next meeting */

= Weekly Zuul meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings about Zuul and Nodepool development in <code><nowiki>#openstack-meeting-alt</nowiki></code>, Mondays at 2200 UTC. Everyone interested in Zuul, Nodepool, and related development is encouraged to attend.

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

== Agenda for next meeting ==
* Announcements
* Actions from last meeting
* Status updates
** Nodepool Zookeeper work
** Devstack-gate roles refactoring
** Zuul test enablement
* Progress summary
* Announcements of areas of interest
* General topics (add agenda items here)
** Fedmsg reporter (pabelanger)
*** https://review.openstack.org/426861
** JJB to ansible-playbook (onetime) converter (pabelanger)
* Open Discussion

== Previous meetings ==

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/zuul/

Meetings/InfraTeamMeeting

2016-11-01T15:17:52Z

Pabelanger: /* Agenda for next meeting */

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html Docs Publishing via AFS]

* General topics
** ''cached image reduction changes'' (ianw 1-Nov-2016)
*** '''summary''' : change devstack's "tools/image_list.sh" to take arguments that allow us to only download test images we use in the gate
**** https://review.openstack.org/377150 <- devstack change
**** https://review.openstack.org/377159 <- project-config cache-devstack change
*** concern -- if we only get certain images, what if we miss new image requirements and start bringing them over network on each run?
**** https://review.openstack.org/391702 <- devstack change to prevent downloading of images during run
**** https://review.openstack.org/391713 <- add sentinel file to enable above
*** thoughts?
**** http://paste.openstack.org/show/587514/ <- current images cached. not a huge problem
** Force gate-{name}-pep8-{node} to build needed wheels - pabelanger
*** https://review.openstack.org/#/c/391875/
*** High chance of breaking pep8 jobs, how to spread the message, date
* Open discussion

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

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

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

Meetings/InfraTeamMeeting

2016-08-30T18:20:57Z

Pabelanger: /* Upcoming Project Renames */

Meetings/InfraTeamMeeting

2016-08-29T16:33:29Z

Pabelanger: /* Upcoming Project Renames */

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** [https://review.openstack.org/276482 Update doc publishing spec for AFS]
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
*** [https://review.openstack.org/360817 Zuul v3: update branches job keyword]
*** [https://review.openstack.org/360819 Zuulv3: drop variable interpolation and add nodesets]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
*** [https://review.openstack.org/360821 Update nodepool zookeeper spec with branch]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
* Design summit session planning (fungi)
* Sprint to test Gerrit online indexing (zaro)
* Open discussion

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

* Rename openstack/smaug to openstack/karbor: https://review.openstack.org/#/c/353278/
* Fix snafu with the openstack-infra/ansible-puppet rename on June 3 (transparent to users, but we need some Gerrit cleanup for a duplicate project)
* Rename openstack/higgins to openstack/zun: https://review.openstack.org/#/c/326306/
* Rename openstack/ansible-role-diskimage-builder to openstack/ansible-role-windmill-diskimage-builder: https://review.openstack.org/#/c/361770
* Rename openstack/ansible-role-jenkins to openstack/ansible-role-windmill-jenkins: https://review.openstack.org/#/c/361771
* Rename openstack/ansible-role-jenkins-job-builder to openstack/ansible-role-windmill-jenkins-job-builder: https://review.openstack.org/#/c/361772
* Rename openstack/ansible-role-jenkins-plugins to openstack/ansible-role-windmill-jenkins-plugins: https://review.openstack.org/#/c/362105
* Rename openstack/ansible-role-nginx to openstack/ansible-role-windmill-nginx: https://review.openstack.org/#/c/362102
* Rename openstack/ansible-role-nodepool to openstack/ansible-role-windmill-nodepool: https://review.openstack.org/#/c/362098
* Rename openstack/ansible-role-shade to openstack/ansible-role-windmill-shade: https://review.openstack.org/#/c/361782
* Rename openstack/ansible-role-ssh to openstack/ansible-role-windmill-ssh: https://review.openstack.org/#/c/361781
* Rename openstack/ansible-role-zuul to openstack/ansible-role-windmill-zuul: https://review.openstack.org/#/c/361780

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

Meetings/InfraTeamMeeting

2016-08-28T21:40:23Z

Pabelanger: /* Upcoming Project Renames */

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** [https://review.openstack.org/276482 Update doc publishing spec for AFS]
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
*** [https://review.openstack.org/360817 Zuul v3: update branches job keyword]
*** [https://review.openstack.org/360819 Zuulv3: drop variable interpolation and add nodesets]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
*** [https://review.openstack.org/360821 Update nodepool zookeeper spec with branch]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
* Design summit session planning (fungi)
* Sprint to test Gerrit online indexing (zaro)
* Open discussion

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

* Rename openstack/smaug to openstack/karbor: https://review.openstack.org/#/c/353278/
* Fix snafu with the openstack-infra/ansible-puppet rename on June 3 (transparent to users, but we need some Gerrit cleanup for a duplicate project)
* Rename openstack/higgins to openstack/zun: https://review.openstack.org/#/c/326306/
* Rename openstack/ansible-role-diskimage-builder to openstack/ansible-role-windmill-diskimage-builder: https://review.openstack.org/#/c/361770
* Rename openstack/ansible-role-jenkins to openstack/ansible-role-windmill-jenkins: https://review.openstack.org/#/c/361771
* Rename openstack/ansible-role-jenkins-job-builder to openstack/ansible-role-windmill-jenkins-job-builder: https://review.openstack.org/#/c/361772

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

Sprints/QAInfraNewtonSprint

2016-08-16T04:54:46Z

Pabelanger: /* Registration */

== Event Details ==
* Date: 19th - 21th September
* Location: SAP HQ Walldorf Germany
* [http://www.sap.com/bin/sapcom/de_de/downloadasset.2014-11-nov-24-17.wdf01_journey_description-pdf.bypassReg.html SAP how to find us and building map]
* Rooms:
** Main room: WDF.03 B2.05 (~30p)
** Breakout rooms:
*** 19th: WDF.03 H3.02 (14p)
*** 20th: WDF.03 BE.02 (14p)
*** 21th: WDF.03 B1.03 (14p)

== Travel ==
* Flight to Frankfurt am Main (FFM) Germany
* Bus transfer ~1h to Walldorf
SHUTTLE SERVICE
Please make an advance reservation if you wish to use this direct minibus service.<br />
Travel time is approximately one hour. At the airport, go to the meeting point in the arrival area.<br />
This shuttle service is provided by Wörns Airport Transfer – to reserve, please contact:Tel. +49/ 62 27/ 5 59 55 Fax +49/ 62 27/ 5 50 61<br />
Bookings can be made by e-mail transfer@woerns-ts.de or online at www.woerns-ts.de.

== Hotels ==
All hotels in walking distance:
* Hotel Villa Verde: http://www.villaverde-walldorf.de/?lang=en
* Hotel Grünshof, grani: http://www.hotel-gruenshof.de/
* Leonardo Hotel Heidelberg-Walldorf: https://www.leonardo-hotels.com/leonardo-hotel-heidelberg-walldorf

== General Help and Visas ==
* In case of general questions feel free to contact:
** Marc Koderer (mkoderer, freenode) marc AT koderer.com
** Maya Tahrilova Linares, maya.tahrilova.linares AT sap.com
* Visa regulations for Germany: http://www.auswaertiges-amt.de/EN/EinreiseUndAufenthalt/Visabestimmungen_node.html

== Topics ==
Please write topics on this wiki or the following etherpad as you like :-)

Etherpad: https://etherpad.openstack.org/p/qa-infra-newton-midcycle
* Proposed Infra topics
** Zuulv3
** Infra Cloud
* Accepted Infra topics
** Puppet-ansible hardening/bugfixing
*** nibalizer

== Registration ==

We have seats for ~30 people.
Please register your info on the following table if you are interested in.

{| class="wikitable sortable"
|-
! || Name !! Company !! IRC name !! Comments !! Email
|-
| 1 || Ken Omichi || NEC || oomichi || || ken1ohmichi at gmail.com
|-
| 2 || Joshua Hesketh || Rackspace || jhesketh || || joshua.hesketh at gmail.com
|-
| 3 || Marc Koderer || SAP || mkoderer || Welcome to Germany again ;) || marc AT koderer.com
|-
| 4 || Tom Patzig || SAP || tpatzig || || tom.patzig at sap.com
|-
| 5 || Daniel Mellado || Red Hat || dmellado || || dmellado at redhat.com
|-
| 6 || Matthew Treinish || HPE || mtreinish || || mtreinish at kortar.org
|-
| 7 || Daniel Gonzalez || SAP || dgonzalez || || daniel at gonzalez-nothnagel.de
|-
| 8 || Ghanshyam Mann || NEC || gmann || || ghanshyammann at gmail.com
|-
| 9 || Masayuki Igawa || HPE || masayukig || || masayuki.igawa at gmail.com
|-
| 10 || Elizabeth K. Joseph || HPE || pleia2 || || lyz at princessleia.com
|-
| 11 || Attila Fazekas || RHT || afazekas || || afazekas KUKAC redhat PONT com
|-
| 12 || Spencer Krum || IBM || nibalizer || || nibz at spencerkrum.com
|-
| 13 || Yolanda Robla || RedHat || yolanda || || info at ysoft.biz
|-
| 14 || Matthew Wagoner || IBM || olaph || || zxkuqyb at gmail.com
|-
| 15 || Clark Boylan || OpenStack Foundation || clarkb || || cboylan at sapwetik.org
|-
| 16 || Ricardo Carrillo Cruz || HPE || rcarrillocruz || || ricardo.carrillo.cruz at gmail.com
|-
| 17 || David Paterson || Dell|| dpaterson || || david_paterson at dell.com
|-
| 18 || Chris Hoge || OpenStack Foundation || hogepodge || || chris@openstack.org
|-
| 19 || Martin Stadtler || Linaro || martinst || || martin.stadtler at linaro.org
|-
| 20 || Gema Gomez || Linaro || gema || || gema.gomez-solano at linaro.org
|-
| 21 || Dong Ma || HPE || larainema || || winterma.dong at gmail.com
|-
| 22 || Paul Belanger || Red Hat || pabelanger || || pabelanger at redhat.com
|}

Meetings/InfraTeamMeeting

2016-07-25T17:12:54Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2016-06-21T13:04:03Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2016-06-14T13:41:16Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2016-06-06T15:32:20Z

Pabelanger: /* Agenda for next meeting */

Meetings/InfraTeamMeeting

2016-05-09T12:58:15Z

Pabelanger: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Golang infra needs for swift
* Publish logs for mirror-update.o.o (pabelanger)
* Tier 3.14159265359 support (pabelanger)
** Out of band contact (phone numbers) for infra-roots
* Open discussion

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

openstack/openstack-ansible-ironic -> openstack/openstack-ansible-os_ironic https://review.openstack.org/299192

openstack-infra/ansible-puppet -> openstack-infra/ansible-role-puppet

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

Meetings/InfraTeamMeeting

2016-05-06T14:21:03Z

Pabelanger: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Golang infra needs for swift
* Tier 3.14159265359 support (pabelanger)
** Out of band contact (phone numbers) for infra-roots
* Open discussion

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

openstack/openstack-ansible-ironic -> openstack/openstack-ansible-os_ironic https://review.openstack.org/299192

openstack-infra/ansible-puppet -> openstack-infra/ansible-role-puppet

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

Meetings/InfraTeamMeeting

2016-03-29T16:25:49Z

Pabelanger: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** VOTING: [https://review.openstack.org/278777 Add Nodepool Zookeeper spec] (jeblair)
** VOTING: [https://review.openstack.org/#/c/287373/ Deploy-Stackviz spec] (austin81, timothyb89)
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Baremetal instances in Nodepool with Ironic (igorbelikov)
* [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004077.html Gerrit tuning] (zaro)
* [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004058.html git-review release request] (zaro/hashar)
* Fuel team is interested in discussing opportunity of running tests on baremetal nodes using Ironic
* Status of gerrit replacement node (anteaya, yolanda)
* Ubuntu Xenial DIBs (pabelanger)
** https://review.openstack.org/#/q/topic:ubuntu-xenial+status:open
* Infra cloud (pabelanger)
** [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004045.html Confirmation of required network drops]
* Open discussion

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

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

Meetings/InfraTeamMeeting

2016-03-29T14:38:54Z

Pabelanger: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

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

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

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** VOTING: [https://review.openstack.org/278777 Add Nodepool Zookeeper spec] (jeblair)
** VOTING: [https://review.openstack.org/#/c/287373/ Deploy-Stackviz spec] (austin81, timothyb89)
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Baremetal instances in Nodepool with Ironic (igorbelikov)
* [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004077.html Gerrit tuning] (zaro)
* [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004058.html git-review release request] (zaro/hashar)
* Fuel team is interested in discussing opportunity of running tests on baremetal nodes using Ironic
* Status of gerrit replacement node (anteaya, yolanda)
* Infra cloud (pabelanger)
** [http://lists.openstack.org/pipermail/openstack-infra/2016-March/004045.html Confirmation of required network drops]
* Open discussion

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

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