65 lines
2.8 KiB
Markdown
65 lines
2.8 KiB
Markdown
# Cloud Slice Concept
|
|
|
|
!!wiki.include page:'slice_intro.md'
|
|
|
|
## Cloud Slice
|
|
|
|
- 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.
|
|
|
|
The default Cloud Slice has
|
|
|
|
- 4GB memory
|
|
- 2 virtual cores of CPU (CPU threads)
|
|
- Minimal 50 GB of fast storage = SSD (can be more, as to be defined by provider)
|
|
- Minimal availability of 1 mbit/s bandwidth at all times slice
|
|
|
|
Terms
|
|
|
|
- The virtual cores are max oversubscribed 4x
|
|
- Min passmark per Cloud Slice is 500 passmark (CPU benchmark)
|
|
- At least 50 GB storage available, more is better
|
|
- At least 99.5% uptime per node and 99.9% for the farming location (cluster)
|
|
|
|
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
|
|
|
|
- 15 Cloud Slices 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 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
|
|
|
|
How does it work:
|
|
|
|
- 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.
|
|
|
|
## Cloud Hour (CH)
|
|
|
|
- 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.
|
|
|
|
## Cloud Slice Properties
|
|
|
|
The ThreeFold Farmer defines the following properties per Cloud Slice
|
|
|
|
- Cost of 1 Cloud Hour (use the slice for 1h)
|
|
- Maximum Discount (based on participation in Liquidity Pool and/or longer renting periods)
|
|
- 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
|
|
- Max aggregation size (how many of the Cloud Slice can be combined)
|
|
- Link to support site if any (find info about hoster and service capabilities)
|
|
- If linked to Farming 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
|
|
|
|
|