s

collections/tfgrid4/slices/aislice.md

@@ -0,0 +1,33 @@
+# AI Slice
+
+!!wiki.include page:'slice_intro.md'
+
+An AI box is a unit of AI capacity (GPU or future TPU driven).
+
+- The mininal GPU supported for now is a Nvidia 4090 or comparable
+
+An AI box can be launched in our Zero-OS and can enable any possible AI workload.
+
+## AI Hour (AH)
+
+AI hour (AH) is like a kwatth unit for electricty: it represents a AISlice being used for 1h and billed as such.
+
+INCA Hosts (our cloud providers) can price the AI Hour themselves in a chosen currency.
+
+## AISlice Properties
+
+The service provider (hoster) defines the following properties per AISlice:
+
+- Type of GPU
+- Price per hour
+- Discounts if used for longer periods & if renter has large amount of TFT in wallet
+- Max bandwidth
+- Min bandwidth (min 1 mbit/sec)
+- Cost per GB bandwidth if any
+- Max aggregation size (how many of the AISlices can be combined in one node if relevant)
+- 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
+
+Each AISlice has unique ID and can be looked at through a portal (or found).
+

collections/tfgrid4/slices/cloudslice.md

@@ -0,0 +1,68 @@
+# Cloud Slice Concept
+
+!!wiki.include page:'slice_intro.md'
+
+## Cloud Slice
+
+A cloudslice is a unit of compute, fast storage and memory.
+There are unlimited different configurations of cloudslice.
+
+A configuration of a machine defines the cloudslice which can be made.
+
+A cloudslice can be aggregated to make a bigger cloudslice.
+
+The default cloudslice has 
+
+- 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
+- Min passmark per cloudslice is 500 passmark (CPU benchmark)
+- At least 50 GB storage available, more is better
+
+**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
+
+- 15 StorageSlices 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 StorageSlices 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, they need to define the required capacity and will be able to make a choice based on these CloudSlices, each CloudSlice 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 cloudhour is like a kwatth unit for electricty: it represents a CloudSlice being used for 1h and billed as such.
+
+INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.
+
+## CloudSlice Properties
+
+The service provider (hoster) defines the following properties per cloud box
+
+- 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
+- Max aggregation size (how many of the cloudslice 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)
+- Pub ip address possible or not (is option)
+- Link to monitoring page (if any)
+- Location & type of location
+
+Each cloudslice has unique ID and can be looked at through a portal (or found).
+

collections/tfgrid4/slices/slice_intro.md

@@ -0,0 +1,7 @@
+
+A Cloud, Storage or AISlice 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 AISlices can be bought by the INCA/TF Community through the INCA marketplace.
+
+
+

collections/tfgrid4/slices/storageslice.md

@@ -0,0 +1,34 @@
+# Storage Slice
+
+!!wiki.include page:'slice_intro.md'
+
+## Storage Slice
+
+A storageslice is a unit of ZDB storage as can be used as backend for Zero-Stor (our quantum safe storage system).
+
+The default cloudslice has:
+
+- 100GB of storage
+
+## Storage Hour (SH)
+
+A storagehour is like a kwatth unit for electricty, it represents a storageslice being used for 1h and billed as such.
+
+INCA Hosts (our cloud providers) can price the StorageHour themselves in a chosen currency.
+
+## Storage Slice Properties
+
+The service provider (hoster) defines the following properties per StorageSlice:
+
+- Min size in GB (100GB+), max size
+- Discounts if used for longer periods & if renter has large amount of TFT in wallet
+- Max bandwidth
+- Min bandwidth (min 1 mbit/sec)
+- Cost per GB bandwidth
+- Max aggregation size (how many of the StorageSlices 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
+
+Each StorageSlice has unique ID and can be looked at through a portal (or found).
+