MTV Scale scripts were updated to allow for defining scenarios inside yaml file.

Specifically MTV/config/tests.yaml describes the test scenario and relevant variables that can be run for example:
scenarios:- name: dsl-4-smalltestcase: 1.0VMsPrefix: dsl-4g-thick-fc-vm # VMsPrefixtotal_vms: 4 # total_vmsMigrationType: coldPlanMigrationName: dsl-4-small-planTargetMigrationNS: dsl-4-smallSourceMTVns: openshift-mtvVDDKURL: quay.io/qiyuan1/test7provider:url: https://rhev-node-13.rdu2.scalelab.redhat.com/sdkname: vsphere-7.0.3-1

• name: windows-sanity
  testcase: 1.2
  VMsPrefix: win2019-55gb-70usage-vm # VMsPrefix
  total_vms: 2 # total_vms
  MigrationType: cold
  PlanMigrationName: windows-sanity
  TargetMigrationNS: windows-sanity
  SourceMTVns: openshift-mtv
  VDDKURL: quay.io/qiyuan1/test7
  provider:
  url: https://rhev-node-13.rdu2.scalelab.redhat.com/sdk
  name: vsphere-7.0.3-1
  Currently the scenarios described are simple cases to test the actual automation.

This file needs to be updated in order to run appropriate regression cases.

After this file is updated, select cases can be run to populate the elastic results