diff --git a/content/en/users/getting-started/architecture/_index.md b/content/en/users/getting-started/architecture/_index.md index 0216055e9a..5d32bd16c2 100644 --- a/content/en/users/getting-started/architecture/_index.md +++ b/content/en/users/getting-started/architecture/_index.md @@ -244,6 +244,34 @@ v0.2 of the format is shown below: A JSON schema defining a valid Public IP Usage message can be found at: +#### GPU Usage Record + +The fedcloud task force has agreed on an GPU Usage Record. The format uses many +of the same fields as the Cloud Usage Record. A table defining _Draft 4 – +24/02/2021_ is shown below: + + + +| GPU Usage Record Property | Type | Null | Definition | +| ------------------------- | -------------- | ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | +| MeasurementMonth | `int` | No | The month/year the reported usage should be assigned to. If the month/year is the current month/year, the usage should be up to the point of reporting. | +| MeasurementYear | `int` | No | | | +| AssociatedRecordType | `varchar(255)` | No | The context in which the reported usage was used. I.e. “cloud” for an accelerator attached to a VM. | +| AssociatedRecord | `varchar(255)` | No | VMUUID if AssociatedRecordType is “cloud” | +| GlobalUserName | `varchar(255)` | Yes | See the definition of your AssociatedRecordType | +| FQAN | `varchar(255)` | No | See the definition of your AssociatedRecordType | +| SiteName | `varchar(255)` | No | See the definition of your AssociatedRecordType | +| Count | `decimal` | No | A count of the Accelerators attached to the VM. At the moment Accelerators are not shared among VMs but it will change when Accelerator virtualization is applied, so we should have the field at decimal type instead of integer (e.g. Count = 0.5 when it is shared between two VMs). | +| Cores | `int(11)` | Yes | Total number of cores. i.e. So if an Accelerator has 64 cores and a VM has 2 like that attached then we would report: Count=2 and Processors=128 | +| ActiveDuration | `int(11)` | Yes | Actual usage duration of the Accelerator in seconds for the given month/year (in case some systems could report actual usage). At the moment, ActiveDuration will be the same as the AvailableDuration due to the limitation of currently used technologies (impossible to get ACCELERATOR utilization from outside of the VM, no ACCELERATOR hot-plug into running VM) but it may change in near future so it is good to have the fields separately. Set to AvailableDuration if AcitveDuration is omitted from the record | +| AvailableDuration | `int(11)` | No | Time accelerator was available in seconds for the given month/year (Wall)Time that a GPU was attached to a VM. | +| BenchmarkType | `varchar(255)` | Yes | Name of benchmark used for normalization of times | +| Benchmark | `decimal` | Yes | Value of benchmark of Accelerator | +| Type | `varchar(255)` | No | High level description of accelerator, i.e. GPU, FPGA, Other | +| Model | `varchar(255)` | Yes | model number, spec, some other concept that 2 ACCELERATORs with the same number of cores might be different etc | + + + #### APEL and accounting portal Once generated, records are delivered to the central accounting repository using