[Paraview] Paraview client-Server

Berk Geveci berk.geveci at gmail.com
Thu Aug 10 13:10:04 EDT 2006


Only the first node has to be connected to the client. They talk to each
other with MPI.

On 8/10/06, Randall Hand <randall.hand at gmail.com> wrote:
>
> This, this is the tile cluster (plasma).
>
> We brought it up with our admins onsite, and they dont' think that setting
> up NAT would be any big problem, so they're looking into it now.  What we
> want to do is use the IceTDesktop render mode to parallel process across our
> 12 nodes with the display piped to a client (probably windows) that's not
> part of the cluster.  It was my understanding (and experience) that in this
> setup (mpirun -np 12 pvserver -rc) that each pvserver process will want an
> independent connection to the Client, which would require full network
> connectivity if it's any host other than the head node.
>
> AM I mistaken?
>
>
> On 8/10/06, Andy Cedilnik <andy.cedilnik at kitware.com> wrote:
> >
> > Hello,
> >
> > Actually, as far as I remember there is no need for connectivity from
> > satellite nodes. I am pretty sure Randal's setup does not use NAT, so
> > there is no way his satellite nodes can access Internet. Randal, this is
> >
> > the tile cluster?
> >
> > But, again, I see no reason for satellite nodes to access client. They
> > will try to access render server nodes if you do render/data server
> > separation.
> >
> >           Andy
> >
> > Wylie, Brian wrote:
> > > Sandia uses reverse connect on all of our cluster deployments.
> > >
> > > Even though you can't 'see' the cluster nodes from outside you can
> > > often 'see' the outside from a cluster node.
> > >
> > > If the cluster node cannot ping an external ip, than perhaps install
> > > NAT on the cluster?  (I'm a bit out of my area here.... but that's
> > > what our administrators have done if there was an issue).
> > >
> > > If you want I can forward your email to our cluster folks....
> > >
> > >   Brian Wylie - Org 1424
> > >   Sandia National Laboratories
> > >   MS 0822 - Building 880/A1-J
> > >   (505)844-2238 FAX(505)845-0833
> > >
> > >
> > >
> > >
> > ------------------------------------------------------------------------
> > >     *From:* paraview-bounces+bnwylie=sandia.gov at paraview.org
> > >     [mailto:paraview-bounces+bnwylie=sandia.gov at paraview.org ] *On
> > >     Behalf Of *Randall Hand
> > >     *Sent:* Wednesday, August 09, 2006 1:46 PM
> > >     *To:* Paraview List
> > >     *Subject:* [Paraview] Paraview client-Server
> > >
> > >     On our cluster, only the head node has true internet
> > >     connectivity.  The remaining cluster nodes are on an internal
> > >     network with no visibility except to each other & the head node.
> > >
> > >     In this configuration, is there any way to run Paraview in
> > >     Parallel-server mode to a client anywhere other than the head
> > >     node?  I would presume that there would need to be some kind of
> > >     Relay on the head node to make this happen.
> > >
> > >     This came up a few months ago with kitware, but I'm kinda curious
> > >     if anyone else out there has a different solution (/poke Bryan,
> > >     Kenneth, *@doe :) ).
> > >
> > >     --
> > >     ----------------------------------------
> > >     Randall Hand
> > >     Visualization Scientist
> > >     ERDC MSRC-ITL
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > ParaView mailing list
> > > ParaView at paraview.org
> > > http://www.paraview.org/mailman/listinfo/paraview
> > >
> >
> >
>
>
> --
> ----------------------------------------
>
> Randall Hand
> Visualization Scientist
> ERDC MSRC-ITL
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20060810/e0f6aaa1/attachment.htm


More information about the ParaView mailing list