[tech] Tech/Wheel Meeting 2023-05-30 18:30 - 24 hour reminder

Mon May 29 20:40:45 AWST 2023

Apologies for this meeting; I am yet again triple booked.

-- Bob

-----Original Message-----
From: tech <tech-bounces+bob=ucc.gu.uwa.edu.au at ucc.asn.au> On Behalf Of
tech-reminder at ucc.asn.au
Sent: Monday, May 29, 2023 6:30 PM
To: tech at ucc.asn.au
Subject: [tech] Tech/Wheel Meeting 2023-05-30 18:30 - 24 hour reminder

Tech/Wheel Meeting Agenda - Tuesday 2023-05-30T18:30
====================================================
- VENUE: UCC Clubroom
  - and online at https://meetings.ucc.asn.au/b/tech

*Meeting opened HH:MM*

## Attendance
- Present
- Apologies
- Absent

## Next meeting
- Schedule next meeting
  - *day 2023-mm-ddTHH:MM
- ACTION: [???] shall be this meeting's secretary! This entails recording
minutes for meeting n (beware mid-meeting glitches) and ensuring meeting n+1
reminders succeed:
  - Checklist follows:
    - Clone a new issue from
[[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32]]
      - Preferably immediately; then reopen it and assign it to yourself
      - This issue is to keep track of any async secretarial duties detailed
ahead
      - Type `/clone` into the "Write a comment" box as a "quick action"
      - Update the title to match today's date
  - [ ] ACTION: Save and commit the minutes of today's meeting, during the
meeting; and at the end
  - [ ] ACTION: Set and (later) verify reminders of next meeting:
    - [ ] Promptly update `agenda.next` with the TIME/DATE/VENUE
    - [ ] Perform initial curation of `agenda.next`, and move any previous
or longstanding action items out of it and into GitLab (see Action Items
section below)
    - [ ] Update the crontab: `motsugo# crontab -e`
    - [ ] Check at T-7days that the notice really went out, fix for T-4days
if needed
- [ ] Everyone, before next meeting: Curate `agenda.next`, and move any
items you think should be tracked as GitLab issues into GitLab issues, as
above

## Optional items - choose at the start of the meeting
- [ ] Ethical guidelines
- [ ] Monitoring
- [ ] Backups
- [ ] Password rotations
- [ ] New members
- [ ] Quick check of ChangeLog
- [ ] Lessons learnt

## Current Action Items
- [333]: Test ceph's `ceph osd set noout` options for upgrading.
- [333] [GPO]: Continue preparing for proxmox upgrades.
- [MPT] and everyone: Figure out what is wanted with
(unigames|unisfa).(guild|gu).uwa.edu.au.
- [MPT] and everyone: Figure out what our view on split DNS for internal vs
UWA vs external, and report back to Steven with our goals.
  - thank you for BYOI tech talk 5/3, 2023-05-11 "What's in a (C)NAME?"
/home/wheel/jimbo/public-html/projects/byoi/BYOI_Part_5.odp
- [I2N]: Continue implementing haveibeenpwned checker script into
ucc-adduser
- [BRD] [MPT]: Pester UWAIT about firewalled IPs
- [I2N] [MTL] [TPG]: Update vendserver to python3
- [GPO] [LIZ]: Look at what is causing late packets in UWA
- [MTL] [MPT] [GPO]: Update ucc-mailman to mailman3
- [GPO]: Sniff out what else is still running python2
- [I2N] [GPO] [NTU]: GET MOLMOL DONE
- [MTL]: Get docker container ansible SOE finished, and then start UCC
mastodon instance
- [MTL] [MPT] [GPO]: Seperate mussel's functions into seperate VMs
- [BRD] [GPO]: Fix uccportal Square payment form

### Boilerplate
- Now maintained in GitLab at
[[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/]]
- Briefly discuss anything in here that's worth discussing, but don't spend
too long rehashing unresolved issues that have already been discussed ;)
- Going forward:
  - New actions: when new ACTION items arise, put them in the minutes once,
but add to GitLab
  - Ongoing actions: don't keep them in the agenda, unless they definitely
need to be discussed in the next meeting
  - Completed actions: mention in the agenda that it's been completed, and
and briefly discuss if need be

### Action items to discuss

## Known Broken Stuff

## Matters arising previously

## Extra items (rename/refile as appropriate)
- [NTU]: Recurring `mailfish` error reports: `May 17 12:50:11 mailfish
procmail[290372]: Error while writing to "./procmaillog"`
  - Re:
https://discord.com/channels/264401248676085760/264401248676085760/109629770
2796574720
  - started on 2023-03-20 - what was the SOE change or manual change that
caused this?
  - anything to do with:
    -
https://discord.com/channels/264401248676085760/264401248676085760/796583161
861242932 ?
    -
https://discord.com/channels/264401248676085760/264401248676085760/712684675
948347444 ?
- [NTU]: Purge docker from motsugo?
https://lists.ucc.gu.uwa.edu.au/pipermail/tech/2023-May/005616.html
- [NTU]: Viral tenancy 2023-05-17 ? anything we could have done to notice?

*Meeting closed HH:MM*

----

```
# https://demo.hedgedoc.org/Hlsapf47RsqpgIjqLVfMUw
cd /home/wheel/docs/meetings
HEDGEDOC_SERVER=https://demo.hedgedoc.org /home/wheel/bin/hedgedoc export
--md Hlsapf47RsqpgIjqLVfMUw ./$(date +%Y-%m-%d).txt git add ./$(date
+%Y-%m-%d).txt git commit -m "Tech meeting minutes $(date +%Y-%m-%d)"
```

<!-- vim: tabstop=2 softtabstop=2 shiftwidth=2 expandtab -->
<!-- Local Variables: -->
<!-- tab-width: 2 -->
<!-- End: -->
_______________________________________________
List Archives: http://lists.ucc.asn.au/pipermail/tech

Unsubscribe here:
https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/bob%40ucc.gu.uwa.edu.au