One of the things I try to do in my technical writing is to harmonize the form and the content. I wrote this up yesterday -- the form of a list of bullet points is consonant with the clear line of reasoning. This allows the content to be precise and to the point
23 likes
this tool has grown to be fairly large with serious design work behind it, and is mostly built by agents these days. it also works very well, due in large part to the amount of forethought that went into it. why would I want to rewrite it?
13 likes
oxidecomputer/skepsis solves a problem that I have with using jj and zed. Zed's diff viewer only understands git so in a jj colocated repo I can only view the diff for the top change in my branch. Skepsis lets me review the full diff of all the changes in my branch easily before I push it.
20 likes
crushing it this weekend
58 likes · 1 repost
Oxide published Virtual Oxide Labs (Voxel) on Oct 14: an open-source software stack that emulates a full Oxide rack so you can run stock Oxide control-plane software without physical hardware.
- Repo: oxidecomputer/voxel (MPL-2.0, Rust). Needs Helios as the host OS.
- Fidelity rule: labs use unmodified stock Oxide software — no special test builds.
- Stack: Propolis VMs for sleds; SoftNPU (software P4) switches; BGP/static networking via Debian + FRR; emulated Service Processor and Root of Trust that flash real Hubris firmware (sp-emu is also open source).
- Author’s home box: Minisforum MS-A2, 32-thread Ryzen 9 9955HX, 96 GB RAM — a 6-sled rack or multirack topology in about 10 minutes.
- Recommended floor: 16+ threads, 64 GB+ RAM, fast NVMe with DRAM.
- Successor to Oxide’s earlier a4x2 virtual labs.
Blog: oxide.computer
6 views
example from today, generating all the comparisons you need to quickly make a design decision that otherwise would be pretty tough
design-system#212
9 likes
@hamzamasoodx A good number of folks run our control plane at home today
github.com/oxidecomputer/omicron/blob/main/docs/h…
38 likes · 1,333 views
Before I joined Oxide I did a little fan-boying (as one does) and put together home lab components as best I could. You _could_ tie 3+ mini-PCs together and wrangle omicron into some semblance of working that way. But it would not be pretty.
However! You absolutely can use non-simulated Omicron: github.com/oxidecomputer/omicron/blob/main/docs/h…
You'll get a single node control plane that's mostly workable, and be able to spin up VMs all day with it. That's what I did. Additionally, if you want to play with microcontrollers you can install Hubris onto STM32H753ZI dev boards! I have one connected to my TrueNAS server over UART and USBTTY for sensors, power management, and console.
@bcantrill Congratulations 🎉 Love seeing you come this far! Have been following your journey, as early as this cute little (and only) PR of mine back in the day lol design-site#10
16 views
Their entire control plan is open source and you can run it on commodity hardware: github.com/oxidecomputer/omicron/blob/main/docs/h…
Mentions
One of the things I try to do in my technical writing is to harmonize the form and the content. I wrote this up yesterday -- the form of a list of bullet points is consonant with the clear line of reasoning. This allows the content to be precise and to the point
this tool has grown to be fairly large with serious design work behind it, and is mostly built by agents these days. it also works very well, due in large part to the amount of forethought that went into it. why would I want to rewrite it?
oxidecomputer/skepsis solves a problem that I have with using jj and zed. Zed's diff viewer only understands git so in a jj colocated repo I can only view the diff for the top change in my branch. Skepsis lets me review the full diff of all the changes in my branch easily before I push it.
crushing it this weekend
Oxide published Virtual Oxide Labs (Voxel) on Oct 14: an open-source software stack that emulates a full Oxide rack so you can run stock Oxide control-plane software without physical hardware. - Repo: oxidecomputer/voxel (MPL-2.0, Rust). Needs Helios as the host OS. - Fidelity rule: labs use unmodified stock Oxide software — no special test builds. - Stack: Propolis VMs for sleds; SoftNPU (software P4) switches; BGP/static networking via Debian + FRR; emulated Service Processor and Root of Trust that flash real Hubris firmware (sp-emu is also open source). - Author’s home box: Minisforum MS-A2, 32-thread Ryzen 9 9955HX, 96 GB RAM — a 6-sled rack or multirack topology in about 10 minutes. - Recommended floor: 16+ threads, 64 GB+ RAM, fast NVMe with DRAM. - Successor to Oxide’s earlier a4x2 virtual labs. Blog: oxide.computer
example from today, generating all the comparisons you need to quickly make a design decision that otherwise would be pretty tough design-system#212
@hamzamasoodx A good number of folks run our control plane at home today github.com/oxidecomputer/omicron/blob/main/docs/h…
Before I joined Oxide I did a little fan-boying (as one does) and put together home lab components as best I could. You _could_ tie 3+ mini-PCs together and wrangle omicron into some semblance of working that way. But it would not be pretty. However! You absolutely can use non-simulated Omicron: github.com/oxidecomputer/omicron/blob/main/docs/h… You'll get a single node control plane that's mostly workable, and be able to spin up VMs all day with it. That's what I did. Additionally, if you want to play with microcontrollers you can install Hubris onto STM32H753ZI dev boards! I have one connected to my TrueNAS server over UART and USBTTY for sensors, power management, and console.
@bcantrill Congratulations 🎉 Love seeing you come this far! Have been following your journey, as early as this cute little (and only) PR of mine back in the day lol design-site#10
Their entire control plan is open source and you can run it on commodity hardware: github.com/oxidecomputer/omicron/blob/main/docs/h…