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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Allow setting an agent to be CPU only from the agent side. #805

Closed
s3inlc opened this issue Aug 19, 2022 · 1 comment
Closed

Feature Request: Allow setting an agent to be CPU only from the agent side. #805

s3inlc opened this issue Aug 19, 2022 · 1 comment
Assignees
@s3inlc
Labels
agent Hashtopolis Agent related new feature New feature to be added

Comments

@s3inlc
Copy link
Member

s3inlc commented Aug 19, 2022

Add a flag to the agent (e.g. --cpu) which makes the agent only querying CPUs and register on the server side as a CPU only agent directly.
This allows easier deployment of agents which should have two agents running (one for GPUs and one for CPUs) without having the GPUs listed on both agents on the server overview, and additionally not having to set to CPU only on the server side after registration.
@s3inlc s3inlc added new feature New feature to be added agent Hashtopolis Agent related labels Aug 19, 2022
@s3inlc s3inlc self-assigned this Aug 19, 2022
@s3inlc s3inlc mentioned this issue Aug 22, 2022
Merged
@zyronix
Copy link
Member

zyronix commented Jun 16, 2023

Fixed in #807

@zyronix zyronix closed this as completed Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s3inlc s3inlc

Labels
agent Hashtopolis Agent related new feature New feature to be added
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@s3inlc @zyronix