Please fill in actual activity for Last Month (March) and intended activity for This Month (April) for projects you are responsible for. For reference, the intended activity recorded for March is included where an entry had been made (it is considered unhelpful to alter this to match what actual activity was :). It is acceptable to change devproj milestones as part of this process, however if you do please indicate that you have done so below, for example by adding a Change of Plan bullet point, so that the meeting is alerted to the changes.

  • Scanning for compromised machines
    • March: Finish.
    • Last Month: No more work. Decision taken to write this up as-is and submit for signoff.
    • This Month: Will submit for signoff at May meeting, at which I will be physically present.

  • Inventory Improvement
    • March:Wake up project
    • Last Month: Nothing
    • This Month: Refresh perl/dbix skills. Start project.

  • Prometheus AFS PTS conduit
    • March:VL Store and conduit tests completed and in gerrit, possibly sign off
    • Last Month: Less than I had hoped.
    • This Month: Sort out Gerrit mixup, finish and sign off

  • Password strength checks
    • March: Wait for 1.10 to be tested, then test the plugin.
    • Last Month: 1.10 tested, but didn't get the plugin tested
    • This Month: test the plugin

  • Account reconciliation
    • March: Delete any accounts which are archived
    • Last Month: Continued to archive staff accounts.
    • This Month: Delete archived accounts.

  • Webmark Reform
    • March: Add basic (form) input and (text) output to prototype. Design "approval queue" subsystem.
    • Last Month: Didn't get time to spend on development.
    • This Month: Make prototype functional. Meet with main customer to guide priority of approval queue work.

  • Collaborative LaTeX System - Remedial Work
    • March: finish
    • Last Month: Tried regressing and upgrading svn. worked through some apache configuration changes. Currently adding debug code to modules to identify what's currently producing a forbidden code.
    • This Month:finish

  • School Database Revamp: Phase 1B & 2B
    • March: More.
    • Last Month: Largely completed new generation process for XSD schema from the replacement change management adapted schema model. Proceeded with diff checks of output against output of existing system.
    • This Month: Continue with diff checks and subsequent adjustments. Finalize the new schema model and XSD generation process.

  • SL6 upgrade for US Unit
    • March: forumtracker move provisionally scheduled 14/3. Final report and sign off.
    • Last Month: forumtracker moved.
    • This Month: final report and sign off

  • SL6 upgrade for Services Unit
    • March: Really will get the last machines done. Note we're not doing maelcum, RAT I believe said they would.
    • Last Month: All done but mail server and backup print server
    • This Month: Remaining machines, sign off

  • System Security Enhancements.
    • March: Finish documentation (mainly BuzzSaw related).
    • Last Month: Finished documentation
    • This Month: Submit for sign-off

  • Windows 7 Upgrade
    • March: Upgrade AT support machine. Finalise decision on file storage.
    • Last Month: Amended report on AFS problems with file storage details.
    • This Month: Finalise decision on file storage

  • Increasing Energy Savings from DICE Desktops
    • March: Continue the testing, broadening the test to volunteers outside the computing staff. (No further software changes are planned.) Finish the basic BuzzSaw sleep data report for the Energy Coordinator. Once testing seems OK, roll it out DICEwide.
    • Last Month: I now have some test volunteers and I've already had some useful feedback from them. The BuzzSaw sleep data report was finished (and the Energy Coordinator will be doing interesting things with the data as soon as he has time).
    • This Month: Continue getting feedback from testing. When the config and docs seem stable and suitable, roll out the new sleep version, with help from the Energy Coordinator.

  • VM / cloud options survey
    • March: generate draft survey and circulate amongst COs & Paul
    • Last Month:nothing
    • This Month: generate draft survey and circulate amongst COs & Paul

  • Lifecycle code design
    • March: Assess what design we have and start to flesh out.
    • Last Month: Initial asessment and discussions.
    • This Month: More of the same; probably some prototyping.

  • Investigate AFS on ECDF storage
    • March: Move to evaluation/implementation. Work wont start on it until SL6 work complete.
    • Last Month: Some news that the extra disk space for all researchers isn't being fully funded.
    • This Month: Arrange meeting with ECDF and IS people and to discuss what space we can get our hands on.

  • Deploy Git/Gerrit as full services
    • March: Smooth off rough edges, update documentation
    • Last Month: Rough edges smoothed, draft of documentation written
    • This Month: Finish Documentation, cross Ts, Dot Is.

  • Review of OpenLDAP DICE client configuration
    • March:
    • Last Month: Have been investigating the state of our current provision and the historical reasons for it. Current notes are at https://wiki.inf.ed.ac.uk/DICE/Project267InitialIdeas
    • This Month: Pursue the same. My preference is to investigate moving to a more conventional client<->server model for LDAP (i.e. having clients refer to a small set of servers) rather than making adjustments to the current provision: a good overall ambition is to simplify what we currently have. If there are objections to the client<->server model on policy grounds (e.g. reliance on network; dead servers => dead clients; etc.), it would be good to raise them now. If we did decide to make such a move, it would need lengthy testing and this project would take quite a while.

    • March: Start the project.
    • Last Month: Added basic compilation tests. Moved some code from rdxprof to LCFG::Client module. Sanitised the way in which subroutines get called. Added some unit tests.
    • This Month: Run through perltidy and perlcritic. Enable warnings and deal with the fallout.

-- TimColles - 28 Mar 2013

Topic revision: r14 - 03 Apr 2013 - 00:57:47 - IainRae
 
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