manual added knowledge_base

collections/manual/knowledge_base/technology/primitives/compute/beyond_containers.md

@@ -0,0 +1,17 @@
+## Beyond Containers
+
+![](img/container_native.jpg)
+
+
+Default features:
+
+- compatible with Docker
+- compatible with any Linux workload
+
+We have following unique advantages:
+
+- no need to work with images, we work with our unique zos_fs.
+- every container runs in a dedicated virtual machine providing more security.
+- the containers talk to each other over a private network: zos_net.
+- the containers can use web_gw to allow users on the internet connect to the applications as running in their secure containers. 
+- can use core-x to manage the workload.

collections/manual/knowledge_base/technology/primitives/compute/compute_toc.md

@@ -0,0 +1,7 @@
+# Compute
+
+<h2>Table of Contents</h2>
+
+- [ZKube](./zkube.md)
+- [ZMachine](./zmachine.md)
+- [CoreX](./corex.md)

collections/manual/knowledge_base/technology/primitives/compute/corex.md

@@ -0,0 +1,21 @@
+
+<h1> CoreX </h1>
+
+<h2>Table of Contents </h2>
+
+- [Introduction](#introduction)
+- [ZMachine Process Manager](#zmachine-process-manager)
+
+***
+
+## Introduction
+
+CoreX allows you to manage your ZMachine over web remotely.
+
+## ZMachine Process Manager
+
+- Provide a web interface and a REST API to control your processes.
+- Allow to watch the logs of your processes.
+- Or use it as a web terminal (access over https to your terminal)!
+
+![](img/corex.jpg)

collections/manual/knowledge_base/technology/primitives/compute/tfgrid_compute.md

@@ -0,0 +1,25 @@
+
+## TFGrid Compute Layer
+
+![](img/tfgrid_compute_.jpg)
+
+We are more than just Container or VM technology, see [our Beyond Container Document](beyond_containers).
+
+A 3Node is a Zero-OS enabled computer which is hosted with any of the TF_Farmers.
+
+There are 4 storage mechanisms which can be used to store your data:
+
+- ZOS_FS is our dedupe unique filesystem, replaces docker images. 
+- ZOS_Mount is a mounted disk location on SSD, this can be used as faster storage location. 
+- QSFS, this is a super unique storage system, data can never be lost or corrupted. Please be reminded that this storage layer is only meant to be used for secondary storage applications.
+- ZOS_Disk, a virtual disk technology, only for TFTech OEM partners.
+
+There are 4 ways how networks can be connected to a Z-Machine.
+
+- Planetary_network : is a planetary scalable network, we have clients for windows, osx, android and iphone.
+- zos_net : is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
+- zos_bridge: connection to a public ipaddress
+- web_gw: web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
+
+
+

collections/manual/knowledge_base/technology/primitives/compute/zkube.md

@@ -0,0 +1,40 @@
+<h1> ZKube </h1>
+
+<h2>Table of Contents </h2>
+
+- [Introduction](#introduction)
+- [Unique for our Kubernetes implementation](#unique-for-our-kubernetes-implementation)
+- [Features](#features)
+- [ZMachine Benefits](#zmachine-benefits)
+- [Architecture](#architecture)
+
+***
+
+## Introduction
+
+TFGrid is compatible with Kubernetes Technology.
+
+Each eVDC as shown above is a full blown Kubernetes deployment.
+
+## Unique for our Kubernetes implementation
+
+- The Kubernetes networks are on top of our [ZNet](../network/znet.md) technology which means all traffic between containers and kubernetes hosts is end2end encrypted independent of where your Kubernetes nodes are deployed.
+- You can mount a QSFS underneath a Kubernetes Node (VM), which means that you can deploy containers on top of QSFS to host unlimited amounts of storage in a super safe way.
+- You Kubernetes environment is for sure 100% decentralized, you define where you want to deploy your Kubernetes nodes and only you have access to the deployed workloads on the TFGrid.
+
+## Features
+
+*   integration with znet (efficient, secure encrypted network between the zmachines)
+*   can be easily deployed at the edge
+*   single-tenant!
+
+## ZMachine Benefits
+
+*   [ZOS Protect](../../zos/benefits/zos_advantages.md#zero-os-protect): no hacking surface to the Zero-Nodes, integrate silicon route of trust
+
+
+![](img/kubernetes_0_.jpg)
+
+## Architecture
+
+![](img/zkube_architecture_.jpg)

collections/manual/knowledge_base/technology/primitives/compute/zmachine.md

@@ -0,0 +1,30 @@
+<h1> ZMachine </h1>
+
+<h2>Table of Contents </h2>
+
+- [Introduction](#introduction)
+- [Features](#features)
+- [Architecture](#architecture)
+
+***
+
+## Introduction
+
+ZMachine is a unified container/virtual machine type. This can be used to start a virtual machine on a zos node.
+
+## Features
+
+*   import from docker (market std for containers)
+*   can be easily deployed at the edge (edge cloud)
+*   single-tenant, fully decentralized!
+*   can deploy unlimited amounts of storage using our qsfs.
+*   [ZOS Protect](../../zos/benefits/zos_advantages.md#zero-os-protect): no hacking surface to the Zero-Nodes, integrate silicon route of trust
+*   [ZOS Filesystem](../storage/qsfs.md): dedupe, zero-install, hacker-proof
+*   [WebGateway](../network/webgw3.md:) intelligent connection between web (internet) and container services
+*   integration with [ZNet](../network/znet.md) (efficient, secure encrypted network between the zmachines)
+
+## Architecture
+
+![](img/zmachine_zos_.jpg)
+
+A ZMachine is running as a virtual machine on top of Zero-OS.