[OpenStack-Infra] Meeting Agenda for February 18, 2020

Clark Boylan cboylan at sapwetik.org
Mon Feb 17 21:29:14 UTC 2020


We will meet at 19:00 UTC February 18, 2020 in #openstack-meeting with this agenda:

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs approval

* Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html 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
*** Upgrade gitea to 1.10.3 https://review.opendev.org/#/c/705804/

* General topics
** Vancouver PTG attendance. (clarkb 20200218)
*** 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 20200218)
*** Wiki updates
** 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 20200218)
** 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.  this can be used for job testing.

* 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?



More information about the OpenStack-Infra mailing list