ansys / ansys/Visual-Interactive-Simulation-Object-Renderer

[Remote rendering 5.3] Remote mode deployment and pvserver packaging

Open
#35 0 comments 0 reactions 0 assignees View on GitHub
maintenance technical
Dominant language
Python
Stars
0
Forks
0
Avg merge
1d 10h
Merged PRs (30d)
37

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_

Contributor guide

Open the contributing guide

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.

Assessment

Tech stack
python
Domain
build-system, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.