Skip to content
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.

CP Resource name not matching the config #10

Open
PlutoNbai opened this issue Jul 25, 2023 · 5 comments
Open

CP Resource name not matching the config #10

PlutoNbai opened this issue Jul 25, 2023 · 5 comments

Comments

@PlutoNbai
Copy link

I got :
"NVIDIA GeForce RTX 2080 Ti",
"GeForce RTX 3090",
"NVIDIA RTX 2080",

It will be really hard if the name is not same format

@Normalnoise
Copy link
Contributor

https://github.com/lagrangedao/lagrange-server/issues/173#issuecomment-1649260511

you can match it with the instance name(the first column ) as discussed last meeting.

image

@PlutoNbai
Copy link
Author

There was some misunderstanding in our communication, and this issue did not arise at the time of the match. This issue arises when I analyze the data reported by cp to get the currently corresponding available instance type.

I need CP to strictly follow the second line of the table you gave to give the corresponding GPU name. Otherwise, the backend can't process the data.

This means that the server will not recognize the cp reporting with a different GPU name.

@Normalnoise
Copy link
Contributor

@PlutoNbai We have developed a tool to get and process the hardware info, so CP will give you the updated config table here(https://github.com/lagrangedao/lagrange-server/issues/173#issuecomment-1649260511), the GPU name by CP reported will be same as the table

@flin-nbai
Copy link
Collaborator

@Normalnoise can you give us a sample request of what the CP is going to report

@Normalnoise
Copy link
Contributor

yes, @sonic-chain will leave a sample request.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants