Migrating encrypted Workloads

Same cloud - different owner

Migration within the same cloud to a different owner Cloud A — Domain A — Project A — User A => Cloud A — Domain A — Project A — User B Cloud A — Domain A — Project A — User A => Cloud A — Domain A — Project B — User B Cloud A — Domain A — Project A — User A =>Cloud A — Domain B — Project B — User B

Steps used:

  1. Create a secret for Project A in Domain A via User A.

  2. Create encrypted workload in Project A in Domain A via User A. Take snapshot.

  3. Reassign workload to new owner

  4. Load rc file of User A & provide read only rights through acl to the new owner

    openstack acl user add --user <userB_id> <secret_href> --insecure

Different cloud

Migration between clouds Cloud A — Domain A — Project A — User A => Cloud B — Domain B — Project B — User B

Steps used:

  1. Create a secret for Project A in Domain A via User A.

  2. Create an encrypted workload in Project A in Domain A via User A. Trigger snapshot.

  3. Reassign workload to Cloud B - Domain B — Project B — User B

  4. Load RC file of User B.

  5. Create a secret for Project B in Domain B via User B with the same payload used in Cloud A.

  6. Create token via “openstack token issue --insecure”

  7. Add migrated workload's metadata to the new secret (provide issued token to Auth-Token & workload id to matadata as below)

Last updated

Was this helpful?