Jump to: navigation, search

Difference between revisions of "OpenStack health tracker"

(Heat)
(Shut down the health tracker)
 
(194 intermediate revisions by 16 users not shown)
Line 1: Line 1:
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.
+
'''This page is no longer in use.''' During discussions at the Train cycle PTG, the OpenStack TC concluded that its experiments in formally tracking problems within individual project teams was not providing enough value for the investment of effort it required. The component of it which is still deemed valuable is having specific TC members officially assigned as liaisons to each project team, so in future that will continue but will be documented in the openstack/governance Git repository's project metadata and on the project pages linked from the https://governance.openstack.org/reference/projects/ page.
 
 
Liaisons should monitor their groups by:
 
* reading meeting logs or participating in meetings
 
* watching summit "project update" videos
 
* reading relevant messages on the mailing list
 
* talking with the PTL, chair, and other group members
 
* checking contribution rates and review turnaround times
 
 
 
== Liaisons ==
 
=== SIGs ===
 
 
 
{| class="wikitable"
 
|-
 
! Group !! TC members
 
|-
 
| API
 
||  mugsie
 
|-
 
| First Contact
 
||  fungi
 
|-
 
| K8s
 
||  dims
 
|-
 
| Meta
 
|| dhellmann
 
|-
 
| Resource Management
 
|| cdent
 
|-
 
| Scientific
 
|| pabelanger
 
|-
 
| Security
 
||  fungi
 
|-
 
| Self-healing
 
|| zaneb
 
|-
 
| Upgrade
 
|| emilien
 
|}
 
 
 
=== Working Groups ===
 
 
 
{| class="wikitable"
 
|-
 
! Group !! TC members
 
|-
 
| App Dev Enablement
 
|| zaneb
 
|-
 
| [[Diversity]]
 
|| fungi
 
|-
 
| Enterprise
 
||
 
|-
 
| Fault Genes
 
||
 
|-
 
| [[InteropWG|Interop]]
 
||  dims, fungi
 
|-
 
| LCOO
 
||
 
|-
 
| Large Deployment
 
|| pabelanger
 
|-
 
| Edge/Massively Distributed Clouds
 
|| ttx
 
|-
 
| Operators Telecom/NFV
 
||  smcginnis
 
|-
 
| Ops Tags
 
||  smcginnis
 
|-
 
| Product
 
||
 
|-
 
| [[ProfessionalCertification]]
 
||
 
|-
 
| Public Cloud
 
||  ttx
 
|}
 
 
 
=== Project Teams ===
 
 
 
