June 2020 - service-discuss - lists.opendev.org

Meeting Agenda for June 30, 2020
by Clark Boylan 29 Jun '20

29 Jun '20

We will meet at 19:00 UTC in #opendev-meeting on June 30, 2020 with this agenda: == Agenda for next meeting == * Announcements ** Clarkb out July 7. Will need someone else to run the meeting. * Actions from last meeting * Specs approval ** Authentication broker service, https://review.opendev.org/#/c/731838/ *** Not yet ready for approval but is worthy of review. * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-… Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine *** Zuul executors running on containers ** OpenDev *** Progress on Governance changes **** http://lists.opendev.org/pipermail/service-discuss/2020-May/000026.html Advisory Board thread. Bumped with July 2, 2020 deadline. *** Gitea api troubles. **** Workaround: https://review.opendev.org/#/c/738109/ **** Upstream fix: https://github.com/go-gitea/gitea/pull/12057 * General topics ** DNS cleanup (ianw 20200630) *** https://etherpad.opendev.org/p/rax-dns-openstack-org First pass of record removals has been done. Could use a second pass. *** On the agenda as a reminder for clarkb to do this second cleanup pass. ** Trusty Upgrade Progress (clarkb 20200630) *** Wiki updates ** Time to retire the openstack-infra ML yet? (fungi 20200630) ** Grafana on containers (clarkb 20200630) *** https://review.opendev.org/#/q/status:open+topic:grafana-container * Open discussion

1 0

Forming the OpenDev Advisory Board
by Clark Boylan 29 Jun '20

29 Jun '20

Hello everyone, I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested. One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well. We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time. For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss(a)lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here. [0] https://docs.opendev.org/opendev/system-config/latest/project.html#governan… Clark

7 7

OpenStack from repo Ubuntu 20.04 LTS
by emre brookes 26 Jun '20

26 Jun '20

Not sure if this is the correct place to post this. I installed the OpenStack clients via $ pip2 install python-openstackclient on a new Ubuntu 20.04 LTS system. $ python2 --version Python 2.7.18rc1 (strange the default repos would use a release candidate version) after installing the openstack clients using pip2 and attempting to run the OpenStack command line client "openstack" I received an "ImportError: No module named queue" Following https://github.com/bit4woo/teemo/issues/1 I had to change "import queue" to "from multiprocessing import Queue" in multiple places. e.g. http://codesearch.openstack.org/?q=import%20queue&i=nope&files=&repos= which got me past the error. HTH, -e.

3 2

Meeting Agenda for June 23, 2020
by Clark Boylan 22 Jun '20

22 Jun '20

We will meet in #opendev-meeting at 19:00 UTC June 23, 2020 with this agenda: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval ** Authentication broker service, https://review.opendev.org/#/c/731838/ *** Not yet ready for approval but is worthy of review. * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-… Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine ** OpenDev *** Progress on Governance changes **** http://lists.opendev.org/pipermail/service-discuss/2020-May/000026.html Advisory Board thread. Bumped with July 2, 2020 deadline. * General topics ** Etherpad Upgrade to 1.8.4 or 1.8.5 (fungi/clarkb 20200623) *** https://review.opendev.org/#/c/729029/ *** Now thinking it may be best to do this upgrade after the OpenDev event June 29 - July 2, 2020 ** DNS cleanup (ianw 20200623) *** https://etherpad.opendev.org/p/rax-dns-openstack-org First pass of record removals has been done. Could use a second pass. ** Getting more stuff off of python2 (clarkb 20200623) *** https://etherpad.opendev.org/p/opendev-tools-still-running-python2 *** I'm sure my audit is incomplete. Please add notes if you are aware of other python2 services/tools that need updating. ** Trusty Upgrade Progress (clarkb 20200623) *** Wiki updates * Open discussion

1 0

Meeting Agenda for June 16, 2020
by Clark Boylan 15 Jun '20

15 Jun '20

