Differences

This shows you the differences between two versions of the page.

--- nndocs:sandbox [2024/12/27 16:12] – combine IQN and NQN schemes. naptastic
+++ nndocs:sandbox [2025/08/28 22:52] (current) – add ssh tunnel shortcut naptastic
@@ Line 27: / Line 27: @@
 Since rocky's host number is 68, any other host wishing to share storage with rocky should do so on their own target bus number 68. The network is responsible to connect rocky's bus 01 with southpark's bus 68.
-Storage subnets don't have a defined numbering scheme yet. I want to make them IPv6-only.
-I also want to try this with SRP.
-Ideally, /etc/iscsi/initiatorname.iscsi gets the right value as part of system provisioning, and the target only ever has to use the host's correct name. There's a strong warning about changing IninitatorName in that file; if you're changing it to the correct value (i.e., the value in the target's ACL) then it's fine.
 ====Interfaces====
@@ Line 67: / Line 61: @@
       hardware ethernet 00:10:18:f8:2e:14;
       hardware ethernet 00:10:18:f8:2e:16;
+====IPv6====
+IPv6 local unique addresses have four parts:
+  - 8 bits of fixed prefix (fd)
+  - 40 bits of pseudorandom prefix
+  - 16 bits of subnet
+  - 64 bits of GUID
+My top 48 bits are going to be fd20:4e41:5020. Subnet bits should match their Infiniband subnet. Host bits come from the hardware address.
 ====IP Addresses====
@@ Line 78: / Line 81: @@
 ====Networks====
+^ Network ^ IPv4 Range ^ IPv6 Range ^ IB Subnet ^ VLAN ^ VXLAN IP ^ VXLAN ID ^
+| green | 172.20.0/22 | fd20:4e41:5020:ffff::/64. | ffff | | 225.172.20.64 | 64 |
   * 0-3/22: "green": all emo* and eth* devices should get bridged to this network.
@@ Line 145: / Line 151: @@
 ----
+=====Where Data Lives=====
+===Storage===
+  * Production volumes:
+    * janet: 4TB Samsung QVO.
+    * Crucial 120GB SATA SSD boot volume
+      * southpark's boot volume
+    * Samsung 850 512GB NVMe
+      * installed in southpark on the motherboard, I think?
+    * Western Digital Black 2TB NVMe
+      * installed in southpark on the x16 riser card
+      * confusingly mounted at /mnt/sabrent
+    * black: Three 4TB Western Digital enterprise drives in a RAID-5 holding backups; currently cold.
+  * ZFS pool "truck"
+    * Two Sabrent 1TB NVMe drive
+      * installed in southpark on the x16 riser card
+      * Partitioned partly for I don't remember, but it makes sense
+    * four 4TB drives that should really just get recycled
+  * Not installed:
+    * 512GB Crucial SATA SSD (probably for duckling)
+    * 2TB Vulcan Z SATA SSD (probably for shark as a backup)
+===So Where Does Shit Live?===
+  * VM Images:
+    * southpark:/mnt/sabrent/images
+      * exported over NFS-RDMA
+  * TV shows, movies, software, stuff like that: janet
+  * Home directories:
+  * OS volumes:
+I am still struggling with the fact that things really have to boot off local storage. Fibre Channel without a switch isn't worth it and a switch isn't worth it.
+----
 =====Big Idea Dumping Ground=====
+===SSH tunnel===
+  ssh -D 1337 -q -C -N david@do.naptastic.com
+====SoC on a PCI card====
+Mostly this is to enable other projects. It needs at least these features:
+  * reasonable amount of CPU and DRAM
+  * PCIe 3.0 x1 or better
+  * Internal ports:
+    - m.2 slot
+    - Explicitly copy rpi's 40-pin header
+    - LP-DIMM
+  * External ports:
+    - HDMI
+    - gigabit Ethernet
+    - (2) USB 3.1
+The card presents itself to its host as one or more devices. It can pass through its USB host adapter, network adapter, and m.2 slot, and act as a GPU. It supports SR-IOV. You can boot off it. With the right hardware support, it should be able to stay awake while the host powers off or reboots.
 ====PCIe networking====
 These products:
@@ Line 164: / Line 220: @@
 Everything except retimer cards needs an API and UI for managing things.
 ====Better Audio Stack====
 Want to:
@@ Line 175: / Line 232: @@
 ====Better DAW====
 Core concept is a piece of virtual tape that's infinitely long, infinitely wide, and has an infinite number of tape heads that can all be accessed remotely. A recording session is a server you log into, send recorded audio, receive mixed audio, and update a database of what should play when and with what settings.
+====RDMA to a Commodore 64====
+The 6502 can't drive the C64's memory anywhere near full-speed, but the ROM port has a DMA pin, so a DMA-capable cartridge can do impossibly cool things. I'd like to find a good demo playback engine that already exists, and adapt it to play back data being streamed in over a network.
 ====Better Mixer====
 FIXME