migrating application data between hosting providers #100

New issue

Open

opened 2025-02-11 10:38:15 +01:00 by kiara · 0 comments

kiara commented

2025-02-11 10:38:15 +01:00

Owner

As a Fediversity user,
given I have deployed services through Fediversity (#99),
I want to be able to take said services to a different hosting provider, including:

domain registration
running of the services
storing all associated data

in order to have freedom of choice among hosting providers.

The required user interaction should take no more than 5 minutes.

Test

Given I want to migrate my applications between Fediversity set-ups,
When I follow the on-screen migration instructions,
Then all configured services will get up-and-running again at the target environment, with minimal downtime.

Assumptions

no change in control of domains
two Fediversity set-ups (to be provided by ProcoliX) with a run-time environment such as ProxmoX, for an initial test using the same version
a Fediversity configuration of at least a single application (to start)

implementation notes

in case hosts did not recommend the same Fediversity versions (or even different forks), the direction to update in could be clarified by whatever branch we specified to be on if we model pinned deployment module repo+branch+revision like dependency pins in flakes/npins. (needs #304)

dependencies

#105 finalize migration data model requirements
#493 portable ephemeral state
#515 orchestrator state
#103 code-based data model
#110 desired subdomains are assigned to deployed services
#514 data model: migrations
#123 enable back-ups of application
#77 Create a deployment migration string
#78 Start deployment migration
#79 View migration progress indicator
#80 Receive a notification when a migration finishes

**As** a Fediversity user, **given** I have deployed services through Fediversity (#99), **I want** to be able to take said services to a different hosting provider, including: 1. domain registration 1. running of the services 1. storing all associated data **in order to** have freedom of choice among hosting providers. The required user interaction should take no more than 5 minutes. ### Test **Given** I want to migrate my applications between Fediversity set-ups, **When** I follow the on-screen migration instructions, **Then** all configured services will get up-and-running again at the target environment, with minimal downtime. #### Assumptions 1. no change in control of domains 1. two Fediversity set-ups (to be provided by ProcoliX) with a run-time environment such as ProxmoX, for an initial test using the same version 1. a Fediversity configuration of at least a single application (to start) ### implementation notes - in case hosts did not recommend the same Fediversity versions (or even different forks), the direction to update in could be clarified by whatever branch we specified to be on if we model pinned deployment module repo+branch+revision like dependency pins in flakes/npins. (needs #304) ### dependencies 1. #105 finalize migration data model requirements 1. #493 portable ephemeral state 1. #515 orchestrator state 1. #103 code-based data model 1. #110 desired subdomains are assigned to deployed services 1. #514 data model: migrations 1. #123 enable back-ups of application 1. #77 Create a deployment migration string 1. #78 Start deployment migration 1. #79 View migration progress indicator 1. #80 Receive a notification when a migration finishes