{| class="wikitable"
 
|-
 
! Group !! TC members
 
|-
 
| Barbican
 
||  fungi, ttx
 
|-
 
| Blazar
 
||  cmurphy, mnaser
 
|-
 
| Chef Openstack
 
||  pabelanger, mnaser
 
|-
 
| Cinder
 
||  smcginnis, dims
 
|-
 
| Cloudkitty
 
||  ttx, dims
 
|-
 
| Congress
 
||  cdent, fungi
 
|-
 
| Cyborg
 
|| ttx, TheJulia
 
|-
 
| Designate
 
||  cmurphy, cdent
 
|-
 
| Documentation
 
||  dhellmann, pabelanger
 
|-
 
| Dragonflow
 
||  dims, cdent
 
|-
 
| Ec2-Api
 
||  TheJulia, cmurphy
 
|-
 
| Freezer
 
||  ttx, mugsie
 
|-
 
| Glance
 
||  smcginnis, mugsie
 
|-
 
| Heat
 
||  zaneb, emilien
 
|-
 
| Horizon
 
||  cmurphy, smcginnis
 
|-
 
| I18n
 
||  emilien, cdent
 
|-
 
| Infrastructure
 
||  fungi, mnaser
 
|-
 
| Ironic
 
||  mugsie, fungi
 
|-
 
| Karbor
 
||  ttx, mugsie
 
|-
 
| Keystone
 
||  fungi,cmurphy
 
|-
 
| Kolla
 
||  dims, TheJulia
 
|-
 
| Kuryr
 
||  dims, cdent
 
|-
 
| Loci
 
|| pabelanger, dims
 
|-
 
| Magnum
 
||  mnaser, dims
 
|-
 
| Manila
 
||  smcginnis, pabelanger
 
|-
 
| Masakari
 
||  pabelanger, cdent
 
|-
 
| Mistral
 
||  zaneb, cmurphy
 
|-
 
| Monasca
 
||  zaneb, TheJulia
 
|-
 
| Murano
 
||  dhellmann, emilien
 
|-
 
| Neutron
 
||  mugsie, dims
 
|-
 
| Nova
 
||  mnaser, dhellmann
 
|-
 
| Octavia
 
||  mnaser, mugsie
 
|-
 
| Openstack Charms
 
||  ttx, emilien
 
|-
 
| Openstack-Helm
 
||  ttx, dims
 
|-
 
| Openstackansible
 
||  mnaser, smcginnis
 
|-
 
| OpenStackClient
 
||  dhellmann, cmurphy
 
|-
 
| Openstacksdk
 
||  pabelanger, TheJulia
 
|-
 
| Oslo
 
||  dhellmann, mugsie
 
|-
 
| Packaging-Rpm
 
||  cmurphy, zaneb
 
|-
 
| Powervmstackers
 
||  emilien, TheJulia
 
|-
 
| Puppet Openstack
 
||  cmurphy, pabelanger
 
|-
 
| Qinling
 
||  zaneb, TheJulia
 
|-
 
| Quality Assurance
 
||  cdent, fungi
 
|-
 
| Rally
 
||  pabelanger, mnaser
 
|-
 
| Refstack
 
||  fungi, TheJulia
 
|-
 
| Release Management
 
||  dhellmann, smcginnis
 
|-
 
| Requirements
 
||  fungi, dhellmann
 
|-
 
| Sahara
 
||  emilien, pabelanger
 
|-
 
| Searchlight
 
||  mugsie, mnaser
 
|-
 
| Security
 
||  fungi, zaneb
 
|-
 
| Senlin
 
||  zaneb, smcginnis
 
|-
 
| Solum
 
||  zaneb, mnaser
 
|-
 
| Stable Branch Maintenance
 
||  fungi, smcginnis
 
|-
 
| Storlets
 
||  ttx, dhellmann
 
|-
 
| Swift
 
||  smcginnis, mugsie
 
|-
 
| Tacker
 
||  TheJulia, emilien
 
|-
 
| Telemetry
 
||  cdent, dhellmann
 
|-
 
| Tricircle
 
||  emilien, cdent
 
|-
 
| Tripleo
 
||  emilien, cmurphy
 
|-
 
| Trove
 
||  ttx, mugsie
 
|-
 
| Vitrage
 
||  emilien, dhellmann
 
|-
 
| Watcher
 
||  smcginnis, TheJulia
 
|-
 
| Winstackers
 
||  pabelanger, cdent
 
|-
 
| Zaqar
 
||  zaneb, dims
 
|-
 
| Zun
 
|| zaneb, ttx
 
|}
 
 
 
== Status updates ==
 
 
 
=== Cinder ===
 
[[File:green.png]]  Update: June 22, 2018, smcginnis
 
 
 
* Some drop off in participation by some cores, but still active enough not to raise any red flags
 
* Overall less community involvement
 
* Project may just be "stable" and doesn't need as much activity as the past
 
* Still a lot of bug fix work to be done, but no major new features on the roadmap
 
 
 
=== Freezer ===
 
Reported issues
 
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
 
* freezer and freezer-web-ui missed the Rocky-2 milestone
 
 
 
=== Heat ===
 
Update: 2018-06-28, zaneb
 
 
 
* Under active development
 
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
 
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
 
* Active on mailing list and IRC
 
* Regular IRC meetings
 
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
 
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].
 
 
 
=== I18n ===
 
Update: June 13, emilien
 
 
 
Reported issues: none, yet.
 
The team changed leadership in Queens.
 
 
 
Queens status:
 
* 87 modules touched (+87%)
 
* 17 languages supported (+6%)
 
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
 
* 7 companies support (-22%)
 
I18n team previously had team meetings but decided to have office hours instead.
 
Usually tracks completion of Rocky community goals.
 
A lot of collaboration with Doc team.
 
Dedicated mailing-list: openstack-i18n - pretty busy
 
 
 
Rocky:
 
* Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.
 
 
 
=== Manila ===
 
[[File:green.png]]  Update: June 22, 2018, smcginnis
 
 
 
* Project appears to be in good shape
 
* Focusing on bug fixes and stabilization rather than any big new features
 
* Drop of in involvement from EU, particularly from HPE and IBM
 
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
 
** Not a lot of involvement on IRC or weekly meeting though
 
* Lots of good interest downstream, particularly from HPC and telco communities
 
 
 
=== Masakari ===
 
Reported issues
 
