git ssb

0+

wanderer🌟 / js-primea-hypervisor



Commit 225d322c572c0729ac669c3a11e008456cfb2888

Update index.md

wanderer authored on 5/23/2017, 2:16:53 PM
GitHub committed on 5/23/2017, 2:16:53 PM
Parent: 83e76dba0665fdb89dc5636cfb77ae5150858b20

Files changed

docs/index.mdchanged
docs/index.mdView
@@ -1,25 +1,5 @@
1-# Architecture
2-
3-```
4- +--------------+
5- | |
6- | Environment |
7- | |
8- +--------------+ +--------------------+
9- | | +--+
10- | +----+ Imports | |
11- | | +--------------------+ |
12- +------------+ +------------+ | | +--------------------------+
13- | | | | | +--------------------+ | | |
14- | Kernel +-------+VM Container+---------+ +------+ Sandboxed VM instance |
15- | | | | | | Imports | | | |
16- +------------+ +------------+ | +--------------------+ | +--------------------------+
17- | |
18- | +--------------------+ |
19- | | | |
20- +----+ Imports +--+
21- +--------------------+
22-
23-```
24-# Overview
25-The `Kernel` is modeled to be somewhat like [actors](https://en.wikipedia.org/wiki/Actor_model). Each Kernel/Actor is bound to a segment of code and a state tree on startup. The Kernel provides the top level API. When the kernel recieves a message from another kernel or an external source (signal) it may run that code in a VM container. The container just provides a uniform way to interact with VMs. The container is given an instance of `Evironment`. The `Evironment` contains all the ephemeral state that need for the VM container and instance. Lastly the VM container start and manages the VM instance which is assumed to be sandboxed. The Sandbox communicates to VM container via `Imports` that are exposed to it on the time of creation.
1+# API
2+- [Hypervisor](./hypervisor.md)
3+- [exoKernel](./exoKernel.md)
4+- [portManager](./portManager.md)
5+- [port](./port.md)

Built with git-ssb-web