Multiple Conductor Golden Configurations

Overview

Wind River Conductor supports separate golden configs for RDCs (Systems Controller) and sub-clouds. Dell Telecom Infrastructure Blocks (DTIB) WR supports separate golden config per platform type as necessary. For more information about using golden configurations, see Conductor Golden Configuration

There are four deployment_config templates created for this release for this feature as an example.

• rdc_deployment_config.yaml.v4.jinja2 (RDC template)
• duplex_subclouds_deployment_config.yaml.v4.jinja2 (duplex subcloud template)
• simplex_subclouds_deployment_config.yaml.v4.jinja2 (simplex subcloud template)
• deployment_config.yaml.v4.jinja2 (default that works for all system types)

Note: For old ciq files without embedded ciq files, deployment_config.yaml.v3.jinja2 should be used.

Using the deployment_config template

1. The deployment_config template (xx_deployment_config.yaml.v4.jinja2 files) must be present the master ciq files if the embedded ciq files are used.

   1. If deployment_config template is present in the master ciq file, the workflow will use this deployment_config template to install RDC or subclouds.

   Note: global_parameters - deployment_template only works in the ciq file with embedded ciq files. Otherwise, the workflow will be broken with exceptions.

   global_parameters:
   deployment_template: "xxx_deployment_config.yaml.v4.jinja2"
   

   2. If deployment_config template is NOT present in the master ciq file, the workflow will use the deployment_config template in the deployment inputs
   3. That means, deployment_config template must exist in either the inputs of creating deployment or in the master ciq files, or both places.

2. The following cases indicates NO valid deployment_config template is defined in the master ciq file. Thus, the default deployment_config template in the inputs when creating the deployment will be used.

case 1:
global_parameters doesn't exist
 
case 2:
global_parameters:
 
case 3:
global_parameters:
  deployment_template:
 
case 4:
global_parameters:
  deployment_template: ""
 
case 5:
global_parameters:
  deployment_template: "  "

3. Key logs:
   Searching the following key words from the workflow logs can help address what template is being used.
   1. For RDC, take a look at ‘provision_sysctl’ workflow log.
   2. For suclouds, take a look into subcloud ‘install’ log.

The following example uses the multiple configuration option:

For comparison, the example below uses the standard configuration:

For further information see Conductor Golden Configuration.