Upgrading host factory configuration after a rolling upgrade from IBM Spectrum Symphony 7.3

Follow this topic only if you used host factory with IBM® Spectrum Symphony Advanced Edition in IBM Spectrum Symphony 7.3. After you have performed a rolling upgrade from version 7.3 to 7.3.2, additionally complete these manual upgrade steps so that you can continue to use host factory with IBM Spectrum Symphony 7.3.2.

Before you begin

Ensure that all cloud hosts provisioned using host factory are returned; and that active cloud provisioning, or return requests, do not take place as you perform these post-upgrade steps for host factory.
This topic guides you to configure IBM Spectrum Symphony 7.3.2 to use host factory as you did with IBM Spectrum Symphony 7.3. It assumes you successfully completed the rolling upgrade prerequisites and process in Before you perform a rolling upgrade and Performing a rolling upgrade to IBM Spectrum Symphony.

Note: The host factory database (hf.db) located in $EGO_CONFDIR/../../eservice/hostfactory/db/ used with IBM Spectrum Symphony 7.3 will not be migrated; instead, after a rolling upgrade to IBM Spectrum Symphony 7.3.2, host factory uses a new hf.db database located at:

%EGO_CONFIDIR%\..\..\hostfactory\db\ on Windows.
$EGO_CONFDIR/../../hostfactory/db/ on Linux®.

Procedure

Update the HostFactory service configuration:
1. Back up the IBM Spectrum Symphony 7.3.2 HostFactory service configuration file:
  - %EGO_CONFDIR%\..\..\hostfactory\conf\hostfactoryconf.json on Windows
  - $EGO_CONFDIR/../../hostfactory/conf/hostfactoryconf.json on Linux
  as hostfactoryconf.json.732, as follows:
  - On Windows:
    copy %EGO_CONFDIR%\..\..\hostfactory\conf\hostfactoryconf.json %EGO_CONFDIR%\..\..\hostfactory\conf\hostfactoryconf.json.732
  - On Linux:
    cp $EGO_CONFDIR/../../hostfactory/conf/hostfactoryconf.json $EGO_CONFDIR/../../hostfactory/conf/hostfactoryconf.json.732
2. Copy your IBM Spectrum Symphony 7.3 hostfactoryconf.json configuration file to the location of the 7.3.2 HostFactory service configuration, as follows:
  - On Windows:
```
copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\hostfactoryconf.json %EGO_CONFDIR%\..\..\hostfactory\conf\
```
  - On Linux:
```
cp $EGO_CONFDIR/../../eservice/hostfactory/conf/hostfactoryconf.json $EGO_CONFDIR/../../hostfactory/conf
```
3. Add the following two parameters to the IBM Spectrum Symphony 7.3.2 hostfactoryconf.json file and save your changes:
```
"HF_LOG_MAX_FILE_SIZE": 10,
"HF_LOG_MAX_ROTATE": 5,
```

Update your registered providers for host factory:

Back up the IBM Spectrum Symphony 7.3.2 providers configuration file:

%EGO_CONFDIR%\..\..\hostfactory\conf\providers/hostProviders.json on Windows
$EGO_CONFDIR/../../hostfactory/conf/providers/hostProviders.json on Linux

as hostProviders.json.732, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\hostfactory\conf\providers\hostProviders.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\hostProviders.json.732

On Linux:

cp $EGO_CONFDIR/../../hostfactory/conf/providers/hostProviders.json $EGO_CONFDIR/../../hostfactory/conf/providers/hostProviders.json.732

If you disabled providers in the IBM Spectrum Symphony 7.3 hostProviders.json file, by setting "enabled": 0, in the file, then disable the corresponding provider instance in the version 7.3.2 hostProviders.json file, under the %EGO_CONFDIR%\..\..\hostfactory\conf\providers\ (on Windows), or $EGO_CONFDIR/../../hostfactory/conf/providers/ (on Linux), directory.

