Skip to content

Commit

Permalink
tip formatted text
Browse files Browse the repository at this point in the history
  • Loading branch information
Milstein committed Jul 22, 2024
1 parent a3eadbb commit 093cac9
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/get-started/allocation/allocation-change-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,16 +28,16 @@ Then submitting the change request, this will notify the NERC admin about it. Pl
wait untill the NERC admin approves/ deny the change request to see the change on
your resource allocation for the selected project.

!!! info "Information"
!!! tip "Important Information"
PI or project managers can put the new values on the textboxes for **ONLY**
quota attributes they want to change others they can be left **blank** so those
quotas will not get changed! To use GPU resources on your VM, you need to
specify the number of GPUs in the "OpenStack GPU Quota" attribute. Additionally,
ensure that your other quota attributes, namely "OpenStack Compute vCPU Quota"
and "OpenStack Compute RAM Quota (MiB)" have sufficient resources to meet the
**vCPU** and **RAM** requirements for one of the GPU tier-based flavors.
quotas will not get changed!

Refer to the [GPU Tier documentation](../../openstack/create-and-connect-to-the-VM/flavors.md#3-gpu-tier)
To use GPU resources on your VM, you need to specify the number of GPUs in the
"OpenStack GPU Quota" attribute. Additionally, ensure that your other quota
attributes, namely "OpenStack Compute vCPU Quota" and "OpenStack Compute RAM
Quota (MiB)" have sufficient resources to meet the **vCPU** and **RAM** requirements
for one of the GPU tier-based flavors. Refer to the [GPU Tier documentation](../../openstack/create-and-connect-to-the-VM/flavors.md#3-gpu-tier)
for specific requirements and further details on the flavors available for GPU
usage.

Expand Down

0 comments on commit 093cac9

Please sign in to comment.