Adding variable to control execution of nvidia driver role in ansible playbook
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- ansible, gcp
- Domain
- cloud, devops, infrastructure
Research direction
Start with devops/ansible/playbook.yml and inspect the nvidia.nvidia_driver role invocation alongside the existing run_worker_container, run_server, and run_viame_cli variables. Add a user-controlled way to skip the driver role, then run the playbook with the relevant variable settings to confirm the role is skipped or executed as intended.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? If so, Please describe.
When deploying dive/viame-web in NOAA GCP space, ie on a hardened VM, I've run into issues installing the GPU drivers via the nvidia.nvidia_driver role. Currently in the DIVE ansible playbook, there is no variable that can control whether the nvidia.nvidia_driver role is executed or not. My current solution is to comment out this line in the ansible yml files, before running the playbook.
Describe the solution you'd like
Updating the ansible playbook such that the user can provide a variable to not install the nvidia.nvidia_driver role. It feels reasonable to simply add when: run_worker_container or run_server or run_viame_cli | bool to the nvidia.nvidia_driver role?
Describe alternatives you've considered
The current workflow is functional, but indirect.
Additional context
N/A
- Dominant language
- TypeScript
- Stars
- 106
- Forks
- 25
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 59
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kitware/dive
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Type: bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Type: Feature Request
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
Type: Feature Request
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·