4 ms·
[Disclaimer: I work for Red Hat in this area, but don't speak for IBM or their CTO] I think reading between the lines this is really about Kata Containers-styl
by rwmj 7y ago
[Disclaimer: I work for Red Hat in this area, but don't speak for IBM or their CTO]
I think reading between the lines this is really about Kata Containers-style fast booting virtual machines which run containers and give you a bit more security. Development of this is very far along, expect to see this being deployed widely soon by enterprises and others who have security sensitive container workloads.
The unikernels stuff seems rather more speculative, and I don't know specifically what IBM is referring to, but I am [at Red Hat] working with a student at BU on turning Linux into a unikernel. You link your application directly to Linux and get a vmlinuz binary which can be run in a variety of places including on cloud VMs, in qemu, in a Kata Container [in theory - not actually tried this one], or even on baremetal. Old article here: https://next.redhat.com/2018/11/14/ukl-a-unikernel-based-on-linux/ https://next.redhat.com/2018/11/14/ukl-a-unikernel-based-on-...
Edit: I should say for completeness there is also KubeVirt, which lets you run your pet VMs in a pod on Kubernetes. Sort of the opposite of Kata.
- angrygoat 7y agoIs what you're doing anything like MirageOS (NetBSD rump kernel linked with an OCaml application [Note, this was an error, see below])? It sounds really interesting – I wonder what advantages Linux vs *BSD have as unikernels, when most hardware details are out of the picture.
- justincormack 7y agoMirageOS does not link to the NetBSD rump kernel. It is a standalone unikernel.
- angrygoat 7y agoThanks for the correction :)
- pnako 7y agoSo if I understand correctly, you end up with some sort of binary, that you can run on top of some system that abstracts away the hardware and manages resources, correct?
- rwmj 7y agoYou end up with a self-contained application binary which runs anywhere that you could run a Linux kernel. However it's different from embedding an initrd into a kernel image in several ways: The kernel is minimal, containing only the bits which are needed by your application or drivers required to run on the hardware. The application runs in kernel space and is linked with the kernel which gives you a nice performance boost because you never context switch (which is the driver behind the whole project actually). You can also call kernel functions which aren't syscalls, eg. for specialized memory management.
- 0x445442 7y ago64-bit DOS?
- ahoka 7y agoWhat's so wrong with the context switch? You need to have some anyway if you want threads in your unikernel.
- eyberg 7y agoThis is a common misunderstanding. There are many different types of context switching and you need the context (heh!) To compare apples to apples. Kernel to userland, thread to thread, process to process, kernel thread vs user thread, etc. It's conflated because different threading models and different kernel/userland separations exist. Generally speaking (in linux) threads perform much much faster than switching processes.
- justincormack 7y agoYou should talk to the Nabla containers and related work team https://nabla-containers.github.io/people/ https://nabla-containers.github.io/people/ in IBM Research, that is where I believe most of the context of this article comes from.
- intheclouddan 7y agoThey also have a slack team for nabla http://slack.nabla-containers.com/ http://slack.nabla-containers.com/
- lima 7y ago> You link your application directly to Linux and get a vmlinuz binary How does this work with proprietary applications and the kernel's GPL license?
- pnako 7y agoIn the cloud no one can hear you violate the GPL.
- rwmj 7y ago"Consult a lawyer" would be the best answer I could give here. The applications we're actually targeting are open source servers of various kinds (think memcached, apache, etc.) so it's not an issue we need to consider ourselves as the licenses will be compatible.
- justincormack 7y agoNo one really knows if the Linux "userspace is not covered by GPL" applies if you link an application to the kernel. Or if you then apply link time optimisation.
- ksec 7y agoI assume all these Unikernels Are targeting the Cloud and Server Usage? Which is perfectly fine for GPL.
- blondin 7y ago> You link your application directly to Linux and get a vmlinuz binary which can be run in a variety of places including on cloud VMs, in qemu, in a Kata Container [in theory - not actually tried this one], or even on baremetal. sounds like the promise java made when they started. but java abstracted away the OS but not the hardware resources. right here the hardware is but not the OS. very curious to see how this turns out.
- windexh8er 7y agoThis feels like IBM/RedHat are playing the "me too" game with Kata or Firecracker. Or maybe, at a higher level, IBM needs something in this space to compete with what AWS has in their Nitro architecture. But, as you say, I'm not sure that "unikernel" means anything specifically at this point other than to, maybe, generate buzz. I don't understand these fluff pieces that sound interesting but are currently vaporware.
- rwmj 7y agoRed Hat works by following open source trends. With Kata we have been following it upstream very closely since the Clear Containers days, as well as having people being involved with the project, and now we're productizing it.
- fock 7y agoso that's basically like putting the whole app in a initrd? One could have done that for some time...
- rwmj 7y agoNo, it's nothing like that. See my other reply: https://news.ycombinator.com/item?id=21920909 https://news.ycombinator.com/item?id=21920909