Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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.

Also, we need to point our dev-ops emails and email bounce notifications to new addresses in the new org.

Slack

DONE

Jira/Confluence

In progress - Ann working with IT

We’ll also need to extract information we need from Virus Scanning of Files

Sumologic

Owner: Dwayne

Only Bridge uses SumoLogic. However, IT still owns the account. Reaching out to IT to see if we can claim ownership of the account.

Note that we will need to update the billing (after the spin-off is finalized).

The work is entirely administrative. I estimate the work doesn’t even reach 1 sprint point.

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.

TODO break down this work and cost it

Jumpcloud

Zoom

G-Suite

New Relic

Owner: Dwayne

Only Bridge uses New Relic. I am an admin on New Relic and can take ownership of it. Reaching out to IT to make confirm that this is okay.

Note we currently log into New Relic using JumpCloud. In order to de-couple New Relic migration from JumpCloud migration, we’ll need to create an Authentication Domain that allows login using username/password.

Note that we will need to update the billing (after the spin-off is finalized).

The work is entirely administrative. I estimate the work doesn’t even reach 1 sprint point.

Synapse Dev

Owner: Dwayne

This is used by Integ Tests. Current assumption is that after the spin-off, we won’t have permission to use Synapse Dev anymore.

The work involved is to create a BridgeTest account in Synapse Prod to run integ tests, and a trivial code change in Integ Test and Worker Integ Test to use this account and to use Synapse Prod instead of Synapse Dev.

Estimated effort: 1 sprint point

CITI Training

Open Bridge team to take CITI Training via Sage this year. We will need to figure this out for next year.

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.

TODO break down this work and cost it

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.

Up for renewal from GoDaddy on Apr 13. We’ll want to take care of this before, let’s say, end of March.

Web Hosting

Make sure S3 buckets where Bridgedigital.health web sites live get transferred to OpenBridge AWS account, along with setting up Cloudfront or whatever other DNS correctly

Firebase/Crashlytics

Android Certs Repo

Open ID

LastPass

DONE

AWS

We own:

  • org-sagebase-bridgedevelop

  • org-sagebase-bridgeprod

Deprecated BridgeDownstream envs (that we can (probably) turn off):

  • org-sagebase-mobilehealth-dataengineering-dev

  • org-sagebase-mobilehealth-dataengineering-prod

  • No labels