https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Lance+Bragstad&feedformat=atomOpenStack - User contributions [en]2024-03-29T08:44:59ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=OSSN/OSSN-0088&diff=177914OSSN/OSSN-00882021-03-17T14:55:35Z<p>Lance Bragstad: /* Recommended Actions */</p>
<hr />
<div>== Some of the Glance metadef APIs likely to leak resources ==<br />
<br />
=== Summary ===<br />
<br />
Metadef APIs are vulnerable and potentially leaking information to<br />
unauthorized users and also there is currently no limit on creation<br />
of metadef namespaces, objects, properties, resources and tags. This<br />
can be abused by malicious users to fill the Glance database resulting<br />
in a Denial of Service (DoS) condition.<br />
<br />
=== Affected Services / Software === <br />
<br />
Glance, Horizon<br />
<br />
=== Discussion === <br />
<br />
There is no restriction on creation of metadef namespaces, objects,<br />
properties, resources and tags as well as it could also leak the<br />
information to unauthorized users or to the users outside of the project. By<br />
taking advantage of this lack of restrictions around metadef APIs, a<br />
a single user could fill the Glance database by creating<br />
unlimited resources, resulting in a Denial Of Service (DoS) style<br />
attack.<br />
<br />
Glance does allow metadef APIs to be controlled by policy. However, the<br />
default policy setting for metadef APIs allows all users to create or<br />
read the metadef information.<br />
<br />
Because metadef resources are not properly isolated to the<br />
owner, any use of them with potentially sensitive names (such as internal<br />
infrastructure details, customer names, etc) could unintentionally<br />
expose that information to a malicious user.<br />
<br />
=== Recommended Actions === <br />
<br />
Since these fundamental issues have been present since the API was introduced, the Glance project is recommending operators to keep create/modify/delete APIs to admin only and provide read access to all users in their deployments. <br />
<br />
<br />
Here is an example of for allowing create/modify/delete metadef APIs to be admin only and read access to normal users in the deployments for current stable OpenStack releases either in policy.json or policy.yaml. <br />
<pre><br />
---- begin example policy.json/policy.yaml snippet ----<br />
"metadef_default": "",<br />
"metadef_admin": "role:admin",<br />
<br />
"get_metadef_namespace": "rule:metadef_default",<br />
"get_metadef_namespaces": "rule:metadef_default",<br />
"modify_metadef_namespace": "rule:metadef_admin",<br />
"add_metadef_namespace": "rule:metadef_admin",<br />
"delete_metadef_namespace": "rule:metadef_admin",<br />
<br />
"get_metadef_object": "rule:metadef_default",<br />
"get_metadef_objects": "rule:metadef_default",<br />
"modify_metadef_object": "rule:metadef_admin",<br />
"add_metadef_object": "rule:metadef_admin",<br />
"delete_metadef_object": "rule:metadef_admin",<br />
<br />
"list_metadef_resource_types": "rule:metadef_default",<br />
"get_metadef_resource_type": "rule:metadef_default",<br />
"add_metadef_resource_type_association": "rule:metadef_admin",<br />
"remove_metadef_resource_type_association": "rule:metadef_admin",<br />
<br />
"get_metadef_property": "rule:metadef_default",<br />
"get_metadef_properties": "rule:metadef_default",<br />
"modify_metadef_property": "rule:metadef_admin",<br />
"add_metadef_property": "rule:metadef_admin",<br />
"remove_metadef_property": "rule:metadef_admin",<br />
<br />
"get_metadef_tag": "rule:metadef_default",<br />
"get_metadef_tags": "rule:metadef_default",<br />
"modify_metadef_tag": "rule:metadef_admin",<br />
"add_metadef_tag": "rule:metadef_admin",<br />
"add_metadef_tags": "rule:metadef_admin",<br />
"delete_metadef_tag": "rule:metadef_admin",<br />
"delete_metadef_tags": "rule:metadef_admin",<br />
---- end example policy.json/policy.yaml snippet ----<br />
</pre><br />
<br />
Operators with users that depend on metadef APIs may choose to leave<br />
these accessible to all users. In that case, education of users about<br />
the potential for information leakage in the resource names is<br />
advisable so that vulnerable practices can be altered as mitigation.<br />
<br />
To re-enable metadef policies to all users, operator(s)<br />
can make a change in respective policy.json or policy.yaml as shown below;<br />
(assuming metadef create/modify/delete policies are configured to use rule:metadeta_admin<br />
as shown in above example)<br />
<pre><br />
---- begin example policy.json/policy.yaml snippet ----<br />
"metadef_admin": "",<br />
---- end example policy.json/policy.yaml snippet ----<br />
</pre><br />
<br />
=== Contacts / References === <br />
<br />
'''Author:'''<br />
* Abhishek Kekane, Red Hat<br />
* Lance Bragstad, Red Hat<br />
<br />
<br />
This OSSN : https://wiki.openstack.org/wiki/OSSN/OSSN-0088<br />
<br />
Original LaunchPad Bug : https://bugs.launchpad.net/glance/+bug/1545702<br />
<br />
Original LaunchPad Bug : https://bugs.launchpad.net/glance/+bug/1916926<br />
<br />
Original LaunchPad Bug : https://bugs.launchpad.net/glance/+bug/1916922<br />
<br />
Mailing List : [Security] openstack-security@lists.openstack.org<br />
<br />
OpenStack Security Project : https://launchpad.net/~openstack-ossg</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Meetings/TechnicalCommittee&diff=171332Meetings/TechnicalCommittee2019-08-04T12:11:28Z<p>Lance Bragstad: /* Apologies for Absence */</p>
<hr />
<div>__NOTOC__<br />
<br />
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .<br />
<br />
In order to include as many people as possible in the discussion, the Technical Committee relies on asynchronous communications as much as possible. We propose and vote on changes through the [http://git.openstack.org/cgit/openstack/governance openstack/governance repository]. Large-impact changes are discussed on the openstack-discuss mailing-list. '''We track current initiatives on the [[Technical_Committee_Tracker]].'''<br />
<br />
We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We meet formally on the first Thursday of each month in #openstack-tc at 1400 UTC.<br />
<br />
<br />
=== Next Meeting ===<br />
<br />
* Date: 8 Aug 2019<br />
* Chair: mnaser<br />
* Agenda to be published on the openstack-discuss mailing list before the meeting<br />
<br />
==== Agenda Suggestions ====<br />
<br />
* Follow up on past action items<br />
<br />
** fungi to add himself as TC liaison for Image Encryption popup team<br />
<br />
** fungi to draft a resolution on proper retirement procedures<br />
<br />
* Active initiatives<br />
<br />
** Python 3: mnaser to sync up with swift team on python3 migration and mugsie to sync with dhellmann or release-team to find the code for the proposal bot<br />
<br />
** Forum follow-up: ttx to organise Milestone 2 forum meeting with tc-members (done)<br />
<br />
** Make goal selection a two-step process (needs reviews at https://review.opendev.org/#/c/667932/)<br />
<br />
* Attendance for leadership meeting during Shanghai Summit on 3 November<br />
<br />
* Reviving Performance WG / Large deployment team into a Large scale SIG (ttx)<br />
<br />
* Summary meeting minutes from 11 July<br />
<br />
http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-07-11-14.00.txt<br />
<br />
==== Apologies for Absence ====<br />
* Lance Bragstad (lbragstad)<br />
<br />
=== Past meetings logs ===<br />
<br />
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc<br />
<br />
[[Category: meetings]]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Denver2019&diff=168488Forum/Denver20192019-02-23T00:42:35Z<p>Lance Bragstad: /* Etherpads from Teams and Working Groups */</p>
<hr />
<div>== Etherpads ==<br />
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!<br />
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.<br />
<br />
==List of Brainstorming Etherpads==<br />
<br />
===Catch-alls===<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]<br />
<br />
===Etherpads from Teams and Working Groups===<br />
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]<br />
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]<br />
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]<br />
<br />
===Etherpads from Pilot projects===<br />
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Denver2019&diff=168466Forum/Denver20192019-02-21T18:16:41Z<p>Lance Bragstad: /* Etherpads from Teams and Working Groups */</p>
<hr />
<div>== Etherpads ==<br />
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!<br />
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.<br />
<br />
==List of Brainstorming Etherpads==<br />
<br />
===Catch-alls===<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]<br />
<br />
===Etherpads from Teams and Working Groups===<br />
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]<br />
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]<br />
<br />
===Etherpads from Pilot projects===<br />
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=166569Forum/Berlin20182018-11-06T15:35:54Z<p>Lance Bragstad: /* Thursday, November 15 */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
See also - [https://www.openstack.org/summit/berlin-2018/summit-schedule/#day=2018-11-13&track_groups=86 Full Forum Schedule]<br />
<br />
===Tuesday, November 13===<br />
* [1100 - 1140] - Release Team onboarding<br />
* [1100 - 1140] - Cells v2 updates - https://etherpad.openstack.org/p/BER-cells-v2-updates<br />
* [1100 - 1140] - Ironic Operator Feedback - https://etherpad.openstack.org/p/BER-ironic-operator-feedback<br />
* [1100 - 1140] - [https://etherpad.openstack.org/p/BER-passport-program-feedback OpenStack Passport Program - feedback and next step]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-Contrib-Portal-Feedback StoryBoard Migration: The Remaining Blockers ]<br />
* [1150 - 1230] - [https://etherpad.openstack.org/p/BER-change-ownership-of-resources Change of ownership of resources ]<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-missing-features-public-cloud Far From Done: Public Clouds Needs You]<br />
* [1430 - 1510] - [https://etherpad.openstack.org/p/BER-getting-users-involved Getting OpenStack users involved in the project ]<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/Creating_a_cinder_data_service Creating a Cinder Data Service]<br />
* [1520 - 1600] - Community outreach when culture, time zones, and language differ - https://etherpad.openstack.org/p/BER-tc-community-outreach<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG Meeting]<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-Cinder_User_Survey_Responses Cinder User Survey Feedback Session]<br />
* [1710 - 1750] - [https://etherpad.openstack.org/p/BER-Cinder_at_the_Edge Cinder and its role at the Edge]<br />
<br />
===Wednesday, November 14===<br />
* [1100 - 1140]<br />
* [1150 - 1230]<br />
** [https://etherpad.openstack.org/p/Berlin2018-Forum-ceph-is-great Ceph is great for openstack and you should use it]<br />
** Boot from volume (BFV) improvements - https://etherpad.openstack.org/p/BER-bfv-improvements<br />
* [1340 - 1420] - [https://etherpad.openstack.org/p/BER-better-expose-what-we-produce OpenStack: Better expose what we produce ]<br />
* [1340 - 1420] - Integrating IOT Device Management with the Edge Cloud - https://etherpad.openstack.org/p/BER-integrating-iot-device-mgmt-with-edge-cloud<br />
* [1430 - 1510] - Extending Blazar reservations to new resource types - https://etherpad.openstack.org/p/Berlin2018-Forum-Extending-Blazar-reservations<br />
* [1430 - 1510] - MVP (Minimum Viable Product) architecture for edge - https://etherpad.openstack.org/p/BER-MVP-architecture-for-edge<br />
* [1520 - 1600] - [https://etherpad.openstack.org/p/BER-Contrib-Guide-Ops The Contributor Guide: Ops Feedback Session]<br />
* [1520 - 1600] - Smartnics, Ironic, Neutron - https://etherpad.openstack.org/p/BER-ironic-smartnics<br />
* [1520 - 1600] - Edge use cases and requirements - https://etherpad.openstack.org/p/BER-edge-use-cases-and-requirements<br />
* [1620 - 1700] - Ask Me Anything ... about StarlingX - https://etherpad.openstack.org/p/BER-ask-me-anything-about-starlingx<br />
* [1620 - 1700] - [https://etherpad.openstack.org/p/BER-deletion-of-project-resources Deletion of project and project resources ]<br />
* [1710 - 1750]<br />
<br />
===Thursday, November 15===<br />
* [0900 - 0940] Bug triage: Why not all the community ? - https://etherpad.openstack.org/p/BER-bug-triage<br />
* [0900 - 0940] Autoscaling Integration, improvement, and feedback - https://etherpad.openstack.org/p/autoscaling-integration-and-feedback<br />
* [0950 - 1030]<br />
* [1050 - 1130] [https://etherpad.openstack.org/p/BER-cross-technical-leadership Cross-technical leadership session (OpenStack, Kata, StarlingX, Airship, Zuul)]<br />
* [1050 - 1130] Ops Docs working session - https://etherpad.openstack.org/p/BER-Ops-Community-Docs<br />
* [1050 - 1130] [https://etherpad.openstack.org/p/BER-Contrib-Portal-Feedback Making the Contributor Portal More Useful]<br />
* [1140 - 1240] [https://etherpad.openstack.org/p/BER-stein-keystone-as-idp Keystone as an Identity Provider Proxy]<br />
* [1340 - 1420] Containerized Applications' Requirements on Kubernetes Cluster at the Edge - https://etherpad.openstack.org/p/BER-containerized-app-reqmts-on-kubernetes-at-edge<br />
* [1340 - 1420] [https://etherpad.openstack.org/p/BER-sdk-certification You don't know nothing about Public Cloud SDKs, yet]<br />
* [1340 - 1420] [https://etherpad.openstack.org/p/BER-stein-keystone-feedback Keystone Operator Feedback]<br />
* [1430 - 1510] Update on placement extraction from nova - https://etherpad.openstack.org/p/BER-placement-extract<br />
* [1520 - 1600] Python bindings for the placement API - https://etherpad.openstack.org/p/BER-python-bindings-for-the-placement-api<br />
* [1520 - 1600] Technical Committee Vision Retrospective - https://etherpad.openstack.org/p/BER-tc-vision-retrospective<br />
* [1620 - 1700]<br />
* [1710 - 1750] T series community goal discussion - https://etherpad.openstack.org/p/BER-t-series-goals<br />
* [1710 - 1750] Fenix - Rolling Mainenance and Upgrade - https://etherpad.openstack.org/p/BER-Forum-Fenix-Upgrade<br />
<br />
==List of Brainstorming Etherpads (Historical)==<br />
Topic selection is now complete, but see below for session idea brainstorming that was done prior to selection.<br />
<br />
'''These are just kept for historical reference. Please do not use for any additional ideas.'''<br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/api-berlin-forum-brainstorming API]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/cinder-berlin-forum-proposals Cinder]<br />
* [https://etherpad.openstack.org/p/cyborg-forum-berlin Cyborg]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/fenix-forum-stein Fenix]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/kolla-forum-stein Kolla]<br />
* [https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm Manila]<br />
* [https://etherpad.openstack.org/p/berlin-monasca-forum-brainstorming Monasca]<br />
* [https://etherpad.openstack.org/p/nova-forum-stein Nova]<br />
* [https://etherpad.openstack.org/p/OSA-berlin-planning OpenStack-Ansible]<br />
* [https://etherpad.openstack.org/p/OpenStackHelmBerlinForumBrainstorming OpenStack-Helm]<br />
* [https://etherpad.openstack.org/p/ops-forum-stein Operators]<br />
* [https://etherpad.openstack.org/p/BER-public-cloud-wg Public Cloud WG]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-scientific-sig Scientific SIG]<br />
* [https://etherpad.openstack.org/p/berlin-self-healing-sig-brainstorm Self-Healing SIG]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/tripleo-forum-stein TripleO]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166259OpenStack health tracker2018-10-24T15:58:55Z<p>Lance Bragstad: /* Glance */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || smcginnis<br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || smcginnis<br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || smcginnis<br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || smcginnis<br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || smcginnis<br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || smcginnis<br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Adjutant ===<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* Team is essentially one core/PTL and lacks diversity. Internal development sometimes stalls upstream work.<br />
* PTL is planning on socializing the project during the Berlin summit in order to attract more contributors.<br />
* No dedicated meeting time, but since the project is currently only one developer the PTL doesn't really see this being an issue. Looking to certainly expand that if/when more contributors start getting involved with the project.<br />
* The team is focused on cleaning up technical debt before jumping into more feature work.<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* The team made some progress on some initiatives like overhauling the documentation site and templates.<br />
* Progress is slow given the team size only being a handful of people.<br />
* PTL has organized a project onboarding session in Berlin to help attract new contributors.<br />
* Meetings are relatively sporadic but do generate useful discussions.<br />
<br />
<br />
Update: 2018-07-18, pabelanger<br />
<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion.<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed.<br />
* Team would benefit the most from code and specification reviews, especially since the select few cores are heads down coding.<br />
* The team has been pushing out a lot of new functionality with respect to team size over the last 3 releases and they're concerned about getting feedback from users and operators.<br />
* Didn't sound like the team was able to secure a slot for a project update or a general purpose feedback session.<br />
* PTL is working with the foundation to massage the user survey questions to be more useful, sounds like the current set is too dated to be relevant.<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166126OpenStack health tracker2018-10-19T16:41:09Z<p>Lance Bragstad: /* Documentation */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Adjutant ===<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* Team is essentially one core/PTL and lacks diversity. Internal development sometimes stalls upstream work.<br />
* PTL is planning on socializing the project during the Berlin summit in order to attract more contributors.<br />
* No dedicated meeting time, but since the project is currently only one developer the PTL doesn't really see this being an issue. Looking to certainly expand that if/when more contributors start getting involved with the project.<br />
* The team is focused on cleaning up technical debt before jumping into more feature work.<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* The team made some progress on some initiatives like overhauling the documentation site and templates.<br />
* Progress is slow given the team size only being a handful of people.<br />
* PTL has organized a project onboarding session in Berlin to help attract new contributors.<br />
* Meetings are relatively sporadic but do generate useful discussions.<br />
<br />
<br />
Update: 2018-07-18, pabelanger<br />
<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166125OpenStack health tracker2018-10-19T16:40:57Z<p>Lance Bragstad: /* Documentation */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Adjutant ===<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* Team is essentially one core/PTL and lacks diversity. Internal development sometimes stalls upstream work.<br />
* PTL is planning on socializing the project during the Berlin summit in order to attract more contributors.<br />
* No dedicated meeting time, but since the project is currently only one developer the PTL doesn't really see this being an issue. Looking to certainly expand that if/when more contributors start getting involved with the project.<br />
* The team is focused on cleaning up technical debt before jumping into more feature work.<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* The team made some progress on some initiatives like overhauling the documentation site and templates.<br />
* Progress is slow given the team size only being a handful of people.<br />
* PTL has organized a project onboarding session in Berlin to help attract new contributors.<br />
* Meetings are relatively sporadic but do generate useful discussions.<br />
<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166123OpenStack health tracker2018-10-19T14:13:19Z<p>Lance Bragstad: /* Adjutant */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Adjutant ===<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* Team is essentially one core/PTL and lacks diversity. Internal development sometimes stalls upstream work.<br />
* PTL is planning on socializing the project during the Berlin summit in order to attract more contributors.<br />
* No dedicated meeting time, but since the project is currently only one developer the PTL doesn't really see this being an issue. Looking to certainly expand that if/when more contributors start getting involved with the project.<br />
* The team is focused on cleaning up technical debt before jumping into more feature work.<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166122OpenStack health tracker2018-10-19T14:08:29Z<p>Lance Bragstad: /* Status updates */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Adjutant ===<br />
Update: 19 October 2018 by lbragstad<br />
<br />
* <br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166102OpenStack health tracker2018-10-18T17:48:17Z<p>Lance Bragstad: /* Oslo */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
<br />
Update: 18 October 2018 by lbragstad<br />
<br />
* Active discussions about moving taskflow out of OpenStack governance.<br />
* Most of the core team is still employed by Red Hat. Red Hat is expanding development in this area with another contributor, which is a good thing, but doesn't necessarily help with diversity.<br />
* Team missed a slot for a project update in Berlin and is looking into ways to have that virtually.<br />
* The team is active and regularly participates in meetings.<br />
* Some concern about large features taking a long time to review.<br />
<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166081OpenStack health tracker2018-10-18T13:44:59Z<p>Lance Bragstad: /* Vitrage */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates. On the waiting list for a project-onboarding session.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166080OpenStack health tracker2018-10-18T13:40:20Z<p>Lance Bragstad: /* Vitrage */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* Will be holding sessions at the Summit in Berlin for onboarding and project updates.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166036OpenStack health tracker2018-10-17T14:29:40Z<p>Lance Bragstad: /* Vitrage */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* PTL reported that the virtual PTG they held was very productive, but continue to look for new contributors.<br />
* Developers were optimistic about what they achieved in Rocky and are looking forward to Stein.<br />
* Interested in the self-healing SIG.<br />
* IRC activity is relatively low, but that doesn't seem to be impacting communications between developers.<br />
* The issues originally reported by Doug are still present.<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166035OpenStack health tracker2018-10-17T14:16:03Z<p>Lance Bragstad: /* Cyborg */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
<br />
Update: 17 October 2018 by lbragstad<br />
<br />
* No account of [http://eavesdrop.openstack.org/meetings/openstack_cyborg_project/ previous meeting logs] (404), but meetings are held in IRC.<br />
* Development team is working on features and a presentation for the summit in Berlin.<br />
* PTL noted that more resources would be a plus in helping with work queues.<br />
* Development pace seems to have maintained through Rocky and into Stein<br />
* IRC is relatively quiet, but there are long discussions with other teams every few days.<br />
<br />
<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=166034OpenStack health tracker2018-10-17T14:02:24Z<p>Lance Bragstad: /* Mistral */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
* New contributors should have the most impact by helping with bug, features, and improving documentation.<br />
* Code review volume doesn't seem to be a huge issue, yet<br />
* Existing developers also noted that it is tough to concisely explain the purpose of the project (why should you care about workflows) and the problems it solves, which probably confuses new developers and raises the barrier to entry<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165998OpenStack health tracker2018-10-16T13:52:30Z<p>Lance Bragstad: /* Glance */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
* Most cores are employed by Red Hat, but this isn't a huge concern for the group since work in this area is needed<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165997OpenStack health tracker2018-10-16T13:51:01Z<p>Lance Bragstad: /* Glance */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Meetings occur weekly and seem to have good discussion<br />
*<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165996OpenStack health tracker2018-10-16T13:30:28Z<p>Lance Bragstad: /* Release Management */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165995OpenStack health tracker2018-10-16T13:30:15Z<p>Lance Bragstad: /* Release Management */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Task automation continues to make workload for the team easier<br />
* Consistent drive-by attendees in weekly meetings<br />
* Concerns over core team and what that means for transitioning leadership<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165994OpenStack health tracker2018-10-16T13:28:21Z<p>Lance Bragstad: /* Mistral */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 16 October 2018 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165993OpenStack health tracker2018-10-16T13:27:39Z<p>Lance Bragstad: /* Mistral */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Update: 2018 October 16 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165992OpenStack health tracker2018-10-16T13:26:34Z<p>Lance Bragstad: /* Mistral */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || cdent <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || gmann<br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || cdent <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || cdent <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad, zaneb<br />
|-<br />
| Barbican || fungi, ttx <br />
|-<br />
| Blazar || gmann<br />
|-<br />
| Chef Openstack || evrardjp<br />
|-<br />
| Cinder || gmann<br />
|-<br />
| Cloudkitty || evrardjp<br />
|-<br />
| Congress || gmann<br />
|-<br />
| Cyborg || lbragstad, ttx<br />
|-<br />
| Designate || evrardjp<br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || ttx<br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || cdent, zaneb<br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || evrardjp<br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || cdent <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || gmann<br />
|-<br />
| Kuryr || gmann<br />
|-<br />
| Loci || lbragstad, evrardjp<br />
|-<br />
| Magnum || cdent <br />
|-<br />
| Manila || gmann<br />
|-<br />
| Masakari || gmann<br />
|-<br />
| Mistral || lbragstad, zaneb<br />
|-<br />
| Monasca || gmann, zaneb<br />
|-<br />
| Murano || ttx <br />
|-<br />
| Neutron || cdent <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || gmann<br />
|-<br />
| Openstack Charms || evrardjp<br />
|-<br />
| Openstack-Helm || evrardjp<br />
|-<br />
| Openstackansible || fungi, evrardjp<br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || evrardjp, zaneb<br />
|-<br />
| Powervmstackers || ttx <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || ttx, zaneb<br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || evrardjp<br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || ttx, zaneb<br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || cdent <br />
|-<br />
| Swift || cdent, zaneb<br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || ttx <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || evrardjp<br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher ||<br />
|-<br />
| Winstackers || ttx <br />
|-<br />
| Zaqar || zaneb<br />
|-<br />
| Zun || gmann, ttx<br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
Updated: 2018 October 16 by lbragstad<br />
<br />
* Lack of development<br />
* Contributors haven't flagged development pace as a major concern yet, but it could become an issue in the future<br />
* Attracting new contributors is a struggle<br />
* Project contributors seem to be taking on multiple tasks that make development time for Mistral challenging<br />
* The team continues to hold office hours weekly<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [https://review.openstack.org/#/c/590601/ Trinh Nguyen has volunteered to be the PTL for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=OpenStack_health_tracker&diff=165851OpenStack health tracker2018-10-12T03:29:01Z<p>Lance Bragstad: /* Project Teams */</p>
<hr />
<div>'''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.'''<br />
<br />
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.<br />
<br />
== Health check list ==<br />
<br />
Liaisons should monitor their groups by:<br />
* reading meeting logs or participating in meetings<br />
* watching summit "project update" videos<br />
* reading relevant messages on the mailing list<br />
* talking with the PTL, chair, and other group members<br />
* checking contribution rates and review turnaround times<br />
<br />
<br />
== Liaisons ==<br />
=== SIGs ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| API || <br />
|-<br />
| Extended Maintenance || <br />
|-<br />
| FEMDC || <br />
|-<br />
| First Contact || fungi <br />
|-<br />
| K8s || <br />
|-<br />
| Meta || <br />
|-<br />
| Operation Docs || <br />
|-<br />
| Resource Management || <br />
|-<br />
| Scientific || <br />
|-<br />
| Security || fungi <br />
|-<br />
| Self-healing || <br />
|-<br />
| Upgrade || <br />
|}<br />
<br />
=== Board Committees and Working Groups ===<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Foundation Finance Committee || <br />
|-<br />
| Interop Working Group || fungi <br />
|-<br />
| Compensation Committee || <br />
|-<br />
| Professional Certification Working Group || <br />
|-<br />
| Diversity Working Group || fungi <br />
|-<br />
| Gold And Platinum Member Committee || <br />
|}<br />
<br />
=== UC Teams and Working Groups ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Financial Team || <br />
|-<br />
| Large Deployment Team || <br />
|-<br />
| Massively Distributed Clouds || <br />
|-<br />
| Operators Telecom/NFV || <br />
|-<br />
| Ops Tags Team || <br />
|-<br />
| Product Team || <br />
|-<br />
| Fault-Genes Working Group || <br />
|-<br />
| LCOO Working Group || <br />
|-<br />
| Public Cloud Working Group || <br />
|}<br />
<br />
=== Project Teams ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group !! TC members<br />
|-<br />
| Adjutant || lbragstad<br />
|-<br />
| Barbican || fungi <br />
|-<br />
| Blazar || <br />
|-<br />
| Chef Openstack || <br />
|-<br />
| Cinder || <br />
|-<br />
| Cloudkitty || <br />
|-<br />
| Congress || <br />
|-<br />
| Cyborg || lbragstad<br />
|-<br />
| Designate || <br />
|-<br />
| Documentation || lbragstad<br />
|-<br />
| Dragonflow || <br />
|-<br />
| Ec2-Api || <br />
|-<br />
| Freezer || <br />
|-<br />
| Glance || lbragstad<br />
|-<br />
| Heat || <br />
|-<br />
| Horizon || <br />
|-<br />
| I18n || <br />
|-<br />
| Infrastructure || fungi <br />
|-<br />
| Ironic || <br />
|-<br />
| Karbor || <br />
|-<br />
| Keystone || fungi <br />
|-<br />
| Kolla || <br />
|-<br />
| Kuryr || <br />
|-<br />
| Loci || lbragstad<br />
|-<br />
| Magnum || <br />
|-<br />
| Manila || <br />
|-<br />
| Masakari || <br />
|-<br />
| Mistral || lbragstad<br />
|-<br />
| Monasca || <br />
|-<br />
| Murano || <br />
|-<br />
| Neutron || <br />
|-<br />
| Nova || lbragstad<br />
|-<br />
| Octavia || <br />
|-<br />
| Openstack Charms || <br />
|-<br />
| Openstack-Helm || <br />
|-<br />
| Openstackansible || fungi <br />
|-<br />
| OpenStackClient || fungi <br />
|-<br />
| Openstacksdk || fungi <br />
|-<br />
| Oslo || lbragstad<br />
|-<br />
| Packaging-Rpm || <br />
|-<br />
| Powervmstackers || <br />
|-<br />
| Puppet Openstack || <br />
|-<br />
| Qinling || <br />
|-<br />
| Quality Assurance || fungi <br />
|-<br />
| Rally || fungi <br />
|-<br />
| Release Management || lbragstad<br />
|-<br />
| Requirements || fungi <br />
|-<br />
| Sahara || <br />
|-<br />
| Searchlight || <br />
|-<br />
| Senlin || <br />
|-<br />
| Solum || fungi <br />
|-<br />
| Storlets || <br />
|-<br />
| Swift || <br />
|-<br />
| Tacker || <br />
|-<br />
| Telemetry || <br />
|-<br />
| Tricircle || <br />
|-<br />
| Tripleo || <br />
|-<br />
| Trove || <br />
|-<br />
| Vitrage || lbragstad<br />
|-<br />
| Watcher || <br />
|-<br />
| Winstackers || <br />
|-<br />
| Zaqar || <br />
|-<br />
| Zun || <br />
|}<br />
<br />
== Status updates ==<br />
<br />
=== Barbican ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
The team seems generally healthy and was considered to have "diverse affiliation" at the time we removed the affiliation diversity tags. Vulnerability reports for its code deliverables are officially overseen by the OpenStack VMT and have no outstanding public security issues unhandled. Changes are reviewed and approved with regularity in most of their deliverables. They're keeping up with applicable cycle goals, release deadlines, holding regular weekly meetings in IRC (if sometimes a bit short and with only a handful of participants) and putting important design discussions on the development mailing list. Over the past cycle they migrated their task and defect tracking from Launchpad to Storyboard, and were bolstered somewhat in their mission by the inclusion of Castellan (though not officially a Barbican deliverable, still maintained by many of the same folks and basically a foster child in Oslo's care) in the base services list.<br />
<br />
=== Blazar ===<br />
Reported issues<br />
* Organizational diversity fragility: NTT represents 79% of core reviews<br />
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)<br />
* A lot of work seems to be going around updating document linking<br />
<br />
=== Chef OpenStack ===<br />
Reported issues<br />
* Individual fragility: Samuel Cassiba represents 75% of commits<br />
<br />
=== Cinder ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Some drop off in participation by some cores, but still active enough not to raise any red flags<br />
* Overall less community involvement<br />
* Project may just be "stable" and doesn't need as much activity as the past<br />
* Still a lot of bug fix work to be done, but no major new features on the roadmap<br />
<br />
=== Cloudkitty ===<br />
Updated July 19, 2018 (ttx)<br />
<br />
* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people<br />
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)<br />
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy<br />
* It's mostly in competition with homegrown solutions, which makes it a bit special<br />
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
<br />
=== Congress ===<br />
<br />
Update 2018-07-30 by cdent<br />
<br />
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)<br />
* Commits and reviews in the hands of a small but diverse group<br />
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html<br />
* IRC logged for both channel and meetings, low but steady traffic.<br />
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.<br />
<br />
=== Cyborg ===<br />
Update: 2018-07-10, TheJulia<br />
* Email responded to by PTL on July 4th. PTL has nothing to really report.<br />
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.<br />
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.<br />
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Designate ===<br />
Last updated 2018-07-23 by cdent<br />
<br />
* Low number of reviews, commits, and contributors but it is somewhat steady.<br />
* 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"<br />
* ML list use is light, but that's always been the case.<br />
* IRC channel is not busy but is responsive.<br />
* Lurking difficulties:<br />
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)<br />
** Low number of reviews means meeting community goals difficult and distracting.<br />
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"<br />
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.<br />
<br />
Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.<br />
<br />
=== Diversity ===<br />
Last updated 2018-07-03 by fungi<br />
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)<br />
* 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)<br />
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities<br />
<br />
=== Documentation ===<br />
Update: 2018-07-18, pabelanger<br />
* Revist meeting format at stein PTG<br />
* To early to report on new office hours, but people still seem to ask questions at random times.<br />
* review queue is pretty stable<br />
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Dragonflow ===<br />
Reported issues<br />
* Organizational diversity fragility: Huawei represents 100% of core reviews<br />
* 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<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== ec2-api ===<br />
Reported issues<br />
* Individual fragility: Andrey Pavlov represents 100% of core reviews<br />
* Standing TODOs to update ec2api to latest Nova APIs (https://bugzilla.redhat.com/show_bug.cgi?id=1612369#c1)<br />
<br />
Last update: July 3, 2018 (cmurphy)<br />
* Low activity due to general maturity<br />
* Still actively used by operators, bugs are reported and fixed<br />
* Three cores, all reportedly active<br />
* Being part of OpenStack is still valued<br />
** Operators are still using the project, so better to be coupled with OpenStack<br />
** Depends on other components of OpenStack, so there is value in collaborating together<br />
<br />
=== Extended Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Newly formed SIG in the Rocky cycle, built on the ruins of the old Stable Branch Management team. They're still feeling out the changes we outlined in Dublin and Vancouver for EM as compared to the old stable/EOL workflow.<br />
<br />
=== First Contact ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
Primarily focused on fleshing out the contributor guide, working with OSF staff on the contributor portal, and most recently the employer guide (targeted at helping management at contributors' employing organizations understand what resources they can provide to help their upstream interactions be more successful and lower-friction). They meet fairly consistently in IRC each week, and while those active in the SIG are fairly few in number they represent work important to the overall health of our community so can use all the support they can get.<br />
<br />
=== Freezer ===<br />
ttx updated Aug 28, 2018<br />
<br />
* Lots of warning lights:<br />
** Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]<br />
** freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones, so Freezer was not included in Rocky<br />
** There was [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s)] for Stein.<br />
** No PTG presence<br />
** No team meeting since August 2017<br />
* That said:<br />
** The historic PTL (Saad Zaher) is working on it on his free time, and was on paternity leave lately (congrats!)<br />
** Several people stepped up to save it from being made unofficial (Trinh Nguyen from Edlab, Geng Changcai from ZTE)<br />
** Activity was significant in Rocky (88 commits), with good diversity<br />
* Recommendation is to reassess before stein-2 milestone<br />
<br />
=== Glance ===<br />
<br />
=== Heat ===<br />
Update: 2018-06-28, zaneb<br />
<br />
* Under active development<br />
* 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.<br />
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)<br />
* Active on mailing list and IRC<br />
* Regular IRC meetings<br />
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky<br />
* 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].<br />
<br />
=== Horizon ===<br />
Update: July 20, cmurphy<br />
<br />
* Lost several core reviewers recently<br />
* Some promising new contributors, could become cores if they help with reviews more<br />
* Nearly complete with mox goal<br />
* Focus on cross-project plugins and CI coverage<br />
* Lots of participation in weekly meetings<br />
* Concern about getting help with AngularJS work<br />
** 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<br />
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python<br />
** Hard in general to attract new JS devs when OpenStack is mostly Python<br />
<br />
=== I18n ===<br />
Update: July 04, emilien<br />
<br />
Reported issues: none, yet.<br />
The team changed leadership in Queens.<br />
<br />
Queens status:<br />
* 87 modules touched (+87%)<br />
* 17 languages supported (+6%)<br />
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)<br />
* 7 companies support (-22%)<br />
I18n team previously had team meetings but decided to have office hours instead.<br />
Usually tracks completion of Rocky community goals.<br />
A lot of collaboration with Doc team.<br />
Dedicated mailing-list: openstack-i18n - pretty busy<br />
<br />
Rocky:<br />
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike><br />
<br />
=== Infrastructure ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Probably the most significant note is that this team is slowly working on disassociating itself from direct OpenStack governance (the draft declaration of independence for it still seeks input from the OpenStack community as a part of its own decision-making processes however). The TC should of course continue to concern itself with the health of this collective under whatever new name and governance it assumes since OpenStack is heavily reliant on the services it provides. Reasonably healthy at present, the team has numerous deliverable repositories under its umbrella which see widely varied levels of contribution and review activity. During Rocky it lost a couple of its more active root sysadmins which has added a renewed strain on available bandwidth. The Zuul (+nodepool et al) project was also split out during this cycle, but the official separation doesn't seem to have particularly drained any of the team away as there is still significant overlap between them. Upcoming concerns are making sure the team is still able to meet its charge with the increased responsibility of serving additional OSF projects beyond OpenStack itself, along with rebranding/debranding efforts coupled with whitelabeling of some relevant services.<br />
<br />
=== Interop ===<br />
Last updated 2018-07-03 by fungi<br />
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository<br />
* Affiliation is fairly diverse, but with so few active that's probably not really relevant<br />
* 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<br />
* Heavily dependent on the RefStack and QA teams for their tool development<br />
<br />
=== Ironic ===<br />
<br />
=== Karbor ===<br />
Update: Oct 5, ttx<br />
<br />
* Activity dropped significantly over the last 6 months: no more meetings, only 16 (mostly cleanup) commits in Rocky<br />
* Pengju Jiao stepped up in August to push the release and apply for the PTL position<br />
* Activity dropped again in September as he was on paternity leave. Activity is expected to pick back up after the Golden Week in China<br />
* Karbor is far from fully-functional and needs a lot of work. Pengju has a clear roadmap for Stein.<br />
* In terms of contribution, Karbor has users involved (China Mobile, Huawei), and other users that are not yet contributing<br />
<br />
=== Keystone ===<br />
Update July 3, 2018 (cmurphy)<br />
* High pressure due to being a central part of OpenStack<br />
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development<br />
* 10 cores with varying levels of activity, nearly all are at most part-time<br />
** Concern over possibility of team burnout<br />
<br />
=== Kolla ===<br />
Update: 2018-07-30, TheJulia<br />
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc<br />
* PTL felt that the team was in a good state, that goals had been progressing.<br />
* Slight increase in review activity/commits, overall seems fairly healthy.<br />
<br />
Update: 2018-07-10, TheJulia<br />
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Kuryr ===<br />
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims<br />
<br />
Reported issues<br />
* Organizational diversity fragility: RedHat represents 79% of core reviews<br />
** Considering moving or adding meetings to reach more timezones<br />
* Making good headway in general<br />
* Have some challenges with infra that they'd like to figure out:<br />
** Would be good to have an openstack-infra k8s registry for containers<br />
** Would be nice to have nested VMs with large RAM to test pods<br />
* Need to work with neutron to deal with API slowness<br />
<br />
=== Large Deployment ===<br />
Update: 2018-07-14, pabelanger<br />
<br />
=== Loci ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
** Sam Yaple has agreed to run as PTL again<br />
<br />
Update: 2018-08-09, pabelanger<br />
* PTL missed original email, reason for delay.<br />
* LOCI is now a single-repo project. Retired other repos.<br />
* Is stable, but have not agreed and implemented a versioning system.<br />
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.<br />
* LOCI has 3 independent efforts right now from a few people that are encouraging.<br />
** aarch64 support though we haven't setup gates yet<br />
** opensuse 15 support<br />
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.<br />
* 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.<br />
* Email send to PTL to initiate communication<br />
<br />
=== Magnum ===<br />
<br />
=== Manila ===<br />
Update: June 22, 2018, smcginnis<br />
<br />
* Project appears to be in good shape<br />
* Focusing on bug fixes and stabilization rather than any big new features<br />
* Drop of in involvement from EU, particularly from HPE and IBM<br />
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage<br />
** Not a lot of involvement on IRC or weekly meeting though<br />
* Lots of good interest downstream, particularly from HPC and telco communities<br />
<br />
=== Masakari ===<br />
Reported issues<br />
* Low activity in Rocky for a "new" project<br />
* Organizational diversity fragility: NTT represents 97% of core reviews<br />
<br />
=== Mistral ===<br />
<br />
* Active development, with a steady stream of reviews and patches spread fairly evenly across a handful of contributors<br />
* Organisational diversity is low, however - most contributions come from Nokia and Red Hat.<br />
* Switched to multiple weekly office hours, logged as meetings. Quoting Dougal on lessons learned:<br />
** Essentially we have ended up with a less formal meeting, but it happens multiple times in the week. The biggest advantage is that we can cover more timezones. I think it generally works well, but sometimes it is very quiet and just me - in those cases I tend to do bug triage and other routine tasks. This has helped reduce the bug backlog by at least 50%! We are a small team and a more formal weekly meeting always felt forced, as we didn't always have specific topics to discuss or there would only be a couple of us. So now the structure of the meetings is generally "Anyone here and want to chat? We have X new bugs we can talk about" and then we take it from there. Having a list of IRC nicks to ping at the start of meetings has helped remind people :)<br />
* Missing PTG4 because it happens that no cores are available, so virtual PTG is planned instead. Mistral have participated in previous PTGs and expect to find it easier being co-located with the Summit.<br />
<br />
=== Monasca ===<br />
Update: August 14th, 2018<br />
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.<br />
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.<br />
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.<br />
<br />
=== Murano ===<br />
* murano and murano-dashboard missed the Rocky-2 milestone<br />
<br />
<br />
Update 13 June 2018, dhellmann<br />
<br />
* 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]<br />
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.<br />
* emilien sent email on 2018-07-17<br />
<br />
Update 6 Aug 2018, dhellmann<br />
<br />
* 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<br />
<br />
=== Nova ===<br />
<br />
Update 5 July 2018, dhellmann<br />
<br />
* melwitt reports "I can't think of any issues we need help with"<br />
<br />
=== Octavia ===<br />
* Feeling a small shortage of contributors (contributions & code review)<br />
* OpenStack-wide "interruptions" affect team heavily<br />
* Moving from screen to systemd affected team for ~4 weeks<br />
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project<br />
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress<br />
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen<br />
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues<br />
<br />
=== Openstack Charms ===<br />
Update: June 20, ttx<br />
<br />
* Currently single-vendor (all cores from Canonical), but with some external participation<br />
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)<br />
* Holds weekly IRC meetings with rotating chair<br />
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging<br />
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])<br />
<br />
=== OpenStack-Helm ===<br />
Update: June 26, ttx<br />
<br />
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)<br />
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)<br />
* Holds weekly IRC meetings, pretty active discussions<br />
* Migrated to StoryBoard<br />
* Limited ML engagement (mostly used for team-wide announcements)<br />
* 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.<br />
<br />
=== OpenStackAnsible ===<br />
<br />
=== OpenStackClient ===<br />
Update: 28 June 2018, dhellmann, cmurphy<br />
<br />
* uses IRC and the mailing list but no meetings<br />
* the review team is small, but there are several active reviewers not on the core team yet who are candidates<br />
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that<br />
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)<br />
<br />
=== Openstacksdk ===<br />
Update: 2018-07-02, TheJulia<br />
* Initial communication with PTL, should expect to follow-up with-in the next few days.<br />
<br />
=== Oslo ===<br />
<br />
Reported issues<br />
<br />
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors<br />
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.<br />
* 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.<br />
* 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.<br />
<br />
Update: 12 June 2018, dhellmann<br />
<br />
* The team is small, but active and working on recruiting.<br />
* Team produces regular and frequent releases for the maintained libraries<br />
* Team meets weekly using IRC<br />
* Team had both onboarding and project update sessions in Vancouver<br />
* The level of activity within each library varies.<br />
* 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]<br />
<br />
=== Packaging-RPM ===<br />
Reported issues<br />
* Organizational diversity fragility: SUSE represents 77% of core reviews<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)<br />
Update 21 Aug 2018 (cmurphy):<br />
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE<br />
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment<br />
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)<br />
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)<br />
* Not sure if it remains valuable to remain under governance<br />
<br />
=== Powervmstackers ===<br />
<br />
* Email sent on August 9th (emilien).<br />
* No help is needed, and their collaboration with other projects became better over time.<br />
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.<br />
* The project looks quite healthy so far, and nothing much to report now.<br />
<br />
=== Puppet Openstack ===<br />
Update: 2018-08-06 (cmurphy)<br />
* Good progress on important features<br />
** Puppet 5 support<br />
** Debian support<br />
* Some frustration with spam changes (compounded over multiple modules)<br />
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators<br />
* Overall seems to be growing traction and staying healthy<br />
<br />
=== Qinling ===<br />
Update: August 20th, 2018, TheJulia<br />
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.<br />
* Emailed PTL on August 14th, 2018.<br />
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.<br />
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.<br />
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.<br />
<br />
=== Quality Assurance ===<br />
<br />
Discussion with gmann, 2018-08-07:<br />
* overall healthy with most repos receiving attention from a diversity of contributors<br />
* grenade is one repo which is of concern, largely due to sdague's departure<br />
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting<br />
* help from individuals usually associated with other projects important aspect of QA health<br />
<br />
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.<br />
<br />
=== Rally ===<br />
Reported issues<br />
* Half on GitHub those days, and unwilling to drop direct branching ACLs<br />
* Individual fragility: Andrey Kurilin represents 56% of commits<br />
* Organizational diversity fragility: GoDaddy represents 97% of core reviews<br />
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann<br />
<br />
=== Refstack ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
Last updated 2018-07-03 by fungi<br />
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)<br />
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals<br />
* 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<br />
* 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<br />
* 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<br />
* 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<br />
<br />
=== Release Management ===<br />
<br />
<br />
Update: 28 June 2018, dhellmann & smcginnis<br />
<br />
* 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.<br />
* Working on a reviewers' guide to help with recruiting.<br />
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.<br />
<br />
=== Requirements Management ===<br />
<br />
<br />
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver<br />
<br />
Update: 14 June 2018, dhellmann<br />
<br />
* team has recently lost several members<br />
* most work is really down to 3 people (Matt, Dirk, Tony)<br />
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable<br />
* 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<br />
* meets regularly<br />
* accomplishments this cycle<br />
** stopped syncing dependencies between projects<br />
** working on networkx upgrade<br />
** uncapped eventlet<br />
** uncapped sphinx<br />
** added optional lower-constraints test jobs for project teams that want them<br />
<br />
=== Resource Management SIG ===<br />
<br />
Update 2018-07-10, cdent. Summary: SIG is idling.<br />
<br />
Concerns or Issues:<br />
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.<br />
* This is likely due to the main participants being overbooked to be able to fit things in.<br />
** cdent is one of those main participants and hasn't had a chance to do anything<br />
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal<br />
<br />
=== Sahara ===<br />
Update: June 13, emilien<br />
<br />
Reported issues: none, yet.<br />
* The team changed leadership in Queens<br />
* Most commits in Rocky are from Red Hat (92% of core reviews)<br />
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews<br />
* 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<br />
* Following goals and releases<br />
* Email sent to PTL on June 13th<br />
<br />
=== Searchlight ===<br />
Reported issues<br />
* searchlight and searchlight-ui missed the Rocky-1 milestone<br />
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]<br />
<br />
=== Security (SIG) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
Operated for a while in parallel with the project team of the same name, during Rocky it assumed responsibility for the corresponding deliverable repositories. Many of its previous members (both the SIG and the team) have slowly faded from the OpenStack community, and most of those who remain have also been drafted into the VMT. It still holds regular weekly meetings, has a consensus chair, is present for events like the PTG and Summit/Forum, and has continued to manage OSSN and security assessment tasks to assist the VMT... but as it's now mostly the same people the lines there have become increasingly blurry.<br />
<br />
=== Security (team) ===<br />
Last updated 2018-09-11 by fungi<br />
<br />
This mostly defunct team was retired at the end of the Rocky cycle, and its deliverable repositories folded into the SIG of the same name.<br />
<br />
=== Scientific ===<br />
Update: July 17, pabelanger<br />
<br />
=== Senlin ===<br />
<br />
=== Solum ===<br />
Reported issues<br />
* Individual fragility: Zhurong represents 100% of core reviews<br />
* Zhurong is employed by ZTE and recent US government actions might affecting contributions<br />
<br />
=== Stable Branch Maintenance ===<br />
Last updated 2018-09-08 by fungi<br />
<br />
This team was disbanded during the Rocky cycle, morphing into the Extended Maintenance SIG.<br />
<br />
=== Storlets ===<br />
<br />
Update: August 9, ttx<br />
<br />
* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews<br />
* 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).<br />
* 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)<br />
<br />
=== Swift ===<br />
Update: July 3, smcginnis<br />
<br />
* Team has recently lost two very active long time cores<br />
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete<br />
* Changed their policy to only require one +2<br />
** Change in policy is allowing to land more code<br />
** No bad side effects of this change have been encountered so far<br />
* Some recent progress has been made on Python 3 compatibility<br />
<br />
=== Tacker ===<br />
Update: August 14th, 2018, TheJulia<br />
* Reached out via email to the new PTL to obtain their perspective as to the current status.<br />
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.<br />
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.<br />
<br />
Reported issues<br />
* Individual fragility: Yong Sheng Gong represents 75% of core reviews<br />
<br />
=== Telemetry ===<br />
Update: 2018-07-25, cdent<br />
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].<br />
* Lowish number of commits and reviews, but about what one would expect for a small and stable project<br />
* Effectively in maintenance mode<br />
* Some potential for greater engagement with Monasca<br />
* 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.<br />
<br />
=== Tricircle ===<br />
Reported issues<br />
* 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<br />
* email sent on July 18th 2018 (emilien)<br />
<br />
=== TripleO ===<br />
Update: June 13, emilien<br />
<br />
* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)<br />
* Number of contributors / core reviewers always increasing<br />
* Quite healthy, no problem reported so far<br />
<br />
=== Trove ===<br />
<br />
Reported issues<br />
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]<br />
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.<br />
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes<br />
<br />
Update: June 12, ttx<br />
<br />
* The team changed leadership in Rocky<br />
* Zhao Chao handles bulk of commits (51%)<br />
* The new team is small, but pretty alive and active. Needs more contributors to be stable.<br />
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)<br />
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens<br />
* 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.<br />
* Regular weekly meetings, well run with clear documentation of outcomes<br />
* Tracks completion of Rocky community goals<br />
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)<br />
* 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].<br />
* 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].<br />
* Reached out to PTL by email on June 12 for additional concerns / questions.<br />
<br />
=== Upgrade SIG ===<br />
WIP (emilien)<br />
<br />
=== Vitrage ===<br />
<br />
Reported issues<br />
* Organizational diversity fragility: Nokia represents 80% of core reviews<br />
* Affected by ZTE situation<br />
<br />
<br />
Update 2018-07-18 (dhellmann)<br />
* Meeting regularly on IRC<br />
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.<br />
* They usually have a hands-on lab at summits to attract users and potential contributors.<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
=== Watcher ===<br />
Update: 2018-07-10 TheJulia<br />
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.<br />
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.<br />
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.<br />
* 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.<br />
* Email sent to the PTL to initiate communication on July 2nd<br />
<br />
=== Winstackers ===<br />
Reported issues<br />
* Individual fragility: Claudiu Belu represents 100% of core reviews<br />
* Claudiu missed the deadline for being PTL but would like to continue<br />
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder<br />
* Increased release velocity by Microsoft means greater change in Hyper-V<br />
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV<br />
<br />
=== Zaqar ===<br />
Reported issues<br />
* zaqar and zaqar-ui missed the Rocky-2 milestone<br />
<br />
=== Zun ===<br />
<br />
* PTL and ~25% of commits (in Queens) are from ZTE<br />
* PTL non-responsive to email so far<br />
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)<br />
* Healthy-looking pace of development still happening<br />
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Berlin2018&diff=164570Forum/Berlin20182018-09-06T14:07:25Z<p>Lance Bragstad: /* Etherpads from Teams and Working Groups */</p>
<hr />
<div>The grand list of all of the Berlin 2018 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Vancouver Forum is the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Rocky''' release in mind. <br />
<br />
[[File:Forum_lead_up_brainstorming.png]]<br />
<br />
Your ideas are welcome! Either:<br />
* Add a link to an etherpad for all of your team's ideas on this wiki page<br />
* Contribute to the "catch-all" etherpads, linked below.<br />
<br />
and then discuss with everyone to refine and shortlist the best topics.<br />
<br />
Within two weeks, we will call for formal submission of your best ideas.<br />
<br />
==List of Etherpads==<br />
<big>Forum brainstorming for Berlin commences August 29th. Please add your etherpad of ideas below!</big><br />
<br />
====Catch-alls====<br />
If you want to post an idea, but aren't working with a specific team or working group, you can use these:<br />
* [https://etherpad.openstack.org/p/BER-TC-brainstorming Technical Committee Catch-all]<br />
* [https://etherpad.openstack.org/p/BER-UC-brainstorming User Committee Catch-all]<br />
<br />
====Etherpads from Teams and Working Groups====<br />
* [https://etherpad.openstack.org/p/AirshipBerlinForumBrainstorming Airship]<br />
* [https://etherpad.openstack.org/p/Berlin-stein-forum-blazar-brainstorming Blazar]<br />
* [https://etherpad.openstack.org/p/ECGBerlinForumBrainstorming Edge Computing Group]<br />
* [https://etherpad.openstack.org/p/FC_SIG_BER_Planning First Contact SIG]<br />
* [https://etherpad.openstack.org/p/BER-infra-brainstorming Infra/Winterscale/TBD]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-heat-brainstorming Heat]<br />
* [https://etherpad.openstack.org/p/BER-stein-forum-ironic-brainstorming Ironic]<br />
* [https://etherpad.openstack.org/p/KataBerlinForum Kata Containers]<br />
* [https://etherpad.openstack.org/p/BER-keystone-forum-sessions Keystone]<br />
* [https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming StarlingX]<br />
* [https://etherpad.openstack.org/p/BER-zuul-brainstorming Zuul]<br />
* [https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming QA]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=160006CrossProjectLiaisons2018-03-05T19:59:07Z<p>Lance Bragstad: /* Vulnerability management */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Cloudkitty || Christophe Sauthier || huats<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Bhagyashri Shewale|| bhagyashris<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || James Anziano || janzian<br />
|-<br />
| Nova || || <br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| Tricircle || Chaoyi Huang || joehuang<br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Petr Kovar || pkovar<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Ying Zuo || ying_zuo<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Keystone || Kristi Nikolla || knikolla<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStackClient || Doug Hellmann || dhellmann<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Packaging_Rpm || Dirk Mueller || dirk<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega || tenobreg/tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Storlets || Kota Tsuyuzaki || kota_<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tricircle || Zhiyuan Cai || zhiyuan<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Alexander Chadin || alexchadin<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Abhishek Kekane || abhishekk<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || ||<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Dustin Schoenbrun || dustins<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj <br />
|-<br />
| Congress || Aimee Ukasick || aimeeu<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Julia Kreger || TheJulia<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || || <br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Boden Russel || boden<br />
|-<br />
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Trevor McCasland || trevormc<br />
|-<br />
| Watcher || Prudhvi Rao Shedimbi || pshedimb<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Colleen Murphy || cmurphy<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Sam Matzek || smatzek<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Gage Hugo || gagehugo<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Manila || Tom Barron || tbarron<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| OpenStack-Ansible || Major Hayden || mhayden<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Manoj Kumar || kumarmn <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ironic || || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || ||<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me<br />
|-<br />
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Megan Rossetti || MeganR<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || || <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Watcher || Yumeng Bao || Yumeng <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean K. Mooney || sean-k-mooney || Neutron liaison for Nova<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Akihiro Motoki || amotoki || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|-<br />
| TripleO / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br />
|-<br />
| Nova / Watcher || || ||<br />
|-<br />
| || Ed Leafe || edleafe || Nova liaison for Watcher<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || ||<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Maciej Jozefczyk || mjozefcz<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=160005CrossProjectLiaisons2018-03-05T19:58:37Z<p>Lance Bragstad: /* Stable Branch */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Cloudkitty || Christophe Sauthier || huats<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Bhagyashri Shewale|| bhagyashris<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || James Anziano || janzian<br />
|-<br />
| Nova || || <br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| Tricircle || Chaoyi Huang || joehuang<br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Petr Kovar || pkovar<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Ying Zuo || ying_zuo<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Keystone || Kristi Nikolla || knikolla<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStackClient || Doug Hellmann || dhellmann<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Packaging_Rpm || Dirk Mueller || dirk<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega || tenobreg/tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Storlets || Kota Tsuyuzaki || kota_<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tricircle || Zhiyuan Cai || zhiyuan<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Alexander Chadin || alexchadin<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Abhishek Kekane || abhishekk<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || ||<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Dustin Schoenbrun || dustins<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj <br />
|-<br />
| Congress || Aimee Ukasick || aimeeu<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Julia Kreger || TheJulia<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || || <br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Boden Russel || boden<br />
|-<br />
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Trevor McCasland || trevormc<br />
|-<br />
| Watcher || Prudhvi Rao Shedimbi || pshedimb<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Colleen Murphy || cmurphy<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Sam Matzek || smatzek<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Manila || Tom Barron || tbarron<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| OpenStack-Ansible || Major Hayden || mhayden<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Manoj Kumar || kumarmn <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ironic || || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || ||<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me<br />
|-<br />
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Megan Rossetti || MeganR<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || || <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Watcher || Yumeng Bao || Yumeng <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean K. Mooney || sean-k-mooney || Neutron liaison for Nova<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Akihiro Motoki || amotoki || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|-<br />
| TripleO / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br />
|-<br />
| Nova / Watcher || || ||<br />
|-<br />
| || Ed Leafe || edleafe || Nova liaison for Watcher<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || ||<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Maciej Jozefczyk || mjozefcz<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=160004CrossProjectLiaisons2018-03-05T19:57:50Z<p>Lance Bragstad: /* Oslo */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Cloudkitty || Christophe Sauthier || huats<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Bhagyashri Shewale|| bhagyashris<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || James Anziano || janzian<br />
|-<br />
| Nova || || <br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| Tricircle || Chaoyi Huang || joehuang<br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Petr Kovar || pkovar<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Ying Zuo || ying_zuo<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Keystone || Kristi Nikolla || knikolla<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStackClient || Doug Hellmann || dhellmann<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Packaging_Rpm || Dirk Mueller || dirk<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Rally || Andrey Kurilin || andreykurilin<br />
|-<br />
| Sahara || Telles Nobrega || tenobreg/tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Storlets || Kota Tsuyuzaki || kota_<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tricircle || Zhiyuan Cai || zhiyuan<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Alexander Chadin || alexchadin<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Abhishek Kekane || abhishekk<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || ||<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Dustin Schoenbrun || dustins<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
| Zun || Hongbin Lu || hongbin <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj <br />
|-<br />
| Congress || Aimee Ukasick || aimeeu<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Julia Kreger || TheJulia<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || || <br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Boden Russel || boden<br />
|-<br />
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Trevor McCasland || trevormc<br />
|-<br />
| Watcher || Prudhvi Rao Shedimbi || pshedimb<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Sam Matzek || smatzek<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme <br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Manila || Tom Barron || tbarron<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| OpenStack-Ansible || Major Hayden || mhayden<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Manoj Kumar || kumarmn <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ironic || || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito<br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || ||<br />
|-<br />
| I18n || Frank Kloeker || eumel8<br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me<br />
|-<br />
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Manoj Kumar || kumarmn<br />
|-<br />
| Watcher || Megan Rossetti || MeganR<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || || <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Watcher || Yumeng Bao || Yumeng <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean K. Mooney || sean-k-mooney || Neutron liaison for Nova<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Akihiro Motoki || amotoki || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|-<br />
| TripleO / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br />
|-<br />
| Nova / Watcher || || ||<br />
|-<br />
| || Ed Leafe || edleafe || Nova liaison for Watcher<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Eric Kao || ekcs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || ||<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Telles Nobrega || tellesnobrega<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Maciej Jozefczyk || mjozefcz<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
| Zun || Hongbin Lu || hongbin<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=PTG/Rocky/Etherpads&diff=159746PTG/Rocky/Etherpads2018-02-21T20:47:03Z<p>Lance Bragstad: </p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Dublin. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
Sign up for [https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0 team video interviews].<br />
<br />
For what's happening '''right now''' (during the event), see the [http://ptg.openstack.org/ptg.html ptgbot page].<br />
<br />
'''Projects:''' <br />
* Blazar - https://etherpad.openstack.org/p/blazar-ptg-rocky<br />
* Cinder - https://etherpad.openstack.org/p/cinder-ptg-rocky<br />
* Cyborg - https://etherpad.openstack.org/p/cyborg-ptg-rocky <br />
* Docs/I18n - https://etherpad.openstack.org/p/docs-i18n-ptg-rocky<br />
* Glance - https://etherpad.openstack.org/p/glance-rocky-ptg-planning<br />
* Heat - https://etherpad.openstack.org/p/heat-rocky-ptg<br />
* Horizon - https://etherpad.openstack.org/p/horizon-ptg-rocky<br />
* Infra - https://etherpad.openstack.org/p/infra-rocky-ptg<br />
* Ironic - https://etherpad.openstack.org/p/ironic-rocky-ptg<br />
* Keystone - https://etherpad.openstack.org/p/keystone-rocky-ptg<br />
* Kolla - https://etherpad.openstack.org/p/kolla-rocky-ptg-planning<br />
* Kuryr - https://etherpad.openstack.org/p/kuryr-ptg-rocky<br />
* Magnum - https://etherpad.openstack.org/p/magnum-ptg-rocky<br />
* Manila - https://etherpad.openstack.org/p/manila-rocky-ptg<br />
* Mistral - https://etherpad.openstack.org/p/mistral-ptg-rocky<br />
* Monasca - https://etherpad.openstack.org/p/monasca-ptg-rocky<br />
* Neutron - https://etherpad.openstack.org/p/neutron-ptg-rocky<br />
* Nova - https://etherpad.openstack.org/p/nova-ptg-rocky<br />
* Octavia - https://etherpad.openstack.org/p/octavia-ptg-rocky<br />
* Openstack-Ansible - https://etherpad.openstack.org/p/osa-rocky-ptg<br />
* OpenStack-Helm - https://etherpad.openstack.org/p/openstack-helm-ptg-rocky<br />
* Oslo - https://etherpad.openstack.org/p/oslo-ptg-rocky<br />
* QA - https://etherpad.openstack.org/p/qa-rocky-ptg<br />
* RelMgt - https://etherpad.openstack.org/p/relmgt-ptg-rocky<br />
* Requirements - https://etherpad.openstack.org/p/rocky-PTG-requirements<br />
* Sahara - https://etherpad.openstack.org/p/sahara-rocky-ptg<br />
* Swift - https://etherpad.openstack.org/p/Dublin_PTG_Swift<br />
* TripleO - https://etherpad.openstack.org/p/tripleo-ptg-rocky<br />
* Vitrage - https://etherpad.openstack.org/p/vitrage-ptg-rocky<br />
* Watcher - https://etherpad.openstack.org/p/rocky-watcher-ptg<br />
<br />
<br />
'''SIG/Theme/Other:'''<br />
* API SIG - https://etherpad.openstack.org/p/api-sig-ptg-rocky<br />
* First Contact SIG - https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG<br />
* Fast-forward Upgrades - https://etherpad.openstack.org/p/ffu-ptg-rocky<br />
* OpenStack Upstream Institute (OUI): https://etherpad.openstack.org/p/OUI-Rocky-PTG <br />
* Public Cloud WG - https://etherpad.openstack.org/p/publiccloud-wg-ptg-rocky<br />
* Security SIG - https://etherpad.openstack.org/p/security-ptg-rocky<br />
* StoryBoard: https://etherpad.openstack.org/p/StoryBoard-Rocky-PTG<br />
* TC (Friday) - https://etherpad.openstack.org/p/PTG-Dublin-TC-topics<br />
* UC (Tuesday) - https://etherpad.openstack.org/p/ptg-dublin-user-committee<br />
* Cross-project identity integration (Monday & Tuesday) - https://etherpad.openstack.org/p/baremetal-vm-rocky-ptg</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=PTG/Rocky/Etherpads&diff=159002PTG/Rocky/Etherpads2018-01-17T14:46:55Z<p>Lance Bragstad: </p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Dublin. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
Sign up for [https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0 team video interviews].<br />
<br />
For what's happening '''right now''' (during the event), see the [http://ptg.openstack.org/ptg.html ptgbot page].<br />
<br />
* Sahara - https://etherpad.openstack.org/p/sahara-rocky-ptg<br />
* Ironic - https://etherpad.openstack.org/p/ironic-rocky-ptg<br />
* Keystone - https://etherpad.openstack.org/p/keystone-rocky-ptg<br />
* Manila - https://etherpad.openstack.org/p/manila-rocky-ptg<br />
* TripleO - https://etherpad.openstack.org/p/tripleo-ptg-rocky</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157725Forum/Sydney20172017-11-06T06:30:55Z<p>Lance Bragstad: /* Wednesday, November 8 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1135-1215] Missing Features and Making Improvements to OpenStack Health https://etherpad.openstack.org/p/SYD-forum-openstack-health-feedback<br />
* [1135-1215] Improving Gopher Cloud and OpenStack K8s Provider https://etherpad.openstack.org/p/SYD-improving-gopher-cloud<br />
* [1330-1410] Kolla Ops feedback session http://etherpad.openstack.org/p/kolla-sydney-ops-feedback<br />
* [1330-1410] Glance Project Onboarding https://etherpad.openstack.org/p/SYD-forum-glance-onboarding<br />
* [1330-1410] Ops Guide Transition and Maintenance https://etherpad.openstack.org/p/SYD-forum-ops-guide-transition<br />
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding] <br />
https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding<br />
* [1420-1500] Interop Working Group Community Feedback and Work Session https://etherpad.openstack.org/p/SYD-interop-working-group<br />
* [1420-1500] Installation Guides and Tutorials Updates and Testing https://etherpad.openstack.org/p/SYD-install-guide-testing<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
*[1510-1550] Fog/Edge/Massively Distributed Clouds (FEMDC) SIG- https://etherpad.openstack.org/p/FEMDC-F2F-meeting-sydney-summit<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1620-1700] Privsep: what is it and operational impacts https://etherpad.openstack.org/p/SYD-forum-privsep<br />
* [1620-1700] User Survey Feedback https://etherpad.openstack.org/p/UserSurveyFeedback<br />
* [1710-1750] What Do Operators Want from Stable Policy https://etherpad.openstack.org/p/SYD-stable-policy<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Self-healing and optimization SIG https://etherpad.openstack.org/p/self-healing-rocky-forum<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0900-0940] Interop Test Library for OpenStack SDKs https://etherpad.openstack.org/p/SYD-forum-sdk-interop-test-library<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [0950-1030] Zuul v3 Feedback Session https://etherpad.openstack.org/p/SYD-zuul-v3-feedback<br />
* [0950-1030] Charms User Feedback session https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback<br />
* [1050-1130] The State of Test Runners and Moving to stestr https://etherpad.openstack.org/p/SYD-forum-test-runners<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1140-1220] openstack-sig-k8s and k8s-sig-openstack collaborations https://etherpad.openstack.org/p/SYD-openstack-sig-k8s-collaborations<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1610-1650] Glance: Operators Feedback Session https://etherpad.openstack.org/p/SYD-forum-glance-feedback<br />
* [1610-1650] OpenStackClient and Nova API microversions https://etherpad.openstack.org/p/SYD-forum-nova-osc<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [0950-1030] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20473/openstack-public-cloud-passport-program OpenStack Public Cloud Passport Program] https://etherpad.openstack.org/p/SYD-forum-public-cloud<br />
* [1100-1140] Bare metal as a service: Ironic vs. Mogan vs. Nova https://etherpad.openstack.org/p/SYD-forum-baremetal-ironic-mogan-nova<br />
* [1100-1140] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] <br />
https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1150-1230] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19798/features-missing-in-openstack-core-for-public-cloud-providers Features missing in OpenStack core for Public Cloud Providers] https://etherpad.openstack.org/p/SYD-forum-missing-features-pc<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1530-1610] Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop https://etherpad.openstack.org/p/SYD-refstack-nfv<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1630-1710] Heat ops and users feedback https://etherpad.openstack.org/p/Sydney-heat-ops-and-users-feedback<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157724Forum/Sydney20172017-11-06T06:30:25Z<p>Lance Bragstad: /* Monday, November 6 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1135-1215] Missing Features and Making Improvements to OpenStack Health https://etherpad.openstack.org/p/SYD-forum-openstack-health-feedback<br />
* [1135-1215] Improving Gopher Cloud and OpenStack K8s Provider https://etherpad.openstack.org/p/SYD-improving-gopher-cloud<br />
* [1330-1410] Kolla Ops feedback session http://etherpad.openstack.org/p/kolla-sydney-ops-feedback<br />
* [1330-1410] Glance Project Onboarding https://etherpad.openstack.org/p/SYD-forum-glance-onboarding<br />
* [1330-1410] Ops Guide Transition and Maintenance https://etherpad.openstack.org/p/SYD-forum-ops-guide-transition<br />
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding] <br />
https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding<br />
* [1420-1500] Interop Working Group Community Feedback and Work Session https://etherpad.openstack.org/p/SYD-interop-working-group<br />
* [1420-1500] Installation Guides and Tutorials Updates and Testing https://etherpad.openstack.org/p/SYD-install-guide-testing<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
*[1510-1550] Fog/Edge/Massively Distributed Clouds (FEMDC) SIG- https://etherpad.openstack.org/p/FEMDC-F2F-meeting-sydney-summit<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1620-1700] Privsep: what is it and operational impacts https://etherpad.openstack.org/p/SYD-forum-privsep<br />
* [1620-1700] User Survey Feedback https://etherpad.openstack.org/p/UserSurveyFeedback<br />
* [1710-1750] What Do Operators Want from Stable Policy https://etherpad.openstack.org/p/SYD-stable-policy<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Self-healing and optimization SIG https://etherpad.openstack.org/p/self-healing-rocky-forum<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0900-0940] Interop Test Library for OpenStack SDKs https://etherpad.openstack.org/p/SYD-forum-sdk-interop-test-library<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [0950-1030] Zuul v3 Feedback Session https://etherpad.openstack.org/p/SYD-zuul-v3-feedback<br />
* [0950-1030] Charms User Feedback session https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback<br />
* [1050-1130] The State of Test Runners and Moving to stestr https://etherpad.openstack.org/p/SYD-forum-test-runners<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1140-1220] openstack-sig-k8s and k8s-sig-openstack collaborations https://etherpad.openstack.org/p/SYD-openstack-sig-k8s-collaborations<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1610-1650] Glance: Operators Feedback Session https://etherpad.openstack.org/p/SYD-forum-glance-feedback<br />
* [1610-1650] OpenStackClient and Nova API microversions https://etherpad.openstack.org/p/SYD-forum-nova-osc<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [0950-1030] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20473/openstack-public-cloud-passport-program OpenStack Public Cloud Passport Program] https://etherpad.openstack.org/p/SYD-forum-public-cloud<br />
* [1100-1140] Bare metal as a service: Ironic vs. Mogan vs. Nova https://etherpad.openstack.org/p/SYD-forum-baremetal-ironic-mogan-nova<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1150-1230] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19798/features-missing-in-openstack-core-for-public-cloud-providers Features missing in OpenStack core for Public Cloud Providers] https://etherpad.openstack.org/p/SYD-forum-missing-features-pc<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1530-1610] Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop https://etherpad.openstack.org/p/SYD-refstack-nfv<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1630-1710] Heat ops and users feedback https://etherpad.openstack.org/p/Sydney-heat-ops-and-users-feedback<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157656Forum/Sydney20172017-11-01T18:21:45Z<p>Lance Bragstad: /* Monday, November 6 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1420-1500] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20434/keystone-project-onboarding Keystone Project Onboarding] https://etherpad.openstack.org/p/SYD-forum-keystone-project-onboarding<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157655Forum/Sydney20172017-11-01T18:20:12Z<p>Lance Bragstad: /* Tuesday, November 7 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
* [1750-1830] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20502/keystone-operator-and-user-feedback Keystone Operator & User Feedback] https://etherpad.openstack.org/p/SYD-forum-keystone-feedback<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157654Forum/Sydney20172017-11-01T18:18:54Z<p>Lance Bragstad: /* Monday, November 6 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20453/application-credentials-feedback Application Credentials Feedback] https://etherpad.openstack.org/p/SYD-forum-application-credentials-feedback<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157653Forum/Sydney20172017-11-01T18:17:55Z<p>Lance Bragstad: /* Monday, November 6 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20452/rbacpolicy-roadmap-feedback RBAC/Policy Roadmap Feedback] https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Sydney2017&diff=157652Forum/Sydney20172017-11-01T18:17:22Z<p>Lance Bragstad: /* Monday, November 6 */</p>
<hr />
<div>The grand list of all of the Sydney 2017 [[Forum]] etherpads. Please add links to etherpads below!<br />
<br />
At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Sydney Forum is the start of the planning phase for the '''Rocky''' development cycle. Please prepare session ideas with feedback from the '''Pike''' release in mind.<br />
<br />
See also - [https://www.openstack.org/summit/sydney-2017/summit-schedule/#tracks=157 Full Forum Schedule]<br />
<br />
===Monday, November 6===<br />
* [1135-1215] Forum 101 https://etherpad.openstack.org/p/SYD-forum-101<br />
* [1135-1215] API-SIG https://etherpad.openstack.org/p/api-sig-sydney-forum<br />
* [1510-1550] Fast-Forward Upgrades https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades<br />
* [1510-1550] RBAC/Policy Roadmap Feedback https://etherpad.openstack.org/p/SYD-forum-policy-roadmap-feedback<br />
* [1620-1700] Protecting Plaintext Passwords in Configuration Files https://etherpad.openstack.org/p/plaintext-secrets<br />
* [1620-1700] TripleO onboarding https://etherpad.openstack.org/p/SYD-forum-tripleo-onboarding<br />
* [1710-1750] Cinder/Nova Cross Project Session on Multi-Attach https://etherpad.openstack.org/p/sydney-cinder-nova-cp-multi-attach<br />
<br />
===Tuesday, November 7===<br />
* [0900-0940] Nova project onboarding https://etherpad.openstack.org/p/SYD-forum-nova-onboarding<br />
* [0950-1030] Making OpenStack more palatable to part-time contributors https://etherpad.openstack.org/p/SYD-part-time-contributors<br />
* [1050-1130] SIGs II: to infinity and beyond https://etherpad.openstack.org/p/SYD-SIGs<br />
* [1050-1130] Edge Computing Use Cases and Architecture https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<br />
* [1350-1430] Supporting General Federation for Large-Scale Collaborations https://etherpad.openstack.org/p/Supporting-General-Federation<br />
* [1350-1430] [https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20470/extremedestructive-testing Extreme/Destructive Testing] https://etherpad.openstack.org/p/SYD-extreme-testing<br />
* [1520-16:00] Ops Meetup Team catch-up https://etherpad.openstack.org/p/SYD-Ops_Meetup_Team_catch-up<br />
* [1700-1740] Ceph in OpenStack BoF https://etherpad.openstack.org/p/SYD-forum-Ceph-OpenStack-BoF<br />
* [1750-1830] Cells v2 update and direction https://etherpad.openstack.org/p/SYD-forum-nova-cellsv2-update<br />
<br />
===Wednesday, November 8===<br />
* [0900-0940] Upstream LTS Releases https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases<br />
* [0900-0940] Hardware in the Cloud https://etherpad.openstack.org/p/SYD-forum-hardware-clouds<br />
* [0950-1030] ETSI NFV Specs’ Requirements vs OpenStack Reality forum https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained<br />
* [1150-1230] Watcher users feedback https://etherpad.openstack.org/p/watcher-sydney-forum<br />
* [1350-1430] Placement update and direction https://etherpad.openstack.org/p/SYD-forum-nova-placement-update<br />
* [1440-1520] Nova: Queens roadmap and checkpoint https://etherpad.openstack.org/p/SYD-forum-nova-queens-update<br />
* [1630-1710] OpenStack Foundation update https://etherpad.openstack.org/p/SYD-foundation-update<br />
* [1720-1800] Technical Committee in-person office hour https://etherpad.openstack.org/p/SYD-tc-office-hour</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=PTG/Queens/Etherpads&diff=156239PTG/Queens/Etherpads2017-08-24T14:58:27Z<p>Lance Bragstad: /* Monday -> Tuesday */</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Denver. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
For what's happening '''right now''', see the [http://ptg.openstack.org/ptg.html ptgbot page].<br />
<br />
=== Whole Week ===<br />
* Infra: https://etherpad.openstack.org/p/infra-ptg-queens<br />
* QA: https://etherpad.openstack.org/p/qa-queens-ptg<br />
<br />
=== Monday -> Tuesday ===<br />
* API: https://etherpad.openstack.org/p/api-ptg-queens<br />
* CLI (OpenStackClient, OpenStackSDK, Shade, etc): https://etherpad.openstack.org/p/osc-queens-ptg<br />
* Docs: https://etherpad.openstack.org/p/denver-doc-PTG<br />
* ETSI NFV & OpenStack Workshop: https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver<br />
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-queens<br />
* i18n: https://etherpad.openstack.org/p/denver-i18n-PTG<br />
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-queens<br />
* Refstack: https://etherpad.openstack.org/p/InteropDenver2017PTG<br />
* Requirements: https://etherpad.openstack.org/p/queens-PTG-requirements<br />
* Skip Level Upgrades: https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades<br />
* Stable: https://etherpad.openstack.org/p/queens-PTG-stable<br />
* Technical Committee / Stewardship WG: https://etherpad.openstack.org/p/queens-PTG-TC-SWG<br />
* VM & BM SIG: https://etherpad.openstack.org/p/queens-PTG-vmbm<br />
* Policy Goals: https://etherpad.openstack.org/p/policy-queens-ptg<br />
<br />
=== Wednesday -> Thursday ===<br />
* Barbican: https://etherpad.openstack.org/p/barbican-ptg-queens<br />
* Charms: https://etherpad.openstack.org/p/ptg-queens-charms<br />
* Congress: https://etherpad.openstack.org/p/congress-ptg-queens<br />
* Freezer: https://etherpad.openstack.org/p/freezer-ptg-queens<br />
* Glare: https://etherpad.openstack.org/p/glare-ptg-queens<br />
* Heat: https://etherpad.openstack.org/p/heat-queens-ptg<br />
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-queens<br />
* Puppet: https://etherpad.openstack.org/p/puppet-queens-ptg <br />
* Sahara: https://etherpad.openstack.org/p/sahara-queens-ptg<br />
* Trove: https://etherpad.openstack.org/p/trove-queens-ptg<br />
<br />
=== Wednesday -> Friday ===<br />
* Ansible: https://etherpad.openstack.org/p/osa-denver-PTG-planning<br />
* Cinder: https://etherpad.openstack.org/p/cinder-ptg-queens<br />
* Glance: https://etherpad.openstack.org/p/glance-queens-ptg-planning <br />
* Ironic: https://etherpad.openstack.org/p/ironic-queens-ptg<br />
* Keystone: https://etherpad.openstack.org/p/keystone-queens-ptg<br />
* Kolla: https://etherpad.openstack.org/p/kolla-queens-ptg-planning<br />
* Neutron: https://etherpad.openstack.org/p/neutron-queens-ptg<br />
* Nova: https://etherpad.openstack.org/p/nova-ptg-queens<br />
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-queens<br />
* Swift: https://etherpad.openstack.org/p/swift-ptg-queens<br />
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-queens<br />
<br />
=== Not In Denver ===<br />
Some teams will not be meeting in Denver but will have separate PTG events.<br />
<br />
* Manila: https://etherpad.openstack.org/p/manila-ptg-queens</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Meetings/Nova&diff=154552Meetings/Nova2017-06-07T16:47:19Z<p>Lance Bragstad: /* Agenda for next meeting */</p>
<hr />
<div><br />
= Weekly Nova team meeting =<br />
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)'''<br />
<br />
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]]. We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.<br />
<br />
NOTE: this wiki page should be 'emptied' at the end of each meeting.<br />
<br />
== Agenda for next meeting ==<br />
<br />
Next meetings scheduled for:<br />
<br />
* June 1st 2017 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170601T140000)<br />
* June 8th 2017 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170608T210000)<br />
* June 15th 2017 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170615T140000)<br />
<br><br />
<br />
Where you see "?" feel free to just edit the wiki and add your item.<br />
<br />
Here is the agenda for the next meeting:<br />
* Release News<br />
** #link Pike release schedule: https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule<br />
** #info Next upcoming milestone: Jun 8: p-2 milestone (1 week)<br />
** #info Blueprints: 72 targeted, 68 approved, 15 completed, 4 not started<br />
** #info Blueprints which are blocked, not started or do not have an owner after the p-2 milestone will likely be deferred to Queens.<br />
* Bugs (stuck/critical)<br />
** [https://bugs.launchpad.net/nova/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bugs]<br />
** #help Need help with bug triage; there are 93 (down 11 from last week) new untriaged bugs as of today (June 1).<br />
** Gate status<br />
*** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html<br />
** 3rd party CI<br />
*** #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days<br />
*** #info XenServer CI is having some known issues with Tempest SSH validation enabled by default; has been removed from nova-ci voting group for now.<br />
* Reminders<br />
** #link Pike Review Priorities etherpad: https://etherpad.openstack.org/p/pike-nova-priorities-tracking<br />
* Stable branch status:<br />
** #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z<br />
*** #info Ocata 15.0.5 has been released.<br />
** #link stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z<br />
*** #info Newton 14.0.7 has been released.<br />
* Subteam Highlights<br />
** Cells v2 (dansmith)<br />
** Scheduler (edleafe)<br />
** API (sdague/alex_xu)<br />
** Notification (gibi) - no meeting this week, back next week<br />
** Cinder (mriedem) - #link need reviews starting here https://review.openstack.org/#/c/469579/ to use new microversion when attaching volumes<br />
* Stuck Reviews<br />
** Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.<br />
** Any stuck code reviews to discuss:<br />
*** ?<br />
* Open discussion<br />
** (mhenkel): Can https://blueprints.launchpad.net/nova/+spec/opencontrail-dpdk-support for a new VIF be approved as a spec-less blueprint?<br />
** (lbragstad): Feedback on policy approach<br />
<br />
== Sub-teams ==<br />
<br />
There are also some Nova subteam meetings. See [[Nova#Active_Sub-teams:]] for details.<br />
<br />
== Previous meetings ==<br />
<br />
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]<br />
<br />
[[category: compute]]<br />
[[category: meetings]]</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153589Forum/Boston20172017-04-26T14:17:06Z<p>Lance Bragstad: /* Wednesday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
= Monday =<br />
* Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [3:40pm-4:20pm] Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
<br />
= Tuesday =<br />
* https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
<br />
<br />
<br />
<br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
<br />
<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153588Forum/Boston20172017-04-26T14:15:20Z<p>Lance Bragstad: /* Monday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
= Monday =<br />
* Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [3:40pm-4:20pm] Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
<br />
= Tuesday =<br />
* https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
<br />
<br />
<br />
<br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
<br />
<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153587Forum/Boston20172017-04-26T14:13:42Z<p>Lance Bragstad: /* Monday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
= Monday =<br />
* Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
<br />
= Tuesday =<br />
* https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
<br />
<br />
<br />
<br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
<br />
<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=152458Forum/Boston20172017-03-17T21:03:20Z<p>Lance Bragstad: /* Project Teams */</p>
<hr />
<div>__NOTOC__<br />
The grand list of all of the Boston Forum etherpads. Please include the name of the team that started the pad.<br />
<br />
==Catch-alls==<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
==Project Teams==<br />
<br />
===Barbican===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
===Cinder===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
===Freezer===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
===Glance===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
===Heat===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
===I18n===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
===Keystone===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
===Nova===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
===Watcher===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
===QA===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
===Swift===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
==UC Working Groups ==<br />
<br />
<br />
<br />
===Telecom/NFV Requirements===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
===Scientific WG===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
===Massively Distributed (Fog/Edge) WG===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
===Public Cloud WG===<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
==Other Working Groups==<br />
<br />
===VM and Bare-metal platform group===<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=151736CrossProjectLiaisons2017-03-03T16:10:24Z<p>Lance Bragstad: /* Release management */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || || <br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Elise Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Alexander Chadin || alexchadin<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || - || -<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || || <br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || Trevor McCasland || trevormc<br />
|-<br />
| Watcher || Prudhvi Rao Shedimbi || pshedimb<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco|| flaper87<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio || njohnston, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Nikita Konovalov, Vitaliy Gridnev || Nikita Konovalov, Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || - || -<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Megan Rossetti || MeganR<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Watcher || Yumeng Bao || Yumeng <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || || ||<br />
|-<br />
| || Jim Rollenhagen || jroll || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|-<br />
| TripleO / Ironic || || ||<br />
|-<br />
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br />
|-<br />
| Nova / Watcher || || ||<br />
|-<br />
| || Ed Leafe || edleafe || Nova liaison for Watcher<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=151137CrossProjectLiaisons2017-02-14T19:32:44Z<p>Lance Bragstad: /* Infra */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Ruby Loo || rloo<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || ChangBo Guo || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Elise Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || || <br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || || <br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen || dtantsur, jroll<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio || njohnston, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Nikita Konovalov, Vitaliy Gridnev || Nikita Konovalov, Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=151136CrossProjectLiaisons2017-02-14T19:32:14Z<p>Lance Bragstad: /* Infra */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Ruby Loo || rloo<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || ChangBo Guo || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Elise Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || || <br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || || <br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen || dtantsur, jroll<br />
|-<br />
| Keystone || Rodrigo Duarte, Lance Bragstad || rodrigods, lbragstad<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio || njohnston, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Nikita Konovalov, Vitaliy Gridnev || Nikita Konovalov, Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=151133CrossProjectLiaisons2017-02-14T19:06:56Z<p>Lance Bragstad: /* QA */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Ruby Loo || rloo<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || ChangBo Guo || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Elise Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || Rodrigo Duarte || rodrigods<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || Robert Starmer || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || || <br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || || <br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen || dtantsur, jroll<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio || njohnston, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Nikita Konovalov, Vitaliy Gridnev || Nikita Konovalov, Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=150993CrossProjectLiaisons2017-02-10T17:02:42Z<p>Lance Bragstad: /* Documentation */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Ruby Loo || rloo<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Victor Morales || electrocucaracha<br />
|-<br />
| Nova || ChangBo Guo || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Elise Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Ian Cordasco || sigmavirus<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Jeffrey Zhang || Jeffrey4l<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Dariusz Smigiel || dasm<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br />
|-<br />
| Oslo || Joshua Harlow || harlowja<br />
|-<br />
| PuppetOpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Winstackers || Claudiu Belu || claudiub<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || Thiago da Silva || tdasilva<br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Alexander Bashmakov || abashmak<br />
|-<br />
| Heat || Rabi Mishra || ramishra<br />
|-<br />
| Horizon || Richard Jones || r1chardj0n3s<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Richard Avelar || ravelar<br />
|-<br />
| Kolla || Sayantani Goswami || sayantani01<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Dougal Matthews || d0ugal<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || John Davidge || john-davidge<br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| OpenStack-Ansible || Amy Marrich || spotz<br />
|-<br />
| Ops || || <br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || Boris Pavlovic || boris-42<br />
|-<br />
| Sahara || || <br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tripleo || Steven Hardy || shardy<br />
|-<br />
| Trove || || <br />
|-<br />
| Watcher || Antoine Cabot || acabot<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Dave McCowan || dave-mccowan<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || Matthew Oliver || mattoliverau <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || David Tardivel || dtardivel<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| Ironic || Jay Faulkner || JayF<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Michal Jastrzebski || inc0<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || ||<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Ironic || Dmitry Tantsur, Jim Rollenhagen || dtantsur, jroll<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Nate Johnston, Armando Migliaccio || njohnston, armax<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Nikita Konovalov, Vitaliy Gridnev || Nikita Konovalov, Vitaliy Gridnev<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
<br />
|-<br />
| TripleO || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || carolbarrett<br />
|-<br />
| Ironic || Yih Leong Sun || leong<br />
|-<br />
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br />
|-<br />
| Kolla || Yih Leong Sun || leong<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manila ||Pete Chadwick || pchadwick<br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| QA || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Rally || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Sahara || Elise Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Akihiro Motoki || amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| TripleO || Julie Pichon || jpich<br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Kevin Benton || kevinbenton || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Sam Betts || sambetts || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|-<br />
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Swapnil Kulkarni || coolsvap<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Adrian Otto || adrian_otto<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Kevin Benton || kevinbenton<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Alex Schultz || mwhahaha<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Steve McLellan || sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Sprints/KeystoneNewtonSprint&diff=125426Sprints/KeystoneNewtonSprint2016-05-17T18:16:23Z<p>Lance Bragstad: /* Hotels */</p>
<hr />
<div>The Keystone team is having their Newton mid-cycle meetup in San Jose, CA, USA.<br />
<br />
* Where: Cisco Campus, San Jose, CA (TBD on specific address and building)<br />
* When: July 20-22 2016<br />
<br />
== Event Details ==<br />
* [https://docs.google.com/forms/d/1To2qx90Am4hcYdgaqTkRosfNOzxr26M0GiahhiWgAJU/viewform RSVP Form]<br />
* Etherpad: https://etherpad.openstack.org/p/keystone-newton-midcycle<br />
* Location<br />
** Cisco Campus, 170 W Tasman Dr, San Jose, CA 95134<br />
*** Specific Rooms/Building TBD<br />
** [https://www.google.com/maps/place/Cisco+Bldg+D,+170+W+Tasman+Dr,+San+Jose,+CA+95134/@37.4083511,-121.956273,17z/data=!3m1!4b1!4m5!3m4!1s0x808fc9af235bc7f5:0x502c319534361879!8m2!3d37.4083511!4d-121.954079 Google Maps]<br />
<br />
== Travel ==<br />
<br />
* Options are typically flying into SFO, OAK, or SJC and then travelling to the office.<br />
<br />
== Hotels ==<br />
<br />
[https://www.google.com/maps/place/Courtyard+San+Jose+North%2FSilicon+Valley/@37.4106295,-121.9668618,15z/data=!4m15!1m9!2m8!1sHotels!3m6!1sHotels!2sCisco+Building+H,+250+W+Tasman+Dr,+San+Jose,+CA+95134!3s0x808fc9adfcd07613:0xaa3aaad96c1bbdfe!4m2!1d-121.958107!2d37.4106086!3m4!1s0x0:0xeb16e32f4d1b1028!8m2!3d37.4189041!4d-121.9540747 Hotels] near the Cisco Campus.<br />
<br />
== General Help and Visas ==<br />
<br />
* TBD</div>Lance Bragstadhttps://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&diff=98442Meetings/KeystoneMeeting2015-12-01T18:06:09Z<p>Lance Bragstad: /* Keystone Weekly Bug Reports */</p>
<hr />
<div>= Weekly Keystone team meeting =<br />
<br />
If you're interested in identity, authentication, authorization, and/or policy for OpenStack, we hold public meetings weekly on [[IRC]] in <code><nowiki>#openstack-meeting</nowiki></code>, on [https://www.google.com/search?q=current+utc+time Tuesdays at 18:00 UTC]. Please feel free to add items to the agenda below with your name and we'll cover them.<br />
<br />
== Regular attendees ==<br />
<br />
Add yourself to this list to be pinged prior to each meeting:<br />
<br />
ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rodrigods, roxanaghe, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub, rderose, samleon, xek, MaxPC, tjcocozz<br />
<br />
== Agenda for next meeting ==<br />
<br />
==== Main Agenda ====<br />
Please add agenda items to the bottom of this section's list (be sure to include your <code>irc_handle</code>!).<br />
<br />
<b>2015-12-01</b><br />
* Roll call for keystone-specs <code>stevemar</code><br />
<br />
==== Review of Keystone Blueprints for No-Spec Requires Status ====<br />
Please add BPs to the bottom of this sections list that should be reviewed as not requiring a spec (include your <code>irc_handle</code>!).<br />
<br />
==== Keystone Weekly Bug Reports ====<br />
Bugs for the various Keystone repositories are collects and published to the following links. (<code>lbragstad</code>)<br />
* [http://openstack-weekly-reports.lbragstad.com/keystone-weekly-bug-report.html Keystone Weekly Bug Report]<br />
<br />
== Previous meetings ==<br />
<br />
Logs and meeting summaries of previous meetings are located [http://eavesdrop.openstack.org/meetings/keystone/ here].</div>Lance Bragstad