[email protected] writes:
> How do I get another slurmctld running for the test cluster?
You just need to point the slurmctld at a different slurm.conf
that uses a different port for slurmctld and slurmd. Then point
slurmd and all slurm commands to this new slurm.conf. If you
are running out of a build directory or alternate path, you
may also need to update PluginDir or other directories (perhaps
epilog and prolog location as well, you decide for your testing)
I used to have a script that would "boot" a test slurm instance
as a SLURM job, but that script doesn't work anymore with
recent versions of SLURM (however, there really wasn't much
to it)
mark
> Howard Gieselman
>
> -----Original Message-----
> From: Mark A. Grondona [mailto:[email protected]]
> Sent: Thursday, July 12, 2012 12:20 PM
> To: slurm-dev
> Subject: [slurm-dev] Re: Setting up a test cluster
>
>
> Moe Jette <[email protected]> writes:
>
>
>
>> Quoting [email protected]:
>
>>
>
>>> I have SLURM 2.3.3 installed and running in production but have found
>
>>> that I need to do some more testing and tweaking before I can migrate
>
>>> all of our LSF jobs to SLURM. I would like to install a test cluster but
>
>>> am unsure about the following:
>
>>>
>
>>>
>
>>>
>
>>> 1. Will I need to install the test cluster on a separate
>
>>> controller or is it enough that I just install it to a different path
>
>>> and use different port numbers?
>
>>
>
>> Different paths and ports are sufficient.
>
>>
>
>>
>
>>> 2. Can I use existing nodes from my production cluster in the test
>
>>> cluster?
>
>>
>
>> Yes.
>
>>
>
>>
>
>>> 3. Are there any other things to look out for in running a
>
>>> parallel cluster?
>
>>
>
>> On pretty much all system types you will just over-subscribe resources.
>
>
>
> Also, be sure to audit your epilog and prolog scripts to make sure
>
> they won't cause harm when running in parallel with another SLURM
>
> instance. Be careful if you are using SLURM cgroups support, as cgroups
>
> created for each parallel instance of SLURM will exist in the same
>
> namespace, and that may cause unexpected issues.
>
>
>
> mark
>
>
>
>
>
>>
>
>>>
>
>>> Thanks,
>
>>>
>
>>>
>
>>>
>
>>> Howard Gieselman
>
>>>
>
>>>