We will meet in #opendev-meeting at 19:00 UTC Tuesday June 16, 2020 with this agenda: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval ** Authentication broker service, https://review.opendev.org/#/c/731838/ *** Not yet ready for approval but is worthy of review. * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-… Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine ** OpenDev *** Progress on Governance changes **** http://lists.opendev.org/pipermail/service-discuss/2020-May/000026.html Advisory Board thread. Clarkb will send reminders to those that haven't responded as suggested during the PTG. * General topics ** pip-and-virtualenv next steps (ianw 20200616) *** This has merged. Keep an eye out for job failures that need fixes. *** Can we clean up the extra content in the nodepool config and mark the spec as implemented now? ** Zookeeper TLS (corvus 20200616) *** https://review.opendev.org/720302 is ready and will require a full zuul restart ** Etherpad Upgrade to 1.8.4 or 1.8.5 (fungi/clarkb 20200616) *** https://review.opendev.org/#/c/729029/ *** We found a bug in Etherpad's UI in 1.8.4. Previous change works around it if we wish to deploy with a workaround or we can wait for 1.8.5 which is also fixed. ** DNS cleanup (ianw 20200616) *** https://review.opendev.org/728739 : Add tool to export Rackspace DNS domains to bind format *** https://etherpad.opendev.org/p/rax-dns-openstack-org Review output of tool. ** Getting more stuff off of python2 (clarkb 20200616) *** https://etherpad.opendev.org/p/opendev-tools-still-running-python2 *** Many cases where we run python3 capable tools under python2 and they simply need a deployment update *** Meetbot and Logstash tooling not yet python3 capable. *** I'm sure my audit is incomplete. Please add notes if you are aware of other python2 services/tools that need updating. ** Trusty Upgrade Progress (clarkb 20200609) *** Wiki updates * Open discussion

1 0

[donate compute resources] Support for MIPS architecture
by zhaoxiaolin 11 Jun '20

11 Jun '20

Hi, We hope that OpenStack can support for mips architecture, As we are not already cloud operators, we prefer to donate mips based compute resources. I hope you can give us some more suggestions. Thanks

2 1

[donate compute resources] Support for MIPS architecture
by 赵晓琳 11 Jun '20

11 Jun '20

Hi, We hope that OpenStack can support for mips architecture, As we are not already cloud operators, we prefer to donate mips based compute resources. We hope you can give us some more suggestions. Thanks

1 0

June 2020 PTG Recap
by Clark Boylan 08 Jun '20

08 Jun '20

