Factorise hardware configurations #21
No reviewers
Labels
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
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "factorise-hardware-config"
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?
This PR merges all hardware-related configurations from VMs in
infra/into ainfra/common/hardware.nixmodule. More factorisation will come in subsequent PRs. It builds on top of #20.It is to be noted that hardware configurations vary between VMs, on mostly between vm02116 on one side and vm02179, vm02186 and vm02187 on the other. Namely:
vm02179, vm02186 and vm02187 all have
imports = [ (modulesPath + "/profiles/qemu-guest.nix") ]while vm02116 doesn't.vm02116 has to following kernel modules available:
ata_piix,uhci_hcd,sr_mod, andxen_blkfront, while vm02179, vm02186 and vm02187 have the following:ata_piix,uhci_hcd,virtio_pci,virtio_scsi,sd_mod, andsr_mod.vm02116 is the only one having:
services.xe-guest-utilities.enable = trueI don't know anything about those things so I don't dare taking decisions and cleaning up. For now, all configurations share
imports = [ (modulesPath + "/profiles/qemu-guest.nix") ]and all the kernel modules.infra/common3edc29b124infra/common25a29c8644infra/commoncecd8544adinfra/commonMakes sense, @koen should check though.
due vm02116 being one of the older fediversity vm's its still running on our old Xen vm environment so its running on completely different hardware
vm02179, vm02186 and vm02187 are allot newer and so they are running on an newer proxmox environment
all 4 vms will have to moved to the fediversity promox in the future
Thank you for your comments. I have kept vm02116's specificities documented in the code.
Merged with
dd56774f34.Pull request closed