Difference between revisions of "Meetings/InfraTeamMeeting"
< Meetings
Ian Wienand (talk | contribs) (→Agenda for next meeting) |
Ian Wienand (talk | contribs) (→Agenda for next meeting) |
||
Line 39: | Line 39: | ||
** pip-and-virtualenv removal (ianw 20200218) | ** pip-and-virtualenv removal (ianw 20200218) | ||
*** https://etherpad.openstack.org/p/pTFF4U9Klz : clarkb writeup of major issues | *** https://etherpad.openstack.org/p/pTFF4U9Klz : clarkb writeup of major issues | ||
− | *** possible removal plan: build images without any | + | *** possible removal plan: use py3 venv (built in) on all platforms for build-time "utility" installs (glean, bindep, stackviz, whatever); ship images without any non-distro-packaged tools; add for backwards compatibility via base jobs |
*** https://review.opendev.org/707499 : discussion in comments | *** https://review.opendev.org/707499 : discussion in comments | ||
*** https://review.opendev.org/707513 : use venv for glean | *** https://review.opendev.org/707513 : use venv for glean |
Revision as of 21:10, 17 February 2020
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
- Actions from last meeting
- Specs approval
- Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
- Update Config Management
- topic:update-cfg-mgmt
- Zuul as CD engine
- OpenDev
- Progress on Governance changes
- https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack governance.
- https://review.opendev.org/#/c/703488 Updates to our project documentation with governance info
- Possible gitea/go-git bug in current version of gitea we are running https://storyboard.openstack.org/#!/story/2006849
- Gitea has added a commit cache and closed the slow performance bug. We should consider an upgrade as soon as is reasonable.
- Progress on Governance changes
- Update Config Management
- General topics
- Vancouver PTG attendance. (clarkb 20200211)
- That time of year where we need to decide if we are going and if so how much time and space we need.
- Trusty Upgrade Progress (clarkb 20200211)
- Status.o.o mostly done. Needs new gerritlib release for e-r IRC bot to get Gerrit events.
- Wiki updates
- Refstack needs changes to upstream code base to make it deployable on our docker python-base image.
- static.openstack.org (ianw,corvus,mnaser,fungi 20200218)
- static.openstack.org transition should be complete
- still tasks remaining (haproxy redirects, few other publishing sites)
- New Airship CI cloud (clarkb 20200211)
- pip-and-virtualenv removal (ianw 20200218)
- https://etherpad.openstack.org/p/pTFF4U9Klz : clarkb writeup of major issues
- possible removal plan: use py3 venv (built in) on all platforms for build-time "utility" installs (glean, bindep, stackviz, whatever); ship images without any non-distro-packaged tools; add for backwards compatibility via base jobs
- https://review.opendev.org/707499 : discussion in comments
- https://review.opendev.org/707513 : use venv for glean
- https://review.opendev.org/707750 : use venv in project-config elements; drop pip-and-virtualenv inclusion from element and move to individual configs; add node type with no pip-and-virtualenv for job testing
- Vancouver PTG attendance. (clarkb 20200211)
- Open discussion
- Need to clarify logging requirements from https://docs.openstack.org/infra/system-config/third_party.html -- mainly the "logs must be browsable; logs requiring download, installation or login to access are not acceptable" phrase. (ssbarnea 20200217)
- Does it apply to any logs or only tempest ones? Current indentation seems wrong, was this expected to be top level?
- Is ever accepted to produce combined .tar.gz files with host-logs?
- In which conditions it would be acceptable to archive a big log file? Example publishing a 1GB single log file is clearly not of any use for browsing it. I suspect after certain size is ok to archive them but this is not mentioned. What would be the magic threshold?
- Need to clarify logging requirements from https://docs.openstack.org/infra/system-config/third_party.html -- mainly the "logs must be browsable; logs requiring download, installation or login to access are not acceptable" phrase. (ssbarnea 20200217)
Upcoming Project Renames
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
None currently.
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/