[Remote rendering 5.3] Remote mode deployment and pvserver packaging
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, devops
Research direction
Start by reading the spike referenced in 5.1 and compare the proposed Python-package and ParaView-base container delivery approaches. Confirm where remote-mode VISOR is deployed and how pvserver is supplied, then verify that it is available there and version-matched to the ParaView/VTK stack.
Written by the indexing model from the issue text.
Description
📝 Description of the feature
Decide and implement how remote-mode VISOR is delivered so pvserver is available where it runs, rather than assumed present in the environment. This will be informed by the spike in 5.1
[Possible shape, if bundling pvserver into VISOR's Python package is not a good option: container built on ParaView base with VISOR installed onto ParaView's Python environment]
Acceptance Criteria
Remote-mode VISOR runs with pvserver available in its deployment, version-matched to the ParaView/VTK stack.
The delivery mechanism is decided and implemented.
💵 Business Value
No response
🔗 Useful links and references
No response
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 47
Contributor guide
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 ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Library updates Opentechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assignee ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assignee ·
-
Release 1.0.2 Openmaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assignee ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assignee ·
All issues in ansys/Visual-Interactive-Simulation-Object-Renderer
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100