Auto cores

[ashton22305]

Fixes #3680

Sets the minimum number of cores to 1 and the maximum number to the maximum available on a node.

Note: This will not cause the job to be submitted with the specified number of cores until ood_core accepts cores in script.

[johrstrom]

Instead of just setting the min and max blindly, we likely need to add directives so it's per cluster. For example at OSC the max for the owens cluster is 28 and for pitzer it's 48.

Though off the top - I'm not sure if we can achieve this here... Seems like we'd need to apply data-max-auto-cores: 28 to the cluster option itself, not here. So I'm not sure off the top how to solve for that.

[ashton22305]

Do we have any existing mechanism for attributes to affect/limit other attributes? If not, maybe setting the max for each cluster here (i.e. data-max-auto-cores-owens) and choosing which option to show on the front end could work?

[johrstrom]

Do we have any existing mechanism for attributes to affect/limit other attributes?

Sure, most things here relate to other things:

Here's auto_qos populating what accounts it's available for and so on.

ondemand/apps/dashboard/app/lib/account_cache.rb

Line 110 in 4b09edb

hash["data-option-for-auto-accounts-#{account}"] = false

If not, maybe setting the max for each cluster here

That's the issue. We can't set the max for each cluster here. All the other examples of relationships are between 2 select options. This being a number field - we can't really have the same thing.

I don't think there's anything to do here really. Seems we'll have to add it to add directives to auto_batch_clusters.

[johrstrom]

Yea I would say just set the min to 1 and forgo the max. Then we can fixup auto_batch_clusters in another PR.

[johrstrom]

Thanks! I'll create a follow up ticket to update auto_batch_clusters to set maxes.