20th February 2019

1. [Neil] Job action timeouts
   1. Downgrade current change to not reject XMLRPC API job submission [Rémi]
      1. lots of jobs on LKFT need changes, likely to be indicative of a wider problem
   2. Implement the XMLRPC check and get lava-schema.py out to people in 2019.02 [Rémi]
   3. Announce the new schema
   4. Leave fatal exceptions until a future release
   5. Confirmed. the schema validation itself is not yet part of lava_scheduler_app submit.
2. [Neil] Aarch64 gitlab-runners
   1. Initial config available, needs optimisation, especially concurrency per machine vs cores per runner
      1. optimisation to be done during 2019.03 cycle.
   2. [Steve] Mustang machine not booting - investigating
      1. could be an issue with upgrade to buster.
3. [Neil] wisdom of running unit tests inside docker builds in the ci-images project?
   1. guarantees that the new image won't break lava.git master.
   2. another item to be added to the docs of how our CI operates.
   3. [Neil] needs an issue.
4. [Neil] Remi to authenticate the GnuPG fingerprint for 4E9995EC67B6560E0A9B97A9597DCC10C0D1B33D to enable lavasoftware.org ansible password_store
   1. Now fixed via keys.gnupg.net and pgp.earth.li
5. [Dean] Feasibility of upgrading django-ldap-auth to version 1.7
   1. https://tracker.debian.org/pkg/django-auth-ldap
   2. To sync LDAP groups into Django auth.
   3. We want to be able to mirror LDAP groups as groups in LAVA (details of this: https://django-auth-ldap.readthedocs.io/en/latest/permissions.html#group-mirroring) but examples of this given in 1.5 docs (oldest I've found) don't appear to work in 1.3
   4. I believe 1.7 is in Buster, so is it a case of moving to buster?
      1. not urgent to migrate to buster now.
6. [Steve] location for documentation
   1. Needs an issue to track this.
      1. avoid the rabbit hole of optimising what is left.
   2. certain elements need to go into the website from lava-server-doc
      1. Release docs
      2. Development process
      3. Design overview
      4. Keep development-intro and update links.
   3. update all the links in lava-server-doc.
   4. website will move to Sphinx instead of Pelican.
   5. a lot of docs are using Sphinx RST.
      1. there will be some conversion needed for items which are currently in Google Docs.
   6. move this doc to the wiki?
      1. no - interactive shared-editing feature is very useful
      2. we can simply copy text to the wiki after the fact
      3. Page per meeting in the wiki with index links
      4. Consider the new document as public by the end of the meeting.
7. [Remi] MuxPi rPi zero. build raw images.
   1. Guestfish based on GuestFS
   2. inside docker? need /boot and /lib/modules volumes. Easy scriptable way to do things.
   3. Should we publish our images and a way to rebuild them?
      1. Let's not do this as an automated public build
         1. Neil to close lava/functional-tests#7 (Use GitLab CI to auto-build functional test image files for files.lavasoftware.org) on the basis that we are not an image building service.
      2. Must document how our images are built
   4. files.lavasoftware.org already includes copies of the scripts which were used to create the Debian standard image files.