MPU Meeting Tuesday 20th January 2015

Systemd

The component has now been documented. The project is almost complete, just a few loose ends to be tidied up.

SL7

The sleep component is now working on SL7, it just needs to be put on SL6 to bring the two platforms back into sync. The DICE desktop will now have it by default for office and lab desktop machines.

The dice package lists and headers seem to be mostly working now. We still need to finish the changes for lightdm, Stephen will push in the PAM changes necessary to use xscreensaver on SL7. Stephen is also dealing with the openssh & wallet changes (see #832 and #833). We should avoid pulling in the dns component for SL7 since it doesn't currently work. We also need to deal with the routing component.

There is now an entry for EL7 on the LCFG website, there is currently an issue with the links to the installer ISOs since the file names refer to "sl7" but the platform is "el7". Stephen will have to come up with a fix.

We should create an SL7 build host for CO usage with a buildsl7 cname. This could be based on the LCFG profile for galavm3 or zip. Chris will do that and announce to COs.

The weekly release scripts need updating for SL7, Stephen will do that once we have an SL7 build host which we can use for building the installer ISO.

The systemd configuration for updaterpms will be changed to have unbuffered output direct to the tty (see #799). This means we can lose some output from the rpm install scripts but that's no different from what we have on SL6. We will provide a macro which can be used to re-enabled the buffered output to journald. Alastair will blog about the changes.

The vboxadditions package has been updated everywhere as the old version did not work on SL7. The install script needed to be patched to avoid returning a non-zero exit status.

Stephen needs to blog about the new ngeneric and sysinfo features which were added to support the changes in logrotate configuration.

Miscellaneous Development

Nothing this week.

Operational

metropolitan
Chris has tested replacing br0 with br33 on metropolitan, this seemed to work fine.

oyster
The KVM server oyster was rebooted to restore sanity after it became very confused when the IBM storage array had a hiccup.

This Week

  • Alastair
    • systemd project
      • 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
      • Add tests
    • EL7 project
      • Consider how components will work with systemd
      • Cook book entry
        • component need to start after daemon in certain cases ..... eg ssh where component will start daemon if daemon isn't already started..
      • 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 lightdm issues
        • Pull into DICE layer
        • power management
      • Look at routing (rdisc) start time - pull routing header for time beingDecided to keep lcfg-routing, but modified to start after network-online.target
      • Look at LCFG bug #799 (systemd buffered output)See bug entry for details.
        • make change to 'tty' * for the record, blog about the issue
      • convert lcfg-dconf and lcfg-lightdm to module
      • apply sensible defaults to xscreensaver rpm - blankscreen and DPMS enabled Still to enable by default - just waiting for final check on a real machine.
      • At some point - look at installroot kdcregister solution
      • Read Stephen's blog article on boot.run functionality replacement
    • 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
    • Read LISA notes
    • Look at KVM server loading
    • Schedule firmware upgrade for DS3254
    • Check scans
    • Spec up new DR server and circulate

  • Chris
    • EL7
      • Create SL7 buildhost (for testing SL7 release and for COs to play with)
      • investigate Gnome power-management and document
    • url shortener (once gdm solved)
    • Create Project entries - for KVM refinement project
    • Update KVM host documentation to say "don't setup with br0 - use wire specific bridge names for all bridges"
    • Think about disk partition policy
    • Review last reviewed date for documentation
    • Identify VMs to move to waterloo and ask Carol to move to balance load
    • 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
        • wallet
        • DNS (avoid pulling in DNS header?)
        • Pull inf layer screensaver config to DICE
      • Ask Kenny to ask around if gdm is working fine for MDP
    • Test northern's SAS disks in metropolitan
    • Junk central
    • Think about PD - Interested in ZeroMQ
    • 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)

-- AlastairScobie - 20 Jan 2015

Topic revision: r8 - 03 Feb 2015 - 10:46:14 - StephenQuinney
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies