style: Improve markdown editor styling and functionality
- Update dark mode button icon and styling - Add styling for new collection button - Apply default iframe styles in preview pane - Adjust vertical divider height in header buttons - Improve handling of JSX-like attributes in markdown - Add support for new collection functionality - Refine file loading logic in view mode - Improve dark mode toggle icon and integration - Update UI for edit/view mode toggle button
This commit is contained in:
50
collections/tech/roadmap/enterprise_roadmap.md
Normal file
50
collections/tech/roadmap/enterprise_roadmap.md
Normal file
@@ -0,0 +1,50 @@
|
||||
|
||||
# Government, Commercial Hosters, Telco and Enterprise Roadmap
|
||||
|
||||
We are working on the government, commercial hosters, telco and enterprise releases of our technology.
|
||||
|
||||
> 90% of the work has been done as part of our base offering but we need additional features for enterprises.
|
||||
|
||||
## 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**: ZOS 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 ZOS 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 high-speed backbones 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 self-healing capabilities to manage in a better way.
|
||||
- This is an integration effort, and not much code changes are needed.
|
||||
24
collections/tech/roadmap/hero_roadmap.md
Normal file
24
collections/tech/roadmap/hero_roadmap.md
Normal file
@@ -0,0 +1,24 @@
|
||||
|
||||
## AI Agent High Level Roadmap
|
||||
|
||||
MyAgent is our private AI agent.
|
||||
|
||||
The first version of our MyAgent enables the management of core services such as an innovative database backend, a autonomous decentralized git system, and the automatic integration and deployment of our workloads.
|
||||
|
||||
This stack allows everyone to deploy scalable Web 2,3 and 4 apps on top of the TFGrid in a fully automated way.
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------ |
|
||||
| MyAgent Publisher | Publish websites, e-books, and more on top of the ThreeFold Grid | H2 25 |
|
||||
| MyAgent CI = Continuous Integration | Easier to use Continuous Integration/Development, very powerfull, with multinode support | H2 25 |
|
||||
| MyAgent Play | Integrate declarative automation and configuration management as part of wiki approach in MyAgent Publisher | H2 25 |
|
||||
| MyAgent Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | H2 25 |
|
||||
| MyAgent DB | Flexible ultra redundant database stor with indexing, queries, stored procedures, super scalable replication | H2 25 |
|
||||
| MyAgent OSIS | Object Storage and Index system | H2 25 |
|
||||
| MyAgent WEB | Web framework, deployable globally on TFGrid, integrated with Mycelium Net and Names | H2 25 |
|
||||
| MyAgent Monitor | Monitor all your different components on redundant monitoring stack | H2 25 |
|
||||
| MyAgent Happs | MyAgent natively supports Holochain HAPPS | Q4 25 |
|
||||
| MyAgent Actors | MyAgent can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps | Q4 25 |
|
||||
| MyAgent Web 3 Gateway | MyAgent aims to have native support for chosen Web3 partner solutions (Bitcoin, Ethereum, and more) | Q4 25 |
|
||||
|
||||
All of the specs above are fully integrated with the Mycelium Network and the ThreeFold Grid.
|
||||
40
collections/tech/roadmap/high_level.md
Normal file
40
collections/tech/roadmap/high_level.md
Normal file
@@ -0,0 +1,40 @@
|
||||
|
||||

|
||||
|
||||
# Roadmap in Phases
|
||||
|
||||
## Phase 1: Wave 1 of Companies, Leading to Our expertise (DONE)
|
||||
|
||||
- Technology creation
|
||||
- This was result of 20 years of evolution
|
||||
- 7 startups acquired as part of this process
|
||||
- Technology used globally by big vendors
|
||||
- +600m USD in exits
|
||||
|
||||
## Phase 2: Proof of Tech (DONE)
|
||||
|
||||
- Open source technology launched globally
|
||||
- +60,000,000 active vCPU
|
||||
- Large scale proof of core technology
|
||||
- Focus on early adoptors in tech space (Cloud, Web2, Web3, etc.)
|
||||
- 50m USD funded by founders, community and hosters (people providing capacity)
|
||||
|
||||
## Phase 3: Commercialization & Global Expansion (START)
|
||||
|
||||
### Phase 3.1: Commercial Partners
|
||||
|
||||
- Mycelium Launches with commercial strategic partners
|
||||
- Telco Operatators
|
||||
- IT Integrators
|
||||
- Enterprise roadmap delivered within 6 months
|
||||
- This is mainly about 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 infrastructures in emerging countries)
|
||||
- Public STO (security token offering)
|
||||
- This lets people around the world to co-own the infrastructure for their internet
|
||||
- Large partnerships drive alternative to Tier 3 and 4 datacenters
|
||||
BIN
collections/tech/roadmap/img/roadmap.jpg
Normal file
BIN
collections/tech/roadmap/img/roadmap.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
50
collections/tech/roadmap/tfgrid_roadmap.md
Normal file
50
collections/tech/roadmap/tfgrid_roadmap.md
Normal file
@@ -0,0 +1,50 @@
|
||||
|
||||
## 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 ZOS are very good.
|
||||
|
||||
Additionally, hardware compatibility is excellent, with most machines now supported out of the box.
|
||||
|
||||
| | Status today | SDK/API | Web UI |
|
||||
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------- | ------ |
|
||||
| ZOS | Used for management of +30,000 logical CPU cores | yes | yes |
|
||||
| MyImage (flists) | Basis for ZOS modules as well as replaces images for VM's ... | yes | yes |
|
||||
| MyImage from Docker | convert docker through our Hub | yes | yes |
|
||||
| MyImage Hub | Mycelium is hosting some as well as everyone can install their own Hub | yes | yes |
|
||||
| Mycelium Core | Integrated in ZOS 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 |
|
||||
| Unbreakable Filesystem | Quantum Safe FS= usable for experts, is a fuse based filesystem on top of the QSS Core | yes | no |
|
||||
| ZOS Kubernetes | Working very well, Integrated in ZOS, uses our overlay networks based on Wireguard, can use Quantum Safe FS underneith. | yes | yes |
|
||||
| ZOS VM's | The base of our service portfolio, missing is better service level management | yes | yes |
|
||||
| ZOS Monitoring | Working well | yes | yes |
|
||||
| ZOS VM Monitoring | Working well, can be retrieved through SDK | yes | yes |
|
||||
| ZOS 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 ZOS all are stateless and capable for full secure boot | yes | yes |
|
||||
|
||||
### 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 Mycelium Network 4.0 mainly to achieve ability to scale to hundred of thousand of nodes.
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ------------------------------- | ------------------------------------------------------------------- | ------- |
|
||||
| ZOS v4 (our next major release) | V4, without Mycelium Chain, mutual credit, marketplace | Q2/3 25 |
|
||||
| MyImage from Docker | CI/CD integration (See MyAgent CI/CD) | Q1 25 |
|
||||
| MyImage Hub Integration | CI/CD integration (See MyAgent CI/CD) no more need for separate Hub | Q1 25 |
|
||||
| Mycelium Core | Just more hardening and testing | Q1 25 |
|
||||
| Mycelium Message Bus | Replace our current RMB, all our own RPC over Mycelium | Q1 25 |
|
||||
| ZOS VM's Cloud Slices | Integration MyAgent CI, use cloud slices to manage | Q2 25 |
|
||||
| ZOS Monitoring Docu | More docu and easier API | Q2 25 |
|
||||
| ZOS Web Gateway Expansion | Need more deployed, better integration with new Mycelium | Q2 25 |
|
||||
| Mycelium Names | In V4, name services | Q2 25 |
|
||||
| ZOS Cloud,Storage,AI Slices | As part of marketplace for V4, flexible billing mutual credit | Q3 25 |
|
||||
| FungiStor | A revolutionary different way how to deliver content | Q3 25 |
|
||||
| MyImage on FungiStor | Can be stored on FungiStor | Q3 25 |
|
||||
Reference in New Issue
Block a user