Please fill in actual activity for Last Month (December) and intended activity for This Month (January) for projects you are responsible for. For reference, the intended activity recorded for December 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.

  • Revisit Account Management
    • December: complete review, start writing up
    • Last Month: waiting for final checks on afs tests coverage
    • This Month: start writing up once afs tests completed

  • School Database Revamp
    • December: Additions/corrections from Graham. Then send out.
    • Last Month: Nothing.
    • This Month: Additions/corrections from Graham. Then send out.

  • Inventory Improvement
    • December: Farr willing, complete final design document and publish.
    • Last Month: Some limited work on workflow document
    • This Month: Complete final design document and publish.

  • Prometheus AFS PTS conduit
    • December: final checks that all branches of VL conduit are tested, sign off
    • Last Month: Nothing
    • This Month: Final checks that all branches of VL conduit are tested, sign off

  • Password strength checks
    • December: Probably just hack the configuration changes in by hand for a basic test. Do it properly through the component if time permits.
    • Last Month: Yet another new version from Russ built but not tested yet
    • This Month: Test, write conclusions, probably stall at next meeting

  • Account reconciliation
    • December: host principal deletion; resolve uid matter with IS either way; Alison, Lindsey and Toby to meet to discuss procedures
    • Last Month: old host principals deleted; further sweep and disabling of old accounts
    • This Month: suggest we drop uid mismatch and solve locally when and if required - not much point pursuing with IS; Alison, Lindsey and Toby to meet to discuss procedures

  • Webmark Reform
    • December:
    • Last Month: disrupted by work arising from talk -> paper conversion
    • This Month: a functional form for user acceptance

  • School Database Revamp: Phase 1B & 2B
    • December: Finish self DDL generation and reload diff check. Implement tool chain.
    • Last Month: Self DDL generation completed and changes to account for differences made. A few small spurious anomalies in the differences remain to be addressed, including a dependency ordering issue. Nothing achieved on tool chain.
    • This Month: Fix remaining self DDL generation anomalies. Commit. Implement tool chain.

  • VM / cloud options survey
    • December: produce preliminary report
    • Last Month:about 1/2 way through prelim report
    • This Month:finish report

  • Lifecycle code design
    • December: wait for code review
    • Last Month: stalled on code review
    • This Month: wait for code review

  • Investigate AFS on ECDF storage
    • December: Get some basic iozone (and/or bonnie) tests to run so we can compare results.
    • Last Month: No news from ECDF.
    • This Month: Again get basic iozone and/or bonnie tests going.

  • Deploy Git/Gerrit as full services
    • December: Migrate appropriate users to new server, update documentation in view of new setup
    • Last Month:initial draft of user documentation done. Work on AFS access
    • This Month: Finish documentation, begin work on supporting CGIs

  • Review of OpenLDAP DICE client configuration
    • December: Possibly look at DICE::Authorize code. However, would now welcome clarification from this meeting: does anybody have any strong philosophical/policy objections to moving DICE to a conventional client/server LDAP setup?
    • Last Month: No effort other than continued testing by all COs - which showed that nslcd restarts need to done when X.509 service certs change ...
    • This Month: Start planning for deployment with SL7: identify loose ends.

  • Replace CVS with SVN on www.inf
    • December: Check test SVN with users, confirm conversion options. Arrange switchover.
    • Last Month: Very little, checking avail => authz file conversion
    • This Month: Check test SVN with users, confirm conversion options. Arrange switchover.

  • DICE virtual image with teaching software for students - trial
    • December: Make it possible to login to a Virtual DICE VM using DICE credentials and get AFS homedir, all from anywhere on EdLAN, rather than just from the Informatics network. Document this, then finally announce the (non-trial) Virtual DICE. Draw up a timetable for the creation of new images. Write up, sign off.
    • Last Month: Some discussion.
    • This Month: Toby is arranging a meeting of interested parties to talk about LDAP and EdLAN and Virtual DICE. If we get an easy and quick solution then I'll adapt Virtual DICE to suit, change the documentation and declare the project finished. If not then I suggest we declare the project finished anyway and allocate further work to project 276, Virtualised DICE image - follow on.

  • Securing School Web Servers
    • December: Update project proposal, make a guess at effort/benefit/affect on users for options listed in the above link.
    • Last Month: Emailed notes to COs. Nothing else.
    • This Month: Update proposal, and estimate effort/benefit/affect on users for options listed on Project287SecuringWebServers

  • remove obsolete deps for LCFG client
    • December: Work out the best way to parse the LCFG XML structure. Design an object-oriented API for the profile information.
    • Last Month: Created a Moose-based prototype which can parse profiles stored as XML and DBM format, can diff profiles and can produce DBM output files.
    • This Month: Convert prototype into a lighter-weight equivalent.

  • Intrusion Detection System
    • December: Started.
    • Last Month: Initial dive into the documentation!
    • This Month: More reading, fire up a prototype

  • Produce a talks.cam not-a-service for trialling
    • December: Started.
    • Last Month: Obtained code from cam, initial email discussion suggests code base is not maintained much (only one developer left who knows about the project and he's on secondment elsewhere)
    • This Month: Start experimenting with code

  • Options for two-factor authentication
    • December: Started.
    • Last Month: Asked some people for detailed requirements. Got some info.
    • This Month: Still need to clarify objectives/aspirations.

-- TimColles - 06 Jan 2014

Topic revision: r17 - 08 Jan 2014 - 09:55:02 - TimColles
 
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