s
This commit is contained in:
@@ -3,9 +3,9 @@
|
||||
|
||||

|
||||
|
||||
This tool allows you to manage your ZMachine over web remotely.
|
||||
This tool allows you to manage your Zero VM over web remotely.
|
||||
|
||||
ZMachine process manager:
|
||||
Zero VM process manager:
|
||||
|
||||
- Provides a web interface and a REST API to control your processes
|
||||
- Allows you to watch the logs of your processes
|
||||
|
BIN
collections/tech/primitives/compute/img/zos_images.jpg
Normal file
BIN
collections/tech/primitives/compute/img/zos_images.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 133 KiB |
7
collections/tech/primitives/compute/zero_image.md
Normal file
7
collections/tech/primitives/compute/zero_image.md
Normal file
@@ -0,0 +1,7 @@
|
||||
|
||||
## Zero-Images
|
||||
|
||||
> A New Way Of Dealing With OS Images
|
||||
|
||||
!!wiki.include page:zero_image_inno.md
|
||||
|
@@ -4,22 +4,20 @@ 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](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.
|
||||
- The Kubernetes networks are on top of our [Mycelium](mycelium.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 Quantum Safe Storage System 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)
|
||||
* integration with znet (efficient, secure encrypted network between the zero_vms)
|
||||
* can be easily deployed at the edge
|
||||
* single-tenant!
|
||||
|
||||
<!--
|
||||
### ZMachine Benefits
|
||||
### Zero VM 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 -->
|
||||
|
@@ -1,6 +1,6 @@
|
||||
# ZMachine
|
||||
# Zero VM
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
### Features
|
||||
@@ -12,5 +12,5 @@
|
||||
* 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 Mycelium (efficient, secure encrypted network between the zmachines)
|
||||
* integration with Mycelium (efficient, secure encrypted network between the zero_vms)
|
||||
|
||||
|
Reference in New Issue
Block a user