This change enables the use of flavors when doing the provisioning. For now, two flavors are supported, m1.medium and m1.large, as these make sense at the moment. However, additional flavors can be added as needed.
* _NOTE:_ * The default flavor is now set to "m1.medium" - i.e.: a change from the m1.large as used before.
A separate PR will be submitted to update the d1/p1 configuration files.
How should this be manually tested?
Run a normal provisioning, i.e.: "./osc-provision --num-nodes=2 --key="
To test running a different flavor, set the "CONF_OS_FLAVOR" in a configuration file and use the --config command line option to run the provisioning, i.e.: "./osc-provision --num-nodes=2 --key= --config="
What does this PR do?
This change enables the use of flavors when doing the provisioning. For now, two flavors are supported, m1.medium and m1.large, as these make sense at the moment. However, additional flavors can be added as needed. * _NOTE:_ * The default flavor is now set to "m1.medium" - i.e.: a change from the m1.large as used before.
A separate PR will be submitted to update the d1/p1 configuration files.
How should this be manually tested?
Run a normal provisioning, i.e.: "./osc-provision --num-nodes=2 --key="
To test running a different flavor, set the "CONF_OS_FLAVOR" in a configuration file and use the --config command line option to run the provisioning, i.e.: "./osc-provision --num-nodes=2 --key= --config="
Is there a relevant Issue open for this?
N/A
Who would you like to review this?
/cc @etsauer