For example, if you disabled ibmcloud by setting "enabled" : 0, in the version 7.3 hostProviders.json file, then also disable the corresponding provider instance ibmcloudinst in the version 7.3.2 hostProviders.json file.

Update provider configuration:

Copy and rename the provider configuration file:

Amazon Web Services (AWS)

Copy and rename the IBM Spectrum Symphony 7.3 awsprov_config.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\aws\conf\awsprov_config.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\awsinst\awsinstprov_config.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/aws/conf/awsprov_config.json $EGO_CONFDIR/../../hostfactory/conf/providers/awsinst/awsinstprov_config.json

IBM Cloud

Copy and rename the IBM Spectrum Symphony 7.3 softlayerprov_config.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\softlayer\conf\softlayerprov_config.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\ibmcloudinst\ibmcloudinstprov_config.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/softlayer/conf/softlayerprov_config.json $EGO_CONFDIR/../../hostfactory/conf/providers/ibmcloudinst/ibmcloudinstprov_config.json

Microsoft Azure (Azure)

Copy and rename the IBM Spectrum Symphony 7.3 azureprov_config.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\azure\conf\azureprov_config.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\azureinst\azureinstprov_config.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/azure/conf/azureprov_config.json $EGO_CONFDIR/../../hostfactory/conf/providers/azureinst/azureinstprov_config.json

(For AWS providers only) Add the following four parameters to your AWS provider configuration file for host factory:
```
"AWS_REQUEST_RETRY_ATTEMPTS" : 0,
"AWS_DESCRIBE_REQUEST_RETRY_ATTEMPTS" : 0,
"AWS_INSTANCE_PENDING_TIMEOUT_SEC" : 180,
"AWS_DESCRIBE_REQUEST_INTERVAL" : 0,
```
For details about these parameters, and an example awsinstprov_config.json file with usage, see awsprov_config.json reference.

Copy and rename the provider template file:

AWS

Copy and rename the IBM Spectrum Symphony 7.3 awsprov_templates.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\aws\conf\awsprov_templates.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\awsinst\awsinstprov_templates.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/aws/conf/awsprov_templates.json $EGO_CONFDIR/../../hostfactory/conf/providers/awsinst/awsinstprov_templates.json

IBM Cloud

Copy and rename the IBM Spectrum Symphony 7.3 softlayerprov_templates.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\softlayer\conf\softlayerprov_templates.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\ibmcloudinst\ibmcloudinstprov_templates.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/softlayer/conf/softlayerprov_templates.json $EGO_CONFDIR/../../hostfactory/conf/providers/ibmcloudinst/ibmcloudinstprov_templates.json

Azure

Copy and rename the IBM Spectrum Symphony 7.3 azureprov_templates.json file, as follows:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\azure\conf\azureprov_templates.json %EGO_CONFDIR%\..\..\hostfactory\conf\providers\azureinst\azureinstprov_templates.json

On Linux:

cp $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/azure/conf/azureprov_templates.json $EGO_CONFDIR/../../hostfactory/conf/providers/azureinst/azureinstprov_templates.json

Add the following configuration to each template in this file:

"rank": ["Numeric", "0"],
"priceInfo": ["String", "price:0.1,billingTimeUnitType:prorated_hour,billingTimeUnitNumber:1,billingRoundoffType:unit"]

Update your registered requestors for host factory:
1. Back up the IBM Spectrum Symphony 7.3.2 requestors configuration file:
  - %EGO_CONFDIR\..\..\hostfactory\conf\requestors\hostRequestors.json on Windows
  - $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json on Linux
  as hostRequestors.json.732, as follows:
  - On Windows:
    copy %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\hostRequestors.json %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\hostRequestors.json.732
  - On Linux:
    cp $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json.732
