info_tfgrid/collections/tfgrid4/boxes/cloudblock.md

77 lines
3.1 KiB
Markdown
Raw Permalink Normal View History

2024-05-02 15:54:26 +00:00
# CloudBlock Concepts
2024-04-25 09:22:51 +00:00
2024-05-02 06:28:43 +00:00
<h2>Table of Contents</h2>
2024-05-02 15:54:26 +00:00
- [CloudBlock Concepts](#cloudblock-concepts)
- [CloudBlock (CB)](#cloudblock-cb)
2024-05-02 06:28:43 +00:00
- [Cloud Hour (CH)](#cloud-hour-ch)
2024-05-02 15:54:26 +00:00
- [CloudBlock Properties](#cloudblock-properties)
2024-05-02 06:28:43 +00:00
2024-04-25 10:14:09 +00:00
!!wiki.include page:'box_intro.md'
2024-05-02 15:54:26 +00:00
## CloudBlock (CB)
2024-04-25 09:22:51 +00:00
2024-05-02 15:54:26 +00:00
A cloudblock is a unit of compute, fast storage and memory.
There are unlimited different configurations of cloudblock.
2024-04-25 09:22:51 +00:00
2024-05-02 15:54:26 +00:00
A configuration of a machine defines the cloudblock which can be made.
2024-04-25 09:22:51 +00:00
2024-05-02 15:54:26 +00:00
cloudblock can be aggregated to make a bigger cloudblock.
2024-04-25 09:22:51 +00:00
2024-05-02 15:54:26 +00:00
The default cloudblock has
2024-04-25 09:22:51 +00:00
- 4GB memory
- 2 virtual cores of CPU
- minimal 50 GB of fast storage (can be more, as to be defined by provider)
- minimal availability of 1 mbit/s bandwidth at all times
Terms
- The virtual cores are max oversubscribed 4x
2024-05-02 15:54:26 +00:00
- Min passmark per cloudblock is 500 passmark (CPU benchmark)
2024-04-25 09:22:51 +00:00
- At least 50 GB storage available, more is better
2024-05-02 06:28:43 +00:00
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
- 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)
2024-04-25 09:22:51 +00:00
2024-05-02 06:28:43 +00:00
A cloudhour is like a kwatth unit for electricty: it represents a CloudBlock being used for 1h and billed as such.
2024-04-25 09:22:51 +00:00
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.
2024-05-02 15:54:26 +00:00
## CloudBlock Properties
2024-04-25 09:22:51 +00:00
The service provider (hoster) defines the following properties per cloud box
2024-04-26 17:54:30 +00:00
- Cost of 1 CloudHour (use the box for 1h)
- Discounts if used for longer periods & if renter has large amount of TFT in wallet
- Min available storage in GB (min 50)
- Max available storage in GB
- Min passmark, max passmark
- Max bandwidth
- Min bandwidth (min 1 mbit/sec)
- Cost per GB bandwidth
- Cost for additional storage HDD or SSD per GB/month
- Max additional storage
2024-05-02 15:54:26 +00:00
- Max aggregation size (how many of the cloudblock can be combined)
2024-04-26 17:54:30 +00:00
- Link to support site if any (find info about hoster and service capabilities)
- If linked to Hosting Pool (company giving support on the machines)
- Pub ip address possible or not (is option)
- Link to monitoring page (if any)
- Location & type of location
2024-04-25 09:22:51 +00:00
2024-05-02 15:54:26 +00:00
Each cloudblock has unique ID and can be looked at through a portal (or found).
2024-04-25 09:22:51 +00:00