update book for typos
update branch to fit with main
This commit is contained in:
@@ -1,38 +1,45 @@
|
||||
---
|
||||
title: Geo-Aware Cloud
|
||||
title: Geo Aware Cloud
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
|
||||
## Zero OS as a generator for Compute, Storage, Network capacity
|
||||
## Capacity Generator
|
||||
|
||||
### Compute (uses CU)
|
||||
Zero OS can be conceived as a generator for compute, storage, network capacity.
|
||||
|
||||
### Compute Features
|
||||
|
||||
- ZKube
|
||||
- kubernetes deployment
|
||||
- Kubernetes deployment
|
||||
- Zero VM
|
||||
- the container or virtual machine running inside ZOS
|
||||
- The container or virtual machine running inside ZOS
|
||||
- CoreX
|
||||
- process manager (optional), can be used to get remote access to your zero_vm
|
||||
- Process manager (optional), can be used to get remote access to your zero_vm
|
||||
|
||||
A 3Node is a Zero-OS enabled computer which is hosted with any of the Cloud Providers.
|
||||
|
||||
### There are 4 storage mechanisms which can be used to store your data:
|
||||
### Storage Mechanisms
|
||||
|
||||
- ZOS FS
|
||||
- is our dedupe unique filesystem, replaces docker images.
|
||||
There are 4 storage mechanisms which can be used to store your data
|
||||
|
||||
- ZOS Filesystem
|
||||
- This 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.
|
||||
- This is a mounted disk location on SSD, this can be used as faster storage location.
|
||||
- Quantum Safe Filesystem
|
||||
- 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.
|
||||
- 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.
|
||||
- A virtual disk technology, only for TFTech OEM partners.
|
||||
|
||||
### There are 4 ways how networks can be connected to a Z-Machine.
|
||||
### Network Connections
|
||||
|
||||
There are three ways how networks can be connected to a Z-Machine.
|
||||
|
||||
- Mycelium = Planetary network
|
||||
- is a planetary scalable network, we have clients for windows, osx, android and iphone.
|
||||
- This is a planetary scalable network
|
||||
- We have clients for Windows, OSx, Android and iPhone.
|
||||
- ZOS NIC
|
||||
- connection to a public ipaddress
|
||||
- Connection to a public IP address.
|
||||
- WEB GW
|
||||
- web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
|
||||
- Web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
|
@@ -7,7 +7,7 @@ description: The computer layer compared.
|
||||
|
||||
| | Zos Compute Layer Benefits | Default |
|
||||
|----------------|--------------------------------------------------------------------------------|------------------------------------------------------------------|
|
||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized e.g. Kubernetes, ... |
|
||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized e.g. Kubernetes, etc. |
|
||||
| OS Deploy | Stateless, there are no files copied on local HDD/SSD. | Deploy image or execute installer on a physical server |
|
||||
| OS Upgrade | Seamless, rolling upgrades, 100% modular and pre-deterministic, decentralized | Difficult and error prone + vulnerable from security perspective |
|
||||
| Tamperproof | If file gets modified Zero-OS will not boot the file. | No, man in middle is possible. |
|
||||
@@ -18,5 +18,5 @@ description: The computer layer compared.
|
||||
| Sovereign | Yes | Mostly not. |
|
||||
| Complexity | Anyone can do it, we made it to allow everyone to be a provider. | Real experts needed. |
|
||||
|
||||
> We do not compare our system with those that claim to be full cloud solutions but merely deploy containers using other management systems and optionally connect to a blockchain for billing purposes. Nor do we compare with marketplace systems that simply act as frontends for other systems. We believe these systems, while visually impressive, lack substantial technological foundations and cannot serve as a fundamental base layer for others.
|
||||
> We do not compare our system with those that claim to be full cloud solutions but merely deploy containers using other management systems and optionally connect to a blockchain for billing purposes, nor do we compare our system with marketplace systems that simply act as frontends for other systems. We believe these systems, while visually impressive, lack substantial technological foundations and cannot serve as a fundamental base layer for others.
|
||||
|
||||
|
@@ -5,7 +5,7 @@ description: 'Everyone can build on top of the ThreeFold new internet'
|
||||
# hide_title: true
|
||||
---
|
||||
|
||||
## Zero-OS is easy to dploy
|
||||
## Zero-OS is Easy to Deploy
|
||||
|
||||

