Distinguish on-demand and spot instances in HostFactory under one application

Hi, Shruti,

Thanks for the explaination, this is not in consideration for now. You can schedule to provision on-demand nodes(not via the symA requestor dynaically) based on the prediction, and use the resource group with all these on-demand resources for the parent tasks. And child can use another resource group with spot.

Thanks, Dennis

Hi Dennis,

Thanks for your inputs. However, the ask here is to be able to request on_demand / spot hostfactory instances based on the parent / child task submission from single application. We followed the below steps provided by Adrian, however it has a constraint to request the on-demand / spot instances based on different applications and it's not helping to solve the purpose.

"I outlined the steps to create a new provider and a new requestor in order to make this use case work. If anything is unclear in the steps let me know. Please note that some of your confPath and scriptPath maybe different due to morganization. Use the paths that you have configured.

To create a provider based on the cws, the steps are given below:

1. Add a new provider inside hostProviders.json for example cws2

2. Change the confPath and scriptPath to be unique

{

"name": "aws2",

"enabled": 1,

"confPath": "${HF_CONFDIR}/providers/aws2/conf/",

"scriptPath": "${HF_TOP}/providers/aws2/scripts/"

},

1. Copy the configuration and scripts from aws into aws2

2. Change the awsprov_templates.json per your specification to use spot or on-demand instances

Create a new requestor per the steps below:

1. https://www.ibm.com/docs/en/spectrum-symphony/7.2.1?topic=bursting-creating-requestors-based-syma

2. Ensure that the new requestor will use aws2 as the provider under providers field"

Thanks,

Shruti

This could be done in Symphony 7.3.2

1. create "dedicated" resource group for on-demand nodes; define external resource attribute(https://www.ibm.com/docs/en/spectrum-symphony/7.3.2?topic=ca-how-do-i-define-external-resource-attributes-resource-requirements) for the on-demand servers and define the filter with the new resource attribute to create the specific resource group

2. In sessionTypes section, define resourceGroupFilter for parent and child task separately, only define the on-demand resource groups for parent task, not for child, and define "spot" resource group for child. Therefore, the parent tasks will only use on-demand nodes.

3. The backfill will not happen with such setting