fricklerhandwerk/Fediversity
1
0
Fork 0
forked from Fediversity/Fediversity
Code Pull requests Activity

Improve upon the notes

Browse source
This commit is contained in:
Nicolas Jeannerod 2024-10-25 15:52:39 +02:00
parent aadb387716
commit d50813daaa
1 changed files with 43 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

67
proxmox-provisioning.org
View file

@ -2,6 +2,10 @@
#+author: Kevin Muller, Hans van Zijst & Nicolas Jeannerod #+author: Kevin Muller, Hans van Zijst & Nicolas Jeannerod
#+date: <2024-10-25 Fri> #+date: <2024-10-25 Fri>
* Quick links
- Fediversity Proxmox :: http://192.168.51.81:8006/
* Basic terminology
- Node :: physical host
* Preparing the machine configuration * Preparing the machine configuration
- It is nicer if the machine is a QEMU guest. On NixOS: - It is nicer if the machine is a QEMU guest. On NixOS:
#+begin_src nix #+begin_src nix
@ -11,29 +15,33 @@
Fediversity testing are: Fediversity testing are:
- 95.215.187.0/24. Gateway is 95.215.187.1. - 95.215.187.0/24. Gateway is 95.215.187.1.
- 2a00:51c0:13:1305::/64. Gateway is 2a00:51c0:13:1305::1. - 2a00:51c0:13:1305::/64. Gateway is 2a00:51c0:13:1305::1.
Check [Netbox](https://netbox.protagio.org) to see which addresses are free - Check [[https://netbox.protagio.org][Netbox]] to see which addresses are free
* Upload your ISO * Upload your ISO
- Upload your ISO - In the left view, expand under the node that you want and click on “local”.
- In the node you want, `local` storage. ISO images. Upload. You can also download from URL. - Select “ISO Images”, then click “Upload”.
- Note: You can also download from URL.
- Note: You should click on “local” and not “local-zfs”.
* Creating the VM * Creating the VM
- Click “Create VM” at the top right corner. - Click “Create VM” at the top right corner.
- Tick “advanced” at the bottom.
** General ** General
- Node :: which actual machine you want to run; same as the ISO - Node :: which node will host the VM; has to be the same
- VM ID :: Has to be unique, probably best to use the "xxxx" in "vm0xxxx" (yet to be decided) - VM ID :: Has to be unique, probably best to use the "xxxx" in "vm0xxxx" (yet to be decided)
- Name :: Usually "vm" + 5 digits, e.g. "vm02199" - Name :: Usually "vm" + 5 digits, e.g. "vm02199"
- Resource pool :: Fediversity - Resource pool :: Fediversity
** OS ** OS
- Storage :: local, means storage of the node. - Use CD/DVD disc image file (iso) ::
- Choose what you want. - Storage :: local, means storage of the node.
- ISO image :: select the image previously uploaded
No need to touch anything else
** System ** System
- BIOS :: OVMF (UEFI) - BIOS :: OVMF (UEFI)
- EFI Storage :: `linstor_storage`; this is a storage shared by all of the Proxmox machines. - EFI Storage :: ~linstor_storage~; this is a storage shared by all of the Proxmox machines.
- Pre-Enroll keys :: MUST be unchecked - Pre-Enroll keys :: MUST be unchecked
- Qemu Agent :: check - Qemu Agent :: check
** Disks ** Disks
- Disk size (GiB) :: 40 - Tick “advanced” at the bottom.
- SSD emulation :: check - Disk size (GiB) :: 40 (depending on requirements)
- SSD emulation :: check (only visible if “Advanced” is checked)
- Discard :: check, so that blocks of removed data are cleared - Discard :: check, so that blocks of removed data are cleared
** CPU ** CPU
- Sockets :: 1 (depending on requirements) - Sockets :: 1 (depending on requirements)
@ -41,25 +49,36 @@
- Enable NUMA :: check - Enable NUMA :: check
** Memory ** Memory
- Memory (MiB) :: choose what you want - Memory (MiB) :: choose what you want
- Ballooning Device :: leave checked - Ballooning Device :: leave checked (only visible if “Advanced” is checked)
** Network ** Network
- Bridge :: - Bridge :: ~vnet1306~. This is the provisioning bridge; we will change it later.
When creating the VM, select the provisioning bridge (`vnet1306`). Once created, switch
- Firewall :: uncheck, we will handle the firewall on the VM itself - Firewall :: uncheck, we will handle the firewall on the VM itself
** Confirm ** Confirm
* Install and start the VM * Install and start the VM
- You see the VM on the left side. - Start the VM a first time.
- Click, go to console, start it. - Select the VM in the left panel. You might have to expand the node on which it is hosted.
- Install it - Select “Console” and start the VM.
- Once the VM has been installed: - Install the VM as you would any other machine.
- Go to the VM, Hardware, remove the CD/DVD Drive. - [[Shutdown the VM]].
- Switch bridge to public ~vnet1305~ - After the VM has been installed:
- Datacenter > SDN > VNets - Select the VM again, then go to “Hardware”.
- Double click on the CD/DVD Drive line. Select “Do not use any media” and press OK.
- Double click on Network Device, and change the bridge to ~vnet1305~, the public bridge.
- Start the VM again.
* Remove the VM * Remove the VM
- Click on the VM. Make sure it is shut down. - [[Shutdown the VM]].
- Shutdown sends a sigshutdown. If the machine doesn't listen to it, use the tiny arrow, choose Stop, check overrule and click. - On the top right corner, click “More”, then “Remove”.
- More > Remove. Enter the ID. Purge from job. Destroy unreference disks. - Enter the ID of the machine.
* Move to other node - Check “Purge from job configurations”
- Check “Destroy unreferenced disks owned by guest”
- Click “Remove”.
* Move the VM to another node
- Make sure there is no ISO plugged in. - Make sure there is no ISO plugged in.
- Click on the VM. Click migrate. Choose target node. Go. - Click on the VM. Click migrate. Choose target node. Go.
- Since the storage is shared, it should go pretty fast (~1 minute). - Since the storage is shared, it should go pretty fast (~1 minute).
* Shutdown the VM
- Find the VM in the left panel.
- At the top right corner appears a “Shutdown” button with a submenu.
- Clicking “Shutdown” sends a signal to shutdown the machine. This might not work if the machine is not listening for that signal.
- Brutal solution: in the submenu, select “Stop”.
- The checkbox “Overrule active shutdown tasks” means that the machine should be stopped even if a shutdown is currently ongoing. This is particularly important if you have tried to shut the machine down normally just before.