|
||||
|
||||
|
@@ -37,4 +37,4 @@ Flists provide the flexibility to manage metadata and data as separate entities,
|
||||
|
||||
### Status
|
||||
|
||||
Usable for years, see Zero-OS.
|
||||
Usable for years, [see Zero-OS](./zos_compute.md) for more information.
|
@@ -10,11 +10,11 @@ The Zero-OS is delivered to the 3Nodes over the internet network (network boot)
|
||||
|
||||
### 3Node Install
|
||||
|
||||
1. Deploy a computer
|
||||
2. Configure a farm on the TFGrid explorer
|
||||
3. Download the bootloader and put on a USB stick or configure a network boot device
|
||||
4. Power on the computer and connect to the internet
|
||||
5. Boot! The computer will automatically download the components of the operating system (Zero-OS)
|
||||
1. Deploy a computer.
|
||||
2. Configure a farm on the TFGrid explorer.
|
||||
3. Download the bootloader and put on a USB stick or configure a network boot device.
|
||||
4. Power on the computer and connect to the internet.
|
||||
5. Boot! The computer will automatically download the components of the operating system (Zero-OS).
|
||||
|
||||
The actual bootloader is very small, it brings up the network interface of your computer and queries TFGrid for the remainder of the boot files needed.
|
||||
|
||||
@@ -24,9 +24,9 @@ The mechanism to allow this to work in a safe and efficient manner is an innovat
|
||||
|
||||
### Process
|
||||
|
||||
- optionally: configure booting from secure BIOS
|
||||
- optionally: install signing certificate in the BIOS, to make sure that only the right bootloader can be started
|
||||
- the bootloader (ISO, PXE, USB, ...) get's downloaded from Internet (TFGrid CDN or private deployment)
|
||||
- core-0 (the first boot process) starts, self verification happens
|
||||
- the metadata for the the required software modules is downloaded and checked against signature and hashes
|
||||
- the core-0 zero_image service
|
||||
- Optionally: Configure booting from secure BIOS.
|
||||
- Optionally: Install signing certificate in the BIOS, to make sure that only the right bootloader can be started.
|
||||
- The bootloader (ISO, PXE, USB, etc.) gets downloaded from the internet (TFGrid CDN or private deployment).
|
||||
- Core-0 (the first boot process) starts and self verification happens.
|
||||
- The metadata for the the required software modules is downloaded and checked against signature and hashes .
|
||||
- The core-0 zero image service starts.
|
||||
|
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: 'ZOS - geo-aware OS'
|
||||
title: 'ZOS - Geo Aware OS'
|
||||
sidebar_position: 1
|
||||
description: The computer layer
|
||||
hide_title: true
|
||||
@@ -8,12 +8,12 @@ hide_title: true
|
||||
|
||||

|
||||
|
||||
# ZOS - geo-aware OS
|
||||
# ZOS - Geo Aware OS
|
||||
|
||||
ThreeFold has developed its own operating system, Zero-OS, which is based on the Linux Kernel. The purpose of Zero-OS is to strip away the unnecessary complexities commonly found in contemporary operating systems.
|
||||
|
||||
|
||||
### Imagine An Operating System With The Following Benefits
|
||||
## Imagine An Operating System With The Following Benefits
|
||||
|
||||
- Up to 10x more efficient for certain workloads (e.g. storage)
|
||||
- No install required
|
||||
@@ -28,7 +28,7 @@ ThreeFold has developed its own operating system, Zero-OS, which is based on the
|
||||
|
||||
> We have created an operating system from scratch. We used the Linux kernel and its components and then built further on it. We have been able to achieve all of the above benefits.
|
||||
|
||||
## Requirements:
|
||||
## Requirements
|
||||
|
||||
- **Autonomy**: TF Grid needs to create compute, storage and networking capacity everywhere. We could not rely on a remote (or a local) maintenance of the operating system by owners or operating system administrators.
|
||||
- **Simplicity**: An operating system should be simple, able to exist anywhere for anyone, and be good for the planet.
|
||||
@@ -36,7 +36,7 @@ ThreeFold has developed its own operating system, Zero-OS, which is based on the
|
||||
|
||||
|
||||
|
||||
## Key Features of Zero-OS:
|
||||
## Key Features of Zero-OS
|
||||
|
||||
Zero-OS is designed with minimalism in mind, supporting only a few fundamental primitives that handle essential low-level functions:
|
||||
|
||||
@@ -52,9 +52,9 @@ Default features:
|
||||
- Integrated unique storage & network primitives
|
||||
- Integrated smart contract for IT layer
|
||||
|
||||
## benefits
|
||||
## Benefits
|
||||
|
||||
- No need to work with images, we work with our unique ZOS FS
|
||||
- No need to work with images, we work with our unique ZOS filesystem
|
||||
- Every container runs in a dedicated virtual machine providing more security
|
||||
- The containers talk to each other over a private network (Mycelium)
|
||||
- The containers can use a web gateway to allow internet users to connect to the applications which are running in their secure containers
|
||||
|
Reference in New Issue
Block a user