omicron
ferros
omicron | ferros | |
---|---|---|
9 | 9 | |
209 | 102 | |
3.8% | 1.0% | |
9.9 | 0.0 | |
3 days ago | 9 months ago | |
Rust | Rust | |
Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
omicron
-
My favourite Git commit (2019)
> On my work I make 1-15 commits a day. If I have to spend thought cycles on the commit message, that is time that goes from other productive endeavours.
I make roughly that many commits a day as well. If something's easy to understand I'll put in a simple commit message (e.g. [1]), but I do put in the effort for more complicated ones.
[1] https://github.com/nextest-rs/nextest/commit/efd194b2e1d8d61...
[2] https://github.com/oxidecomputer/omicron/commit/b07a8f593325...
-
Oxide Computer releases distribution of illumos intended to power the Oxide Rack
> I also wonder if internally Linux is used for development of the platform itself
Developers at Oxide work on whatever platform they'd like. I will say I am in the minority as a Windows user though, most are on some form of Unix.
> so they can create "virtual" racks to dogfood the product without full blown physical racks.
So one of the reasons why Rust is such an advantage for us is its strong cross-platform support: you can run a simulated version of the control plane on Mac, Linux, and Illumos, without a physical rack. The non-simulated version must run on Helios. [1]
That said we do have a rack in the office (literally named dogfood) that employees can use for various things if they wish.
1: https://github.com/oxidecomputer/omicron?tab=readme-ov-file#...
-
Oxide: The Cloud Computer
> I think the question is how well they can do the management plane.
Docs:
* https://docs.oxide.computer/api/guides/responses
See perhaps "This repo houses the work-in-progress Oxide Rack control plane."
* https://github.com/oxidecomputer/omicron
-
OpenAI Used Kenyan Workers on Less Than $2 per Hour to Make ChatGPT Less Toxic
When we started the company, we knew it would be a three year build -- and indeed, our first product is in the final stages of development (i.e. EMC/safety certification). We have been very transparent about our progress along the way[0][1][2][3][4][5][6][7] -- and our software is essentially all open source, so you can follow along there as well.[8][9][10]
If you are asking "does anyone want a rack-scale computer?" the (short) answer is: yes, they do. The on-prem market has been woefully underserved -- and there are plenty of folks who are sick of Dell/HPE/VMware/Cisco, to say nothing of those who are public cloud borne and wondering if they should perhaps own some of their own compute rather than rent it all.
[0] https://oxide-and-friends.transistor.fm/episodes/holistic-bo...
[1] https://oxide-and-friends.transistor.fm/episodes/the-oxide-s...
[2] https://oxide-and-friends.transistor.fm/episodes/bringup-lab...
[3] https://oxide-and-friends.transistor.fm/episodes/more-tales-...
[4] https://oxide-and-friends.transistor.fm/episodes/another-lpc...
[5] https://oxide-and-friends.transistor.fm/episodes/the-pragmat...
[6] https://oxide-and-friends.transistor.fm/episodes/tales-from-...
[7] https://oxide-and-friends.transistor.fm/episodes/the-sidecar...
[8] https://github.com/oxidecomputer/omicron
[9] https://github.com/oxidecomputer/propolis
[10] https://github.com/oxidecomputer/hubris
- CockroachDB crashed in Go runtime during test run: s.allocCount = s.nelems
- Debugging CockroachDB crash in Go runtime during test run
- Oxide Builds Servers
- Apparent CockroachDB data corruption due to CockroachDB issue 74475
-
Hubris – An OS from Oxide Computer
Speaking of interesting names, their control plane is called Omicron: https://github.com/oxidecomputer/omicron
ferros
-
Unix-like OS in Rust inspired by xv6-riscv
My company, https://www.auxon.io. We created https://github.com/auxoncorp/ferros originally to enable a customer project early in the company's life cycle.
Some time later we had another customer interested in using it and having us add some features to it (e.g. some device drivers and a persistence layer utilizing https://docs.rs/tickv/latest/tickv/). It was becoming a massive pain in the neck to work out source code sharing agreements with them, so we decided to just open source it.
There are quite a number of things that we would do differently if we had to build it again, and at some point will likely do that work to revise it. The biggest one of those is root task synthesis. The other is to build and bring in facilities for running tasks that are compiled to WASM.
-
Writing an OS in Rust to run on RISC-V
When we add WASM support to https://github.com/auxoncorp/ferros it'll sorta be like what you're angling at there in your description.
-
My Fear of Commitment to the First CPU Core
We've built things on seL4 (https://github.com/auxoncorp/ferros). We like to joke that it's the most perfect piece of nearly featureless software ever made.
There's... A LOT... of work to do before seL4 is going to be anywhere near usability parity with something like Linux, unfortunately.
Rather than make a general purpose OS, we decided to use it more like a unikernel or "library OS" where you're trying to make a well defined kind of "appliance" image to deploy to specific hardware rather than try to fake being a POSIX-y shaped OS.
-
FerrOS: Rust-y unikernels on seL4
For what it's worth, here's FerrOS's repo as well as the underlying selfe repo
-
Tokio Console
That's basically what we did with https://github.com/auxoncorp/ferros, Bundle Rust programs together as tasks to run atop the formally verified seL4 microkernel.
-
Hubris – An OS from Oxide Computer
We also built a Rust framework called FerrOS (https://github.com/auxoncorp/ferros) atop the formally-verified seL4 microkernel.
It has a similar set of usage idioms to Hubris it looks like in terms of trying to setup as much as possible ahead of time to assemble what's kind of an application specific operating system where everything your use case needs is assembled at build-time as a bunch of communicating tasks running on seL4.
We recently added a concise little persistence interface that pulls in TicKV (https://docs.tockos.org/tickv/index.html) from the Tock project you referenced above, and some provisions are being added for some more dynamic task handling based on some asks from an automotive OEM.
-
Genode – Sculpt Operating System 21.10
We built a thing to enable combining Rust applications together to be hosted on the seL4 microkernel. The developer experience is more akin to that of something like an RTOS where the OS and your applications are built and deployed together. The whole premise of it is decidedly non-POSIX-like. The current point is for assembling software for use-case-specific/appliance computing, not general purpose computing. (https://github.com/auxoncorp/ferros)
We're looking both for contributors and also actively hiring for a couple engineering positions for the above and for or mainline product.
-
OSv Unikernel – Optimizing Guest OS to Run Stateless and Serverless Apps
I tried and failed to bring unikernels to my former work when I was at Visa. Specifically, LING.
At my current company, Auxon, we recently open sourced[1] some work we did a couple years back which is more or less an attempt at the basic foundations for blending the seL4 microkernel with fairly normal no_std Rust application development and assembling them all together to make a purpose built OS/application to deploy directly to hardware or within a VM. We have some work to do to keep building it up as a foundation for broader use, but we're looking into partnering with the seL4 Foundation (now under the Linux Foundation) to iterate on it further with some of our other mutual partners. The developer experience is much closer to that of developing for an RTOS than it is like typical general purpose computing development.
I'm of course biased, but I think there's a lot of room to innovate in the space of use case specific software stacks where the domain and constraints are well understood and too many degrees of freedom are actually a hindrance and a liability, not an advantage.
[1] https://github.com/auxoncorp/ferros
-
Open sourced: Easier builds and stronger types for seL4 with Rust
On top of that is ferros (no relation to to ferrous-systems), a higher-level userland of unreasonably strong types for compile-time resource tracking. No more discovering you need more memory, or capability slots or IPC rights at runtime. These types help you fit the right seL4 screw to the right seL4 screwdriver.
What are some alternatives?
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
nanos - A kernel designed to run one and only one application in a virtualized environment
terraform-provider-oxide - Oxide Terraform provider
propolis - VMM userspace for illumos bhyve
Trusted-CGI - Lightweight runner for lambda functions/apps in CGI like mode
git-subrepo
rust - Empowering everyone to build reliable and efficient software.
oxide-and-friends - Show notes from Oxide and Friends recordings
tracing - Application level tracing for Rust.
third-party-api-clients - A place for keeping all our generated third party API clients.
console - a debugger for async rust!