applications deployed on command #99

Open
opened 2025-02-11 10:33:52 +01:00 by kiara · 0 comments
Owner

As a Fediversity user,
I want to deploy my initial specified configuration onto VMs,
so that I may use my selected applications.

Test:

Given I have a configuration in the FediPanel, but no deployment yet,
When I run the deployment
Then, all configured services are accessible under the specified domain.

dependencies

  1. #494 data model used
  2. #313 ProxmoX back-end supports multiple users
  3. #116 Proxmox resources are provisioned to deploy services to
  4. #76 Deployed services are accessible under the configured domain
  5. #110 desired subdomains are assigned to deployed services
  6. #515 orchestrator state persisted

implementation notes

data model needs

this may involve facilitating data model (see #103) resources for:

  • nixos configurations
  • deployments
  • IP addresses (#113)
  • DNS (#110)

any of those may involve steps:

  1. concept
  2. hard-coded PoC implementation
  3. reproduced
    • packages upstreamed
  4. test
  5. module
    • upstreamed
  6. SHB module (#369)
    • upstreamed
  7. battery replaceable (by unmanaged instance)
  8. resource may be swapped out
**As** a Fediversity user, **I want** to deploy my initial specified configuration onto VMs, **so that** I may use my selected applications. ### Test: **Given** I have a configuration in the FediPanel, but no deployment yet, **When** I run the deployment **Then**, all configured services are accessible under the specified domain. ### dependencies 1. #494 data model used 1. #313 ProxmoX back-end supports multiple users 1. #116 Proxmox resources are provisioned to deploy services to 1. #76 Deployed services are accessible under the configured domain 1. #110 desired subdomains are assigned to deployed services 1. #515 orchestrator state persisted ### implementation notes <details> <summary> data model needs </summary> this may involve facilitating data model (see #103) [resources](https://git.fediversity.eu/Fediversity/meta/src/branch/main/architecture-docs/architecture.md#configuration-data-flow) for: - [x] nixos configurations - [x] deployments - IP addresses (#113) - DNS (#110) <!-- - domains --> any of those may involve steps: 1. concept 1. hard-coded PoC implementation 1. reproduced - packages upstreamed 1. test 1. module - upstreamed 1. SHB module (#369) - upstreamed 1. battery replaceable (by unmanaged instance) 1. resource may be swapped out </details>
kiara changed title from deploying Fediverse services to 'one-click' deployment of Fediverse services 2025-02-11 10:51:36 +01:00
kiara added this to the Fediversity project 2025-04-18 10:26:33 +02:00
kiara changed title from 'one-click' deployment of Fediverse services to 'one-click' deployment of Fediversity applications 2025-06-01 13:40:25 +02:00
kiara changed title from 'one-click' deployment of Fediversity applications to deploying Fediversity applications 2025-06-01 16:59:25 +02:00
kiara changed title from deploying Fediversity applications to applications deployed on command 2025-06-10 18:44:54 +02:00
kiara removed this from the Fediversity project 2025-06-10 19:07:17 +02:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: fediversity/fediversity#99
No description provided.