Architecture discussion

[fschmllr]

This issue is supposed to document the choices we have taken with regards to the architecture of our unikernel system.

Possible discussion points include

• choice of dev environment
• choice of unikernel framework, programming language
• unikernel lifecycle (e.g. ephemeral)
• communication protocol between unikernels

[fschmllr]

My dev environment is as follows:

• Ubuntu 20.04 running as virtual machine
• Unikraft running in Docker containers with /dev/kvm passed as device to use as platform

Here is the command I use to run it using Docker:

1. mkdir BDSPRO && cd BDSPRO
2. docker run -it --rm -v $(pwd):/usr/src/unikraft --entrypoint bash --device /dev/kvm --privileged unikraft/kraft:staging

For Docker networking (incomplete):

1. docker network create virbr0
2. Pass --network virbr0 to docker run

Please add your dev environments as well @ls-1801 @tipa12 @JossephMedina.

[ls-1801]

• Weird Arch Linux Distro with the 6.0.8-zen kernel
• KVM + qemu
• x86_64

Using the do-httpreply script, I could build the app with

./do-httpreply setup ./do-httpreply build ./do-httpreply run

[fschmllr]

We should decide if we want to implement a pull or push-based unikernel architecture with regards to the tuple orchestration, Also look into what #12 is doing.