Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/vsha 547 #55

Merged
merged 5 commits into from
Apr 14, 2023
Merged

Feature/vsha 547 #55

merged 5 commits into from
Apr 14, 2023

Conversation

erl-hpe
Copy link
Collaborator

@erl-hpe erl-hpe commented Apr 5, 2023

Summary and Scope

Add Helm chart content and code to enable the logic for setting the architecture and type when generating the iPXE binary that has been latent in the code for quite a while. This is needed to used cms-ipxe on vShasta because vShasta uses KPXE binaries not EFI.

Backward compatible change.

Issues and Related PRs

Testing

Tested on:

  • Virtual Shasta

Test description:

Installed on vShasta v2 system and verified that I could build a KPXE binary using cray-ipxe. Also verified that the chart with no special customizations creates a cray-ipxe that builds an EFI / x86 binary.

  • Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
  • Were continuous integration tests run? If not, why?
  • Was upgrade tested? If not, why?
  • Was downgrade tested? If not, why?
  • Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations

There are no known risks or issues with this change.

Pull Request Checklist

  • Version number(s) incremented, if applicable
  • Copyrights updated
  • License file intact
  • Target branch correct
  • CHANGELOG.md updated
  • Testing is appropriate and complete, if applicable
  • HPC Product Announcement prepared, if applicable

@github-advanced-security
Copy link

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

@erl-hpe erl-hpe marked this pull request as ready for review April 10, 2023 18:35
@erl-hpe erl-hpe requested a review from a team as a code owner April 10, 2023 18:35
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@mharding-hpe mharding-hpe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good other than the changelog nit. I can help this get shepherded through once we get a second approval.

@erl-hpe
Copy link
Collaborator Author

erl-hpe commented Apr 10, 2023

Thanks! I appreciate the help with the versioning, that was confusing me.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@mharding-hpe
Copy link
Contributor

Thanks! I appreciate the help with the versioning, that was confusing me.

No problem. In theory we follow the process defined here:
https://github.com/Cray-HPE/community/wiki/Gitflow-Development-Process

Although there are various deviations from it.

@mharding-hpe mharding-hpe merged commit e269730 into develop Apr 14, 2023
@mharding-hpe mharding-hpe deleted the feature/VSHA-547 branch April 14, 2023 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants