access:access_server_2015_maintenance

This is an old revision of the document!


Sprint 5A - 2015 Maintenance

Start 2015-04-10

Task Number Owner Estimate Actual Status Description
5.2 WebApplcation
5.2.1 Mike A 0.0 Done Add “.kml” to track download
5.2.2 Mike A 3 Better display of vehicle configuration.
5.2.3 Mike A 3 0.5 Done Allow for edit of alias on trackers.
5.2.4 Mike A 2 Implement “Map All Trackers” button on trackers page
5.2.5 Mike A 0.0 Done Tacks page, remove “Name”, change Vehicle to source, V or T, entry should href to vehicle or tracker entry
5.2.6 Mike A 0.0 Done Track statistics, remove NAME column
5.2.7 Mike A 0.5 1.25 Done Vehicle page, associate with Tracker, edit details, file Clean up, need set job? Also link to tracker.
5.2.8 Mike A 0.5 1.25 Done Tracker page, edit associate with Vehicle (perhaps vehicle page?), clean up tracker page in general, add sorting
5.3 Reports
5.3.1 Mike A 0.5 0.5 Done Fix writing of products to be fixed width, w/ leading zeros. See if there is a way of retrofitting existing db.
5.3.2 Mike A 5 2 Done Fix utilization report for John
5.4 API
5.4.1 Mike A 3 Fix getConfiguration to include some filtering args (serial)
5.4.2 Mike A 0.5 0.8 Done Test and verify “out of space” exception for Windows clients
5.4.3 Mike A 0.5 0.7 Done Test and verify lastMod setting from client (And & Windows)
5.4.5 Mike A 3 0.4 Done Lock out application update API, support tool iface
5.6 Bugs
Accserv-17 Mike A 0.5 0.1 Done Prevent slashes (both kinds) in file and folder names
5.6.1 Mike A 0.5 0.5 Done Fix uptime to be after midnight next day instead of just 24 hours + delta. To prevent drift of uptime snaps.
5.7 Mike A Access client
Accclt-13 Mike A 0.5 0.1 Done Make sure out of space is dealt with
Accclt-8 Mike A 3 Drag-n-drop to windows explorer
Accclt-15 Mike A 0.5 Windows install sets install to 0.0.0
5.7.1 Mike A 5 Archive project to zip file. Specify what gets zipped etc
Total 32 7.6

Story Velocity

Complete

Prediction: The only stories with velocities are Story 1 (1.5) and Story 2 (1.4). Using an average velocity of 1.45 the predicted end of work is May 13, 2015 (30 work days).

How to archive a project:

  • Project contents are placed in a zip file, named same as project
  • A new folder is created /Projects/Archived to hold zip files once complete.
  • Zip archives are built, then stored in S3, only then are project items removed.
  • All file system items for the project are stored in same path in zip; e.g. Photos/picture12345.jpg, etc.
  • KMZ tracks etc. are stored in Tracks/foo.kmz (per previous rule)
  • Track system tracks are stored in Tracks/gps/date/serial/YYYY/MMDD.txt (same as server file system).
  • Track stats are stored in Tracks/gps/date/serial/YYYY/MMDD.stats.txt (from MySQL)
  • upon completion and storage of project archive, the following items are deleted from normal stores:
    • Project removed from project table
    • Track entries removed from track table
    • Track statistics for associated tracks are removed from trackstats table
    • All files in the project folder, AND the project folder will be deleted from the file store.
  • A complementary API method will exist allowing the project zip to be restored.
    • Sanity/legality tests for table based data will be undertaken to prevent sql injection attacks.
    • The zip file is not modified during a restoration.
  • Both archive and restore methods are to be atomic.
    • It is possible that some data may not be able to be deleted during archive, but this will not affect the state of the zip archive.
  • The customer file store may exceed their storage quota during archive or restore processing.
    • After archive or restore the customer quota may be exceeded.
    • The customer is responsible for deleting files to restore the quota balance.
  • All functionality occurs via a single API call (part of project API)
  • User must be CustomerAdmin in order to execute.
  • Archived project is just like any other file, may be deleted by anyone.
  • Project archiving will be available via menu options in the access client.

Sprint 6 - 2015 Maintenance / Track support

Start 2015-08-06

Task Number Owner Estimate Actual Status Description
6.1 Tracks
6.1.1 1 Add multiple telemetry channels per tracker
6.1.2 0 Add telemetry history for each tracker channel, 5 min per channel, 1 week history This is a tracker task
6.1.3 1 Add TZ to point upload msg to allow for local break @ midnight.
6.1.4 2 GPS Track point orphan detector.
6.2 Architecture
6.2.1 Mike A 1 Characterize current file store performance (track, file )
6.2.2 Mike A 5 Design HSM flow and table structure
6.2.3 Mike A 5 Implement HSM for files
6.2.4 Mike A 3 Implement HSM for tracks
6.2.5 Mike A 3 Test dual server install, requires HSM, rollover DNS
6.3 2 4 Done Add archive project to Access Client. (cust admin only)
6.4 Files
6.4.1 1 When referencing public url for “.html” file, post file contents, not file object.
6.5 3 Characterize file / track upload performance
6.6 3 Investigate and scope a REST API, minimal file and track
Accclt-15 Mike A 0.5 Windows install sets install to 0.0.0
Total 34.5 X

Prediction: 24 actual, using velocity of 1.45.

access/access_server_2015_maintenance.1439396637.txt.gz · Last modified: 2015/08/12 16:23 by mjallison