Skip to content

docs(changelog): version 0.4.0 [citest_skip]#107

Merged
spetrosi merged 1 commit intolinux-system-roles:mainfrom
spetrosi:changelog-20262303
Mar 23, 2026
Merged

docs(changelog): version 0.4.0 [citest_skip]#107
spetrosi merged 1 commit intolinux-system-roles:mainfrom
spetrosi:changelog-20262303

Conversation

@spetrosi
Copy link
Copy Markdown
Collaborator

@spetrosi spetrosi commented Mar 23, 2026

Update changelog and .README.html for version 0.4.0

Signed-off-by: Sergei Petrosian spetrosi@redhat.com

Summary by Sourcery

Document new Azure- and NVIDIA-related capabilities and storage options in the HPC role and record the 0.4.0 release changes in the changelog.

Documentation:

  • Expand the README HTML to describe new Azure-specific packages, NVIDIA tooling options, storage configuration (including /var logical volume), and updated example playbooks.
  • Add a 0.4.0 changelog entry summarizing new features, bug fixes, and CI/test/build updates for the HPC role.

Update changelog and .README.html for version 0.4.0

Signed-off-by: Sergei Petrosian <spetrosi@redhat.com>
@spetrosi spetrosi requested a review from richm as a code owner March 23, 2026 10:23
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Mar 23, 2026

Reviewer's Guide

Update documentation for version 0.4.0 by expanding the README HTML with new Azure- and NVIDIA-related HPC variables and storage behavior, and by adding a detailed 0.4.0 entry to the changelog describing new features, bug fixes, and CI/testing updates.

Flow diagram for storage management with rootvg rootlv usrlv varlv in hpc role v0.4.0 docs

flowchart TD
  A[hpc_manage_storage true] --> B[Identify root volume group hpc_rootvg_name]
  B --> C[Ensure logical volume hpc_rootlv_name exists]
  B --> D[Ensure logical volume hpc_usrlv_name exists]
  B --> E[Ensure logical volume hpc_varlv_name exists]

  C --> F[If LV size < hpc_rootlv_size then extend LV]
  D --> G[If LV size < hpc_usrlv_size then extend LV]
  E --> H[If LV size < hpc_varlv_size then extend LV]

  F --> I[Mount hpc_rootlv_name at hpc_rootlv_mount]
  G --> J[Mount hpc_usrlv_name at hpc_usrlv_mount]
  H --> K[Mount hpc_varlv_name at hpc_varlv_mount]

  A --> L[If Azure platform detected]
  L --> M[Run growpart on backing partition]
  M --> N[Run pvresize on PV]
  N --> B
Loading

File-Level Changes

Change Details Files
Document new Azure- and NVIDIA-related HPC variables and updated storage behavior in the generated HTML README.
  • Extend the table of contents with new sections for Azure-specific packages, additional NVIDIA tooling, Azure health checks, tuning and SKU customisation, and new storage variables.
  • Add detailed sections describing Azure platform packages (WALinuxAgent, aznfs), new NVIDIA services (IMEX, DCGM, container toolkit), Azure monitoring and diagnostics tools, and Azure-specific networking and RDMA options.
  • Describe new tuning and SKU customisation variables for Azure VM types and their role in configuring HPC hardware optimally.
  • Expand the storage configuration docs to include management of /var via new logical volume variables and automatic disk/partition/VG expansion behavior.
  • Update example playbooks to show the new var logical volume variables and adjust IDs of code blocks to remain consistent.
.README.html
Add a changelog entry for release 0.4.0 summarizing feature, bugfix, and CI/testing changes.
  • Introduce a [0.4.0] section dated 2026-03-23 with categorized lists for New Features, Bug Fixes, and Other Changes.
  • List new Azure-related capabilities (Moneo, diagnostics, health checks, SKU customisations, disk expansion, AZNFS, Docker/NVIDIA container toolkit) and core HPC role improvements.
  • Capture bug fixes around Azure platform detection, storage sizing, NVIDIA tooling behavior, and repo/version locking issues.
  • Record CI, testing, and build-related updates, including new tests, ansible-lint/tox-lsr bumps, and CI behavior changes like citest_skip handling.
CHANGELOG.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've found 3 issues, and left some high level feedback:

  • In the Storage section, the sentence "the role ensures that rootlv, usrlv and varlv in Azure has enough storage" should use the plural verb form ("have enough storage").
  • The new hpc_install_azurehpc_health_checks section is marked up as an <h1> while most variable descriptions are <h2>; consider aligning its heading level with the surrounding variable sections for consistent structure.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In the Storage section, the sentence "the role ensures that `rootlv`, `usrlv` and `varlv` in Azure has enough storage" should use the plural verb form ("have enough storage").
- The new `hpc_install_azurehpc_health_checks` section is marked up as an `<h1>` while most variable descriptions are `<h2>`; consider aligning its heading level with the surrounding variable sections for consistent structure.

## Individual Comments

