Thanks for the info. Could this be put on the docket for the next
update? In the meantime we can work around it.
-Paul Edmon-
On 12/4/2012 3:17 PM, [email protected] wrote:
it would be pretty simple to add, but there is no mechanism to do this
today
--
Sent from my Android phone. Please excuse my brevity and typos.
Paul Edmon <[email protected]> wrote:
We've been testing SLURM to use on our cluster and we ran into a bit of
a snag with srun. Our test slurmctld is on a different network and
behind a firewall and thus didn't have all ports open. We didn't
realize that srun picked random high number port to do its
communications over when it ran other than the port defined in slurm.conf.
Is there a way to limit the range of ports that srun can pick for this?
That way we could put a blanket ACL in place for it. I know that the
preferred method is to have the master on the same network as everything
else but we intend to use SLURM in a complex environment with compute
nodes spread over multiple data centers and networks. So it would be
good to be able to do some fine control on what ports it uses.
-Paul Edmon-
