...
This commit is contained in:
5
tosort/architecture/_category_.json
Normal file
5
tosort/architecture/_category_.json
Normal file
@@ -0,0 +1,5 @@
|
||||
{
|
||||
"label": "Architecture",
|
||||
"position": 10,
|
||||
"link": {"type": "generated-index"}
|
||||
}
|
||||
14
tosort/architecture/architecture.md
Normal file
14
tosort/architecture/architecture.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
|
||||
# Base Layer for Many Usecases
|
||||
|
||||
|
||||
|
||||
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||
|
||||
Our Zero-OS operating system also supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||
|
||||
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
||||
27
tosort/architecture/cloudengine.md
Normal file
27
tosort/architecture/cloudengine.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
||||
# Architecture Cloud Engine
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The 3 Nodes form the base layer, providing compute, storage, and network capabilities.
|
||||
|
||||
The quantum safe network enables all IT workloads to communicate with one another using the most efficient route and the strongest security measures.
|
||||
|
||||
|
||||
|
||||
The Storage layer make sure we all have perfect control over our storage and can never loose our information.
|
||||
|
||||
|
||||
|
||||
## Autonomous Deployments
|
||||
|
||||
|
||||
|
||||
The hero's can deploy and manage IT workloads on our behalf.
|
||||
|
||||
32
tosort/architecture/hero_virtual_admin.md
Normal file
32
tosort/architecture/hero_virtual_admin.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Hero as Virtual System Administrator
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Every individual has a personal Hero—a virtual assistant that manages your digital life and serves as your system administrator for AI or Edge Cloud workloads.
|
||||
|
||||
These Heroes communicate with each other over the private Mycelium network, which offers a secure message bus for scalable and secure communication.
|
||||
|
||||
A Hero can store an unlimited amount of information, and only your Hero has access to this data, deciding how and when it can be shared with other Heroes or AI systems.
|
||||
|
||||
Active 24/7, your Hero continuously monitors your IT infrastructure. If something goes wrong, the Hero will automatically resolve the issue, ensuring smooth and uninterrupted service.
|
||||
|
||||
|
||||
### Natural Evolution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
We believe this represents the natural evolution away from reliance on centralized services.
|
||||
|
||||
With millions of Heroes working together, can form a collective global intelligence, leveraging various tools to interact with existing services on behalf of their users within all safety of our own sovereignity.
|
||||
|
||||
|
||||
|
||||
64
tosort/architecture/internet_arch.md
Normal file
64
tosort/architecture/internet_arch.md
Normal file
@@ -0,0 +1,64 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Architecture for an Upgraded Internet
|
||||
|
||||
|
||||
|
||||
|
||||
- **3Nodes**: Deliver compute, storage, and GPU capacity.
|
||||
- **Mycelium Routers**: Allow all Mycelium Network participants to communicate with each other and also connect over existing Internet links. Mycelium Routers provide bandwidth to our ecosystem.
|
||||
- **WebGateways**: Provide a bridge between the current Internet and the Mycelium Network.
|
||||
- **Hero 3Bots**: Represent our digital lives and possess the knowledge to act as virtual system administrators, ensuring our IT workloads remain operational.
|
||||
- **Users**: Arrange their digital lives through their Hero 3Bots.
|
||||
- **AI Clouds**: Are created by connecting GPUs from the 3Nodes over the Mycelium Network.
|
||||
|
||||
## 3Nodes
|
||||
|
||||
Each 3node provides compute, storage and network capacity, its the core capacity layer of the cloud.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Each 3Node is running our Zero-OS operating system.
|
||||
|
||||
## Mycelium Routers
|
||||
|
||||
Mycelium is an end-to-end encrypted overlay meshed wireless network with agents available for any desktop and mobile operating system.
|
||||
|
||||
We have also created a dedicated Mycelium Router. Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||
|
||||
These Mycelium Routers are compatible not only with Satelite, Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||
|
||||
The Mycelium Routers can be installed in locations with substantial network capacity, allowing everyone to bridge between the current Internet and the overlay Mycelium network.
|
||||
|
||||
## Web Gateways
|
||||
|
||||
The Web Gateway serves as a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet.
|
||||
|
||||
By not providing an open and direct path into the private network, many malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||
|
||||
The Web Gateways provide HTTP(S) and, in the future, other web services, which get forwarded to the relevant service exposing itself over Mycelium. This setup offers multiple access points to various backend services.
|
||||
|
||||
|
||||
## TFChain: Our Blockchain
|
||||
|
||||
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.
|
||||
|
||||
|
||||
## Ultra Scalable
|
||||
|
||||
|
||||
|
||||
This architecture scales to the planet.
|
||||
34
tosort/features/compute/zkube.md
Normal file
34
tosort/features/compute/zkube.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
sidebar_position: 5
|
||||
title: ZKube
|
||||
---
|
||||
|
||||
|
||||
# ZKube
|
||||
|
||||
TFGrid is compatible with Kubernetes Technology.
|
||||
|
||||
|
||||
|
||||
### Unique for our Kubernetes implementation
|
||||
|
||||
- The Kubernetes networks are on top of our Mycelium 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 zero_vms)
|
||||
* can be easily deployed at the edge
|
||||
* single-tenant!
|
||||
|
||||
<!--
|
||||
### 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 -->
|
||||
|
||||
### Architecture
|
||||
|
||||
|
||||
|
||||
7
tosort/roadmap/_category_.json
Normal file
7
tosort/roadmap/_category_.json
Normal file
@@ -0,0 +1,7 @@
|
||||
{
|
||||
"label": "Roadmap",
|
||||
"position": 6,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
53
tosort/roadmap/enterprise_roadmap.md
Normal file
53
tosort/roadmap/enterprise_roadmap.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: Enterprise Roadmap
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
||||
# Government, Commercial hosters, Telco and Enterprise Roadmap
|
||||
|
||||
We are working on our Government, Commercial hosters, Telco and Enterprise Release of our Technology.
|
||||
|
||||
> 90% of the work has been done as part of our base offering but we need additional features for enterprise
|
||||
|
||||
## Enterprise User Interface
|
||||
|
||||
The current user interface is designed for an open-source tech audience. For enterprise use, we need a different approach to meet the unique needs of enterprise environments:
|
||||
|
||||
- **Private or Hybrid Context**: All operations should be conducted within a private or hybrid cloud context to ensure security and compliance.
|
||||
- **Enhanced Monitoring**: We need more comprehensive monitoring dashboard screens to provide real-time insights and analytics.
|
||||
- **Identity Management Integration**: Integration with enterprise-grade Identity Management solutions, such as LDAP, Active Directory, and SSO (Single Sign-On), is essential.
|
||||
- **Enterprise-Friendly UI**: The user interface needs to be redesigned to be more intuitive and tailored to enterprise users, focusing on usability and efficiency.
|
||||
- **Token Irrelevance**: Tokens are not a priority in this context and should be de-emphasized in the solution.
|
||||
|
||||
## Windows Support
|
||||
|
||||
The virtual Machine technology we use does support windows, but we need to do some further integration.
|
||||
|
||||
## High Performance Network Integration
|
||||
|
||||
- **Local Network Integration**: Zero-OS is designed to support a wide range of technologies, though additional integration work is required to optimize performance.
|
||||
- **High-Speed Backbones**: We aim to support high-speed Ethernet and RDMA (Infiniband) based backbones.
|
||||
- **Instrumentation Enhancements**: Additional instrumentation needs to be incorporated into Zero-OS to achieve optimal performance.
|
||||
- **Target Performance**: Our goal is to achieve network speeds exceeding 100 Gbps.
|
||||
- **Custom Integration**: We offer integration with selected network equipment from our customers, accommodating custom integration requirements.
|
||||
|
||||
## High Performance Storage Block Device Integration
|
||||
|
||||
Next to the existing already integrated storage backends we want to support a high performance redundant storage block device.
|
||||
|
||||
- High performance redundant storage network
|
||||
- Supports our high speed backbone as defined above
|
||||
- Scalable to thousands of machines per cluster.
|
||||
- Replication capability between zones.
|
||||
- **Custom Integration**: We offer integration with selected storage equipment from our customers, accommodating custom integration requirements.
|
||||
|
||||
## Service Level Management
|
||||
|
||||
- The system will have hooks and visualization for achievement of Service levels.
|
||||
- This will allow a commercial service provider to get to higher revenue and better uptime management.
|
||||
|
||||
## Support for Liquid Cooling tanks
|
||||
|
||||
- Do a test setup in liquid cooling rack or node, we can use our selfhealing capabilities to manage better.
|
||||
- Is Integration effort, not really code changes
|
||||
28
tosort/roadmap/hero_roadmap.md
Normal file
28
tosort/roadmap/hero_roadmap.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Hero Roadmap
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
|
||||
## Hero (3Bot) High Level Roadmap
|
||||
|
||||
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign git system, and the automatic integration and deployment of our workloads.
|
||||
|
||||
This stack allows everyone to deploy scalable web 2/3/4 apps on top of the TFGrid.
|
||||
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------ |
|
||||
| Hero Publisher | Publish websites, e-books, ... on top of TFGrid | Q4 24 |
|
||||
| Hero CI = Continuous Integration | Easier to use Continuous Integration / Development, very powerfull, with multi node support | Q4 24 |
|
||||
| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in hero Publisher | Q4 24 |
|
||||
| Hero Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | Q4 24 |
|
||||
| Hero DB | Flexible ultra redundant database stor with indexing, queries, stored procesudes, super scalable replication | Q4 24 |
|
||||
| Hero OSIS | Object Storage and Index system integrates with hero Git, all data on git based backend | Q4 24 |
|
||||
| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names. | Q4 24 |
|
||||
| Hero Monitor | Monitor all your different components on redundant monitoring stack | Q4 24 |
|
||||
| Hero Happs | Hero natively supports Holochain HAPPS | Q1 25 |
|
||||
| Hero Actors | Hero can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps. | Q1 25 |
|
||||
| Hero Web 3 Gateway | Hero aims to have native support for chosen Web3 partner solutions | Q1 25 |
|
||||
|
||||
All of above is fully integrated with Mycelium Network and the TF Grid.
|
||||
43
tosort/roadmap/roadmap.md
Normal file
43
tosort/roadmap/roadmap.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Roadmap in Phases
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
# Roadmap in Phases
|
||||
|
||||
## phase 1: wave 1 of companies, leading to our expertise
|
||||
|
||||
- technology creation, was result of 20 years of evolution
|
||||
- 7 startups acquired as part of this process
|
||||
- technology used globally by big vendors
|
||||
- +600m USD Exits
|
||||
|
||||
## phase 2: proof of tech
|
||||
|
||||
- Technology launched globally (as opensource)
|
||||
- +60,000,000 vcpu active
|
||||
- Large scale proof of core technology
|
||||
- Focus on early adoptors in tech space (cloud, web 2/3 ...)
|
||||
- 50m USD funded by founders, community and farmers (people providing capacity)
|
||||
|
||||
## phase 3: commercialization & global expansion
|
||||
|
||||
### phase 3.1: Commercial Partners
|
||||
|
||||
- ThreeFold Launches with Commercial Strategic Partners
|
||||
- Telco Operatators
|
||||
- IT Integrators
|
||||
- Enterprise Roadmap delivered < 6 months (is mainly integration, documentation and UI work)
|
||||
- Together with partners we deliver on the many projects which are in our funnel today e.g. East Africa, Brazil
|
||||
|
||||
### phase 3.2: Large Scale Financancing for Infrastructure
|
||||
|
||||
**Large scaling financing round**
|
||||
|
||||
- financing for infrastructure projects (trillions available right now for infra in emerging countries)
|
||||
- Public STO (security token offering), let world co-own the infra for their Internet
|
||||
- large partnerships drive alternative to Tier 3/4 Datacenters
|
||||
|
||||
61
tosort/roadmap/tfgrid_roadmap.md
Normal file
61
tosort/roadmap/tfgrid_roadmap.md
Normal file
@@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Open-Source TFGrid Roadmap
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
|
||||
## TFGrid High Level Roadmap
|
||||
|
||||
### Status Today
|
||||
|
||||
The core offering is functioning effectively, maintained through a community-driven, best-effort approach. Currently,
|
||||
there are no Service Level Agreements (SLAs) in place, and there should be increased visibility for users regarding their expectations for uptime,
|
||||
performance, and other service related requirements.
|
||||
|
||||
The uptime and stability of Zero-OS are very good.
|
||||
|
||||
Additionally, hardware compatibility is excellent, with most machines now supported out of the box.
|
||||
|
||||
|
||||
| | Status today | SDK/API | Web UI |
|
||||
| ----------------------- | ------------------------------------------------------------------------------------------------------------ | ------- | ------ |
|
||||
| Zero-OS | Used for management of +30,000 logical CPU cores | yes | yes |
|
||||
| Zero-Images (flists) | Basis for Zero-OS modules as well as replaces images for VM's ... | yes | yes |
|
||||
| Zero-Images from Docker | convert docker through our Hub | yes | yes |
|
||||
| Zero-Images Hub | ThreeFold is hosting some as well as everyone can install their own Hub | yes | yes |
|
||||
| Mycelium Core | Integrated in Zero-OS for VM's as well s ZDB and monitoring | yes | yes |
|
||||
| Mycelium Message Bus | Can be used by any developer for their own usecases | NA | NA |
|
||||
| Quantum Safe Storage | Usable for experts only, is reliably working for +6 years, +100 MB/sec per stream | yes | no |
|
||||
| Quantum Safe Filesystem | QSFS= usable for experts, is a fuse based filesystem on top of the QSS Core | yes | no |
|
||||
| Zero-OS Kubernetes | Working very well, Integrated in ZOS, uses our overlay networks based on Wireguard, can use QSFS underneith. | yes | yes |
|
||||
| Zero-OS VM's | The base of our service portfolio, missing is better service level management | yes | yes |
|
||||
| Zero-OS Monitoring | Working well | yes | yes |
|
||||
| Zero-OS VM Monitoring | Working well, can be retrieved through SDK | yes | yes |
|
||||
| Zero-OS Web Gateway | Working well, but documentation not good enough, and not enough of them deployed | yes | yes |
|
||||
| Zero-Boot | There are multiple ways active on how to deploy Zero-OS all are stateless and capable for full secure boot | | |
|
||||
|
||||
### Planned new features:
|
||||
|
||||
Considerable effort is being made to enable our partners to go into production;
|
||||
however, for this initiative to truly succeed on planetary level, we need many more nodes deployed in the field.
|
||||
|
||||
Below you can find some of the planned features of TFGrid 4.0 mainly to achieve ability to scale to hundred of thousand of nodes.
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
||||
| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q1 25 |
|
||||
| FungiStor | A revolutionary different way how to deliver content | Q1 25 |
|
||||
| Zero-Images on FungiStor | Can be stored on FungiStor | Q1 25 |
|
||||
| Zero-Images from Docker | CI/CD integration (See Hero CI/CD) | Q4 24 |
|
||||
| Zero-Images Hub | CI/CD integration (See Hero CI/CD) no more need for separate Hub | Q4 24 |
|
||||
| Mycelium Core | Just more hardening and testing | Q4 24 |
|
||||
| Mycelium Message Bus | Replace our current RMB, all our own RPC over Mycelium | Q4 24 |
|
||||
| Quantum Safe Storage | Integration in UI, better documentation | Q4 24 |
|
||||
| Quantum Safe Filesystem | Integration in UI, better documentation | Q4 24 |
|
||||
| Zero-OS Kubernetes | No changes planned | |
|
||||
| Zero-OS VM's | Integration Hero CI , use cloud slices to manage | Q1 25 |
|
||||
| Zero-OS Monitoring | More docu and easier API | Q1 25 |
|
||||
| Zero-OS Web Gateway | Need more deployed, better integration with new Mycelium | Q4 24 |
|
||||
| Zero-Boot | No changes planned | |
|
||||
| Mycelium Names | in v4, name services | Q1 25 |
|
||||
| Zero-OS Cloud,Storage,AI Slices | as part of marketplace for v4, flexible billing mutual credit | Q1 25 |
|
||||
Reference in New Issue
Block a user