Skip to content

Commit

Permalink
Minor formatting update
Browse files Browse the repository at this point in the history
  • Loading branch information
@enolfc
enolfc committed Dec 18, 2023
1 parent cae8e33 commit a23b75e
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions content/en/providers/cloud-compute/openstack/gpu.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -49,15 +49,15 @@ Users should be able to easily discover the flavours that provide GPUs (or
accelerators in general). The following table describes the agreed metadata for
EGI providers to add to those flavours:

| Metadata | Definition | Comments |
| ------------------------------ | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Accelerator:Type | Type of accelerator (e.g. `GPU`) | Possible values: `GPU`, `MIC`, `FPGA`, `TPU`, `NPU` |
| Metadata | Definition | Comments |
| ------------------------------ | ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Accelerator:Type | Type of accelerator (e.g. `GPU`) | Possible values: `GPU`, `MIC`, `FPGA`, `TPU`, `NPU` |
| Accelerator:Number | Number of accelerators available in the flavour (e.g. `1.0`) | Non integers allowed for the case of sharing GPU between VMs |
| Accelerator:Vendor | Name of accelerator Vendor (e.g. `NVIDIA`) | |
| Accelerator:Model | Model of accelerator (e.g. `Tesla V100`) | Need to make consensus and enforce. A100 is usually marketed without "Tesla" classname. Similarly, RTX A6000 usually marketed without “GeForce”. For clarity, full names should be used: “Tesla A100” and “GeForce RTX A6000” |
| Accelerator:Version | Version of the accelerator | Some cards have different versions, e.g. A100 PCIe and NVLink. Openstack does not allow empty value, so we should give 0 if no version is specified |
| Accelerator:Memory | RAM in GB of the accelerator | |
| Accelerator:VirtualizationType | Type of virtualisation used (e.g. `PCI passthrough`) | Not relevant for accounting, but may be still useful in some cases |
| Accelerator:Vendor | Name of accelerator Vendor (e.g. `NVIDIA`) | |
| Accelerator:Model | Model of accelerator (e.g. `Tesla V100`) | Need to make consensus and enforce. A100 is usually marketed without "Tesla" classname. Similarly, RTX A6000 usually marketed without “GeForce”. For clarity, full names should be used: “Tesla A100” and “GeForce RTX A6000” |
| Accelerator:Version | Version of the accelerator | Some cards have different versions, e.g. A100 PCIe and NVLink. Openstack does not allow empty value, so we should give 0 if no version is specified |
| Accelerator:Memory | RAM in GB of the accelerator | |
| Accelerator:VirtualizationType | Type of virtualisation used (e.g. `PCI passthrough`) | Not relevant for accounting, but may be still useful in some cases |

There are some extra fields that are defined in the GLUE2.1 schema but not so
relevant for GPUs and therefore not considered at the moment. These are listed
Expand Down

0 comments on commit a23b75e

Please sign in to comment.