This commit is contained in:
2024-05-02 08:28:43 +02:00
parent 46912722d1
commit 28f366cb14
43 changed files with 381 additions and 108 deletions

View File

@@ -1,7 +1,7 @@
A Cloud, Storage or AI Box is a part of a server/computer (3Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
A Cloud, Storage or AI Box is a part of a server/computer (TF or INCA Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
These Cloud, Storage or AI Boxes can be bought by the INCA/TF Community through the INCA marketplace.
The boxes are hosted on 3Nodes.

View File

@@ -1,5 +1,13 @@
# CloudBox Concepts
<h2>Table of Contents</h2>
- [CloudBox Concepts](#cloudbox-concepts)
- [CloudBox (CB)](#cloudbox-cb)
- [Cloud Hour (CH)](#cloud-hour-ch)
- [CloudBox Properties](#cloudbox-properties)
!!wiki.include page:'box_intro.md'
## CloudBox (CB)
@@ -24,9 +32,22 @@ Terms
- Min passmark per cloudbox is 500 passmark (CPU benchmark)
- At least 50 GB storage available, more is better
## CloudHour (CH)
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
A cloudhour is like a kwatth unit for electricty: it represents a cloudbox being used for 1h and billed as such.
- 15 Storage Blocks each:
- 4 GB of memory (60 GB total)
- 120 GB of SSD capacity
- 6.4 logical CPU core (oversubscription of 4, which means user can max use 4x CPU capacity if system allows)
- when a user choses the full machine, then he/she will have reserved all Storage Blocks capacity which means the machine is now dedicated reserved for the user, the hoster specifies the discount for this typically 50%. On a dedicated machine the user has full access to the GPU.
- min 2GB always needs to be left as buffer for memory and 10% of SSD capacity
How does it work:
- When a developer wants to deploy a virtual machine, he/she needs to define the required capacity and will be able to make a choice based on these CloudBlocks, each CloudBlock has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these Storage Blocks need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
## Cloud Hour (CH)
A cloudhour is like a kwatth unit for electricty: it represents a CloudBlock being used for 1h and billed as such.
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.

View File

@@ -25,7 +25,7 @@ The service provider (hoster) defines the following properties per StorageBox:
- Max bandwidth
- Min bandwidth (min 1 mbit/sec)
- Cost per GB bandwidth
- Max aggregation size (how many of the storage boxes can be combined)
- Max aggregation size (how many of the Storage Blockes can be combined)
- Link to support site if any (find info about hoster and service capabilities)
- If linked to Hosting Pool (company giving support on the machines)
- Location & type of location