Hi,
Can the slicer3D be hosted off a render server so that multiple clients can access it with less powerful client hardware?
Thank you
@muratmaga @pieper Do you have experience in setting up a docker swarm with web VNC and reverse proxy so that multiple users can log on through the same webpage, each seeing his own Slicer instance?
We could host such a server in our lab, but we would need help with setting it up.
It could be used to demonstrate that Slicer can “run in a web browser” and it could be also configured to do segmentation or other tasks initiated from OHIF DICOM web viewer (download the data set, allow user to interact with it, then push back the data). It would be awesome to have this for RSNA.
Sorry, I have no experience with docker. But would love to see what you describe in action…
I don’t have a fully worked out example now, but have discussed working on this at project week with Emel to test with ePad.
I was planning to set something up using google cloud technologies so it would scale and basically be open to anyone willing to sign up for an account (at least for the first $300 worth of testing) can try it out. But the same basic functionality should also be good to work with a server at Perk if you want to open it up. Main issues I can think of are dealing with user accounts, TLS, allocating ports to users, etc.
On google I’ve been playing with the Identity Aware Proxy which allows TLS and you can control authorization of connections to VMs or instances via google logins so we can get out of demo mode into something you could use for real work. All this stuff can be controlled via the gcloud API, so my thought would be that you would be in OHIF or ePad and you’d ask for a Slicer instance to open up with the same study (hence I was calling the project SlicerStudyBuddy - name subject to discussion 
). If you are logged to your google account and accessing one of their dicomweb servers it’s possible to pass the authentication token to the virtual Slicer instance so it can inherit that access to pull the data.
Would be interesting to try setting this up for RSNA, but of course the time is short.
1 Like
There are alternatives:
NSF/XSEDE supports a program called Science Community Gateways Initiative. https://sciencegateways.org/
We can request computational resources to be used by the public, as well as support for a gateway interface. These are free-of-charge services, but require competitive renewal every 12 months. Most likely the allocation will be on their Jetstream VM farm (https://jetstream-cloud.org/). Jetstream currently does not support GPUs, but there can be a hybrid solution.
Like any grant application, it will require a demonstrable need by the community.
Thank you indeed for all your replies and your time.
Regards
This would be awesome to have for RSNA. Do you think you could have a chance to set this up?
In the long term, we will need both cloud and self hosting setup - cloud hosting is very scaleable and lots of pre-configured services are available; self hosting has no data privacy issues, can be more vendor neutral, and may cost less.
Science Community Gateways could be good, too, but if you need to write a proper proposal (not just a formality like filling out a form) every 12 months then I don’t see the point, as you could spend that time with writing larger grants that can fund cloud computing resources or buying your own hardware.
XSEDE grants look somewhat like a regular grant initially, but competitive renewals (every 12 months) are much simpler, especially if you are hitting your target user numbers and can justify maintaining the resource. If not, you can dial down your request to more meaningful numbers.
It is really the lack of GPU on those VM is my main hesitation. Perhaps that will have that soon…
With the short week here I don’t think I’ll have time to set anything up before RSNA, but we can probably try some things on the fly there.
1 Like
I would be interested in this as well - let me know if you get together to work on this at RSNA!
Hi, I hope everyone is doing fine! Out of curiosity, has there been any progress on the topic of this thread?
Recently we ran our week long SlicerMorph workshop on cloud using Docker containers. I made some comments on how it worked out here:
Overall it went well. VNC sessions can be managed better (specifically issue #6), but otherwise experience has been quite pleasant.
1 Like