<div dir='auto'>Hi All,<div dir="auto"><br></div><div dir="auto">My apologies, but it completely slipped my mind that we had a wheel meeting set for today, and I've had a pretty busy weekend, so I'll probably have to pass on this one, sorry!</div><div dir="auto"><br></div><div dir="auto">Thanks, and kind regards,</div><div dir="auto">Dylan Hicks [333]</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 Sep 2021 2:00 pm, root <root@ucc.gu.uwa.edu.au> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Tech/Wheel Meeting Agenda - Sunday 2021-09-05 14:00<br>
===================================================<br>
- VENUE: UCC Clubroom<br>
- and online at https://meetings.ucc.asn.au/b/bob-yrk-uy6</p>
<p dir="ltr">*Meeting opened hh:mm*</p>
<p dir="ltr">## Attendance<br>
- Present<br>
- Apologies<br>
- [NTU]<br>
- Absent</p>
<p dir="ltr">## Next meeting<br>
- Schedule next meeting<br>
- *day 2021-MM-ddThh:mm<br>
- not too soon, let's have more doing than talking?<br>
- ACTION: [???] Set and verify reminders of next meeting: `motsugo# crontab -e`<br>
- Promptly update agenda.next with the TIME/DATE/VENUE<br>
- Update the crontab: `motsugo# crontab -e`<br>
- skip the `4day` , unless there's issues at `1week`<br>
- Check at T-7days that the notice really went out, fix for T-4days if needed<br>
- Everyone, pre-meeting: Curate agenda.next</p>
<p dir="ltr">## Optional items - choose at the start of the meeting<br>
- Ethical guidelines<br>
- Monitoring<br>
- Backups<br>
- Password rotations<br>
- New members<br>
- Quick check of ChangeLog<br>
- Lessons learnt</p>
<p dir="ltr">## Known Broken Stuff<br>
- IPv6 inbound<br>
- ACTION: [TEC] to email UWA IT<br>
- lard<br>
- Still needs a spare PSU OR replacement with something less... fatty.<br>
- ACTION: [???] to send email out requesting a 1U Cisco switch to replace Lard<br>
- samson the https://wiki.ucc.asn.au/ActiveDirectory server has no freshly built DC friends<br>
- this is risky, a single-point-of-failure, which in turn depends on the running VM cluster<br>
- something to do with the current configuration is probably why mussel<br>
and mooneye still have auth problems<br>
- can we upgrade or rebuild or document our way out of this?<br>
- ...so making a quick clone and calling it "done" really isn't enough, continuous integration is called for?<br>
- vucc testbed in https://wiki.ucc.asn.au/NewActiveDirectory</p>
<p dir="ltr">## Matters arising previously</p>
<p dir="ltr">## Extra items (rename/refile as appropriate)<br>
- Monitoring<br>
- Drive health<br>
- Uncorrectable errors, reallocated sectors, TBW on SSDs<br>
- ACTION: [NTU] and [MTL] to work together on how best to start drive monitoring, and make it standard/SOE config via ansible</p>
<p dir="ltr">- [MTL] continues looking at DNS<br>
- Not much progress<br>
- Have played with coredns for a resolving server<br>
- Need to do some more testing of resolving internal UWA things (to check behaviours)<br>
- Working on ansible to set up a primary DNS server<br>
- Done a little bit of playing with Gitlab CI<br>
- Need to finalise working out the best way to do this securely<br>
- split out ucc.machines from zonemake.py code</p>
<p dir="ltr">- Group Policy and Ansible on Windows machines<br>
- ACTION: [333] to figure out most supported way to install official SSHD build on Windows<br>
- ACTION: [MTL] promises to look at this in more detail once back in the clubroom, including WinRM<br>
- Best host to run playbooks from for the Windows machines?</p>
<p dir="ltr">- Post-O-Day account locking<br>
- cleanup accounts e.g. `getent passwd|grep zv`, primary group memberships<br>
- ACTION: [TEC] and [MPT] still need to get this sorted<br>
- Specifically, the Comite™ get a list of people who haven't paid and send to Wheel, so we can do the locking, if James and Tim don't do the locking themselves</p>
<p dir="ltr">- Staging storage server:<br>
- [TEC] Old DELL R710 server[s] from dadams<br>
- Store images or less selective backups onsite, for rapid recovery or offsite replication<br>
- zfs send? btrfs send? borgbackup? expose to https://pbs.proxmox.com/ appliance?<br>
- ACTION: [NTU] followup the previously budgetted 3.5" bulk backup drive purchase<br>
- Done, drives bought<br>
- https://lists.ucc.gu.uwa.edu.au/pipermail/tech/2021-March/005446.html<br>
- https://lists.ucc.gu.uwa.edu.au/pipermail/tech/2021-August/005474.html<br>
- Would like some extra caddies: 3.5" slots, 3.5" + 2.5" SATA drives<br>
- https://discord.com/channels/264401248676085760/264401248676085760/878831917133353031<br>
- https://discord.com/channels/264401248676085760/264401248676085760/879354657976229958<br>
- 3D print? does [DBA] or anyone else at UWA Makers have the model?<br>
- or ebay?</p>
<p dir="ltr">- [MPT] Began (unofficial) discussions with [DBA] and CS faculty about making GPU compute accessible to students<br>
- Potential for funding? No assurances yet<br>
- What else would UCC need to buy/build to make it happen in our MR?</p>
<p dir="ltr">- ACTION: [MTL] to update Ansible scripts for mail*<br>
- In response to spam campaign</p>
<p dir="ltr">- Build and break a PC<br>
- Brand new motherboard missing audio capacitor, but [DBA] will resolder it<br>
- ACTION: [DBA] to resolder audio capacitor on new motherboard</p>
<p dir="ltr">- Rebuild rather than upgrade `discord-irc` ?<br>
- ansible driven install<br>
- config files:<br>
- `~discord/discord-irc-config.json`<br>
- `/etc/systemd/system/discord-irc.service`<br>
- this machine is a non-complicated test case?<br>
- https://github.com/reactiflux/discord-irc<br>
- requires Debian 11 "bullseye", DebianPkg:nodejs 12.x<br>
- occasionally dies, config tweaks could help?<br>
- https://github.com/reactiflux/discord-irc/issues/594<br>
- `journalctl -xe -u discord-irc.service`<br>
```<br>
Aug 31 17:45:40 discord-irc discord-irc[45040]: TypeError: Converting circular structure to JSON<br>
Aug 31 17:45:40 discord-irc systemd[1]: discord-irc.service: Main process exited, code=exited, status=1/FAILURE<br>
Aug 31 17:45:40 discord-irc systemd[1]: discord-irc.service: Start request repeated too quickly.<br>
```</p>
<p dir="ltr">*Meeting closed hh:mm*</p>
<p dir="ltr">----</p>
<p dir="ltr">```<br>
# https://demo.hedgedoc.org/Hlsapf47RsqpgIjqLVfMUw<br>
cd /home/wheel/docs/meetings<br>
HEDGEDOC_SERVER=https://demo.hedgedoc.org /home/wheel/bin/hedgedoc export --md Hlsapf47RsqpgIjqLVfMUw ./$(date +%Y-%m-%d).txt<br>
git commit -am "Tech meeting minutes $(date +%Y-%m-%d)"<br>
```</p>
<p dir="ltr"><!-- vim: tabstop=2 shiftwidth=2 expandtab<br>
--><br>
<!-- Local Variables: --><br>
<!-- tab-width: 2 --><br>
<!-- End: --><br>
_______________________________________________<br>
List Archives: http://lists.ucc.asn.au/pipermail/tech</p>
<p dir="ltr">Unsubscribe here: https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/dylanh333%40ucc.asn.au<br>
</p>
</blockquote></div><br></div>