Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPU Resource Enablement page should contain directions to Provider Feature Discovery - GPU Configuration Integration Guide & Akash Provider Feature Discovery Upgrade/Enablement pages #139

Open
andy108369 opened this issue Apr 17, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@andy108369
Copy link
Contributor

Page https://akash.network/docs/providers/build-a-cloud-provider/gpu-resource-enablement/ should contain some link/info about these two pages, critical for enabling GPU support:

As new providers may find their provider does not detect the GPU because it is not in the https://github.com/akash-network/provider-configs/blob/main/devices/pcie/gpus.json file and they have to run the following command in order to update the gpus.json file:

provider-services tools psutil list gpu | jq '.cards[] | .pci | {vendor: .vendor, product: .product}'

Also, this page https://akash.network/docs/providers/akash-provider-feature-discovery-upgrade-enablement/#akash-provider-upgrade does not reflect all the attributes necessary, e.g.:

  - key: capabilities/gpu/vendor/nvidia/model/a100
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/ram/80Gi
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/ram/80Gi/interface/pcie
    value: true
  - key: capabilities/gpu/vendor/nvidia/model/a100/interface/pcie
    value: true
@brewsterdrinkwater brewsterdrinkwater added the documentation Improvements or additions to documentation label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants