Difference between revisions of "Meetings/InfraTeamMeeting"
< Meetings
Ian Wienand (talk | contribs) (→Agenda for next meeting) |
Clark Boylan (talk | contribs) (→Agenda for next meeting) |
||
Line 10: | Line 10: | ||
* Announcements | * Announcements | ||
+ | ** Last meeting of 2018: December 18 | ||
+ | ** First meeting of 2019: January 8 | ||
* Actions from last meeting | * Actions from last meeting | ||
* Specs approval | * Specs approval | ||
+ | ** https://review.openstack.org/623033 OpenDev Repo Hosting Rework Spec | ||
+ | ** https://review.openstack.org/607377 Storyboard Attachements | ||
+ | ** https://review.openstack.org/581214 Anomaly Detection in CI Logs | ||
* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) | * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) |
Revision as of 17:02, 10 December 2018
Contents
Weekly Project Infrastructure team meeting
The OpenStack Project Infrastructure Team holds public weekly meetings in #openstack-meeting
, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.
Please feel free to add agenda items (and your IRC nick in parenthesis).
Agenda for next meeting
- Announcements
- Last meeting of 2018: December 18
- First meeting of 2019: January 8
- Actions from last meeting
- Specs approval
- https://review.openstack.org/623033 OpenDev Repo Hosting Rework Spec
- https://review.openstack.org/607377 Storyboard Attachements
- https://review.openstack.org/581214 Anomaly Detection in CI Logs
- Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
- A Task Tracker for OpenStack
- Update Config Management
- topic:puppet-4 and topic:update-cfg-mgmt
- Zuul as CD engine
- General topics
- Proposal: make core infra team members +OP on irc in order to make it visible which core is online. That is because most irc client display ops before the other accounts and with different colors, this being the only way to distinguish them from other users. This practice seems to be used by many projects, is not about "op" rights.
- OpenDev update (corvus)
- DNS working
- Website (needs content, call for volunteers)
- Collecting inner ARA results for system-config jobs (ianw 2018-12-04)
- dmsimard proposed ara installation for bridge stalled on who would maintain db and how we would publish it
- actually mostly seems useful for presentation of results during CI runs
- stack for review : https://review.openstack.org/#/q/topic:inner-ara-results+(status:open+OR+status:merged)
- sample of "inner" ara results for system-config job
- glean + NetworkManager support (ianw 2018-12-04)
- request for reviews to unblock Fedora 29
- https://review.openstack.org/#/q/status:open+topic:fedora29
- FIx cloud-launcher (ianw 2018-12-04)
- Later ansible release needed to work around issues trying to delete routers
- https://review.openstack.org/#/c/617218/4
- note graphs available : http://grafana.openstack.org/d/qzQ_v2oiz/bridge-runtime?orgId=1
- Open discussion
Upcoming Project Renames
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
Previous meetings
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/