Skip to main content

Run a project on some nodes only

Every project runs on All: every enabled node of your organization. Jaah picks a node for each task as it starts, and a node you add later joins All by itself. There is nothing to set up.

To keep a project on some nodes only, such as the machines with a GPU or the ones your client paid for, put those nodes in a node group and give the project that group.

Plan: making node groups and giving them to projects is on the Business plan. On other plans every project runs on All, and a project's Node groups reads All.

Who can do this: making and changing a group needs the permission to edit nodes. Choosing a project's groups needs the org admin role and the permissions to create and delete projects.

What All is​

All is built in. It holds every enabled node of your organization and can't be edited or deleted. It leaves out:

  • Multi-Node Hosts, which run nodes rather than tasks.
  • A shared node your organization uses for Easy Mode. Easy Mode projects run there and only there.
  • Disabled nodes, until you enable them.

Make a group​

  1. In the sidebar, select Directory, then the Machines tab.
  2. Select the Groups tab. All is on top, with its number of nodes, then your groups.
  3. Select New group.
  4. Type a Name, and a Description if you want one.
  5. In Members, type a node's name and pick it. Pick as many as you need.
  6. Select Create.

To change a group later, or add a node to one from the node's side, see Change or delete a node group.

Give a project its groups​

  1. In the sidebar, select Directory, then the Projects tab.
  2. Select the project's name, then its Settings tab, section Nodes.
  3. In Node groups, pick a group. It replaces All, and the change applies at once, with no Save.
  4. Pick more groups if you need them. The project runs on any node in any of its groups.

New projects start on All, and the form to create a project doesn't ask.

A node in several groups​

A node may be in as many groups as you like. It runs the tasks of every project that has any of those groups, and of every project on All.

On the Nodes tab, set Group by to Group to see your nodes under each group. A node in two groups shows under both, and nodes in no group come last, under Not in a group.

Back to All​

To put a project back on All, remove its last group (the × on its chip). All comes back by itself.

Deleting a group does the same for every project that had only that group. Before it deletes, Jaah lists the projects that lose the group.

If your organization leaves the Business plan, its projects run on All again. Their groups are kept, and Node groups shows them as Not active on your plan; they apply again if the plan comes back.

What happens to running tasks​

Changing groups never stops a task. A task already running on a node that a change leaves out finishes there; the project's next tasks start on its new nodes. When a change would take nodes away from tasks that are running, Jaah asks first.

When a project's groups have no enabled node, its tasks wait and say why, for example: Waiting: no node in Website's node groups (GPU). Change them in Website's Node groups. Add a node to the group, enable one, or change the project's groups.

Where your organization lets tasks pick a node (Node on a task), the node must be one the project runs on, or the task is refused when you save it. If that node later leaves the project's groups, the task can't start there and says why.

Each task starts from a fresh copy​

Each task starts with a fresh copy of the project's repository on its node, made as the task starts, and the copy is removed when the task is done. On a large repository the first minutes of a task go to that copy.