access:access_server_2015_maintenance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:access_server_2015_maintenance [2015/04/27 19:41] mjallison |
access:access_server_2015_maintenance [2015/08/31 23:15] (current) mjallison [Sprint 6 - 2015 Maintenance / Track support] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| 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). | 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). | ||
| - | ======== Sprint 5B - 2015 Maintenance ====== | + | 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. | ||
| - | **Start** 2015-04-10 | + | * 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 ^ | ^ Task Number ^ Owner ^ Estimate ^ Actual ^ Status ^ Description ^ | ||
| - | | **5.1** | | | | | **Tracks** | | + | | **6.1** | | | | | **Tracks** | |
| - | | **5.5** | | | | | **Architecture** | | + | | 6.1.1 | | 1 | 1 | Done | Add multiple telemetry channels per tracker | |
| - | | 5.5.1 | Mike A | 1 | | | Characterize current file store performance | | + | | 6.1.2 | | 0 | | | <del>Add telemetry history for each tracker channel, 5 min per channel, 1 week history</del> This is a tracker task | |
| - | | 5.5.2 | Mike A | 5 | | | Design HSM flow and table structure | | + | | 6.1.3 | | 1 | 0.5 | Done | Add TZ to point upload msg to allow for local break @ midnight. | |
| - | | 5.5.3 | Mike A | 5 | | | Implement HSM for files | | + | | 6.1.4 | | 2 | | | GPS Track point orphan detector. | |
| - | | 5.5.4 | Mike A | 3 | | | Implement HSM for tracks | | + | | **6.2** | | | | | **Architecture** | |
| - | | 5.5.5 | Mike A | 3 | | | Test dual server install, requires HSM, rollover DNS | | + | | 6.2.1 | Mike A | 1 | 3 | Done | Characterize current file store performance (track, file ) | |
| - | | **Total** | | **17** | **X** | | | | + | | 6.2.2 | Mike A | 5 | | N/A | Design HSM flow and table structure | |
| + | | 6.2.3 | Mike A | 5 | | N/A | Implement HSM for files | | ||
| + | | 6.2.4 | Mike A | 3 | | N/A | Implement HSM for tracks | | ||
| + | | 6.2.6 | | new | 7 | Done | Implement streaming of file upload | | ||
| + | | 6.2.5 | Mike A | 3 | 0 | Defer | 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 | 0 | N/A | Can't be done <del>When referencing public url for ".html" file, post file contents, not file object.</del> | | ||
| + | | 6.5 | | 3 | | Done | Characterize file / track upload performance | | ||
| + | | 6.6 | | 3 | | | Investigate and scope a REST API, minimal file and track | | ||
| + | | 6.7 | | new | 2 | Done | Add track/cust-active bits to control access to server functionality | | ||
| + | | Accclt-15 | Mike A | 0.5 | | | Windows install sets install to 0.0.0 | | ||
| + | | **Total** | | **34.5** | **17.5** | | | | ||
| - | Prediction: 12 actual, using velocity of 1.45. | + | Prediction: 24 actual, using velocity of 1.45. |
access/access_server_2015_maintenance.1430163710.txt.gz · Last modified: 2015/04/27 19:41 by mjallison
Page Tools
