lots of fixes and add ons
This commit is contained in:
@@ -2,11 +2,11 @@
|
||||
|
||||

|
||||
|
||||
True peer2peer is a principle that exists everywhere within Threefold's technology stack, especially on its Network Architecture. Farmers produce IT capacity by connecting hardwares to the network and installing Zero-OS. The peer2peer network of devices forms the TF Grid. This TF Grid is an universal TFChain of which a large variety of IT workloads exist and run.
|
||||
True peer2peer is a principle that exists everywhere in our technology stack, especially on its Network Architecture. Farmers produce IT capacity by connecting hardwares to the network and installing Zero-OS. The peer2peer network of devices forms the TF Grid. This TF Grid is an universal TFChain of which a large variety of IT workloads exist and run.
|
||||
|
||||
## Peer2peer networking
|
||||
|
||||
The TF Grid is built by TFNodes (hardware + Zero-OS) that are connected to the internet by using the IPv6 protocol. To future-proof this grid, IPv6 has been chosen as ThreeFold Grid's native networking technology. The TF Grid operates on IPv6 (where available) and creates peer2peer network connections between all the containers (and other primitives). Please find more about Zero-OS primitives in our [SDK manual](manuals).
|
||||
The TF Grid is built by 3Nodes (hardware + Zero-OS) that are connected to the internet by using the IPv6 protocol. To future-proof this grid, IPv6 has been chosen as native networking technology. The TF Grid operates on IPv6 (where available) and creates peer2peer network connections between all the containers (and other primitives). Please find more about Zero-OS primitives in our [SDK manual](manuals).
|
||||
|
||||
This creates a many-to-many web of (encrypted) point-to-point network connections which together make a (private) secure **overlay network**. This network is completely private and connects only the primitives that have been deployed in your network.
|
||||
|
||||
@@ -21,7 +21,7 @@ TF Network Characteristics:
|
||||
|
||||
## Existing Enterprise Private Networks
|
||||
|
||||
At Threefold, we are aware of the existence of private networks, IPsec, VPN, WAN's and more. We have the facility to create bridges to make these networks part of the deployed private overlay networks. This is in an early stage development, but with the right level(s) of interest this could be built out and carried out in the near future.
|
||||
We are aware of the existence of private networks, IPsec, VPN, WAN's and more. We have the facility to create bridges to make these networks part of the deployed private overlay networks. This is in an early stage development, but with the right level(s) of interest this could be built out and carried out in the near future.
|
||||
|
||||

|
||||
|
||||
|
@@ -2,9 +2,9 @@
|
||||
|
||||

|
||||
|
||||
The Zero-OS is delivered to the TFNodes over the internet network (network boot) and does not need to be installed.
|
||||
The Zero-OS is delivered to the 3Nodes over the internet network (network boot) and does not need to be installed.
|
||||
|
||||
### TFNode Install
|
||||
### 3Node Install
|
||||
|
||||
1. Acquire a computer (server)
|
||||
2. Configure a farm on the TFGrid explorer
|
||||
@@ -16,7 +16,7 @@ The actual bootloader is very small, it brings up the network interface of your
|
||||
|
||||
The operating system is not installed on any local storage medium (hard disk, ssd), Zero-OS is stateless.
|
||||
|
||||
The mechanism to allow this to work in a safe and efficient manner is a ThreeFold innovation called our container virtual filesystem.
|
||||
The mechanism to allow this to work in a safe and efficient manner is an innovation called our container virtual filesystem.
|
||||
|
||||
|
||||
This is explained in more detail [in our SDK manual](https://library.threefold.me/info/manual/#/booting_node).
|
||||
|
@@ -1,10 +1,10 @@
|
||||
|
||||
## TFGrid Flist Hub
|
||||
## Flist Hub
|
||||
|
||||
We provide a public hub you could use to upload your own Flist or filesystem directly and take advantages of Flist out-of-box on Zero-OS.
|
||||
You can convert an existing docker image the same way.
|
||||
|
||||
Public hub: [hub.grid.tf](https://hub.grid.tf)
|
||||
Example TFGrid Public hub: [hub.grid.tf](https://hub.grid.tf)
|
||||
|
||||
|
||||
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 152 KiB |
Binary file not shown.
Before Width: | Height: | Size: 254 KiB |
BIN
collections/tech/zos/img/zos23.png
Normal file
BIN
collections/tech/zos/img/zos23.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 304 KiB |
BIN
collections/tech/zos/img/zos_overview.png
Normal file
BIN
collections/tech/zos/img/zos_overview.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 360 KiB |
@@ -1,8 +1,10 @@
|
||||
# Zero-OS
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||
A revolutionary operating system which can be booted on most modern computers. Once installed Zero-OS locks the hardware and makes it accessible to the decentralized marketplace or a centralized ultra secure deployment system. Blockchain mechanism can be used to strongly control how workloads are deployed on the system.
|
||||
|
||||

|
||||
|
||||
## ZOS Compute & Storage Overview
|
||||
|
||||
@@ -26,9 +28,9 @@
|
||||
- A smart contract for the IT layer allows groups of people to deploy IT workloads with consensus and full control
|
||||
- All workloads which can run on linux can run on Zero-OS but in a much more controlled, private and safe way
|
||||
|
||||
> ThreeFold has 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.
|
||||
> 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.
|
||||
|
||||
## The Requirements For Our TFGrid Based On Zero OS Are:
|
||||
## 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.
|
||||
|
@@ -1,6 +1,6 @@
|
||||
### Zero OS install
|
||||
|
||||
The Zero-OS is delivered to the TFNodes over the internet network (network boot) and does not need to be installed.
|
||||
The Zero-OS is delivered to the 3Nodes over the internet network (network boot) and does not need to be installed.
|
||||
|
||||
# Zero-OS Install Mechanism
|
||||
|
||||
@@ -16,5 +16,5 @@ The actual bootloader is very small. It brings up the network interface of your
|
||||
|
||||
The operating system is not installed on any local storage medium (hard disk, ssd). Zero-OS is stateless.
|
||||
|
||||
The mechanism to allow this to work in a safe and efficient manner is a ThreeFold innovation called our container virtual filesystem. This is explained in more detail [here](flist)
|
||||
The mechanism to allow this to work in a safe and efficient manner is an innovation called our container virtual filesystem. This is explained in more detail [here](flist)
|
||||
|
||||
|
@@ -2,35 +2,33 @@
|
||||
|
||||
### Compute (uses CU)
|
||||
|
||||
- [ZKube](../primitives/compute/zkube.md)
|
||||
- [ZKube](tech:zkube.md)
|
||||
- kubernetes deployment
|
||||
- [ZMachine](../primitives/compute/zmachine.md)
|
||||
- [ZMachine](tech:zmachine.md)
|
||||
- the container or virtual machine running inside ZOS
|
||||
- [CoreX](../primitives/compute/corex.md)
|
||||
- [CoreX](tech:corex.md)
|
||||
- process manager (optional), can be used to get remote access to your zmachine
|
||||
|
||||
A TFNode is a Zero-OS enabled computer which is hosted with any of the ThreeFold Farmers.
|
||||
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:
|
||||
|
||||
- [ZOS FS](../storage/zos_fs.md)
|
||||
- [ZOS FS](tech:zos_fs.md)
|
||||
- is our dedupe unique filesystem, replaces docker images.
|
||||
- [ZOS Mount](../storage/zmount.md)
|
||||
- [ZOS Mount](tech:zmount.md)
|
||||
- is a mounted disk location on SSD, this can be used as faster storage location.
|
||||
- [Quamtum Safe Filesystem](../../qsss/qss_filesystem.md)
|
||||
- [Quamtum Safe Filesystem](tech:qss_filesystem.md)
|
||||
- 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](../storage/zdisk.md)
|
||||
- [ZOS Disk](tech:zdisk.md)
|
||||
- a virtual disk technology, only for TFTech OEM partners.
|
||||
|
||||
### There are 4 ways how networks can be connected to a Z-Machine.
|
||||
|
||||
- [Planetary network](../network/planetary_network.md):
|
||||
- [Mycelium = Planetary network](tech:mycelium.md):
|
||||
- is a planetary scalable network, we have clients for windows, osx, android and iphone.
|
||||
- [ZOS Net](../network/znet.md):
|
||||
- is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
|
||||
- [ZOS NIC](../network/znic.md):
|
||||
- [ZOS NIC](tech:znic.md):
|
||||
- connection to a public ipaddress
|
||||
- [WEB GW](../network/webgw.md):
|
||||
- [WEB GW](tech:webgw.md):
|
||||
- web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user