2. If you enabled requestors in your IBM Spectrum Symphony 7.3 hostRequestors.jsons file, by setting "enabled": 1, in the file, then enable the corresponding requestor instance in the version 7.3.2 hostRequestors.json file, under the %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\ (on Windows), or $EGO_CONFDIR/../../hostfactory/conf/requestors/ (on Linux), directory.
  
  For example, if you enabled symA by setting "enabled" : 1, in the version 7.3 hostRequestors.json file, then also enable the corresponding requestor instance symAinst in the version 7.3.2 hostRequestors.json file.
3. For each requestor in the requestors JSON array in your IBM Spectrum Symphony 7.3 hostProviders.json file, if you updated the providers field to add or remove one or more providers (aws, ibmcloud, or azure), then update the providers field in the version 7.3.2 hostRequestors.json file, under the %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\ (on Windows), or $EGO_CONFDIR/../../hostfactory/conf/requestors/ (on Linux) directory, to add or remove the corresponding provider instances (awsinst, ibmcloudinst, or azureinst).
4. Copy and rename the configuration files for the built-in symA requestor:
  1. Copy and rename the symAreq_config.json file, as follows:
    - On Windows:
      copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\symA\conf\symAreq_config.json %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\symAinst\symAinstreq_config.json
    - On Linux:
      cp $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/symA/conf/symAreq_config.json $EGO_CONFDIR/../../hostfactory/conf/requestors/symAinst/symAinstreq_config.json
  2. Copy and rename the symAreq_policy_config.json file, as follows:
    - On Windows:
      copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\symA\conf\symAreq_policy_config.json %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\symAinst\symAinstreq_policy_config.json
    - On Linux:
      cp $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/symA/conf/symAreq_policy_config.json $EGO_CONFDIR/../../hostfactory/conf/requestors/symAinst/symAinstreq_policy_config.json
If you created multiple requestors based on the built-in symA requestor plug-in with IBM Spectrum Symphony 7.3, check the requestors JSON array in the version 7.3 requestors configuration file:
- %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\hostRequestors.json on Windows
- $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/hostRequestors.json on Linux
Look for any requestors that are in addition to symA, cws, or admin requestors. If there are additional requestors present that is based on the symA configuration (for example, a symB requestor), then complete the following steps for each additional requestor (otherwise, if there are no additional requestors, then skip this step):
1. Create a directory for this requestor. The directory name should be the same as the requestor name:
  - On Windows:
```
md %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\requestor_name
```
  - On Linux:
```
mkdir $EGO_CONFDIR/../../hostfactory/conf/requestors/requestor_name
```
  For example, if the requestor name is symB:
  - On Windows:
    md %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\symB
  - On Linux:
    mkdir $EGO_CONFDIR/../../hostfactory/conf/requestors/symB
2. Copy the configuration files of this requestor to the new requestor directory:
  - On Windows:
```
copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\requestor_name\conf\*.* %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\requestor_name\
```
  - On Linux:
