The params.json file includes flags and parameters that determine various conditions in the testing and validation process.

The params.json file is passed as a parameter when boot.py is run.
Note: You must download the params.json file from the S3 repository.

The following table describes the flags and keys that are used in the params.json file.

Table 1. Flags and Keys Used in params.json
Flag/Key Values and Description
rc Determines whether the bits must be pushed to production or not.
  • true - Do not promote the bits to production. Bits pushed to test?
  • false - Promote the bits to production
stage Determines what has to be run in the Master Orchestrator (MO) pipeline.
  • setup - Set up Stage-1 and do not trigger the MO.
  • first - Run only Stage-1 and do not trigger Stage-2.
  • both - Run both Stage-1 and Stage-2
prom Determines the components or bundle that must be promoted to production.
  • sddc
  • cp
Note: Include sddc=n and cp=m if you want to specify the bundle version of the SDDC and the Cloud Provider (CP) product version to be used for testing and acceptance.
stop_on_error Defines if Master Orchestrator (MO) execution must stop on error or not.
  • true - Stop MO on error.
  • false - Continue the process and publish the results in the end.
sp_type Identify VCPS Service Provider
stage_bringup_current_enabled Run bring-up LCM flow in MO if set to true
stage_add_host_enabled Run Add Host LCM flow in MO if set to true
stage_remove_host_enabled Run Remove Host LCM flow in MO if set to true
nfs_enabled Enable the NFS-datastore feature in all LCM flows in MO if set to true
stage_add_cluster_enabled Run Add Cluster LCM flow in MO if set to true
stage_remove_cluster_enabled Run Remove Cluster LCM flow in MO if set to true
uuid Unique ID for each MO run in a particular stage. For example, "STAGE1-001" or "STAGE2-001"
hcx_service_mesh_creation_enabled Create HCX Service Mesh in MO if set to true
hcx_service_mesh_deletion_enabled Delete HCX Service Mesh in MO if set to true
is_resume_previous_run_enabled Resume the flow on previously fetched Hosts for dynamic Host Service if set to true
stage_release_hosts_enabled Release hosts after all LCM flows are run in MO for dynamic Host Service if set to true

params.json File to Trigger Stage-1

The value of stage is set to first in this example, which means only Stage-1 will be triggered. Set this value to both to trigger Stage-2.

{
 
    "root_manifest_url_current": "s3://vcps-rtm/REL_1_1_0_0/root-manifest.json",
 
    "rc" : "true",
 
    "stage" : "first",
 
    "stop_on_error" : "true",
 
    "prom" : "[sddc, cp]",
 
    "sp_type": "0",
 
    "stage_bringup_current_enabled" : "true",
 
    "stage_add_host_enabled" : "false",
 
    "add_host_spec_path" : "/data/vcps/host_spec.json",
 
    "add_host_cluster_name" : "MGMT_CLU",
 
    "stage_remove_host_enabled" : "false",
 
    "remove_host_spec_path" : "/data/vcps/host_spec.json",
 
    "remove_host_name" : "esx123.lab.xxx",
 
    "stage_patch_enabled" : "false",
 
    "stage_bringup_previous_enabled" : "false",
 
    "nfs_enabled" : "false",
 
    "add_cluster_spec_path" : "/data/vcps/add_cluster_spec.json",
 
    "remove_cluster_spec_path": "/data/vcps/remove_cluster_spec.json",
 
    "remove_cluster_name" : "SEC_CLU",
 
    "stage_add_cluster_enabled" : "false",
 
    "stage_remove_cluster_enabled" : "true",

    "uuid": "CI-ENV-157",

    "hcx_service_mesh_creation_enabled": "false",

    "hcx_service_mesh_deletion_enabled": "false",

     "rbac_enabled": "false",
    
     "um_enabled": "false",

     "um_unregister": "false"
 
}