info_tfgrid/collections/tfgrid4/slices/cloudslice.md

64 lines
2.7 KiB
Markdown
Raw Normal View History

2024-05-23 08:09:37 +00:00
# Cloud Slice Concept
2024-04-25 09:22:51 +00:00
2024-05-23 08:09:37 +00:00
!!wiki.include page:'slice_intro.md'
2024-04-25 10:14:09 +00:00
2024-05-23 08:09:37 +00:00
## Cloud Slice
2024-04-25 09:22:51 +00:00
2024-08-16 12:04:37 +00:00
- A Cloud Slice is a unit of compute, fast storage and memory.
- A configuration of a machine defines the Cloud Slice which can be made.
- A Cloud Slice can be aggregated to make a bigger Cloud Slice.
2024-04-25 09:22:51 +00:00
2024-08-15 23:40:17 +00:00
The default Cloud Slice has
2024-04-25 09:22:51 +00:00
- 4GB memory
- 2 virtual cores of CPU
2024-05-10 12:13:09 +00:00
- 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
2024-04-25 09:22:51 +00:00
Terms
- The virtual cores are max oversubscribed 4x
2024-08-15 23:40:17 +00:00
- Min passmark per Cloud Slice 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.**
2024-08-16 12:04:37 +00:00
- 15 Cloud Slices each:
2024-05-02 06:28:43 +00:00
- 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)
2024-08-16 12:04:37 +00:00
- when a user choses the full machine, then he/she will have reserved all Compute Slices capacity which means the machine is now dedicated reserved for the user, the hoster specifies the discount for this typically 50%.
- Min 2GB always needs to be left as buffer for memory and 10% of SSD capacity on the host machine
2024-05-02 06:28:43 +00:00
How does it work:
2024-08-15 23:40:17 +00:00
- When a developer wants to deploy a virtual machine, they need to define the required capacity and will be able to make a choice based on these Cloud Slices, each Cloud Slice has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these StorageSlices 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.
2024-05-02 06:28:43 +00:00
## Cloud Hour (CH)
2024-04-25 09:22:51 +00:00
2024-08-16 12:04:37 +00:00
- A Cloud Hour is like a kwatth unit for electricty: it represents a Cloud Slice being used for 1h and billed as such.
- ThreeFold Farmers (Providers) can define the proce of the Cloud Hour in a chosen currency.
2024-04-25 09:22:51 +00:00
2024-08-15 23:40:17 +00:00
## Cloud Slice Properties
2024-04-25 09:22:51 +00:00
2024-08-16 12:04:37 +00:00
The ThreeFold Farmer defines the following properties per Cloud Slice
2024-04-25 09:22:51 +00:00
2024-08-16 12:04:37 +00:00
- Cost of 1 Cloud Hour (use the slice for 1h)
- Maximum Discount (based on participation in Liquidity Pool and/or longer renting periods)
2024-04-26 17:54:30 +00:00
- Min available storage in GB (min 50)
- Max available storage in GB
2024-08-16 12:04:37 +00:00
- Min passmark, Max passmark
2024-04-26 17:54:30 +00:00
- 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-08-15 23:40:17 +00:00
- Max aggregation size (how many of the Cloud Slice can be combined)
2024-04-26 17:54:30 +00:00
- Link to support site if any (find info about hoster and service capabilities)
2024-08-16 12:04:37 +00:00
- If linked to Farming Pool (company giving support on the machines)
- Pub IP address possible or not (is option)
2024-04-26 17:54:30 +00:00
- Link to monitoring page (if any)
- Location & type of location
2024-04-25 09:22:51 +00:00