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

Node Option Not Available in version 2.2.0 #2032

Closed
rajpatel-msstate opened this issue Mar 7, 2024 · 10 comments
Closed

Node Option Not Available in version 2.2.0 #2032

rajpatel-msstate opened this issue Mar 7, 2024 · 10 comments
Assignees

Comments

@rajpatel-msstate
Copy link
Contributor

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Admin tools'
  2. Click on 'Nodes'
  3. Click on the hyperlink for any of the 'Node'
  4. You will see the following behavior

Expected behavior
The node should have listed the option on the right-hand side for each relevant option on the left-hand

Screenshots
If applicable, add screenshots to help explain your problem.

Server (please complete the following information):

  • OS: Ubuntu 22.04 LTS

  • Ravada Version: 2.2.0 (stable and beta)

Client (please complete the following information):

  • Browser: Firefox and Safari
  • OS: Windows 11

Additional context
I have tested the with Ravada version 2.1.9, and it seems to be working fine there. I am guessing that there may be some dependencies files that I maybe missing or the newer version does not have the code to support it. Please guide me on this issue!

Node Option - 2 2 0 v
Node Option - 2 1 9 v

@frankiejol frankiejol self-assigned this Mar 8, 2024
frankiejol added a commit that referenced this issue Mar 8, 2024
frankiejol added a commit that referenced this issue Mar 8, 2024
frankiejol added a commit that referenced this issue Mar 11, 2024
@frankiejol
Copy link
Member

Thank you very much @rajpatel-msstate for your accurate bug report. We provided test and fix for this problem just released on v2.2.1.

@rajpatel-msstate
Copy link
Contributor Author

Thank you very much @rajpatel-msstate for your accurate bug report. We provided test and fix for this problem just released on v2.2.1.

You're welcome! Thank you for your work on this Project and making it available to all of us.

@rajpatel-msstate
Copy link
Contributor Author

May I enquire about one more thing? I see the option for "GPU Mediated Device". Is this feature available in version 2.2.1 or will it be implemented in the next release?

image

@frankiejol
Copy link
Member

Glad you noticed !
GPU mediated devices are supported in this release. We have not provided documentation nor announced this feature because we want to test it and document it properly. Notice you need NVIDIA hardware that supports grid. Also you have to manage the GPU and partition the devices manually from the OS using mdevctl.
Feel free to try it, feedback is appreciated.

@rajpatel-msstate
Copy link
Contributor Author

Thank you so much for the information! I will gladly give it a try and will let you know if I am not able to make it work. We do have all the pre-requisites you mentioned in our environment.

@frankiejol
Copy link
Member

The packages uploaded were not correct. We just put the correct v2.2.1 final release. Sorry for the inconvenience.

@rajpatel-msstate
Copy link
Contributor Author

No worries at all! I will get the latest v2.2.1 installed and give it a try again. Thank you again.

@rajpatel-msstate
Copy link
Contributor Author

May I please contact you via your university email? It seems that I am not able to use any of the "hostdev" functionality on any of my "child" nodes except of the "master" node.

@frankiejol
Copy link
Member

Please contact me directly if you have my email. We have yet to test this feature with nodes, so it is likely you spotted a problem already. Anyway, please open a new issue and we can add more official comments.

@rajpatel-msstate
Copy link
Contributor Author

Please contact me directly if you have my email. We have yet to test this feature with nodes, so it is likely you spotted a problem already. Anyway, please open a new issue and we can add more official comments.

I do have your email, but I think you are right that I should submit this in the GitHub issue. Please see the newly submitted bug report at: #2035 (comment)

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

No branches or pull requests

2 participants