fediversity/fediversity
13
2
Fork 6
Code Issues 157 Pull requests 29 Projects 1 Activity Actions

Proxmox resources are provisioned to deploy services to #116

New issue
Open
opened 2025-02-11 16:06:12 +01:00 by kiara · 2 comments
kiara commented 2025-02-11 16:06:12 +01:00
Owner
Copy link

As a Fediversity user,
I want my deployment to automatically provision VMs,
so that I do not need to perform additional manual steps.

Test:

Given I have a configuration in FediPanel, but no deployment yet, and no resources (machines) provisioned for that deployment,
When I run the deployment,
Then, the necessary VMs are provisioned within specified resource constraints.

implementation notes

needed resources include:

  • MAC addresses
  • IP-addresses
  • Virtual Machine(s)
  • Storage

This process should further prevent conflicting ownership claims over resources, i.e. a given VM cannot be claimed by multiple deployments at once.

ephemeral state to un-hardcode (c.f. #314):

  • hardware/VM info (from the nixos perspective) - to be passed on vm creation, if not using nixos-facter
  • proxmox info (as per #319): make configurable (to host)?
    • instance
    • credentials
    • hardware info - could be covered by say nixos-facter?
    • where to put things
    • resources to allocate
    • target system architecture (x86_64-linux, while our proposal involved open-source hardware e.g. riscv64-linux)
  • authorized SSH keys (users.nix, keys/) (c.f. #199) - move to input?

orchestrator state to un-hardcode (c.f. #515):

**As** a Fediversity user, **I want** my deployment to automatically provision VMs, **so that** I do not need to perform additional manual steps. ### Test: **Given** I have a configuration in FediPanel, but no deployment yet, and no resources (machines) provisioned for that deployment, **When** I run the deployment, **Then**, the necessary VMs are provisioned within specified resource constraints. ### implementation notes needed resources include: - MAC addresses - IP-addresses - Virtual Machine(s) - Storage This process should further prevent conflicting ownership claims over resources, i.e. a given VM cannot be claimed by multiple deployments at once. - c.f. infra variant (#433) - c.f. [`proxmox-provision.sh`](https://git.fediversity.eu/Fediversity/Fediversity/src/commit/5db04d0c50514423959fc246c4a873da7f12019c/infra/proxmox-provision.sh) which imperatively performs similar logic ephemeral state to un-hardcode (c.f. #314): - [ ] hardware/VM info (from the nixos perspective) - to be passed on vm creation, if not using `nixos-facter` - [ ] proxmox info (as per #319): make configurable (to host)? - [ ] instance - [ ] credentials - [ ] hardware info - could be covered by say `nixos-facter`? - [ ] where to put things - [ ] resources to allocate - [ ] target system architecture (`x86_64-linux`, while our proposal involved open-source hardware e.g. `riscv64-linux`) - [ ] authorized SSH keys (`users.nix`, `keys/`) (c.f. #199) - move to input? orchestrator state to un-hardcode (c.f. #515): - [ ] IPs/gateways - e.g. [netbox](https://github.com/netbox-community/netbox) ([open-core](https://netboxlabs.com/pricing/), tho as per several reddit threads with limited competition) - [`services.netbox`](https://search.nixos.org/options?channel=unstable&show=services.netbox.settings&query=netbox) - [nixos wiki](https://wiki.nixos.org/wiki/NetBox) - `POST` request to [`/api/ipam/prefixes/{id}/available-ips/`](https://netbox.protagio.org/api/schema/swagger-ui/#/ipam/ipam_prefixes_available_ips_create) for [protagio prefix `480`](https://netbox.protagio.org/ipam/prefixes/480/) - [TF provider](https://github.com/e-breuninger/terraform-provider-netbox) (not yet in nixpkgs, [IP](https://registry.terraform.io/providers/e-breuninger/netbox/latest/docs/resources/available_ip_address#prefix_id-1)) - [ ] where to deploy (could be expressed as IPs, but is currently expressed by domain `abundos.eu` with some sub-domains) - see IP
kiara added this to the Fediversity project 2025-04-14 11:30:17 +02:00
kiara commented 2025-04-14 11:40:31 +02:00
Author
Owner
Copy link

given we published test machines' private keys, we will need to redo our infra before we deploy this (for using this story we can). as our existing nixops lacks such integrations, this will need #309.

given we published test machines' private keys, we will need to redo our infra before we deploy this (for using this story we can). as our existing nixops lacks such integrations, this will need #309.
kiara self-assigned this 2025-04-22 21:45:49 +02:00
kiara commented 2025-04-23 20:54:44 +02:00
Author
Owner
Copy link

TF's most mature proxmox provider offers both resources:

going by the similar examples these are looking fairly interchangeable. procolix seems more experienced with VMs, which seems like one potential data point in hosts' preferences.

TF's [most mature proxmox provider](https://registry.terraform.io/providers/bpg/proxmox/latest/docs#example-usage) offers both resources: - [vm](https://registry.terraform.io/providers/bpg/proxmox/latest/docs/resources/virtual_environment_vm) - [container](https://registry.terraform.io/providers/bpg/proxmox/latest/docs/resources/virtual_environment_container) going by the similar examples these are looking fairly interchangeable. procolix seems more experienced with VMs, which seems like one potential data point in hosts' preferences.
👀 1
kiara removed this from the Fediversity project 2025-06-10 19:06:40 +02:00
kiara added this to the Fediversity project 2025-08-02 16:40:55 +02:00
kiara referenced this issue from a commit 2025-10-25 21:53:36 +02:00
proxmox deployment (#510)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/pixelfed
pixelfed-ci
No results found.
Labels
Clear labels   
0 points

fibonacci complexity: 0 points

  
0.5 points

fibonacci complexity: 0.5 points

  
1 point

fibonacci complexity: 1 point

  
13 points

fibonacci complexity: 13 points

  
2 points

fibonacci complexity: 2 points

  
21 points

fibonacci complexity: 21 points

  
3 points

fibonacci complexity: 3 points

  
34 points

fibonacci complexity: 34 points

  
5 points

fibonacci complexity: 5 points

  
55 points

fibonacci complexity: 55 points

  
8 points

fibonacci complexity: 8 points

  
api service

features that may relate more to a (to be created) API service

  
blocked

   
component: fediversity panel

   
component: nixops4

   
documentation

   
estimation high: >3d

   
estimation low: <2h

   
estimation mid: <8h

   
infinite points

fibonacci complexity: infinite points

  
productisation

features out-scoped with the decoupling of the productisation effort

  
project-management

Project management related tasks

  
question

   
role: application developer

   
role: application operator

   
role: hosting provider

   
role: maintainer

   
security

   
technical debt

   
testing

   
type unclear

   
type: bug

Anything that doesn't work as advertised

  
type: deliverable

   
type: key result

   
type: objective

   
type: task

   
type: user story

   
user experience
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Fediversity
Assignees
Clear assignees
No assignees
kiara
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.

Blocks
#69 Separate test environments for staging vs. production
fediversity/fediversity
#99 applications deployed on command
fediversity/fediversity
#200 reproduce DNS VM
fediversity/fediversity
#225 kick-started initial feedback cycle
fediversity/fediversity
#313 ProxmoX back-end supports multiple users
fediversity/fediversity
#483 [D2.2] Software release beta version [2027-03-31]
fediversity/fediversity
#617 operator can restart nodes
fediversity/fediversity
Depends on
#309 port infra to terraform
fediversity/fediversity
#325 Reproducible proxmox installation
fediversity/fediversity
Reference: fediversity/fediversity#116
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?