Allow unique configuration for each compute resource #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE Minor changes to the config schema. DisableSimultaneousMultithreading has move to the InstanceConfig section so that it can be set per compute resource.
Right UseOnDemand, UseSpot, and DisableSimultaneousMultithreading are global parameters affect all instance types.
Add new configuration option to use the existing parameters as defaults for each instance type, but allow them to be configured for each included instance family and each included instance type.
This allows admins to reduce the number of compute resources by, for example, only configuring spot for small instance types, but not for larger ones.
Resolves #277
Add documentation of manual commands for deconfiguring before deleting cluster.
Resolves #282
=========================================================================
Go through everything and change the original term I used, Submitter, to External Login Node. Just need to make things consistent.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.