Red Hat's emerging technologies group writes about unikernels, trusted computing, RISC-V, Kubernetes, and edge computing.
HN links it for details on UKL, the Linux-based unikernel, and for related work on security and model signing.
Yeah sorry my answer was more than insufficient to be honest. I wrote it _in bed_ and was embarrassed the next day because it was of really low quality. Thought of expanding it later. So yeah I screwed the pooch here and I'm sorry, I will try to do better now by expanding on my answer.
First of all this is all from memory and I didn't try seaweedfs again for this.
So first things first. I evaluated seaweedfs for HPC Cluster usage in 2020 (oh my this is some time ago), but my test setup were VMs. I tried it with many small and larger files and it didn't scale at all (at least when I tested it) for parallel loads. The response time was acceptable, but the throughput was very low. When I tried it "weed server" spun up everything more or less fine, but had problems binding correctly that a distributed setup worked. Based on the wiki documentation I configured a master server, a filer and a few volume server (iirc).
My main gripes at that time were as follows:
* the syntax of the different clients was incosistent
* the throughput was rather low
* the components didn't work well together in a certain configuration and I had to specify many things manually
* the wiki was lacking
I tried filer (fuse), s3 and hadoop. s3 wasn't compatible enough to work with everything I tried with it so I spun up a minIO instance as a gateway to test the whole thing.
When working over a longer period I had some hangs as well.
That's sadly everything I remember on it but I made a…
Here's some words Red Hat folks wrote[0] about Keylime[1][2], "open source scalable trust system harnessing TPM Technology,"[3] written in python and rust, originally created within MIT Lincoln Labs.[4] It leverages TMP 1.2 and 2.0[5] and also involves/includes/references code from Intel[6] and Cloudflare[7].
[0] https://next.redhat.com/2019/06/25/keylime-using-tpm-to-secure-your-slice-of-the-cloud/
[1] https://keylime.dev/
[2] https://www.youtube.com/watch?v=Qhr_aVBCZPw
[3] https://github.com/keylime/keylime
[4] https://www.ll.mit.edu/news/laboratory-staff-develop-new-cybersecurity-solutions-cloud-computing
[5] https://github.com/tpm2-software
[6] https://www.intel.com/content/www/us/en/architecture-and-technology/security-libraries-for-data-center-article.html
[7] https://github.com/cloudflare/cfssl
Semantics but the article is describing model "fingerprints" for basically stylometrics; that's a partial not a signature.
These are "signatures":
https://github.com/sigstore/model-transparency
"Model authenticity and transparency with Sigstore" (2025) https://next.redhat.com/2025/04/10/model-authenticity-and-transparency-with-sigstore/
Actually there is support for using WASM as a container runtime. You could in theory have WASM containers and Linux containers next to each other on the same K8s cluster. Not sure that I’d recommend it in production just yet, but it’s certainly usable
https://next.redhat.com/2023/02/01/running-webassembly-workloads-on-container-runtimes/
Not in RHEL 8 but I'm working with a student on this. There's a rather general non-technical article here:
https://next.redhat.com/2018/11/14/ukl-a-unikernel-based-on-linux/
More info https://next.redhat.com/2018/11/14/ukl-a-unikernel-based-on-linux/
https://github.com/razaaliraza/ukl