Please fill in actual activity for Last Month (February) and intended activity for This Month (March) for projects you are responsible for. For reference, the intended activity recorded for February 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
    • February: start writing up once afs tests completed
    • Last Month: Draft final report written, pending comments/figures
    • This Month: Complete final report

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

  • Inventory Improvement
    • February: Publish as is. Stall
    • Last Month: Chris fed back some comments
    • This Month: Incorporate Chris's comments and publish

  • Password strength checks
    • February: Some more testing. Then either do the necessary component changes to allow it to be deployed "properly" or write up conclusions and staill pending EASE KDC progress.
    • Last Month: George, Kenny and Toby met. Notes are here.
    • This Month: ?

  • Webmark Reform
    • February: a functional form for user acceptance
    • Last Month: holiday.
    • This Month: as Feb.

  • School Database Revamp: Phase 1B & 2B
    • February: Complete XSLT data generation and loading process. Implement each individual command in tool chain.
    • Last Month: Completed XSLT data generation and loading process. Started and nearly completed Coupler integration. Started repeat of full QA through all process steps.
    • This Month: Complete Coupler integration. Conduit meta data integration. Complete QA of full process. Start writing process documentation.

  • Lifecycle code design
    • February: wait for code review
    • Last Month: Code review done. Only a few minor issues. Code is in testing with real data.
    • This Month: Continue testing. Address issues raised in code review.

  • Investigate AFS on ECDF storage
    • February: Get some more bonnie++ figures for things like our AFS served from local RAID 10 disks. But probably not much more unless ECDF people are suddenly free.
    • Last Month: Nothing
    • This Month: Not much probably. Depends on ECDF time.

  • Deploy Git/Gerrit as full services
    • February: finish and test cgis
    • Last Month: CGIs nearly done. Docs tested on more users, new repositories created.
    • This Month: Finish CGIs, docs

  • Replace CVS with SVN on www.inf
    • February: Complete user testing, finalise configuration, and arrange switchover.
    • Last Month: configuration of apache/SeaMonkey more work than expected, and turned into can of worms. User(s) requested delay until end of teaching (April)
    • This Month: finish configuration, finalise testing, confirm switchover schedule

  • Securing School Web Servers
    • February: Move to project to "Implementation" and start working through the various options in priority order. I'll have a chat with Stephen (or anyone else who wants to give some input) to see if he agrees with my ordering.
    • Last Month: Moved to implementation. Looking through the Detonator scan results, lead to some small changes to apacheconf headers to be less verbose about our PHP version. Also while dealing with WordPress operation stuff, came across a security plugin Wordfence, which looks like it might be useful to install on WP sites. Not much on the actual list of securing options though.
    • This Month: Work through the list of securing options.

  • Intrusion Detection System
    • February: This is currently queued behind password-strength-checking and lifecycle code review, so perhaps no prototype this month.
    • Last Month: No prototype, but some tests using tcpdump to capture self-managed web server site names. That looks promising,and doesn't appear to load the edge router much at all.
    • This Month: Package up the web-server hunter, then move back to snort.

  • Options for two-factor authentication
    • February: Get results of above.
    • Last Month: Last date for call for requirements was Friday 28th Feb. Have received some submissions, which I will now synthesize. At least one initial idea can immediately be shelved owing to lack of interest.
    • This Month: Publish findings - these should/might provide a tentative plan for some work/investigation.

  • RHEL7 based LCFG port
    • February: Create installbase and installroot package lists. Attempt build of LCFG core. Deploy F19 PkgForge. Decide on SL or Centos?
    • Last Month: In the absence of SL7 news or releases we're currently porting to Fedora 20. Stephen has got a Fedora 20 Package Forge build service up and running. Chris is using it to build updaterpms, the LCFG client, and numerous dependencies. Also made an F19 installbase package list. Read the SL7 port diary for more detail.
    • This Month: We expect work on this project to accelerate as Stephen is freed up to join it this month. We'll carry on with the plan.

  • LCFG systemd component
    • February: Identify how systemd impacts on component framework. Present to COs on systemd. Decide on approach wrt LCFG components. Design component schema.
    • Last Month: Presented talk to COs. Designed and 90% wrote component to produce systemd configuration (simplistic, no abstraction)
    • This Month: Complete component. Try configuring systemd on a Fedora 20 machine (requires working rdxprof). Further look at how components will work (with minimal changes)

-- TimColles - 03 Mar 2014

Topic revision: r18 - 05 Mar 2014 - 10:02:31 - GrahamDutton
 
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