* Low activity in Rocky for a "new" project
 
 
 
=== Murano ===
 
* murano and murano-dashboard missed the Rocky-2 milestone
 
 
 
 
 
Update 13 June 2018, dhellmann
 
 
 
* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
 
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
 
 
 
=== Openstack Charms ===
 
[[File:green.png]] Update: June 20, ttx
 
 
 
* Currently single-vendor (all cores from Canonical), but with some external participation
 
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
 
* Holds weekly IRC meetings with rotating chair
 
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
 
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])
 
 
 
=== OpenStackClient ===
 
[[File:orange.png]] Update: 28 June 2018, dhellmann, cmurphy
 
 
 
* uses IRC and the mailing list but no meetings
 
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
 
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
 
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)
 
 
 
=== OpenStack-Helm ===
 
[[File:green.png]] Update: June 26, ttx
 
 
 
* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
 
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
 
* Holds weekly IRC meetings, pretty active discussions
 
* Migrated to StoryBoard
 
* Limited ML engagement (mostly used for team-wide announcements)
 
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.
 
 
 
=== Oslo ===
 
[[File:orange.png]] 
 
 
 
Reported issues
 
 
 
* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
 
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
 
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
 
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.
 
 
 
Update: 12 June 2018, dhellmann
 
 
 
* The team is small, but active and working on recruiting.
 
* Team produces regular and frequent releases for the maintained libraries
 
* Team meets weekly using IRC
 
* Team had both onboarding and project update sessions in Vancouver
 
* The level of activity within each library varies.
 
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]
 
 
 
=== Rally ===
 
Reported issues
 
* Half on GitHub those days, and unwilling to drop direct branching ACLs
 
 
 
=== Release Management ===
 
[[File:green.png]]
 
 
 
Update: 28 June 2018, dhellmann & smcginnis
 
 
 
* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
 
* Working on a reviewers' guide to help with recruiting.
 
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.
 
 
 
=== Requirements Management ===
 
[[File:orange.png]] 
 
 
 
* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver
 
 
 
Update: 14 June 2018, dhellmann
 
 
 
* team has recently lost several members
 
* most work is really down to 3 people (Matt, Dirk, Tony)
 
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
 
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
 
* meets regularly
 
* accomplishments this cycle
 
** stopped syncing dependencies between projects
 
** working on networkx upgrade
 
** uncapped eventlet
 
** uncapped sphinx
 
** added optional lower-constraints test jobs for project teams that want them
 
 
 
=== Sahara ===
 
Update: June 13, emilien
 
 
 
Reported issues: none, yet.
 
* The team changed leadership in Queens
 
* Last PTG was virtual
 
* Most commits in Rocky are from Red Hat
 
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
 
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
 
* Following goals and releases
 
* Email sent to PTL on June 13th
 
 
 
=== Searchlight ===
 
Reported issues
 
* searchlight and searchlight-ui missed the Rocky-1 milestone
 
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone
 
 
 
=== Telemetry ===
 
[[File:orange.png]] Update: June 21, cdent, WIP
 
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
 
* more to come
 
 
 
=== Tricircle ===
 
Reported issues
 
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
 
 
 
=== TripleO ===
 
Update: June 13, emilien
 
 
 
* Mainly Red Hat. Some contributors from vendors (storage/network plugins)
 
* Number of contributors / core reviewers always increasing
 
* Quite healthy, no problem reported so far
 
 
 
=== Trove ===
 
[[File:orange.png]] Update: June 12, ttx
 
 
 
* The team changed leadership in Rocky
 
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
 
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
 
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
 
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
 
* Regular weekly meetings, well run with clear documentation of outcomes
 
* Tracks completion of Rocky community goals
 
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
 
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
 
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
 
* Reached out to PTL by email on June 12 for additional concerns / questions.
 
 
 
=== Upgrade SIG ===
 
WIP (emilien)
 
 
 
=== Zaqar ===
 
Reported issues
 
* zaqar and zaqar-ui missed the Rocky-2 milestone
 

Latest revision as of 18:02, 11 June 2019

This page is no longer in use. During discussions at the Train cycle PTG, the OpenStack TC concluded that its experiments in formally tracking problems within individual project teams was not providing enough value for the investment of effort it required. The component of it which is still deemed valuable is having specific TC members officially assigned as liaisons to each project team, so in future that will continue but will be documented in the openstack/governance Git repository's project metadata and on the project pages linked from the https://governance.openstack.org/reference/projects/ page.