This, this is the tile cluster (plasma).<br><br>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.
<br><br>AM I mistaken?<br><br><div><span class="gmail_quote">On 8/10/06, <b class="gmail_sendername">Andy Cedilnik</b> <<a href="mailto:andy.cedilnik@kitware.com">andy.cedilnik@kitware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>Actually, as far as I remember there is no need for connectivity from<br>satellite nodes. I am pretty sure Randal's setup does not use NAT, so<br>there is no way his satellite nodes can access Internet. Randal, this is
<br>the tile cluster?<br><br>But, again, I see no reason for satellite nodes to access client. They<br>will try to access render server nodes if you do render/data server<br>separation.<br><br> Andy<br><br>Wylie, Brian wrote:
<br>> Sandia uses reverse connect on all of our cluster deployments.<br>><br>> Even though you can't 'see' the cluster nodes from outside you can<br>> often 'see' the outside from a cluster node.<br>><br>> If the cluster node cannot ping an external ip, than perhaps install
<br>> NAT on the cluster? (I'm a bit out of my area here.... but that's<br>> what our administrators have done if there was an issue).<br>><br>> If you want I can forward your email to our cluster folks....<br>
><br>> Brian Wylie - Org 1424<br>> Sandia National Laboratories<br>> MS 0822 - Building 880/A1-J<br>> (505)844-2238 FAX(505)845-0833<br>><br>><br>><br>> ------------------------------------------------------------------------
<br>> *From:* paraview-bounces+bnwylie=<a href="mailto:sandia.gov@paraview.org">sandia.gov@paraview.org</a><br>> [mailto:<a href="mailto:paraview-bounces+bnwylie=sandia.gov@paraview.org">paraview-bounces+bnwylie=sandia.gov@paraview.org
</a>] *On<br>> Behalf Of *Randall Hand<br>> *Sent:* Wednesday, August 09, 2006 1:46 PM<br>> *To:* Paraview List<br>> *Subject:* [Paraview] Paraview client-Server<br>><br>> On our cluster, only the head node has true internet
<br>> connectivity. The remaining cluster nodes are on an internal<br>> network with no visibility except to each other & the head node.<br>><br>> In this configuration, is there any way to run Paraview in
<br>> Parallel-server mode to a client anywhere other than the head<br>> node? I would presume that there would need to be some kind of<br>> Relay on the head node to make this happen.<br>><br>> This came up a few months ago with kitware, but I'm kinda curious
<br>> if anyone else out there has a different solution (/poke Bryan,<br>> Kenneth, *@doe :) ).<br>><br>> --<br>> ----------------------------------------<br>> Randall Hand<br>> Visualization Scientist
<br>> ERDC MSRC-ITL<br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> ParaView mailing list<br>> <a href="mailto:ParaView@paraview.org">
ParaView@paraview.org</a><br>> <a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a><br>><br><br></blockquote></div><br><br clear="all"><br>-- <br>----------------------------------------
<br>Randall Hand<br>Visualization Scientist<br>ERDC MSRC-ITL