Hello Everyone, Last week we both helped host the PTG (with the meetpad service) and attended the event as participants. Now that the event is over I'll try to recap things for us. On the meetpad side of things we scaled up the Jitsi Video Bridge service from a single instance to five. Based on Cacti data I think this scale up worked well. Unfortunately, it seems that Jitsi Meet is also limited by client side capabilities in addition to the server itself. In particular, having many people in a room with video enabled impacts the performance of that conference in clients. It seems that using Chrome/Chromium, setting your local settings to low bandwidth mode, and simply reducing the number of people using video helps. Overall, I think the service did well considering its recency, and the teams that used it were happy. In general that seemed to be groups with 20 or fewer participants. Since then we've scaled the Jitsi Video Bridge service down to two instances. This should give us reasonable capacity for non PTG periods of time, while consuming a reasonable set of resources. We may also want to look into running the Jibri service which would enable us to stream a conference. This way only active participants would need to fit into that ~20 person limit and lurkers can view via a live stream. Our time at the PTG as participants also went well. We had three 2 hour blocks across a range of time zones which enabled us to talk about a variety of subjects. I'll try to call out notable items in this email, but you can find all of the notes we kept at https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020 We are starting to dig into what is required to upgrade Gerrit now that it is running on containers. We expect we'll upgrade from 2.13 to 2.16 and then sit there for a while. One reason for this is 2.16 is the last version with the existing UI. 3.0 and beyond drop the existing UI in favor of PolyGerrit UI. Since 2.16 has both UIS this gives us the chance to have people transition over to the new UI. Once we are ready to go to 3.0 that should be a trivial upgrade as the only change was removal of the current existing UI. We do still need to figure out if one large single outage is our best option or if we should upgrade to 2.14, perform online migrations, then upgrade to 2.15, perform online migrations, and finally repeat with an online upgrade to 2.16. To determine which option is best for us we plan to spin up a copy of the production server and try these different options to see how reliable they are and how much time is required to perform each one. To enable more updates of configuration management from Puppet to Ansible, Monty plans to set up Ansible driven testing of our existing puppetry with testinfra. Using that, we can then replace the Puppet with Ansible and be confident things continue to work with our testinfra tests. Hopefully, this makes it easier for more people to get involved in the configuration management updates. Another place where we have "legacy" code that needs updating is porting any existing python2 utilities to python3. I'll try to get a list of those put up so that people can volunteer to do the conversions. The conversions themselves should be straightforward but not everyone knows what needs porting. We hope the list addresses this. Using the data collected in the previous two items we may identify services and tools that should simply be retired rather than ported. One example could be pbx.openstack.org in favor of meetpad.opendev.org. Once we've got lists of work to be done we can evaluate if any of them need to be deleted and can make individual arguments for each one. Over time we've become more and more aware that having a diverse set of identity options for login would make OpenDev more appealing to a broader set of users. One of the big speed bumps to making that change has been enacting a transition that doesn't break existing users. In particular the existing identity service in use, Ubuntu One, requires OpenID v1 and none of the modern identity brokers support this protocols. Jeremy has started to put a spec together on how we might do this, https://review.opendev.org/#/c/731838/, and during the PTG Kristi Nikolla made an excellent suggestion for using SimplySAMLphp to front OpenID v1 for identify brokers that don't speak OpenID v1. With that we now have a plan to move forward on making this a reality. The topic of statistics, metrics, and logging came up again. We asked a few difficult questions that likely need further discussion in separate threads: * How do we make it easier for people to build grafana dashboards? * Should we replace Cacti with something like collectd + graphite/grafana? * Should we consider shutting down the ELK stack since the main user (OpenStack) of this service is not really using it much anymore? The future of Bup for backups was discussed briefly. Bup is still very python2 specific though I think they've recently started to work on a python3 port. I mentioned that I use borg backup for home backups happily, and like Bup, borg claims to support append only backups. Whether or not we want to switch to another tool and what that tool should be if so will require more investigation. Input is welcome. Finally, we discussed generating a bit more involvement in OpenDev from our users. On the Advisory Board side of things I'll be sending out some gentle reminders in the near future to see if we can get anyone else to sign up. Then in a couple weeks move forward with those who have volunteered already. The thought is that starting small and leading by example will drive involvement. We also discussed advertising tools, like the docker image build tooling that OpenDev uses, towards audiences that might be inclined to use them, like Airship. Involvement isn't limited to the Advisory Board or Zuul Jobs. If any of the topics you've just read sound interesting to you and you'd like to get involved please reach out. We're more than happy to incorporate others in what we are doing. Thank you for reading this very long email, Clark

1 0

Meeting Agenda for June 9, 2020
by Clark Boylan 08 Jun '20

08 Jun '20

We will meet at 19:00 UTC in #opendev-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-… Update Config Management] *** topic:update-cfg-mgmt *** Gerrit on docker updates **** Gerritbot still outstanding todo item. *** Zuul as CD engine **** Split of base and service playbooks is underway. ** OpenDev *** Progress on Governance changes **** http://lists.opendev.org/pipermail/service-discuss/2020-May/000026.html Advisory Board thread. Clarkb will send reminders to those that haven't responded as suggested during the PTG. * General topics ** Project Renames (clarkb 20200609) *** We've got a single project rename queued and now that OpenStack release is done cost of doing renames is lower *** Aiming for June 12, 2020 currently. ** pip-and-virtualenv next steps (ianw 20200609) *** remove from more popular distros *** notify and merge? ** DNS cleanup (ianw 20200609) *** Clearing out old mirrors and lots of old stuff seems to be there *** https://review.opendev.org/728739 : Add tool to export Rackspace DNS domains to bind format *** Should I post the results of the above to a etherpad for group audit (is equivalent of high latency zone xtfr) *** run as backup? ** PTG Recap (clarkb 20200609) *** Meetpad seemed to work well up to 20 conference participants. Client issues with cpu consumption became a problem beyond that. *** Provide your event feedback at https://etherpad.opendev.org/p/June2020-PTG-Feedback *** Decompress with online group activity of some sort? ** Trusty Upgrade Progress (clarkb 20200609) *** Wiki updates * Open discussion

1 0

Retiring several opendev/puppet modules
by Andreas Jaeger 05 Jun '20

05 Jun '20

We've used a lot puppet modules for the OpenDev infrastructure and migrate to ansible, thus we can drop a couple of modules and retire them formally! For details, see https://review.opendev.org/#/c/720901/ and https://review.opendev.org/733850 Andreas -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

1 0