Placeholder for doc migration process for SaaS

Aqsaxvv092 commented 4 years ago

Document migration process from self-host to SaaS.

Highlights:

This is a one time process hence CS team's involvement is necessary.
Back up restore only works one way - from self hosted to SaaS (not the other way).
Like the regular backup restore process - versions (SaaS and self hosted) must match before restore.
Aporeto integration will not be migrated. Only Compute core functionalities (including CNAF).

Tests to do for this doc:

[ ] Backup restore from self hosted to SaaS.
[ ] Check what happens with projects since SaaS only supports one console.
[ ] Check user management after migration to SaaS
[ ] Sanity check migration of policies, audits, image info etc that are part of normal restore process.

Points to note:

Note that we cannot migrate anything that is not part of the existing backup and restore (e.g., registry).
Also, once restore is done, any existing data on the cloud account is deleted (e.g., defenders and accounts). Customer will have to reinstall defenders and repopulate any data it had on PCC.
Defender / Monitor / Radar - we will migrate all data except registry. Only the registry images will be excluded, the registry settings will also be migrated The cloud accounts credentials will also be migrated.
Manage - we will only migrate: collections / tags alerts defender page (we have no simple way to exclude it) Credential store + secrets Proxy

Aqsaxvv092 commented 4 years ago

Jonathan Brown will be working on this.

iansk commented 4 years ago

@jb4lsu Aqsa mentioned that you're working on this one. How's it coming along?

twistlock / docs