# Basic confusion about cluster config

**URL:** <https://discourse.openondemand.org/t/basic-confusion-about-cluster-config/2670>\
**Category:** Get Help\
**Tags:** question\
**Created:** [April 27, 2023, 6:28pm UTC](https://discourse.openondemand.org/t/basic-confusion-about-cluster-config/2670 "2023-04-27T18:28:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dtenenba](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/dtenenba/32/1075_2.png) [@dtenenba](https://discourse.openondemand.org/u/dtenenba)\
**Post date:** [April 27, 2023, 6:28pm UTC](https://discourse.openondemand.org/t/basic-confusion-about-cluster-config/2670/1 "2023-04-27T18:28:33Z")

</div>

Hi all,

I think I am misunderstanding something basic. I thought that if I specified a section like this in my cluster config:

```auto
v2:
  ...
  login:
    host: "login_node_name.my.org"

```

…that OOD would ssh to that node to submit cluster jobs and run other cluster-related binaries. But when I try it I get an error that the sbatch binary is not found (it’s there on the login node, but not on my web node (yet)).

So it seems that if I really want to ssh to the head/login node I need to set up bin\_overrides.

OK. But that leaves me to wonder what the `login` section is for. We run slurm here and as long as you are on a head node you don’t need to know the names of any other nodes, you can submit a job via the command line with `sbatch`.

So I am wondering what the `login/host` section is for. Maybe other schedulers work differently and require it?

Just a note about how I am setting things up - at the moment I am just putting together some ansible code to set up the web host (and I see there are ansible roles to set up cluster configs, that is awesome). Currently the web host does not have slurm installed but eventually it will. In the meantime I plan to use bin\_overrides just for the few of us who are testing this out. I realize that using an ssh wrapper in a bin\_overrides script is not really ideal for a production scenario because we can’t guarantee that every user will have passwordless ssh access to the login node.

BTW, what threw me off was step 2 [here](https://osc.github.io/ood-documentation/latest/installation/add-cluster-config.html#cluster-configuration). It seemed to imply (to me anyway) that OOD would ssh to this node to kick off jobs.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [April 27, 2023, 7:29pm UTC](https://discourse.openondemand.org/t/basic-confusion-about-cluster-config/2670/2 "2023-04-27T19:29:20Z")

</div>

> [@dtenenba](#):
>
> So I am wondering what the `login/host` section is for. Maybe other schedulers work differently and require it?

It is for the shell app. The host listed here will be the host you shell into in the `Clusters` menu.

Instead of `bin_overrides`, I believe you can supply a `submit_host` instead. That may be easier.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [October 24, 2023, 7:29pm UTC](https://discourse.openondemand.org/t/basic-confusion-about-cluster-config/2670/3 "2023-10-24T19:29:59Z")

</div>

Closed on October 24, 2023, 7:29pm UTC

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.