Provide details on how Tartarus tables are accessed to Ian D for inclusion in his privileged access discussion paper
Add requirement to computing.help project stuff to reimplement new computing help form using REST API
Produce an Legitimate Interest Declaration and Privacy Statement
records machine to user allocation (with their UUN, cname, sname, user category)
records who requests which order (usually just uun, but can be cname+sname)
records who makes a change in inventory (just uun)
consider what can be removed once a user has left the University
any rows in the 'person' table where 'upstream' is false and where there isn't an 'item' row with a matching 'allocated_to' field should be deleted by a periodic script. Arguably 'category' should be set to NULL where 'upstream' is false?
Decommission ordershost
need to replicate kvmreport mechanism on Tartarus (or somewhere)
submit data via clientreport mechanism
take snapshot of files (no need to take snapshot of SQL as this is automatically recreated from orders files)
power off for 3 months prior to deleting to see if anything breaks
Document Tim's theon old inv snapshot and what its purpose now is. Also modify invquery to remark that data is historical only.
client report to take 'sysinfo.manager' and populate item.manager from this
client report to flag when hyperthreading disabled or not (in CPU report)
client report to take 'ipfilter.export'
Apply Stephen's code cleanup patches
Take a look at RT #78875
WON'T LOOK UNLESS A BIG ISSUE (Ask Tom)
Look at Stephen's 'Thoughts on shell components'
Investigate systemd reboot bug on gaivota and add some more debugging (store tree diff somewhere)
drupal username collection re GDPR
Perioidically run user expiry script every month until August 2019 and if no problems configure to run automatically
Check with Tim / George about capability for login to student machines - where are we
Tim says that we should create a capability that is given to the base cohort and set that capability to no-grace
Meet Tim with Chris to review RAT involvement
Look at using php-5.6 on computing.help
Check with Tim whether we still need service catalogue entry (eg for XRDP service) as part of project deliverables
Read SL7 coordination project final report
Have a look at how APT / DPKG works, particularly wrt API
Look at KVM / host-model issue on oyster (See my actions from 13/03/19)
Look at idea of marking KVM guests as disabled (See my actions from 13/03/19)
Look at low hanging fruit re computing.help pages that need refreshed
Check spending plan
Chris
Look at RT
User training materials project #403
complete and then publish ThoughtsOn403 - and ask for comments
Produce a 'guest only' version of Virtual DICE based on SL7.6
Meet Tim with Alastair to review RAT involvement
Investigate whether small Virtual DICE image is sufficient for 1st and 2nd year teaching
investigate whether we could use yum groups to install additional software for each class (at least for the big classes)
Investigate whether we need to be careful about configuration SSD RAID sets (wrt KB KVM servers)
Divvy up the Forum and AT KVM server upgrades to SL7.6 - remember hyperthreading and enable KSM
Look at low hanging fruit re computing.help pages that need refreshed
Stephen
Take issue of disable per user journald logs on certain servers to OPS
Look at where we're using ALL in access.conf
Continue with RT ticket clearout as discussed in October
Read George's mail of 8th November wrt DPIA
clientreport
Complete module errors report
Add an 'old locks' report
'Old kernels' report
Report on core files in / directory
Produce an Legitimate Interest Declaration and Privacy Statement for svn history and LCFG profile history
Convert steen to staff.ssh (decommissioning hare) - check hyperthreading and virtualisation disabled
Write SL7.6 final report
Look at low hanging fruit re computing.help pages that need refreshed