472176 - Migration procedure

Status: RESOLVED INCOMPLETE

(Webtools Graveyard :: Graph Server, defect)

Description

[Ryan Doherty (:rdoherty)]

Creating this bug to discuss migration strategies for when we launch 1.0.

Initial possibilities:

1) Dump all old data and start with only new datasets
 Pros: easy
 Cons: lose all old data, lots of angry people

2) Push data from Talos to both old and new graph servers for 2-3 weeks
 Pros: New graph server starts of with lots of data, good for testing db
 Cons: More difficult. Will have to either rewrite Talos or Graph server to update both databases

3) Migrate old database to new database, then switchover to new graph server
 Pros: all data is in new database
 Cons: Could take weeks to port data (or never finish). Lots of places for things to break.


What are everyone's thoughts or other ideas?

Comment 2

[Ryan Doherty (:rdoherty)]

Per Alice's advice, if we migrate, we would only need continuous data, not discrete. 

Some tests are junk.

Dead branches are important for historical trends and comparisons.

Comment 3

[Ryan Doherty (:rdoherty)]

From our weekly meetings, we think option #2 is our best option. But we still want community feedback.

Comment 4

[Ryan Doherty (:rdoherty)]

I just talked with John and he had a use case for keeping old data around. 

During releases we often look back at many of our previous releases to see performance improvements. So we need to pull test data for previous releases. More information gathering will be necessary to get the dates and tests.