Describe the feature
There is a PR almost ready for review and merging to OpenCHAMI Release that contains changes that require new configuration of deploy-openchami. These changes need to be in place in order for vTDS based integration testing of OpenCHAMI to proceed. The changes are to set the default (base) configuration to take on these new settings:
coredhcp_named_parameters: true
use_boot_service: true
metadata_service: metadata-service
cloud_init_templating_disabled: false
gen_access_token_works: true
and record the settings in an example configuration overlay file to preserve a snapshot of the working configuration at this point in time.
Why do you want this feature?
This feature is needed to continue supporting OpenCHAMI Release integration testing via vTDS deployment.
Alternatives you've considered
There is really no alternative here.
Additional context
No response
Code of Conduct
Describe the feature
There is a PR almost ready for review and merging to OpenCHAMI Release that contains changes that require new configuration of deploy-openchami. These changes need to be in place in order for vTDS based integration testing of OpenCHAMI to proceed. The changes are to set the default (base) configuration to take on these new settings:
coredhcp_named_parameters: true
use_boot_service: true
metadata_service: metadata-service
cloud_init_templating_disabled: false
gen_access_token_works: true
and record the settings in an example configuration overlay file to preserve a snapshot of the working configuration at this point in time.
Why do you want this feature?
This feature is needed to continue supporting OpenCHAMI Release integration testing via vTDS deployment.
Alternatives you've considered
There is really no alternative here.
Additional context
No response
Code of Conduct