...

collections/technology/primitives/compute/beyond_containers.md

@@ -1,17 +0,0 @@
-## 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/technology/primitives/compute/compute.md

@@ -1,8 +0,0 @@
-
-## TFGrid Compute Layer
-
-![](img/tfgrid_compute_.jpg)
-
-We are more than just Container or VM technology, see [our Beyond Container Document](../../primitives/compute/beyond_containers.md).
-
-For more information see [ZeroOS](../../zos/zos_toc.md)

collections/technology/primitives/compute/corex.md

@@ -1,13 +0,0 @@
-
-# CoreX
-
-![](img/corex.jpg)
-
-This tool 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)!
-

collections/technology/primitives/compute/zkube.md

@@ -1,30 +0,0 @@
-# ZKube
-
-TFGrid is compatible with Kubernetes Technology.
-
-![](img/kubernetes_0_.jpg)
-
-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](znet) 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_protect): no hacking surface to the Zero-Nodes, integrate silicon route of trust
-*   [ZNet](znet) and [Planetary Net](planetary_network): a true global single backplane network connecting us all -->
-
-### Architecture
-
-![](img/zkube_architecture_.jpg)
-

collections/technology/primitives/compute/zmachine.md

@@ -1,22 +0,0 @@
-# ZMachine
-
-
-
-### 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
-*   minimal hacking surface to the Zero-Nodes, integrate silicon route of trust
-*   ZOS Filesystem: dedupe, zero-install, hacker-proof
-*   Webgateway: intelligent connection between web (internet) and container services
-*   integration with ZNet (efficient, secure encrypted network between the zmachines)
-*   Planetary Net: a true global single backplane network connecting us all
-
-### Architecture
-
-![](img/zmachine_zos_.jpg)
-
-A ZMachine is running as a virtual machine on top of Zero-OS.
-