Just to close loop on this.
This was not as Slurm issue it was more of AD configuration.
AD needs to be installed on all nodes of cluster that way SLURM knows the USER
ID. I had trouble with sssd DB folders missing and sssd.conf file having
appropriate permissions. So look put for those. You
Matthew, that deserves an explanation. Bright Computing Proof of Concept
causes nightmares?
That is a pretty strong assertion. Please give more details.
On Wed, 13 Feb 2019 at 16:01, Matthew BETTINGER <
matthew.bettin...@external.total.com> wrote:
> One of the main guy Panos left Bright so no ans
One of the main guy Panos left Bright so no answer to your specific question
but I hope you can get some support with it. We dumped our BC PoC, the
sysadmin working on the PoC still has nightmares.
On 2/13/19, 6:54 AM, "slurm-users on behalf of John Hearns"
wrote:
Yugendra, the Brigh
one method I've used a lot of times in bright is to integrate a compute
node in the same way as the master and logins (I normally use realm
join...) and then grab the changes back into to the image in cmsh, If you
are worried you can clone into a new image
Then you can make sure your compute nodes
Thanks Guys. I will go through all resources and report back how it goes.
Thanks,
Yugi
> On Feb 13, 2019, at 7:58 AM, John Hearns wrote:
>
> please have a look at section 6.3 of the Bright Admin Manual
> You have run updateprovisioners then rebooted the nodes?
>
>
> Configuring The Cluster To
please have a look at section 6.3 of the Bright Admin Manual
You have run updateprovisioners then rebooted the nodes?
Configuring The Cluster To Authenticate Against An External LDAP Server The
cluster can be configured in different ways to authenticate against an
external LDAP server. For smaller
Yugendra, the Bright support guys are excellent.
Slurm is their default choice. I would ask again. Yes, Slurm is technically
out of scope for them, but they shoudl help a bit.
By the way, I think your problem is that you have configured authentication
using AD on your head node.
BUT you have not
Can you ssh in as root and the su to the AD user to make sure that the node
is integrated correctly?
If you cannot su to an AD user on the node then Slurm will not be able to
resolve the UID either as they use the same methods.
On Wed, 13 Feb 2019, 12:35 Yugendra Guvvala,
wrote:
> No, we can’t
Yugendra Guvvala writes:
>> On Feb 13, 2019, at 1:50 AM, Loris Bennett
>> wrote:
>>
>> Yugendra Guvvala writes:
>>
>>> Hi,
>>>
>>> We are bringing a new cluster online. We installed SLURM through Bright
>>> Cluster Manager how ever we are running into a issue here.
>>>
>>> We are able
On 2/13/19 1:14 PM, Yugendra Guvvala wrote:
Thank you, this is strange. Is there a way to integrate AD authentication with
SLURM or Munge. Or allow all users who login to run jobs with out any
restrictions .
Integration of Slurm with LDAP accounts have been implemented at EPFL in
Switzerland
Also reached out to bright computing support and they say slurm is out of scope
for them.
Thanks,
Yugi
> On Feb 13, 2019, at 7:27 AM, Antony Cleave wrote:
>
> can you ssh to the compute node that job was trying to run on as as the AD
> user in question?
>
> I've seen similar issues on AD i
No, we can’t ssh to compute nodes. And this is by design that no one should be
able to ssh to compute nodes other than root.
I figure that munge is not configured for AD. We have configured our login
image for AD and slurm and mung configurations are on head node. Not sure how
to integrate the
can you ssh to the compute node that job was trying to run on as as the AD
user in question?
I've seen similar issues on AD integrated systems where some nodes boot
from a different image that have not yet been joined to the domain.
Antony
On Wed, 13 Feb 2019 at 04:58, Yugendra Guvvala <
yguvv.
Hi Loris,
Thank you, this is strange. Is there a way to integrate AD authentication with
SLURM or Munge. Or allow all users who login to run jobs with out any
restrictions .
Thanks,
Yugi
> On Feb 13, 2019, at 1:50 AM, Loris Bennett wrote:
>
> Yugendra Guvvala writes:
>
>> Hi,
>>
>> We ar
Yugendra Guvvala writes:
> Hi,
>
> We are bringing a new cluster online. We installed SLURM through Bright
> Cluster Manager how ever we are running into a issue here.
>
> We are able to run jobs as root user and users created using bright cluster
> (cmsh commands). How ever we use AD authent
15 matches
Mail list logo
