[Paraview] ParaViewWeb on remote machine w/ port forwarding

[Scott Wittenburg]

Hi Ken,

   Yes, ParaViewWeb supports either option, though option 1 seems better in
your case.  Additionally, unless you have your own job management software
running on the rendering computer, you may want to look at using the Python
launcher we provide.  See this document:

http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/python_launcher

   Using the Python launcher along with an Apache web server provides you
with seemingly infinite ways to set your system up, so we have provided
another guide which describes some of the common configurations.  That
document is located here:

http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/launching_examples

   The section titled "Second Example: Two machines" shows a diagram of the
use case I think you'll want, and it has an example configuration file for
the Python launcher as well as Apache virtual host configuration example.

Hope this helps,
Scott


On Tue, Nov 17, 2015 at 1:46 PM, Ken Mankoff <mankoff at gmail.com> wrote:

> Hi Scott,
>
> IT says 2.4.6, but that they have all the modules listed in your
> requirements.
>
> We're considering two approaches since their webserver VMs also don't have
> good graphics virtualization: 1) Some ParaView software running on the the
> web VM that has another computer doing the rendering for it. This seems to
> be an officially supported method of running PVW, but I can't quite figure
> out how to set this up from the docs, and 2) No PV/Kitware software on the
> web VM. Just pass everything (via Apache) to another computer. Not sure
> which would be easier for IT, better for the end user, etc.
>
> Thanks,
>
>   -k.
>
> On Tue, Nov 17, 2015 at 3:10 PM, Scott Wittenburg <
> scott.wittenburg at kitware.com> wrote:
>
>> The reason I ask is that Apache 2.4.7 is the oldest version in which all
>> the required modules are present and work correctly.  You can see the list
>> of needed modules here:
>>
>>
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04-section-5
>>
>> Cheers,
>> Scott
>>
>> On Tue, Nov 17, 2015 at 1:04 PM, Scott Wittenburg <
>> scott.wittenburg at kitware.com> wrote:
>>
>>> Hi Ken,
>>>
>>>    Before doing much debugging, can you check and report back here what
>>> version of Apache you're running on the web-facing servers?
>>>
>>> Cheers,
>>> Scott
>>>
>>> On Tue, Nov 17, 2015 at 12:53 PM, Ken Mankoff <mankoff at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm trying to get ParaViewWeb (PVW) running. I've read the
>>>> documentation and have the QuickStart section working, but am still having
>>>> trouble with a more complicated setup.
>>>>
>>>> My IT support team has the web-facing servers as VMs running a slighly
>>>> outdated CentOS. I don't think this is a good setup for PVW.
>>>>
>>>> Is it possible to tell apache to just forward all requests to a remote
>>>> computer? My computer inside the web firewall does run PVW successfully,
>>>> and I'd like to access that rendering hardware and storage space. Is this a
>>>> PVW config option? Or just an apache option? Or a paraview server option?
>>>> Can someone advise what ports to forward?
>>>>
>>>> Thanks,
>>>>
>>>>   -k.
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20151117/63841794/attachment.html>