add support for ppc64le architecture

[seth-priya]

Signed-off-by: Priya Seth sethp@us.ibm.com

Description

add support for ppc64le architecture

Issues Resolved

#1303

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[seth-priya]

The changes are based on #4001

The basic build (localDisto), precommit check pass, gradle-check on ppc64le fails with same issue as reported at #4173

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/7647/
• CommitID: e2c7b93

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.02%. Comparing base (cb26035) to head (0c153bc).
⚠️ Report is 4384 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #5459      +/-   ##
============================================
+ Coverage     70.95%   71.02%   +0.07%     
- Complexity    58304    58340      +36     
============================================
  Files          4733     4733              
  Lines        278256   278262       +6     
  Branches      40249    40249              
============================================
+ Hits         197441   197649     +208     
+ Misses        64628    64433     -195     
+ Partials      16187    16180       -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[saratvemulapalli]

@seth-priya thank you for contributing the change. Is there a way to add a test for these changes?
I know we do verify if the tars are generated for each architecture/distribution.

[dbwiddis]

Looks good... one fix needed (comments) and one suggestion (constants).

Agree with the question about tests -- I suspect we can at least test the enum determination by manipulating os.arch property.

[dbwiddis]

(Preference) I would really like if at least some these values could be made constants. I see above they correspond to AUDIT_ARCH_XXX, __NR_xxx, etc.

[seth-priya]

thanks @saratvemulapalli @dbwiddis for your feedback, I will work on it and get back soon.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/7778/
• CommitID: 1d16bc6

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/7865/
• CommitID: d1be35e
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/7985/
• CommitID: 1cd45fa

[saratvemulapalli]

Thanks @seth-priya , looks like inherently gradle scripts are testing the expected distributions.

[saratvemulapalli]

@seth-priya could you update CHANGELOG.md and take care of conflicts. We should be good to merge.

[seth-priya]

thanks @saratvemulapalli for the feedback and review comments , agree on the test, addressed the conflict

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/8182/
• CommitID: 0c153bc

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-5459-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d76adf3504e3001a84d53177af8ea36af2cc65c1
# Push it to GitHub
git push --set-upstream origin backport/backport-5459-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-5459-to-2.x.