Difference between revisions of "OpenStack health tracker"
(→Status updates) |
(Added info about missing Rocky 2 milestones) |
||
Line 292: | Line 292: | ||
== Status updates == | == Status updates == | ||
− | |||
=== Freezer === | === Freezer === | ||
Reported issues | Reported issues | ||
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html] | * Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html] | ||
+ | * freezer and freezer-web-ui missed the Rocky-2 milestone | ||
+ | |||
+ | |||
+ | === Murano === | ||
+ | * murano and murano-dashboard missed the Rocky-2 milestone | ||
+ | |||
+ | |||
+ | === Searchlight === | ||
+ | Reported issues | ||
+ | * searchlight and searchlight-ui missed the Rocky-1 milestone | ||
+ | * Release forced for searchlight and searchlight-ui for the Rocky-2 milestone | ||
Line 308: | Line 318: | ||
* Missed rocky-2 milestone | * Missed rocky-2 milestone | ||
* Questions from some public cloud providers on whether they can count on it | * Questions from some public cloud providers on whether they can count on it | ||
+ | |||
+ | |||
+ | === Zaqar === | ||
+ | Reported issues | ||
+ | * zaqar and zaqar-ui missed the Rocky-2 milestone | ||
Revision as of 15:06, 12 June 2018
TC members are attached as liaisons to each of the project teams, SIGs, or UC working groups. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.
Liaisons should monitor their groups by:
- reading meeting logs or participating in meetings
- watching summit "project update" videos
- reading relevant messages on the mailing list
- talking with the PTL, chair, and other group members
- checking contribution rates and review turnaround times
Contents
Liaisons
SIGs
Group | TC members |
---|---|
API | mugsie |
First Contact | fungi |
K8s | dims |
Meta | dhellmann |
Resource Management | cdent |
Scientific | |
Security | fungi |
Self-healing | zaneb |
Upgrade |
Working Groups
Group | TC members |
---|---|
App Dev Enablement | zaneb |
Diversity | fungi |
Enterprise | |
Fault Genes | |
Interop | dims, fungi |
LCOO | |
Large Deployment | |
Edge/Massively Distributed Clouds | ttx |
Operators Telecom/NFV | smcginnis |
Ops Tags | smcginnis |
Product | |
ProfessionalCertification | |
Public Cloud | ttx |
Project Teams
Group | TC members |
---|---|
Barbican | fungi, ttx |
Blazar | |
Chef Openstack | |
Cinder | smcginnis |
Cloudkitty | ttx |
Congress | |
Cyborg | ttx |
Designate | |
Documentation | dhellmann |
Dragonflow | |
Ec2-Api | |
Freezer | ttx, mugsie |
Glance | smcginnis, mugsie |
Heat | zaneb |
Horizon | cmurphy |
I18n | |
Infrastructure | fungi, mnaser |
Ironic | mugsie |
Karbor | ttx |
Keystone | fungi,cmurphy |
Kolla | |
Kuryr | |
Loci | |
Magnum | mnaser |
Manila | smcginnis |
Masakari | |
Mistral | zaneb |
Monasca | |
Murano | |
Neutron | mugsie |
Nova | mnaser |
Octavia | mnaser, mugsie |
Openstack Charms | ttx |
Openstack-Helm | ttx |
Openstackansible | mnaser |
Openstackclient | dhellmann |
Openstacksdk | |
Oslo | dhellmann, mugsie |
Packaging-Rpm | cmurphy |
Powervmstackers | |
Puppet Openstack | cmurphy |
Qinling | zaneb |
Quality Assurance | cdent |
Rally | |
Refstack | fungi |
Release Management | dhellmann, smcginnis |
Requirements | fungi, dhellmann |
Sahara | |
Searchlight | mugsie |
Security | fungi |
Senlin | zaneb |
Solum | |
Stable Branch Maintenance | fungi, smcginnis |
Storlets | ttx |
Swift | smcginnis, mugsie |
Tacker | |
Telemetry | cdent |
Tricircle | |
Tripleo | |
Trove | ttx, mugsie |
Vitrage | |
Watcher | |
Winstackers | |
Zaqar | zaneb |
Zun | zaneb, ttx |
Status updates
Freezer
Reported issues
- Still uses pycrypto [1]
- freezer and freezer-web-ui missed the Rocky-2 milestone
Murano
- murano and murano-dashboard missed the Rocky-2 milestone
Searchlight
Reported issues
- searchlight and searchlight-ui missed the Rocky-1 milestone
- Release forced for searchlight and searchlight-ui for the Rocky-2 milestone
Solum
Reported issues
- Still uses pycrypto [2]
Trove
Reported issues
- No project update in Vancouver
- Missed rocky-2 milestone
- Questions from some public cloud providers on whether they can count on it
Zaqar
Reported issues
- zaqar and zaqar-ui missed the Rocky-2 milestone
Update: June 12, ttx
- The team changed leadership in Rocky
- The new team is small, but pretty alive and active
- Mostly contributors in China (AWCloud, China Telecom, China Mobile)
- Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
- Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
- Regular weekly meetings, well run with clear documentation of outcomes
- Tracks completion of Rocky community goals
- A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
- Missed Rocky-2 milestone, but mostly due to a misunderstanding of release policy.
- No project update in Vancouver, but was discussed in meeting: sadly no team member was present.
- Reached out to PTL by email on June 12 for additional concerns / questions.