This doc captures the work needed to migrate off of Sage-owned services and infrastructure.
Gmail
This will include individuals setting up or transferring accounts from their sagebase.org emails to their new emails. Also, individuals will need to backup their email or otherwise make sure we don’t lose knowledge when we change our email addresses.
Slack
Jira/Confluence
Sumologic
Owner: Dwayne
VPN
Owner: Dwayne
Bridge Server, Worker, Jenkins, and DB are all associated with the Bridge VPN. Part of this work involves moving them to a different network not owned by Sage. This may mean abandoning our Cloud Formation templates. More investigation is required.
Jumpcloud
Zoom
G-Suite
New Relic
Owner: Dwayne
Note: We currently log in to New Relic using Jumpcloud.
Synapse Dev
Owner: Dwayne
This is used by Integ Tests.
CITI Training
Transition Apps to New Accounts
GitHub Repo Transfer
Owner: Dwayne
Right now, a lot of server-side repos are still under Sage-Bionetworks. This is because we use Travis, and Travis keys are encrypted using a key specific to the repo. Migrating or forking the repos will require us to re-encrypt all of our keys in Travis. This isn’t difficult work, but it is work that needs to be enumerated and costed.
Does not include license stuff, which will be handled separately.
Web Domains
sagebridge.org
We have existing customers with existing apps that talk to Bridge Server using sagebridge.org. Ideally, we keep ownership of this domain.