• Alastair
  • systemd project
    • Consider how components will work with systemd
    • Continue work on documentation - guidance for other COs on how to use
    • Look at getting Stop method to rebuild /etc/systemd regardless of whether there have been resource changes (remember Stop doesn't call Configure)
    • convert to module
  • EL7 project
    • what sort of level of space is required by systemd journald logging (for desktop /var sizing)
      • (By default journald logs to /run/log. Have to mkdir /var/log/journal to keep data). Have enabled on one machine
      • identify default retention policyDefault retention is to use up to 10% of partition. Can use either space or time as a constraint on space. Logs are per user + system, so users can read their own data. Each log file starts at 8MB, so a popular machine will have lots of log data.
      • Blog about journald retention policy - and document how to set...
      • Blog about decision to keep journald and /var/lcfg/log/syslog duplication - and resulting configuration change.
    • check installroot stuff same version across SL6 and EL7
      • and pull out old SL5 stuff
    • Look at whether we need anything better than existing network component for desktops
    • Look at lightdm issues
      • locking (dm-lock doesn't actually lock, just respawns greeter on different VT - can still switch back to original VT
      • power management
    • Blog about dconf and lightdm components
    • Look at LCFG bug #799 (systemd buffered output)
    • convert lcfg-dconf and lcfg-lightdm to module
    • Fix systemd, dconf, and lightdm components so appropriate default values are in the defaults file, not just in the schema file
    • Check dconf and lightdm schemas at LCFG level - should be same as live/defaults.h. Check dconf in LCFG default desktop
    • Take to CEG - DICE EL7 by 1st Feb, COs desktops in February, guinea pigs by 1st March.
  • RT 65774 - try two identical monitors on my machine
  • Need to remove default bridge from kvmtool create
  • Think about disk partition policy
  • Review last reviewed date for documentation
  • Consider more cores as default for KVM guests
  • Is there a way of disabling debugging information being displayed by drupal when there are problems?Can't see how to do safely (needs disable backtrace in /etc/php.ini?)- Ask David Marsh in Physics?
  • Read LISA notes
  • Look at KVM server loading
  • At some point - look at installroot kdcregister solution
  • Look at lcfg-lvm component BUG #807)
  • Look at jubilee lvm config Design flaw in lvm component - requires scsi /dev names to be static, which on a SAN attached machine isn't the case. Surprised haven't tripped up already on this
  • RT 65774

• Chris
  • EL7
    • continue with Sleep component
    • investigate Gnome power-management and document
  • url shortener (once gdm solved)
  • Create Project entries - for KVM refinement project
  • Experiment rename br0 as br33 on metropolitan
  • Think about disk partition policy
  • Review last reviewed date for documentation
  • Commission jubilee's extra disks as an extra pool
  • Identify VMs to move to waterloo and move to balance load
  • Quick look at rootmail
  • RT 69276, 61762

• Stephen
  • LCFG client refactor stage 1
    • schedule debrief meeting
  • EL7
    • Continue thinking about boot.run functionality
    • Complete porting MPU managed resources to the DICE level
      • Coordinate a meeting of COs - for first week of January
    • Finish working towards a stable EL7 release
  • Think about PD - Interested in ZeroMQ
  • Deploy northern as staff.nx (first open up holes and test from home) - awaiting disks
  • Think about disk partition policy
  • Review last reviewed date for documentation
  • Add extra memory to waterloo (and if those work, order up more memory for hammersmith)
  • Incorporate comments into pandemic security doc
  • Blog/announce cronie patch to users
  • RT 68529, 68269

-- AlastairScobie - 16 Dec 2014