Idk

automation/ansible.md

@@ -13,6 +13,7 @@ breadcrumbs:
 - Specify sudo password: `--ask-become-pass`
 - Specify username: `--username=<username>`
 - Specify SSH key: `--private-key=<key>` (use `/dev/null` to explicitly avoid SSH keys)
+- Hide unchanged/skipped tasks: `export ANSIBLE_DISPLAY_SKIPPED_HOSTS=false; export ANSIBLE_DISPLAY_OK_HOSTS=false`
 
 ### Ad Hoc
 

linux-server/storage-zfs.md

@@ -88,7 +88,7 @@ The backports repo is used to get the newest version of ZoL.
     - Basic example: `zpool create [-f] [options] <name> {[mirror|raidz|raidz2|spare|...] <drives>}+`
         - Use `-f` (force) if the disks aren't clean.
         - See example above for recommended options.
-    - Recommended example: `zpool create -o ashift=<9|12> -o autotrim=on -O compression=zstd -O xattr=sa -O dnodesize=auto -O atime=off -O relatime=on <disks>` (`autotrim` only for SSDs)
+    - Recommended example: `zpool create -o ashift=<9|12> -o autotrim=on -O compression=zstd -O xattr=sa -O dnodesize=auto -O atime=off -O relatime=on <pool> <disks>` (`autotrim` only for SSDs)
     - Specifying options during creation: For `zpool`/pools, use `-o` for pool options and `-O` for dataset options. For `zfs`/datasets, use `-o` for dataset options.
     - Set physical block/sector size (pool option): `ashift=<9|12>`
         - Use 9 for 512 (2^9) and 12 for 4096 (2^12). Use 12 if unsure (bigger is safer).

make-index.sh

@@ -14,7 +14,7 @@ index_file="${1:-index.md}"
 cat >> "$index_file" <<EOF
 ---
 no_breadcrumbs: true
-no_toc: true
+no_toc: false
 ---
 {% include header.md %}
 

virt-cont/proxmox-ve.md

@@ -49,7 +49,7 @@ Tips:
 
 #### Ansible Method
 
-See [lae.proxmox](https://github.com/lae/ansible-role-proxmox).
+See [HON95/ansible](https://github.com/HON95/ansible) (Debian role) and [lae.proxmox](https://github.com/lae/ansible-role-proxmox).
 
 ### Initial Configuration
 
@@ -66,18 +66,15 @@ PVE-specific instructions:
     1. Run a full upgrade: `apt update && apt full-upgrade`
 1. Install basics:
     1. `apt install sudo vim`
-1. Update network config:
+1. (Optional) Update network config using Open vSwitch (OVS):
     1. (Note) Do NOT manually modify the configs for DNS, NTP, IPTables, etc. The network config (`/etc/network/interfaces`) and PVE configs _may_ however be manually modified, but the GUI or API is still recommended.
-    1. (Note) Consider using Open vSwitch (OVS):
-        - Plain Linux stuff (the way PVE uses it at least) may break for certain setups where e.g. PVE has a VLAN L3 interface on the same bridge as a VM has one.
-        - Install Open VSwitch: `apt install openvswitch-switch`
-        - If using VLANs and an optionally an LACP link:
-            1. (Note) Do this in a way to avoid taking the node offline, e.g. by only adding IPv6 to the new uplink and making sure it works before moving IPv4. Preferably use a separate link for the temporary uplink during install.
-            1. Create the OVS bridge (`vmbr<N>`). If *not* using LAG/LACP then add the physical interface. When adding tagged or untagged VM interfaces later, use this bridge.
-            1. If using LAG/LACP: Create the OVS bond (LACP) (`bond<N>`). Use the created bridge as the "OVS bridge" and the physical interfaces as the "slaves". Use mode "LACP (balance-tcp)" and add the OVS option `other_config:lacp-time=fast`.
-            1. Create the OVS IntPort (VLAN interface) (`vlan<VID>`), which PVE will use to access the network. Use the OVS bridge and specify the VLAN ID. Set the IP addresses for PVE here.
-
-    1. Update network config: Use the web GUI.
+    1. (Note) Plain Linux stuff (the way PVE uses it at least) may break for certain setups where e.g. PVE has a VLAN L3 interface on the same bridge as a VM has one.
+    - Install Open VSwitch: `apt install openvswitch-switch`
+    - If using VLANs and an optionally an LACP link:
+        1. (Note) Do this in a way to avoid taking the node offline, e.g. by only adding IPv6 to the new uplink and making sure it works before moving IPv4. Preferably use a separate link for the temporary uplink during install.
+        1. Create the OVS bridge (`vmbr<N>`). If *not* using LAG/LACP then add the physical interface. When adding tagged or untagged VM interfaces later, use this bridge.
+        1. If using LAG/LACP: Create the OVS bond (LACP) (`bond<N>`). Use the created bridge as the "OVS bridge" and the physical interfaces as the "slaves". Use mode "LACP (balance-tcp)" and add the OVS option `other_config:lacp-time=fast`.
+        1. Create the OVS IntPort (VLAN interface) (`vlan<VID>`), which PVE will use to access the network. Use the OVS bridge and specify the VLAN ID. Set the IP addresses for PVE here.
 1. Update MOTD:
     1. Disable the special PVE banner: `systemctl disable --now pvebanner.service`
     1. Clear or update `/etc/issue` and `/etc/motd`.

virt-cont/virtualbox.md

@@ -0,0 +1,21 @@
+---
+title: VirtualBox
+breadcrumbs:
+- title: Virtualization, Containerization and Orchestration
+---
+{% include header.md %}
+
+libvirt is a tool for managing platform virtualization like KVM and QEMU (among others).
+I'll only focus on using it with KVM (and QEMU) here.
+
+## General
+
+- Requires Intel VT or AMD-V to be enabled to function optimally.
+
+## Usage
+
+### Storage
+
+- Resize VM disk: `VBoxManage modifyhd <disk>.vdi --resize <size-in-MB>`
+
+{% include footer.md %}