[Gb200] Support IMEX configuration to be local to a node

[himani2411]

Description of changes

[Gb200] Support IMEX configuration to be local to a node

• we remove /opt/parallelcluster/shared/nvidia-imex directory creation
• We keep default path of /etc/nvidia-imex/nodes_config.cfg and /etc/nvidia-imex/config.cfg for IMEX configuration
• We override /etc/nvidia-imex/nodes_config.cfg only if it is missing to avoid Imex start failures.
• Update unit test

Tests

• [Success] DLAMi AMI Build - AL2023
  • [Success]test_gb200 - Cluster creation successful. IMEX Heath status check manually to verify Imex Prolog works Submitted a Job with sbatch --segment=2 -N 2 /opt/parallelcluster/shared/nvidia-imex-status.job https://github.com/aws/aws-parallelcluster/pull/7013/files
• [Success] Normal Vanilla AMI Build - rocky9
  • [Success] test_gb200 - Cluster creation successfull. IMEX Heath status check manually to verify Imex Prolog works Submitted a Job with sbatch --segment=2 -N 2 /opt/parallelcluster/shared/nvidia-imex-status.job https://github.com/aws/aws-parallelcluster/pull/7013/files

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[gmarciani]

[minor] this comment is correct, but it makes more sense to write it where create_configuration_files is called.

[himani2411]

Its Create or update because as per chef template the action create is https://docs.chef.io/resources/template/

(default) Create a file. If a file already exists (but does not match), update that file to match.

[gmarciani]

[minor] What about calling any the action install_configuration_files? I think could be a good practice to call actions that are part of the install phase as install_SOMETHING and actions called in configuration phase configure_SOMETHING.

[himani2411]

I prefer keeping the action name as creation as the action of the template is create. Even though we use it in Install phase of our recipes, we are creating these configuration files.