fediversity/fediversity

back-end supports multiple users #313

New issue

Closed

opened 2025-04-18 10:28:28 +02:00 by kiara · 3 comments

kiara commented

2025-04-18 10:28:28 +02:00

Owner

As an operator using the Fediversity panel,
I want to be able to deploy applications owned by my separate user,
so that I don't have to share them.

implementation notes

so far, our demo code has deployed to a hard-coded set of machines. to fix our Django implementation to live up to its promise of offering distinct users, we should instead have it allow each operator to spin up their own services instead.
ideally the hypervisor should deploy from a user specific to the operator for security
c.f. #314 on making state explicit, which could then perhaps be exposed back into TF state
c.f. #241
c.f. our hypervisor test, which already creates a user
c.f. #615, providing an LDAP that a hypervisor could plug into as well

**As** an operator using the Fediversity panel, **I want** to be able to deploy applications owned by my separate user, **so that** I don't have to share them. ## implementation notes - so far, our demo code has deployed to a hard-coded set of machines. to fix our Django implementation to live up to its promise of offering distinct users, we should instead have it allow each operator to spin up their own services instead. - ideally the hypervisor should deploy from a user specific to the operator for security - c.f. #314 on making state explicit, which could then perhaps be exposed back into TF state - c.f. #241 - c.f. our hypervisor test, which already creates a user - c.f. #615, providing an LDAP that a hypervisor could plug into as well

kiara added this to the Fediversity project

2025-04-18 10:28:28 +02:00

kiara added a new dependency

2025-04-18 10:28:36 +02:00

#116 hypervisor resources are provisioned to deploy services to

kiara added a new dependency

2025-04-18 10:28:50 +02:00

#99 applications deployed on command

kiara added a new dependency

2025-04-19 13:10:05 +02:00

#225 kick-started initial feedback cycle

fricklerhandwerk commented

2025-04-21 13:54:56 +02:00

Owner

The data model already allows multiple deployments per operator, so this is "merely" a UI issue (i.e. needs proper user stories).

The data model already allows multiple deployments per operator, so this is "merely" a UI issue (i.e. needs proper user stories).

kiara commented

2025-04-21 16:43:58 +02:00

Author

Owner

the front-end needs probably the least amount of change here - if given #116 we could recreate current VMs, this ticket would complete that by ensuring VM identities are distinguished between users.

the front-end needs probably the least amount of change here - if given #116 we could recreate current VMs, this ticket would complete that by ensuring VM identities are distinguished between users.

kiara added the

label

2025-05-01 11:59:59 +02:00

kiara referenced this issue

2025-05-01 16:54:28 +02:00

button works deployed #307

kiara added the

label

2025-05-21 13:50:52 +02:00

kiara added a new dependency

2025-05-21 13:54:28 +02:00

#158 users can update their deployment configurations

kiara changed title from ~~multi-tenancy / separate operators' deployments~~ to demonstrate support for multiple users

2025-06-01 16:32:10 +02:00

kiara changed title from ~~demonstrate support for multiple users~~ to ProxmoX back-end supports multiple users

2025-06-01 16:37:17 +02:00

~~kiara referenced this issue 2025-06-04 18:38:26 +02:00~~

API specification published #334

kiara removed this from the Fediversity project

2025-06-10 19:07:10 +02:00

kiara referenced this issue

2025-06-10 19:40:00 +02:00

applications deployed on command #99

kiara referenced this issue

2025-06-10 20:41:11 +02:00

kick-started initial feedback cycle #225

kiara added a new dependency

2025-07-30 09:06:01 +02:00

#483 [D2.2] Software release beta version [2027-03-31]

kiara added this to the Fediversity project

2025-08-02 16:41:01 +02:00

kiara added the

label

2025-12-02 21:27:22 +01:00

kiara added a new dependency

2025-12-04 11:07:26 +01:00

#615 applications integrated with user management

kiara added a new dependency

2025-12-04 11:39:01 +01:00

#291 code passes security check

kiara referenced this issue

2025-12-11 15:30:24 +01:00

code passes security check #291

kiara changed title from ~~ProxmoX back-end supports multiple users~~ to hypervisor back-end supports multiple users

2026-05-02 17:15:58 +02:00

kiara referenced this issue

2026-05-04 16:26:07 +02:00

panel: run deployments asynchronously, notify via WAMP #900

kiara referenced this issue from a commit

2026-05-04 19:44:59 +02:00

panel: run deployments asynchronously, notify via WAMP (#900)

kiara changed title from ~~hypervisor back-end supports multiple users~~ to back-end supports multiple users

2026-05-14 18:48:24 +02:00

~~kiara referenced this issue 2026-05-14 19:38:31 +02:00~~

panel: enforce per-user deployment isolation #967

kiara commented

2026-05-14 19:42:33 +02:00

Author

Owner

should be fixed with #967 given for incus the user distinction may not apply

should be fixed with #967 given for incus the user distinction may not apply

kiara referenced this issue from a pull request that will close it,

2026-05-14 19:43:44 +02:00

panel: enforce per-user deployment isolation #967

kiara referenced this issue from a commit

2026-05-14 20:18:06 +02:00

panel: enforce per-user deployment isolation (#967)

kiara removed a dependency

2026-05-14 20:18:39 +02:00

#615 applications integrated with user management

kiara removed a dependency

2026-05-14 20:18:43 +02:00

#116 hypervisor resources are provisioned to deploy services to

kiara closed this issue

2026-05-14 20:18:45 +02:00

Sign in to join this conversation.

No labels

application-offering

configure-applications

ambition/install-applications

update-applications

user-management

component: fediversity panel

component: nixops4

estimation high: >3d

estimation low: <2h

estimation mid: <8h

infinite points

project-management

role: application developer

role: application operator

role: hosting provider

role: maintainer

type: deliverable

type: key result

type: objective

type: user story

user experience

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#99 applications deployed on command

fediversity/fediversity

#158 users can update their deployment configurations

fediversity/fediversity

#225 kick-started initial feedback cycle

fediversity/fediversity

#291 code passes security check

fediversity/fediversity

#483 [D2.2] Software release beta version [2027-03-31]

fediversity/fediversity

Reference

fediversity/fediversity#313

No description provided.