```
cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/requestor_name/conf/*  $EGO_CONFDIR/../../hostfactory/conf/requestors/requestor_name/
```
  For example, if the requestor name is symB:
  - On Windows:
    copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\symB\conf\*.* %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\symB\
  - On Linux:
    cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/symB/conf/* $EGO_CONFDIR/../../hostfactory/conf/requestors/symB/
3. Edit the IBM Spectrum Symphony 7.3.2 requestors configuration file:
  - %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\hostRequestors.json on Windows
  - $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json on Linux
  Create a requestor instance item in the requestors JSON array. Create this item based on the configuration of this requestor in the version 7.3 hostRequestors.json file, and specify the following information in the version 7.3.2 file:
  - Update the configuration to enable or disable the requestor instance (to enable, specify "enabled": 1,; to disable, specify "enabled": 0,.
  - Update the providers array to add the corresponding provider instances (specify "providers": ["awsinst"], for aws, specify "providers": ["ibmcloudinst"], for ibmcloud, or specify "providers": ["azureinst"], for azure).
  For example, this requestors JSON array is configured to enable the requestor instance for an AWS provider for the symB requestor provider:
```
{
            "name": "symB",
            "enabled": 1,
            "plugin": "symB",
            "confPath": "${HF_CONFDIR}/requestors/symB/",
            "workPath": "${HF_WORKDIR}/requestors/symB/",
            "logPath": "${HF_LOGDIR}/",
            "providers": ["awsinst"],
            "requestMode": "POLL",
            "resourceRequestParameters": {
                "hostSelectionPolicy": "rank",
                "typicalHostRetentionTimeMinutes": 43200,
                "fulfillmentType": "partial"
            }
        },
```
If you created multiple providers based on an existing AWS provider with IBM Spectrum Symphony 7.3, check the providers JSON array in the version 7.3 host providers configuration file:
- %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\hostProviders.json on Windows
- $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/hostProviders.json on Linux
Look for any providers in addition to aws, ibmcloud, or azure. If there are additional providers present that are based on the aws configuration (for example, aws1 and aws2 providers), then complete the following steps for each additional provider (otherwise, if there are no additional providers, then skip this step):
1. Create a directory for this provider. The directory name should be the same as the provider name:
  - On Windows:
```
md %EGO_CONFDIR%\..\..\hostfactory\conf\providers\provider_name
```
  - On Linux:
```
mkdir $EGO_CONFDIR/../../hostfactory/conf/providers/provider_name
```
  For example, if the provider name is aws1:
  - On Windows:
    md %EGO_CONFDIR%\..\..\hostfactory\conf\providers\aws1
  - On Linux:
    mkdir $EGO_CONFDIR/../../hostfactory/conf/providers/aws1
2. Copy the configuration files of this provider to the new provider directory:
  - On Windows:
```
copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\provider_name\conf\ $%EGO_CONFDIR%\..\..\hostfactory\conf\providers\provider_name\*.*
```
  - On Linux:
```
cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/provider_name/conf/ $EGO_CONFDIR/../../hostfactory/conf/providers/provider_name/*
```
  For example, if the provider name is aws1:
  - On Windows:
    copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\aws1\conf\*.* %EGO_CONFDIR%\..\..\hostfactory\conf\providers\aws1\
  - On Linux:
    cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/aws1/conf/* $EGO_CONFDIR/../../hostfactory/conf/providers/aws1/
3. Rename the IBM Spectrum Symphony 7.3.2 configuration files that contain the prefix aws, to use a prefix of provider_name. The files to rename are in:
  - On Windows:
```
%EGO_CONFDIR%/../../hostfactory/conf/providers/provider_name
```
  - On Linux:
```
$EGO_CONFDIR/../../hostfactory/conf/providers/provider_name
```
  For example, if provider_name is aws1, then rename the awsprov_conf.json configuration file to aws1prov_conf.json; similarly, rename the awsprov_templates.json file to aws1prov_templates.json:
  - On Windows:
    ren %EGO_CONFDIR%\..\..\hostfactory\conf\providers\aws1\awsprov_config.json aws1prov_config.json ren %EGO_CONFDIR%\..\..\hostfactory\conf\providers\aws1\awsprov_templates.json aws1prov_templates.json
  - On Linux:
    mv $EGO_CONFDIR/../../hostfactory/conf/providers/aws1/awsprov_conf.json $EGO_CONFDIR/../../hostfactory/conf/providers/aws1/aws1prov_config.json mv $EGO_CONFDIR/../../hostfactory/conf/providers/aws1/awsprov_templates.json $EGO_CONFDIR/../../hostfactory/conf/providers/aws1/aws1prov_templates.json
4. Edit the IBM Spectrum Symphony 7.3.2 host providers configuration file:
  - %EGO_CONFDIR\..\..\hostfactory\conf\providers\hostProviders.json on Windows
  - $EGO_CONFDIR/../../hostfactory/conf/providers/hostProviders.json on Linux
  Create a provider instance item in the providers JSON array. Create this item based on the configuration of this provider in the version 7.3 hostProviders.json file, and specify the following information in the version 7.3.2 file:
```
{
            "name": "provider_name",
            "enabled": 1,
            "plugin": "aws",
            "confPath": "${HF_CONFDIR}/providers/provider_name/",
            "workPath": "${HF_WORKDIR}/providers/provider_name/",
            "logPath": "${HF_LOGDIR}/"
        },
```
  For example, this providers JSON array is configured to enable the requestor instance for an AWS provider called aws1:
```
{
            "name": "aws1",
            "enabled": 1,
            "plugin": "aws",
            "confPath": "${HF_CONFDIR}/providers/aws1/",
            "workPath": "${HF_WORKDIR}/providers/aws1/",
            "logPath": "${HF_LOGDIR}/"
        },
```
5. For each requestor in the %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\hostRequestors.json (on Windows), or $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/hostRequestors.json (on Linux) file, verify that the provider_name is included in the providers JSON array.
  Update the corresponding requestor instance in the %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\hostRequestors.json (on Windows), or $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json (on Linux) file to specify the provider_name in the providers JSON array.
  For example, to configure requestor instance symB to use the added custom provider instance aws1, set:
```
{
            "name": symB,
            "enabled": 1,
            "providers": ["awsinst","aws1"],
            "requestMode": "POLL",
            "resourceRequestParameters": {
                "hostSelectionPolicy": "rank",
                "typicalHostRetentionTimeMinutes": 43200,
                "fulfillmentType": "partial"
            }
        },
```

If you created a custom provider plug-in with IBM Spectrum Symphony 7.3, identify the custom provider plug-in registered in the host providers configuration file:

%EGO_CONFDIR\..\..\eservice\hostfactory\conf\providers\hostProviders.json on Windows
$EGO_CONFDIR/../../eservice/hostfactory/conf/providers/hostProviders.json on Linux

A custom provider plug-in is one that does not include aws, ibmcloud, azure, or any provider based on aws (that is, with "vendor":"aws"). If there are custom providers present, then complete the following steps for each custom provider (otherwise, if there are no custom providers, then skip this step):

Copy the libraries and scripts associated with your custom provider:

On Windows:

copy Installation_top\EGO_version\hostfactory\providers\custom_provider_name Installation_top\hostfactory\1.2\providerplugins\

On Linux:

cp -rf $EGO_TOP/EGO_version/hostfactory/providers/custom_provider_name $EGO_TOP/hostfactory/1.2/providerplugins/

For example, if the custom provider name is abccloud:

On Windows:

copy Installation_top\EGO_version\hostfactory\providers\abccloud Installation_top\hostfactory\1.2\providerplugins\

On Linux:

cp -rf $EGO_TOP/EGO_version/hostfactory/providers/abccloud $EGO_TOP/hostfactory/1.2/providerplugins/

Edit the IBM Spectrum Symphony 7.3.2 host providers plug-ins configuration file:

%EGO_CONFDIR\..\..\hostfactory\conf\providerplugins\hostProviderPlugins.json on Windows
$EGO_CONFDIR/../../hostfactory/conf/providerplugins/hostProviderPlugins.json on Linux

{
            "name": "custom_provider_name",
            "enabled": 1,
            "scriptPath": "${HF_TOP}/${HF_VERSION}/providerplugins/custom_provider_name/scripts/"
            },

For example, if your custom provider is abccloud:

{
            "name": "abccloud",
            "enabled": 1,
            "scriptPath": "${HF_TOP}/${HF_VERSION}/providerplugins/abccloud/scripts/"
            },

Edit the IBM Spectrum Symphony 7.3.2 host providers configuration file:

%EGO_CONFDIR\..\..\hostfactory\conf\providers\hostProviders.json on Windows
$EGO_CONFDIR/../../hostfactory/conf/providers/hostProviders.json on Linux

{
            "name": "custom_provider_name",
            "enabled": 1,
            "plugin": "custom_provider_name",
            "confPath": "${HF_CONFDIR}/providers/custom_provider_name/",
            "workPath": "${HF_WORKDIR}/providers/custom_provider_name/",
            "logPath": "${HF_LOGDIR}/"
           },

For example, if your custom provider is abccloud:

{
            "name": "abccloud",
            "enabled": 1,
            "plugin": "abccloud",
            "confPath": "${HF_CONFDIR}/providers/abccloud/",
            "workPath": "${HF_WORKDIR}/providers/abccloud/",
            "logPath": "${HF_LOGDIR}/"
           },

Copy the configuration files for the custom provider:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\custom_provider_name\conf\*.* %EGO_CONFDIR%\..\..\hostfactory\conf\providers\custom_provider_name\

On Linux:

cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/custom_provider_name/conf/* $EGO_CONFDIR/../../hostfactory/conf/providers/custom_provider_name/

For example, if your custom provider is abccloud:

On Windows:

copy %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\providers\abccloud\conf\*.* %EGO_CONFDIR%\..\..\hostfactory\conf\providers\abccloud\

On Linux:

cp -rf $EGO_CONFDIR/../../eservice/hostfactory/conf/providers/abccloud/conf/* $EGO_CONFDIR/../../hostfactory/conf/providers/abccloud/

For each custom requestor in the %EGO_CONFDIR%\..\..\eservice\hostfactory\conf\requestors\hostRequestors.json (on Windows), or $EGO_CONFDIR/../../eservice/hostfactory/conf/requestors/hostRequestors.json (on Linux) file, verify that the custom_provider_name is included in the providers JSON array.
Update the corresponding requestor instance in the %EGO_CONFDIR%\..\..\hostfactory\conf\requestors\hostRequestors.json (on Windows), or $EGO_CONFDIR/../../hostfactory/conf/requestors/hostRequestors.json (on Linux) file directory to specify the custom_provider_name in the providers JSON array.
For example, to configure requestor instance symB to use the added custom provider instance abccloud, set:
```
{
            "name": symB,
            "enabled": 1,
            "providers": ["awsinst","abccloud"],
            "requestMode": "POLL",
            "resourceRequestParameters": {
                "hostSelectionPolicy": "rank",
                "typicalHostRetentionTimeMinutes": 43200,
                "fulfillmentType": "partial"
            }
        },
```

IBM Spectrum Symphony 7.3.2 Advanced Edition on Linux x86 64-bit supports IBM Cloud Gen 2 as cloud provider for your cluster. If you plan to use IBM Cloud Gen 2 with host factory in IBM Spectrum Symphony 7.3.2, configure your cluster for IBM Cloud Gen 2:
1. Enable the IBM Cloud Gen 2 provider plug-in as a cloud provider for your cluster:
  1. Open the hostProviderPlugins.json file file in a text editor: $EGO_CONFDIR/../../hostfactory/conf/providerplugins/hostProviderPlugins.json.
  2. Add the IBM Cloud Gen 2 provider plug-in name (ibmcloudgen2), set it to enabled, and provide the IBM Spectrum Symphony 7.3.2 script path:
```
{
"name": "ibmcloudgen2",
"enabled": 0,
"scriptPath": "${HF_TOP}/${HF_VERSION}/providerplugins/ibmcloudgen2/scripts/"
}
```
2. Enable the IBM Cloud Gen 2 provider:
  1. Open the hostProvider.json file in a text editor.
  2. Add the IBM Cloud Gen 2 provider name (ibmcloudgen2inst), set it to enabled, add the provider plug-in name (ibmcloudgen2), and provide the IBM Spectrum Symphony 7.3.2 configuration, work, and log paths:
```
{
"name": "ibmcloudgen2inst",
"enabled": 0,
"plugin": "ibmcloudgen2",
"confPath": "${HF_CONFDIR}/providers/ibmcloudgen2inst/",
"workPath": "${HF_WORKDIR}/providers/ibmcloudgen2inst/",
"logPath": "${HF_LOGDIR}/"
}
```

What to do next

Once you have completed these post-upgrade steps for host factory with IBM Spectrum Symphony 7.3.2, you can verify and test your rolling upgrade.