### Comment 1
<location path=".README.html" line_range="604-607" />
<code_context>
-<code>usrlv</code> in Azure has enough storage for packages to be
-installed. You can use variables described in this section to control
-the exact sizes and paths.</p>
+<p>By default, the role ensures that <code>rootlv</code>,
+<code>usrlv</code> and <code>varlv</code> in Azure has enough storage
+for packages to be installed. You can use variables described in this
+section to control the exact sizes and paths.</p>
</code_context>
<issue_to_address>
**nitpick (typo):** Subject-verb agreement issue in storage description sentence

`rootlv, usrlv and varlv in Azure has enough storage` uses a plural subject with a singular verb. Please change `has` to `have`, or rephrase along the lines of `the role ensures that the logical volumes rootlv, usrlv, and varlv in Azure have enough storage ...` for correct grammar.

```suggestion
<p>By default, the role ensures that the logical volumes <code>rootlv</code>,
<code>usrlv</code> and <code>varlv</code> in Azure have enough storage
for packages to be installed. You can use variables described in this
section to control the exact sizes and paths.</p>
```
</issue_to_address>

### Comment 2
<location path="CHANGELOG.md" line_range="42" />
<code_context>
+- fix: correct typo in service running test (#92)
+- fix: moneo test-script fixes (#95)
+- fix: install cuda-toolkit-config-common-12.9.79-1 with cuda-toolkit 12 (#97)
+- fix: install RDMA test script after azure specific resource path created (#98)
+- fix: add opt-in net.ifnames=0 for Azure images (#101)
+- fix: resolve nvidia-persistenced service failure issue on race condition (#102)
</code_context>
<issue_to_address>
**suggestion (typo):** Improve grammar and hyphenation for "azure specific" phrase

Consider rephrasing to "install RDMA test script after the Azure-specific resource path is created," or at least hyphenate "Azure-specific" to match standard usage and the other entries.

```suggestion
- fix: install RDMA test script after the Azure-specific resource path is created (#98)
```
</issue_to_address>

### Comment 3
<location path="CHANGELOG.md" line_range="68" />
<code_context>
+- ci: Ansible version must be string, not float [citest_skip] (#82)
+- test: add test script for aznfs package (#86)
+- ci: bump actions/upload-artifact from 6 to 7 (#88)
+- test: add testing Nvidia docker container script (#89)
+- test: add validation for hpc tuning (#93)
+- ci: tox-lsr 3.16.0 - fix qemu tox test failures - rename to qemu-ansible-core-X-Y [citest_skip] (#94)
</code_context>
<issue_to_address>
**suggestion (typo):** Align NVIDIA brand capitalization

Elsewhere in this changelog (e.g., "NVIDIA IMEX", "NVIDIA DCGM"), the brand is written as "NVIDIA". For consistency with the brand name and other entries, please change "Nvidia" here to "NVIDIA".

```suggestion
- test: add testing NVIDIA docker container script (#89)
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +604 to +607
<p>By default, the role ensures that <code>rootlv</code>,
<code>usrlv</code> and <code>varlv</code> in Azure has enough storage
for packages to be installed. You can use variables described in this
section to control the exact sizes and paths.</p>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

nitpick (typo): Subject-verb agreement issue in storage description sentence

rootlv, usrlv and varlv in Azure has enough storage uses a plural subject with a singular verb. Please change has to have, or rephrase along the lines of the role ensures that the logical volumes rootlv, usrlv, and varlv in Azure have enough storage ... for correct grammar.

Suggested change
<p>By default, the role ensures that <code>rootlv</code>,
<code>usrlv</code> and <code>varlv</code> in Azure has enough storage
for packages to be installed. You can use variables described in this
section to control the exact sizes and paths.</p>
<p>By default, the role ensures that the logical volumes <code>rootlv</code>,
<code>usrlv</code> and <code>varlv</code> in Azure have enough storage
for packages to be installed. You can use variables described in this
section to control the exact sizes and paths.</p>

- fix: correct typo in service running test (#92)
- fix: moneo test-script fixes (#95)
- fix: install cuda-toolkit-config-common-12.9.79-1 with cuda-toolkit 12 (#97)
- fix: install RDMA test script after azure specific resource path created (#98)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (typo): Improve grammar and hyphenation for "azure specific" phrase

Consider rephrasing to "install RDMA test script after the Azure-specific resource path is created," or at least hyphenate "Azure-specific" to match standard usage and the other entries.

Suggested change
- fix: install RDMA test script after azure specific resource path created (#98)
- fix: install RDMA test script after the Azure-specific resource path is created (#98)

- ci: Ansible version must be string, not float [citest_skip] (#82)
- test: add test script for aznfs package (#86)
- ci: bump actions/upload-artifact from 6 to 7 (#88)
- test: add testing Nvidia docker container script (#89)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (typo): Align NVIDIA brand capitalization

Elsewhere in this changelog (e.g., "NVIDIA IMEX", "NVIDIA DCGM"), the brand is written as "NVIDIA". For consistency with the brand name and other entries, please change "Nvidia" here to "NVIDIA".

Suggested change
- test: add testing Nvidia docker container script (#89)
- test: add testing NVIDIA docker container script (#89)

@spetrosi spetrosi merged commit d5071d7 into linux-system-roles:main Mar 23, 2026
12 checks passed
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.

1 participant