lots of fixes and add ons
6
books/duniayetu_dar/sync_production.sh
Executable file
@ -0,0 +1,6 @@
|
|||||||
|
#!/bin/bash
|
||||||
|
set -ex
|
||||||
|
export NAME=duniayetu_dar
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
åç
|
@ -1,26 +1,19 @@
|
|||||||
- [Intro](hero/intro.md)
|
- [Intro](hero/intro.md)
|
||||||
- [ThreeFold Grid](hero/threefold.md)
|
- [ThreeFold Grid](hero/threefold.md)
|
||||||
- [TFGrid Utilization](partners_utilization/partners.md)
|
- [Partners](partners_utilization/partners.md)
|
||||||
- [Digital Freezone](partners_utilization/freezone.md)
|
- [Digital Freezone](partners_utilization/freezone.md)
|
||||||
- [Tanzania Internet](partners_utilization/tanzania.md)
|
- [Tanzania Internet](partners_utilization/tanzania.md)
|
||||||
- [Elestio](partners_utilization/elestio.md)
|
|
||||||
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
||||||
- [Holochain](partners_utilization/holochain.md)
|
- [Holochain](partners_utilization/holochain.md)
|
||||||
- [Sikana](partners_utilization/sikana.md)
|
- [Sikana](partners_utilization/sikana.md)
|
||||||
- [vindo](partners_utilization/vindo.md)
|
- [vindo](partners_utilization/vindo.md)
|
||||||
- [vverse](partners_utilization/vverse.md)
|
- [vverse](partners_utilization/vverse.md)
|
||||||
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
|
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
|
||||||
- [TFGrid Key Innovations](tech/key_innovations_overview.md)
|
- [Architecture Innocation](tech/key_innovations_overview.md)
|
||||||
- [Mycelium Network](tech/mycelium_innovation.md)
|
- [Mycelium Network](tech/mycelium_innovation.md)
|
||||||
- [Zero-OS](tech/zos_innovation.md)
|
|
||||||
- [Quantum Safe Storage](tech/zstor_innovation.md)
|
- [Quantum Safe Storage](tech/zstor_innovation.md)
|
||||||
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
||||||
- [FList: better OS Images](tech/flist_innovation.md)
|
|
||||||
- [FungiStor](tech/fungistor_innovation.md)
|
- [FungiStor](tech/fungistor_innovation.md)
|
||||||
- [Network Wall](tech/network_wall_innovation.md)
|
|
||||||
- [TFGrid Technology](tech/technology.md)
|
|
||||||
- [Architecture](tech/architecture.md)
|
|
||||||
- [Energy Efficient](tech/energy_efficient.md)
|
|
||||||
- [Why](why/why.md)
|
- [Why](why/why.md)
|
||||||
- [Human Right](why/internet_human_right.md)
|
- [Human Right](why/internet_human_right.md)
|
||||||
- [The Internet is Broken](tech/internet_today.md)
|
- [The Internet is Broken](tech/internet_today.md)
|
||||||
|
@ -1,3 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/hero
|
set -ex
|
||||||
rsync -rv ~/hero/www/info/hero/ root@info.ourworld.tf:/root/hero/www/info/hero/
|
export NAME=hero
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
5
books/info_grid/sync_production.sh
Normal file → Executable file
@ -1,2 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
rsync -rv ~/hero/www/info/info_grid/ root@info.ourworld.tf:/root/hero/www/info/info_grid/
|
set -ex
|
||||||
|
export NAME=info_grid
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
@ -1,3 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/kristof -o
|
set -ex
|
||||||
rsync -rv ~/hero/www/info/kristof/ root@info.ourworld.tf:/root/hero/www/friends/kristof/
|
export NAME=kristof
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
5
books/legal/sync_production.sh
Executable file
@ -0,0 +1,5 @@
|
|||||||
|
#!/bin/bash
|
||||||
|
set -ex
|
||||||
|
export NAME=legal
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
5
books/manual/sync_production.sh
Normal file → Executable file
@ -1,2 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
rsync -rv ~/hero/www/info/tfmanual/ root@info.ourworld.tf:/root/hero/www/info/tfmanual/
|
set -ex
|
||||||
|
export NAME=manual
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
5
books/mbweni/sync_production.sh
Executable file
@ -0,0 +1,5 @@
|
|||||||
|
#!/bin/bash
|
||||||
|
set -ex
|
||||||
|
export NAME=mbweni
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
@ -1,6 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
set -ex
|
set -ex
|
||||||
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/projectinca
|
export NAME=projectinca
|
||||||
rsync -rv ~/hero/www/info/solana/ root@info.ourworld.tf:/root/hero/www/friends/projectinca/
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
echo "**OK**"
|
|
||||||
|
@ -1,3 +1,5 @@
|
|||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/projectmycelium
|
set -ex
|
||||||
rsync -rv ~/hero/www/info/projectmycelium/ root@info.ourworld.tf:/root/hero/www/info/projectmycelium/
|
export NAME=projectmycelium
|
||||||
|
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/heroscript/$NAME
|
||||||
|
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||||
|
8
books/syncall.sh
Executable file
@ -0,0 +1,8 @@
|
|||||||
|
set -ex
|
||||||
|
#~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/manual/sync_production.sh
|
||||||
|
~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/kristof/sync_production.sh
|
||||||
|
~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/legal/sync_production.sh
|
||||||
|
~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/tech/sync_production.sh
|
||||||
|
~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/tfgrid3/sync_production.sh
|
||||||
|
#~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/mbweni/sync_production.sh
|
||||||
|
#~/code/git.ourworld.tf/tfgrid/info_tfgrid/books/duniayetu_dar/sync_production.sh
|
@ -14,7 +14,7 @@
|
|||||||
- [Network Wall](tech/network_wall_innovation.md)
|
- [Network Wall](tech/network_wall_innovation.md)
|
||||||
- [Architecture](tech/architecture.md)
|
- [Architecture](tech/architecture.md)
|
||||||
- [Energy Efficient](tech/energy_efficient.md)
|
- [Energy Efficient](tech/energy_efficient.md)
|
||||||
- [ThreeFold Cloud Core Capabilities](tech/features.md)
|
- [Decentralized Cloud Core Capabilities](tech/features.md)
|
||||||
- [Storage](tech/qsss_home.md)
|
- [Storage](tech/qsss_home.md)
|
||||||
- [Quantum Safe Storage Algo](tech/qss_algorithm.md)
|
- [Quantum Safe Storage Algo](tech/qss_algorithm.md)
|
||||||
- [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
|
- [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
|
||||||
|
11
collections/legal/disclaimerinfo/disclaimer_info.md
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
# DISCLAIMER
|
||||||
|
|
||||||
|
_The information provided herein is for informational purposes only. While we strive to present the most up-to-date and accurate information, please be aware that this information is subject to change and is not binding in any way._
|
||||||
|
|
||||||
|
_We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the information provided. Any reliance you place on such information is therefore strictly at your own risk._
|
||||||
|
|
||||||
|
_This information is provided with the understanding that it does not constitute professional advice or services. If expert assistance or counseling is needed, the services of a competent professional should be sought._
|
||||||
|
|
||||||
|
_In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from reliance on information provided. We expressly disclaim any liability or responsibility for any decisions made or actions taken in reliance on the information presented._
|
||||||
|
|
||||||
|
_Please ensure to verify the information provided through your own independent research or consult with a qualified professional as appropriate._
|
1
collections/tech/architecture/.done
Normal file
@ -0,0 +1 @@
|
|||||||
|
image.png
|
@ -1,23 +1,78 @@
|
|||||||
|
|
||||||
## Architecture
|
## Architecture
|
||||||
|
|
||||||
|
|
||||||
![](img/architecture.png)
|
![](img/architecture.png)
|
||||||
|
|
||||||
### TF Nodes (or 3Nodes)
|
### 3nodes
|
||||||
|
|
||||||
The network of nodes which make up the cloud. Each node provides compute, storage and network capacity.
|
The network of nodes which make up the cloud. Each node provides compute, storage and network capacity.
|
||||||
|
|
||||||
### TF Routers
|
![](img/3node.png)
|
||||||
|
|
||||||
With the introduction of new devices in TFGrid 4.0, anyone can now operate as a network service provider.
|
A cloud needs hardware/servers to function. Servers of all shapes and sizes can be added. The production of Cloud Capacity is called Farming and parties who add these servers to the grid are called Farmers.
|
||||||
|
|
||||||
TF Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
Farmers download the Zero-OS operating system and boot their servers. Once booted, these servers become 3Nodes. The 3Nodes will register themselves in a blockchain. Once registered, the capacity of the 3Nodes will become available. This enables a peer2peer environment for people or companies to reserve their Internet Capacity directly from the hardware but yet allowing full control by commercial parties if that would be required.
|
||||||
|
|
||||||
These TF Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
## Ultra Scalable
|
||||||
|
|
||||||
|
![](img/architecture_scalable.png)
|
||||||
|
|
||||||
|
This architecture scales to the planet.
|
||||||
|
|
||||||
|
## Zero-OS
|
||||||
|
|
||||||
|
We have build our own operating system called Zero-OS, which was based starting from a Linux Kernel with as purpose to remove all the unnecessary complexities found on contemporary OS's.
|
||||||
|
|
||||||
|
Zero-OS supports a small number of primitives, and performs low-level functions natively.
|
||||||
|
|
||||||
|
It delivers 3 primitive functions:
|
||||||
|
|
||||||
|
- storage capacity
|
||||||
|
- compute capacity
|
||||||
|
- network capacity
|
||||||
|
|
||||||
|
There is no shell, local nor remote attached to Zero-OS. Given its shell-less nature, the people and organizations, called farmers, that run 3nodes cannot issue any commands nor access its features. In that sense, Zero-OS enables a "zero people" (autonomous) Decentralzied Cloud, meaning hackers cannot get in, while also eliminating human error from the paradigm.
|
||||||
|
|
||||||
|
|
||||||
|
### Mycelium Routers
|
||||||
|
|
||||||
|
Thanks to Mycelium Routers anyone can now operate as a network service provider.
|
||||||
|
|
||||||
|
Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||||
|
|
||||||
|
These Mycelium Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||||
|
|
||||||
|
## 3Bots = autonomous layer
|
||||||
|
|
||||||
|
![](img/autonous3bots.png)
|
||||||
|
|
||||||
|
### Smart Contract for IT
|
||||||
|
|
||||||
|
The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
|
||||||
|
|
||||||
|
Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
|
||||||
|
|
||||||
|
### TFChain
|
||||||
|
|
||||||
|
This blockchain does the following:
|
||||||
|
|
||||||
|
- registry for all 3bots (identity system, aka phonebook)
|
||||||
|
- registry for all farmers & 3nodes
|
||||||
|
- registry for our reputation system
|
||||||
|
- info as required for the Smart Contract for IT
|
||||||
|
|
||||||
|
This is the hart of our operational system of our decentralized cloud.
|
||||||
|
|
||||||
|
### Web Gateways
|
||||||
|
|
||||||
|
The Web Gateway is a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet. By not providing an open and direct path in to the private network, a lot of malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||||
|
|
||||||
### Web3 & Decentralized AI Compatibility
|
### Web3 & Decentralized AI Compatibility
|
||||||
|
|
||||||
The TFGrid is the ideal platform for hosting any web3 and AI workloads. Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||||
|
|
||||||
|
Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||||
|
|
||||||
|
|
||||||
> Any workload (web2/3 and AI) can run on TFGrid.
|
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
BIN
collections/tech/architecture/image.png
Normal file
After Width: | Height: | Size: 257 KiB |
@ -1 +1,4 @@
|
|||||||
architecture.png
|
architecture.png
|
||||||
|
3node.png
|
||||||
|
architecture_scalable.png
|
||||||
|
autonous3bots.png
|
||||||
|
BIN
collections/tech/architecture/img/3node.png
Normal file
After Width: | Height: | Size: 220 KiB |
Before Width: | Height: | Size: 244 KiB After Width: | Height: | Size: 804 KiB |
BIN
collections/tech/architecture/img/architecture_scalable.png
Normal file
After Width: | Height: | Size: 257 KiB |
BIN
collections/tech/architecture/img/autonous3bots.png
Normal file
After Width: | Height: | Size: 229 KiB |
@ -1,10 +1,10 @@
|
|||||||
# Energy Efficient
|
# Energy Efficient
|
||||||
|
|
||||||
Below are some of the ways in which ThreeFold achieves energy efficiency as compared to traditional models.
|
Below are some of the ways in which we achieve energy efficiency as compared to traditional models.
|
||||||
|
|
||||||
![alt text](energy_efficient.png)
|
![alt text](energy_efficient.png)
|
||||||
|
|
||||||
In addition, a decentralized peer-to-peer infrastructure which finds the shortest path between end points is by nature energy-efficient. Data needs to travel a much shorter distance.
|
In addition, a decentralized peer-to-peer infrastructure which finds the shortest path between end points is by nature energy-efficient. Data needs to travel a much shorter distance.
|
||||||
|
|
||||||
> Depending on the use case the ThreeFold approach can lead to 10x energy savings.
|
> Depending on the use case the our approach can lead to 10x energy savings.
|
||||||
|
|
||||||
|
@ -1 +1,5 @@
|
|||||||
# ThreeFold Cloud Features
|
# Decentralized Cloud Technology Features
|
||||||
|
|
||||||
|
![](img/cloud_features.png)
|
||||||
|
|
||||||
|
!!wiki.include page:'tech:zos_toc.md'
|
@ -5,7 +5,7 @@ Oracles are external resources of information.
|
|||||||
|
|
||||||
The TFChain captures and holds that information so we get more certainty about the accuracy.
|
The TFChain captures and holds that information so we get more certainty about the accuracy.
|
||||||
|
|
||||||
We have oracles for price & reputation for e.g. TFFarmers and TFNodes.
|
We have oracles for price & reputation for e.g. TFFarmers and 3Nodes.
|
||||||
|
|
||||||
These oracles are implemented on TF_CHAIN for TFGrid 3.0.
|
These oracles are implemented on TF_CHAIN for TFGrid 3.0.
|
||||||
|
|
||||||
@ -22,9 +22,9 @@ graph TB
|
|||||||
OracleEngine --> Exch3[other... exchanges]
|
OracleEngine --> Exch3[other... exchanges]
|
||||||
end
|
end
|
||||||
subgraph ThreeFold Grid
|
subgraph ThreeFold Grid
|
||||||
Monitor_Engine --> TFNode1
|
Monitor_Engine --> 3Node1
|
||||||
Monitor_Engine --> TFNode2
|
Monitor_Engine --> 3Node2
|
||||||
Monitor_Engine --> TFNode3
|
Monitor_Engine --> 3Node3
|
||||||
end
|
end
|
||||||
subgraph TFChainNode1[TFGrid Blockchain Node]
|
subgraph TFChainNode1[TFGrid Blockchain Node]
|
||||||
Monitor_Engine
|
Monitor_Engine
|
||||||
|
@ -30,15 +30,15 @@ graph TB
|
|||||||
click Explorer2 "/info/threefold/#tfexplorer"
|
click Explorer2 "/info/threefold/#tfexplorer"
|
||||||
|
|
||||||
end
|
end
|
||||||
Monitor_Engine1 --> TFNode1
|
Monitor_Engine1 --> 3Node1
|
||||||
Monitor_Engine1 --> TFNode2
|
Monitor_Engine1 --> 3Node2
|
||||||
Monitor_Engine1 --> TFNode3
|
Monitor_Engine1 --> 3Node3
|
||||||
Monitor_Engine2 --> TFNode1
|
Monitor_Engine2 --> 3Node1
|
||||||
Monitor_Engine2 --> TFNode2
|
Monitor_Engine2 --> 3Node2
|
||||||
Monitor_Engine2 --> TFNode3
|
Monitor_Engine2 --> 3Node3
|
||||||
click TFNode1 "/info/threefold/#3node"
|
click 3Node1 "/info/threefold/#3node"
|
||||||
click TFNode2 "/info/threefold/#3node"
|
click 3Node2 "/info/threefold/#3node"
|
||||||
click TFNode3 "/info/threefold/#3node"
|
click 3Node3 "/info/threefold/#3node"
|
||||||
click Monitor_Engine1 "/info/threefold/#monitorengine"
|
click Monitor_Engine1 "/info/threefold/#monitorengine"
|
||||||
click Monitor_Engine2 "/info/threefold/#monitorengine"
|
click Monitor_Engine2 "/info/threefold/#monitorengine"
|
||||||
|
|
||||||
|
@ -10,4 +10,4 @@ The original Commodore 64, with only 64 KB of memory, was a remarkably capable m
|
|||||||
|
|
||||||
This highlights a regression in our ability to fully utilize computer hardware.
|
This highlights a regression in our ability to fully utilize computer hardware.
|
||||||
|
|
||||||
At Threefold, we are committed to bridging this gap by optimizing our approach to hardware utilization, thereby unlocking its full potential.
|
We are committed to bridging this gap by optimizing our approach to hardware utilization, thereby unlocking its full potential.
|
@ -4,3 +4,4 @@ manual.png
|
|||||||
tech_overview.png
|
tech_overview.png
|
||||||
tech_overview2.png
|
tech_overview2.png
|
||||||
web_remade.png
|
web_remade.png
|
||||||
|
cloud_features.png
|
||||||
|
BIN
collections/tech/img/cloud_features.png
Normal file
After Width: | Height: | Size: 361 KiB |
@ -1,52 +0,0 @@
|
|||||||
## ThreeFold Capacity Layer
|
|
||||||
|
|
||||||
![](img/architecture_why_us.jpg)
|
|
||||||
|
|
||||||
### Zero-OS
|
|
||||||
|
|
||||||
ThreeFold has build its own operating system called Zero-OS, which was based starting from a Linux Kernel with as purpose to remove all the unnecessary complexities found on contemporary OS's.
|
|
||||||
|
|
||||||
Zero-OS supports a small number of primitives, and performs low-level functions natively.
|
|
||||||
|
|
||||||
It delivers 3 primitive functions:
|
|
||||||
|
|
||||||
- storage capacity
|
|
||||||
- compute capacity
|
|
||||||
- network capacity
|
|
||||||
|
|
||||||
There is no shell, local nor remote attached to Zero-OS. It does not allow for inbound network connections to happen to the core. Also, given its shell-less nature, the people and organizations, called farmers, that run 3nodes cannot issue any commands nor access its features. In that sense, Zero-OS enables a "zero people" (autonomous) Internet, meaning hackers cannot get in, while also eliminating human error from the paradigm.
|
|
||||||
|
|
||||||
### TFNode
|
|
||||||
|
|
||||||
The ThreeFold_Grid needs hardware/servers to function. Servers of all shapes and sizes can be added to the grid by anyone, anywhere in the world. The production of Internet Capacity on the Threefold Grid is called Farming and people who add these servers to the grid are called Farmers. This is a fully decentralized process and they get rewarded by the means of TFT.
|
|
||||||
|
|
||||||
Farmers download the Zero-OS operating system and boot their servers themselves. Once booted, these servers become TFNodes. The TFNodes will register themselves in a database called the TF Explorer. Once registered in the TF Explorer, the capacity of the TFNodes will become available on the TF Grid Explorer. Also, given the autonomous nature of the ThreeFold Grid, there is no need for any intermediaries between the user and TFNodes.
|
|
||||||
|
|
||||||
This enables a complete peer2peer environment for people to reserve their Internet Capacity directly from the hardware.
|
|
||||||
|
|
||||||
### Smart Contract for IT
|
|
||||||
|
|
||||||
The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
|
|
||||||
|
|
||||||
Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
|
|
||||||
|
|
||||||
Learn more about smart contract for IT [here](../smartcontract_it/smartcontract_it_full.md).
|
|
||||||
|
|
||||||
### TFChain
|
|
||||||
|
|
||||||
A blockchain running on the TFGrid stores the following information (TFGrid 3.0)
|
|
||||||
|
|
||||||
- registry for all digital twins (identity system, aka phonebook)
|
|
||||||
- registry for all farmers & 3nodes
|
|
||||||
- registry for our reputation system
|
|
||||||
- info as required for the Smart Contract for IT
|
|
||||||
|
|
||||||
This is the hart of our operational system of the TFGrid
|
|
||||||
|
|
||||||
### Peer-to-Peer Network
|
|
||||||
|
|
||||||
The peer2peer network allows any zmachine or user to connect with other zmachine or users on the TF Grid securely, and creates a private shortest path peer2peer network.
|
|
||||||
|
|
||||||
### Web Gateway
|
|
||||||
|
|
||||||
The Web Gateway is a mechanism to connect the private (overlay) networks to the open Internet. By not providing an open and direct path in to the private network, a lot of malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
|
@ -1 +0,0 @@
|
|||||||
# Layers
|
|
BIN
collections/tech/mycelium/image.png
Normal file
After Width: | Height: | Size: 341 KiB |
12
collections/tech/mycelium/rmb.md
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
|
||||||
|
#### Reliable Message Bus
|
||||||
|
|
||||||
|
The user sends the contractID and workload through the RMB to the destination Node.
|
||||||
|
|
||||||
|
RMB is our Reliable Message Bus, workload definitions don't get registerd on the TFChain but directly send peer2peer, this is more secure and private, the smart contract still controls the overall process.
|
||||||
|
|
||||||
|
The Node reads from the [RMB](https://github.com/threefoldtech/rmb) and sees a deploy command, it reads the contractID and workload definition from the payload.
|
||||||
|
It decodes the workload and reads the contract from chain using the contract ID, the Node will check if the user that created the contract and the deployment hash on the contract is the same as what the Node receives over RMB. If all things check out, the Node deploys the workload.
|
||||||
|
|
||||||
|
> In our ZOS 4.0 RMB will be implemented using our Mycelium network and fully integrated.
|
||||||
|
|
27
collections/tech/natural_progression/cloud_requirements.md
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
|
||||||
|
|
||||||
|
## Requirements For A New Genertion of Cloud Technology
|
||||||
|
|
||||||
|
![alt text](requirements.png)
|
||||||
|
|
||||||
|
- Compute, Storage, Network need to be
|
||||||
|
- Local
|
||||||
|
- Sovereign
|
||||||
|
- Private
|
||||||
|
- More Secure
|
||||||
|
- Storage needs to be
|
||||||
|
- More reliable with less overhead (only 20% overhead needed)
|
||||||
|
- Capable to be global and be used as CDN (Content Delivery Network)
|
||||||
|
- Fast enough for the Use Case at hand
|
||||||
|
- Data can never get lost nor corrupted.
|
||||||
|
- Storage can scale to Zetabytes as Easily as Petabytes
|
||||||
|
- Network needs to be
|
||||||
|
- Working no matter what happens with existing network, route around issues.
|
||||||
|
- Local sensitive (chose shortest path)
|
||||||
|
- End2End Encrypted
|
||||||
|
- Capable to really know where information goes to or comes from (authenticity)
|
||||||
|
- The full system needs to be
|
||||||
|
- Autonomous & self Healing
|
||||||
|
- It should be possible to operate without human Intervention
|
||||||
|
- Green
|
||||||
|
- We believe Internet / Cloud can be delivered using at least 10x less energy.
|
44
collections/tech/natural_progression/evolution.md
Normal file
@ -0,0 +1,44 @@
|
|||||||
|
# The Cloud Natural Progression
|
||||||
|
|
||||||
|
|
||||||
|
The Internet was always meant to be a peer-to-peer infrastructure, centralization has lead to many issues to do with security, cost, loss of sovereignity, ...
|
||||||
|
|
||||||
|
> We have a vision of the Internet which is much more close to how the Internet was intended to be yet in full respect to organization who want to make a commercial cloud business.
|
||||||
|
|
||||||
|
![](img/natural_progression_3bot.png)
|
||||||
|
|
||||||
|
|
||||||
|
We believe in a world where every person is the center of his/her digital life. In this new Internet each person has his/her own digital avatar which we call a hero.
|
||||||
|
|
||||||
|
The technical component which makes hero possible is a compoment called 3bot. This 3Bot server is only owned and managed by you lives on top of the Decentralized Cloud.
|
||||||
|
|
||||||
|
All the 3Bots communicate to each other over the shortest possible path, this path is end2end encrypted.
|
||||||
|
|
||||||
|
|
||||||
|
![alt text](arch_minimal.png)
|
||||||
|
|
||||||
|
The underlying network of capacity is the Decentralized Cloud which is the IT Energy which makes all possible.
|
||||||
|
|
||||||
|
The Decentralized Cloud is the result of more than 10 years of development and now active on more than 2000 nodes.
|
||||||
|
|
||||||
|
|
||||||
|
## Requirements For A New Internet
|
||||||
|
|
||||||
|
![alt text](requirements.png)
|
||||||
|
|
||||||
|
- Compute, Storage, Network need to be
|
||||||
|
- Local
|
||||||
|
- Sovereign
|
||||||
|
- Private
|
||||||
|
- More Secure
|
||||||
|
- Storage needs to be
|
||||||
|
- More reliable with less overhead (only 20% overhead needed)
|
||||||
|
- Capable to be global and be used as CDN (Content Delivery Network)
|
||||||
|
- Fast enough for the Use Case at hand
|
||||||
|
- Network needs to be
|
||||||
|
- Working no matter what happens with existing network, route around issues.
|
||||||
|
- Local sensitive (chose shortest path)
|
||||||
|
- End2End Encrypted
|
||||||
|
- Capable to really know where information goes to or comes from (authenticity)
|
||||||
|
|
||||||
|
![](img/evolution.png)
|
20
collections/tech/natural_progression/evolution_3bot.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
# The Cloud Natural Progression
|
||||||
|
|
||||||
|
The Internet was always meant to be a peer-to-peer infrastructure, centralization has lead to many issues to do with security, cost, loss of sovereignity, ...
|
||||||
|
|
||||||
|
> Imagine a cloud which can empower a new Internet which uses less than 1 watt per person and provides ultimate in security, scalablity and sovereignity.
|
||||||
|
|
||||||
|
![](img/natural_progression_3bot.png)
|
||||||
|
|
||||||
|
All the 3Bots communicate to each other over the shortest possible path, this path is end2end encrypted.
|
||||||
|
|
||||||
|
|
||||||
|
![alt text](arch_minimal.png)
|
||||||
|
|
||||||
|
The network of 3nodes provides the IT Energy which makes all possible.
|
||||||
|
|
||||||
|
Our tech is the result of more than 10 years of development and now active on more than 2000 nodes.
|
||||||
|
|
||||||
|
## (R)Evolution
|
||||||
|
|
||||||
|
![](img/evolution.png)
|
@ -11,16 +11,16 @@ The Internet was always meant to be a peer-to-peer infrastructure. As large co
|
|||||||
|
|
||||||
We believe in a world where every person is the center of his/her digital life. In this new Internet each person has his/her own digital avatar which we call a hero.
|
We believe in a world where every person is the center of his/her digital life. In this new Internet each person has his/her own digital avatar which we call a hero.
|
||||||
|
|
||||||
The technical component which makes hero possible is a compoment called 3bot. This 3Bot server is only owned and managed by you lives on top of the ThreeFold Cloud.
|
The technical component which makes hero possible is a compoment called 3bot. This 3Bot server is only owned and managed by you lives on top of the Decentralized Cloud.
|
||||||
|
|
||||||
All the 3Bots communicate to each other over the shortest possible path, this path is end2end encrypted.
|
All the 3Bots communicate to each other over the shortest possible path, this path is end2end encrypted.
|
||||||
|
|
||||||
|
|
||||||
![alt text](arch_minimal.png)
|
![alt text](arch_minimal.png)
|
||||||
|
|
||||||
The underlying network of capacity is the ThreeFold Cloud which is the IT Energy which makes all possible.
|
The underlying network of capacity is the Decentralized Cloud which is the IT Energy which makes all possible.
|
||||||
|
|
||||||
The ThreeFold Cloud is the result of more than 10 years of development and now active on more than 2000 nodes.
|
The Decentralized Cloud is the result of more than 10 years of development and now active on more than 2000 nodes.
|
||||||
|
|
||||||
|
|
||||||
## Requirements For A New Internet
|
## Requirements For A New Internet
|
||||||
|
2
collections/tech/natural_progression/img/.done
Normal file
@ -0,0 +1,2 @@
|
|||||||
|
evolution.png
|
||||||
|
natural_progression_3bot.png
|
BIN
collections/tech/natural_progression/img/evolution.png
Normal file
After Width: | Height: | Size: 375 KiB |
After Width: | Height: | Size: 274 KiB |
@ -1,19 +1,19 @@
|
|||||||
|
|
||||||
# ThreeFold grid inspired by nature
|
# Inspired by nature
|
||||||
|
|
||||||
![](nature.png)
|
![](nature.png)
|
||||||
|
|
||||||
- Just like we have trillions of cells in our body, so can billions of twins live next to each other
|
- Just like we have trillions of cells in our body, so can billions of 3bots live next to each other
|
||||||
- Each twin has memory, knows how to communicate, has knowledge, history, ...
|
- Each 3bot has memory, knows how to communicate, has knowledge, history, ...
|
||||||
- Twins like cells cannot live without a body = TFGrid.
|
- 3Botss like cells cannot live without a body = which is the network of the 3Nodes.
|
||||||
|
|
||||||
## This approach scales for ever
|
## This approach scales for ever
|
||||||
|
|
||||||
![](scaleout.png)
|
![](scaleout.png)
|
||||||
|
|
||||||
- There can be unlimited amounts 3Nodes and 3Bots (Digital Twins)
|
- There can be unlimited amounts 3Nodes and 3Bots
|
||||||
- There are no bottlenecks nor centralization points
|
- There are no bottlenecks nor centralization points
|
||||||
- Our peer2peer network technology takes care of routing and security issues between the Twins and the TFNodes (3Nodes). The shortest paths is always looked for.
|
- Our peer2peer network technology takes care of routing and security issues between the Twins and the 3Nodes. The shortest paths is always looked for.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,9 +1,7 @@
|
|||||||
|
|
||||||
## TFGrid Compute Layer
|
## Compute Layer
|
||||||
|
|
||||||
![](img/tfgrid_compute_.jpg)
|
![](img/zos_compute.png)
|
||||||
|
|
||||||
We are more than just Container or VM technology.
|
|
||||||
|
|
||||||
Default features:
|
Default features:
|
||||||
|
|
||||||
@ -11,6 +9,7 @@ Default features:
|
|||||||
- Compatible with any VM (Virtual Machine)
|
- Compatible with any VM (Virtual Machine)
|
||||||
- Compatible with any Linux workload
|
- Compatible with any Linux workload
|
||||||
- Integrated unique storage & network primitives
|
- Integrated unique storage & network primitives
|
||||||
|
- Integrated smart contract for IT layer
|
||||||
|
|
||||||
We have the following unique advantages:
|
We have the following unique advantages:
|
||||||
|
|
||||||
|
Before Width: | Height: | Size: 209 KiB |
Before Width: | Height: | Size: 272 KiB |
BIN
collections/tech/primitives/compute/img/zos_compute.png
Normal file
After Width: | Height: | Size: 426 KiB |
@ -3,9 +3,8 @@
|
|||||||
|
|
||||||
![](img/planet_net_.jpg)
|
![](img/planet_net_.jpg)
|
||||||
|
|
||||||
> TODO: Need to update this image, also digital twin needs to be named '3bot'
|
|
||||||
|
|
||||||
The planetary network is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created. In this network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
|
The planetary network called Mycelium is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created. In this network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
|
||||||
|
|
||||||
Each user end network point is strongly authenticated and uniquely identified, independent of the network carrier used. There is no need for a centralized firewall or VPN solutions, as there is a circle-based networking security in place.
|
Each user end network point is strongly authenticated and uniquely identified, independent of the network carrier used. There is no need for a centralized firewall or VPN solutions, as there is a circle-based networking security in place.
|
||||||
|
|
||||||
@ -45,4 +44,3 @@ In addition, wireless meshing requires you to know a lot about the network aroun
|
|||||||
|
|
||||||
![](img/planetary_net.jpg)
|
![](img/planetary_net.jpg)
|
||||||
|
|
||||||
The Planetary Network is a continuation and implementation of the [Planetary Network](https://Planetary Network-network.github.io/about.html) network initiative. This technology is in beta but has been proven to work already quite well.
|
|
@ -1,7 +1,7 @@
|
|||||||
|
|
||||||
# ThreeFold Network Technology Overview
|
# Network Technology Overview
|
||||||
|
|
||||||
ThreeFold's decentralized networking platform allows any compute and storage workload to be connected together on a private (overlay) network and exposed to the existing Internet network. The peer-to-peer network platform allows any workload to be connected over secure encrypted networks, which will look for the shortest path between nodes.
|
Our decentralized networking platform allows any compute and storage workload to be connected together on a private (overlay) network and exposed to the existing Internet network. The peer-to-peer network platform allows any workload to be connected over secure encrypted networks, which will look for the shortest path between nodes.
|
||||||
|
|
||||||
### Secure Mesh Overlay Network (Peer-to-Peer)
|
### Secure Mesh Overlay Network (Peer-to-Peer)
|
||||||
|
|
||||||
@ -26,6 +26,6 @@ As integrated with [Web Gateway (WebGW)](webgw):
|
|||||||
|
|
||||||
![](network_wall.png)
|
![](network_wall.png)
|
||||||
|
|
||||||
For OEM projects we can implement the ThreeFold project without using TCP-IP or Ethernet this can lead to super secure environments, ideal to battle the Cuber Pandemic.
|
For OEM projects we can implement a cloud deployment without using TCP-IP or Ethernet this can lead to super secure environments, ideal to battle the Cuber Pandemic.
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,4 +1,4 @@
|
|||||||
# TF Grid Web Gateway
|
# Web Gateway
|
||||||
|
|
||||||
The Web Gateway is a mechanism to connect private networks to the open Internet in such a way that there is no direct connection between the Internet and the secure workloads running in the ZMachines.
|
The Web Gateway is a mechanism to connect private networks to the open Internet in such a way that there is no direct connection between the Internet and the secure workloads running in the ZMachines.
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ Any application which can run on linux can run on the TFGrid.
|
|||||||
- [CoreX](compute/corex.md)
|
- [CoreX](compute/corex.md)
|
||||||
- process manager (optional), can be used to get remote access to your zmachine
|
- process manager (optional), can be used to get remote access to your zmachine
|
||||||
|
|
||||||
A TFNode is a Zero-OS enabled computer which is hosted by any of the ThreeFold Farmers.
|
A 3Node is a Zero-OS enabled computer which is hosted by any cloud operator.
|
||||||
|
|
||||||
### There are 4 storage mechanisms which can be used to store your data:
|
### There are 4 storage mechanisms which can be used to store your data:
|
||||||
|
|
||||||
|
@ -6,5 +6,5 @@ The technology is designed to be redundant without having to do anything.
|
|||||||
|
|
||||||
## Roadmap
|
## Roadmap
|
||||||
|
|
||||||
- The virtual disk technology is available for OEM's only, contact ThreeFold Tech.
|
- The virtual disk technology is available for OEM's only.
|
||||||
|
|
||||||
|
@ -1 +1,2 @@
|
|||||||
qsss_overview.png
|
qsss_overview.png
|
||||||
|
qss_fs_arch.png
|
||||||
|
@ -1,2 +1,5 @@
|
|||||||
qss_scaleout.png
|
qss_scaleout.png
|
||||||
qsss_intro.png
|
qsss_intro.png
|
||||||
|
qsss_intro2.png
|
||||||
|
qsfs_arch.png
|
||||||
|
storage_arch.png
|
||||||
|
Before Width: | Height: | Size: 170 KiB |
BIN
collections/tech/qsss/img/qsfs_arch.png
Normal file
After Width: | Height: | Size: 262 KiB |
Before Width: | Height: | Size: 801 KiB |
BIN
collections/tech/qsss/img/qsss_intro2.png
Normal file
After Width: | Height: | Size: 286 KiB |
BIN
collections/tech/qsss/img/storage_arch.png
Normal file
After Width: | Height: | Size: 233 KiB |
@ -15,7 +15,11 @@ Unique features
|
|||||||
|
|
||||||
Today we produce more data than ever before. We cannot continue to make full copies of data to make sure it is stored reliably. This will simply not scale. We need to move from securing the whole dataset to securing all the objects that make up a dataset.
|
Today we produce more data than ever before. We cannot continue to make full copies of data to make sure it is stored reliably. This will simply not scale. We need to move from securing the whole dataset to securing all the objects that make up a dataset.
|
||||||
|
|
||||||
ThreeFold is using space technology to store data fragments over multiple devices (physical storage devices in TFNodes). The solution does not distribute and store parts of an object (file, photo, movie etc.) but describes the part of an object. This can be visualized by thinking of it as equations.
|
We are using technology which was originally used for communication in space.
|
||||||
|
|
||||||
|
The algo stores data fragments over multiple devices (physical storage devices ).
|
||||||
|
|
||||||
|
The solution is not based on replication or sharding, the algo represents the data as equasions which are distributed over multiple locations.
|
||||||
|
|
||||||
|
|
||||||
## How Data Is Stored Today
|
## How Data Is Stored Today
|
||||||
@ -32,9 +36,9 @@ In well optimized systems overhead will be 400% but in some it can be orders of
|
|||||||
|
|
||||||
![alt text](qsss_overview.png)
|
![alt text](qsss_overview.png)
|
||||||
|
|
||||||
ThreeFold has developed a new storage algorithm which is more efficient, ultra reliable and gives you full control over where your data is stored.
|
We have developed a new storage algorithm which is more efficient, ultra reliable and gives you full control over where your data is stored.
|
||||||
|
|
||||||
ThreeFold's approach is different. Let's try to visualize this new approach with a simple analogy using equations.
|
Our approach is different. Let's try to visualize this new approach with a simple analogy using equations.
|
||||||
|
|
||||||
Let a,b,c,d.... be the parts of the original object. You could create endless unique equations using these parts. A simple example: let's assume we have 3 parts of original objects that have the following values:
|
Let a,b,c,d.... be the parts of the original object. You could create endless unique equations using these parts. A simple example: let's assume we have 3 parts of original objects that have the following values:
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
# Quantum Safe Filesystem
|
# Quantum Safe Filesystem
|
||||||
|
|
||||||
![](img/qsss_intro.png)
|
![](qss_fs_arch.png)
|
||||||
|
|
||||||
A redundant filesystem, can store PB's (millions of gigabytes) of information.
|
A redundant filesystem, can store PB's (millions of gigabytes) of information.
|
||||||
|
|
||||||
@ -8,7 +8,7 @@ Unique features:
|
|||||||
|
|
||||||
- Unlimited scalability (many petabytes)
|
- Unlimited scalability (many petabytes)
|
||||||
- Quantum Safe:
|
- Quantum Safe:
|
||||||
- On the TFGrid no farmer knows what the data is
|
- No farmer knows what the data is
|
||||||
- Even a quantum computer cannot decrypt the data
|
- Even a quantum computer cannot decrypt the data
|
||||||
- Data can't be lost
|
- Data can't be lost
|
||||||
- Protection for datarot, data will autorepair
|
- Protection for datarot, data will autorepair
|
||||||
@ -16,20 +16,19 @@ Unique features:
|
|||||||
- Data is dispersed over multiple sites
|
- Data is dispersed over multiple sites
|
||||||
- Even if the sites go down the data will not be lost
|
- Even if the sites go down the data will not be lost
|
||||||
- Up to 10x more efficient than storing on classic storage cloud systems
|
- Up to 10x more efficient than storing on classic storage cloud systems
|
||||||
- Can be mounted as filesystem on any OS or any deployment system (OSX, Linux, Windows, Docker, Kubernetes, TFGrid etc.)
|
- Can be mounted as filesystem on any OS or any deployment system (OSX, Linux, Windows, Docker, Kubernetes etc.)
|
||||||
- Compatible with ± all data workloads (not high performance data driven workloads like a database)
|
- Compatible with ± all data workloads (not high performance data driven workloads like a database)
|
||||||
- Self-healing: when a node or disk is lost, the storage system can get back to the original redundancy level
|
- Self-healing: when a node or disk is lost, the storage system can get back to the original redundancy level
|
||||||
- Helps with compliance for regulations like GDPR (as the hosting facility has no view on what is stored: information is encrypted and incomplete)
|
- Helps with compliance for regulations like GDPR (as the hosting facility has no view on what is stored: information is encrypted and incomplete)
|
||||||
- Hybrid: can be installed onsite, public and private
|
- Hybrid: can be installed onsite, public and private
|
||||||
- Read-write caching on encoding node (the front end)
|
- Read-write caching on encoding node (the front end)
|
||||||
|
|
||||||
![](img/planet_fs.jpg)
|
|
||||||
|
|
||||||
## Mount Any Files In Your Storage Infrastructure
|
## Mount Any Files In Your Storage Infrastructure
|
||||||
|
|
||||||
The QSFS is a mechanism to mount any file system (in any format) on the grid, in a quantum secure way.
|
The QSFS is a mechanism to mount any file system (in any format) on the grid, in a quantum secure way.
|
||||||
|
|
||||||
This storage layer relies on 3 primitives of the ThreeFold technology :
|
This storage layer relies on 3 primitives:
|
||||||
|
|
||||||
- [0-db](https://github.com/threefoldtech/0-db) is the storage engine.
|
- [0-db](https://github.com/threefoldtech/0-db) is the storage engine.
|
||||||
It is an always append database, which stores objects in an immutable format. It allows history to be kept out-of-the-box, good performance on disk, low overhead, easy data structure and easy backup (linear copy and immutable files).
|
It is an always append database, which stores objects in an immutable format. It allows history to be kept out-of-the-box, good performance on disk, low overhead, easy data structure and easy backup (linear copy and immutable files).
|
||||||
@ -42,7 +41,7 @@ to multiple 0-DBs. The number of generated chunks is configurable to make it mor
|
|||||||
|
|
||||||
Together they form a storage layer that is quantum secure: even the most powerful computer can't hack the system because no single node contains all of the information needed to reconstruct the data.
|
Together they form a storage layer that is quantum secure: even the most powerful computer can't hack the system because no single node contains all of the information needed to reconstruct the data.
|
||||||
|
|
||||||
![](img/quantum_safe_storage.jpg)
|
|
||||||
|
|
||||||
This concept scales forever, and you can bring any file system on top of it:
|
This concept scales forever, and you can bring any file system on top of it:
|
||||||
- S3 storage
|
- S3 storage
|
||||||
@ -50,30 +49,13 @@ This concept scales forever, and you can bring any file system on top of it:
|
|||||||
- an ftp-server
|
- an ftp-server
|
||||||
- IPFS and Hypercore distributed file sharing protocols
|
- IPFS and Hypercore distributed file sharing protocols
|
||||||
|
|
||||||
![](img/quantum_safe_storage_scale.jpg)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Architecture
|
## Architecture
|
||||||
|
|
||||||
By using our filesystem inside a Virtual Machine or Kubernetes, the TFGrid user can deploy any storage application on top e.g. Minio for S3 storage, OwnCloud as online fileserver.
|
By using our filesystem inside a Virtual Machine or Kubernetes, the cloud user can deploy any storage application on top e.g. Minio for S3 storage, OwnCloud as online fileserver.
|
||||||
|
|
||||||
![](img/qsstorage_architecture.jpg)
|
![](img/qsstorage_architecture.jpg)
|
||||||
|
|
||||||
Any storage workload can be deployed on top of the zstor.
|
Any storage workload can be deployed on top of the zstor.
|
||||||
|
|
||||||
```mermaid
|
|
||||||
graph TD
|
|
||||||
subgraph Data Ingress and Egress
|
|
||||||
qss[Quantum Safe Storage Engine]
|
|
||||||
end
|
|
||||||
subgraph Physical Data storage
|
|
||||||
st1[Virtual Storage Device 1]
|
|
||||||
st2[Virtual Storage Device 2]
|
|
||||||
st3[Virtual Storage Device 3]
|
|
||||||
st4[Virtual Storage Device 4]
|
|
||||||
st5[Virtual Storage Device 5]
|
|
||||||
st6[...]
|
|
||||||
qss -.-> st1 & st2 & st3 & st4 & st5 & st6
|
|
||||||
end
|
|
||||||
```
|
|
BIN
collections/tech/qsss/qss_fs_arch.png
Normal file
After Width: | Height: | Size: 244 KiB |
@ -6,6 +6,6 @@ The Quantum Safe Storage System is zero knowledge proof compliant. The storage s
|
|||||||
|
|
||||||
![](img/qss_system.jpg)
|
![](img/qss_system.jpg)
|
||||||
|
|
||||||
The zero proof knowledge compliancy comes from the fact that all of the physical storage nodes (TFnodes) can prove that they store a valid part of the data that the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all of the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the original data and have no access to the original data part or the complete original data objects.
|
The zero proof knowledge compliancy comes from the fact that all of the physical storage nodes (3Nodes) can prove that they store a valid part of the data that the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all of the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the original data and have no access to the original data part or the complete original data objects.
|
||||||
|
|
||||||
|
|
||||||
|
@ -2,13 +2,29 @@
|
|||||||
|
|
||||||
# Quantum Safe Storage System
|
# Quantum Safe Storage System
|
||||||
|
|
||||||
i![](img/qsss_intro.png)
|
![](img/qsss_intro2.png)
|
||||||
|
|
||||||
Our storage architecture follows the true peer2peer design of the TF grid. Any participating node only stores small incomplete parts of objects (files, photos, movies, databases etc.) by offering a slice of the present (local) storage devices. Managing the storage and retrieval of all of these distributed fragments is done by a software that creates development or end-user interfaces for this storage algorithm. We call this '**dispersed storage**'.
|
Our storage architecture follows the true peer2peer design of the Decentralized Cloud System. Any participating node only stores small incomplete parts of objects (files, photos, movies, databases etc.) by offering a slice of the present (local) storage devices. Managing the storage and retrieval of all of these distributed fragments is done by a software that creates development or end-user interfaces for this storage algorithm. We call this '**dispersed storage**'.
|
||||||
|
|
||||||
![](img/qsss_intro_0_.jpg)
|
## Benefits
|
||||||
|
|
||||||
|
- Not even a quantum computer can hack
|
||||||
|
- Zetabytes can be stored as easily as Petabytes
|
||||||
|
- The system is truly autonomous & self healing
|
||||||
|
- Datarot is detected and fixed.
|
||||||
|
- There is 100% contorl over where data is (GDPR)
|
||||||
|
|
||||||
|
## Architecture
|
||||||
|
|
||||||
|
![](img/storage_arch.png)
|
||||||
|
|
||||||
|
The cloud user can mix and match storage technologies as are required for their application.
|
||||||
|
|
||||||
|
## Peer2Peer Advantages
|
||||||
|
|
||||||
Peer2peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. You might also want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture, and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
|
Peer2peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. You might also want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture, and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
|
||||||
|
|
||||||
|
> There is 100% control over where the data is positioned and the security is incredible.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Before Width: | Height: | Size: 396 KiB |
Before Width: | Height: | Size: 279 KiB |
BIN
collections/tech/smartcontract_it/img/smartcontract_iac2.png
Normal file
After Width: | Height: | Size: 341 KiB |
BIN
collections/tech/smartcontract_it/img/smartcontractit_2.png
Normal file
After Width: | Height: | Size: 444 KiB |
BIN
collections/tech/smartcontract_it/img/smrt_contract_it2.png
Normal file
After Width: | Height: | Size: 261 KiB |
@ -6,5 +6,6 @@ IAC = DevOps is a process framework that ensures collaboration between Developme
|
|||||||
|
|
||||||
In simple terms, DevOps can be defined as an alignment between development and IT operations with better communication and collaboration.
|
In simple terms, DevOps can be defined as an alignment between development and IT operations with better communication and collaboration.
|
||||||
|
|
||||||
![](img/smartcontract_iac.png)
|
|
||||||
|
![](img/smartcontract_iac2.png)
|
||||||
|
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
|
|
||||||
### Smart Contract IT Flow
|
### Smart Contract IT Flow (ZOS3)
|
||||||
|
|
||||||
|
|
||||||
The TFChain Blockchain will keep a record of all Entities, Twins, Nodes and Farmers in the TF-Grid network. This makes it easy to integrate the Smart Contract on TFChain as well since we can read from that storage in runtime.
|
The TFChain Blockchain will keep a record of all Entities, Twins, Nodes and Farmers in the TF-Grid network. This makes it easy to integrate the Smart Contract on TFChain as well since we can read from that storage in runtime.
|
||||||
|
@ -32,15 +32,6 @@ If `public_ips` is specified, the contract will reserve the number of public ips
|
|||||||
|
|
||||||
This contract is registered on the blockchain.
|
This contract is registered on the blockchain.
|
||||||
|
|
||||||
#### Reliable Message Bus
|
|
||||||
|
|
||||||
The user sends the contractID and workload through the RMB to the destination Node.
|
|
||||||
|
|
||||||
RMB is our Reliable Message Bus, workload definitions don't get registerd on the TFChain but directly send peer2peer, this is more secure and private, the smart contract still controls the overall process.
|
|
||||||
|
|
||||||
The Node reads from the [RMB](https://github.com/threefoldtech/rmb) and sees a deploy command, it reads the contractID and workload definition from the payload.
|
|
||||||
It decodes the workload and reads the contract from chain using the contract ID, the Node will check if the user that created the contract and the deployment hash on the contract is the same as what the Node receives over RMB. If all things check out, the Node deploys the workload.
|
|
||||||
|
|
||||||
#### consumption reports
|
#### consumption reports
|
||||||
|
|
||||||
The Node periodically sends consumption reports back to the chain for each deployed contract. The chain will compute how much is being used and will charte the user in TFT.
|
The Node periodically sends consumption reports back to the chain for each deployed contract. The chain will compute how much is being used and will charte the user in TFT.
|
||||||
|
@ -1,14 +1,15 @@
|
|||||||
## Smart Contract for IT
|
## Smart Contract for IT
|
||||||
|
|
||||||
Ability for developers to launch IT workloads (applications) on the ThreeFold Grid using our TFGrid primitives secured by blockchain concepts.
|
![](img/smartcontractit_2.png)
|
||||||
|
|
||||||
|
Ability for developers to launch IT workloads (applications) on a Decentralized Cloud e.g the ThreeFold Grid is using these deployment primitives secured by blockchain concepts.
|
||||||
|
|
||||||
![](img/smart_contrac_it1.png)
|
![](img/smrt_contract_it2.png)
|
||||||
|
|
||||||
Following benefits
|
Following benefits
|
||||||
|
|
||||||
- IT workloads can be deployed 100% deterministic, this means all specific properties of the workloads like necessary files, network bridges, processes, ... are all known at build time, this leads to good security and predictability.
|
- IT workloads can be deployed 100% deterministic, this means all specific properties of the workloads like necessary files, network bridges, processes, ... are all known at build time, this leads to good security and predictability.
|
||||||
- Consensus can be required for deploying a workload on the ThreeFold grid.
|
- Consensus can be required for deploying a workload.
|
||||||
- Auditing and full transparancy on what has been deployed by who at what time.
|
- Auditing and full transparancy on what has been deployed by who at what time.
|
||||||
|
|
||||||
|
|
||||||
|
22
collections/tech/technology_generic.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
|
||||||
|
# Decentralized Cloud Technology
|
||||||
|
|
||||||
|
Thanks to our autonomous IT system, providing Cloud capacity is as easy as buying or building a node and connecting it to the internet.
|
||||||
|
|
||||||
|
![](3node_simple.png)
|
||||||
|
|
||||||
|
Example deployment is the TFGrid which is the opensource deployment of our tech, a lot of capacity has been deployed in the world, TFGrid farmers buy a computer and they connect it to the internet, as such they use our operating system to provide Internet capacity to the world.
|
||||||
|
|
||||||
|
There are multiple ways in which people can interact with our platform (as a developer or IT an expert: sysadmin):
|
||||||
|
|
||||||
|
![](img/architecture_usage.png)
|
||||||
|
|
||||||
|
This technology is being used for the ThreeFold grid (see https://www.threefold.io) which is the deployment of a new internet which is green, safe and owned by all of us.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1,14 +1,14 @@
|
|||||||
|
|
||||||
|
|
||||||
# ThreeFold Infrastructure Layer
|
# Infrastructure Layer
|
||||||
|
|
||||||
ThreeFold has developed a highly efficient infrastructure layer with 3 layers:
|
We have developed a highly efficient infrastructure layer with 3 layers:
|
||||||
|
|
||||||
- compute - a flexible way to deploy any workload on edge cloud computers
|
- compute - a flexible way to deploy any workload on edge cloud computers
|
||||||
- storage - a quantum safe storage system
|
- storage - a quantum safe storage system
|
||||||
- network - a planetary scalable overlay network
|
- network - a planetary scalable overlay network
|
||||||
|
|
||||||
ThreeFold nodes provide Internet (storage, compute and network) to the people around.
|
3Nodes provide Internet (storage, compute and network) to the people around.
|
||||||
|
|
||||||
## Developers Platform
|
## Developers Platform
|
||||||
|
|
||||||
|
@ -2,11 +2,11 @@
|
|||||||
|
|
||||||
![](img/network_architecture2.jpg)
|
![](img/network_architecture2.jpg)
|
||||||
|
|
||||||
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
|
## 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.
|
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
|
## 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.
|
||||||
|
|
||||||
![](img/network_architecture.jpg)
|
![](img/network_architecture.jpg)
|
||||||
|
|
||||||
|
@ -2,9 +2,9 @@
|
|||||||
|
|
||||||
![](img/boot.png)
|
![](img/boot.png)
|
||||||
|
|
||||||
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)
|
1. Acquire a computer (server)
|
||||||
2. Configure a farm on the TFGrid explorer
|
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 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).
|
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.
|
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.
|
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)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Before Width: | Height: | Size: 152 KiB |
Before Width: | Height: | Size: 254 KiB |
BIN
collections/tech/zos/img/zos23.png
Normal file
After Width: | Height: | Size: 304 KiB |
BIN
collections/tech/zos/img/zos_overview.png
Normal file
After Width: | Height: | Size: 360 KiB |
@ -1,8 +1,10 @@
|
|||||||
# Zero-OS
|
# Zero-OS
|
||||||
|
|
||||||
![](img/zos22.png)
|
![](img/zos23.png)
|
||||||
|
|
||||||
![](img/zero_os_overview.jpg)
|
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.
|
||||||
|
|
||||||
|
![](img/zos_overview.png)
|
||||||
|
|
||||||
## ZOS Compute & Storage Overview
|
## 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
|
- 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
|
- 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.
|
- **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.
|
- **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
|
### 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
|
# 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 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)
|
### Compute (uses CU)
|
||||||
|
|
||||||
- [ZKube](../primitives/compute/zkube.md)
|
- [ZKube](tech:zkube.md)
|
||||||
- kubernetes deployment
|
- kubernetes deployment
|
||||||
- [ZMachine](../primitives/compute/zmachine.md)
|
- [ZMachine](tech:zmachine.md)
|
||||||
- the container or virtual machine running inside ZOS
|
- 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
|
- 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:
|
### 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.
|
- 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.
|
- 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.
|
- 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.
|
- a virtual disk technology, only for TFTech OEM partners.
|
||||||
|
|
||||||
### There are 4 ways how networks can be connected to a Z-Machine.
|
### 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.
|
- is a planetary scalable network, we have clients for windows, osx, android and iphone.
|
||||||
- [ZOS Net](../network/znet.md):
|
- [ZOS NIC](tech:znic.md):
|
||||||
- is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
|
|
||||||
- [ZOS NIC](../network/znic.md):
|
|
||||||
- connection to a public ipaddress
|
- 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.
|
- web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
|
||||||
|
|
||||||
|
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
```js
|
```js
|
||||||
|
|
||||||
!!book.generate name:'manual' title:'ThreeFold Manual Hero Version'
|
!!book.generate name:'manual' title:'ThreeFold Manual Version'
|
||||||
url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/manual'
|
url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/manual'
|
||||||
|
|
||||||
!!doctree.add
|
!!doctree.add
|
||||||
|