Skip to content

MGMT-20237: Change tooltip for Openshift AI bundle#2943

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ammont82:MGMT-20237-change-tooltip-for-openshift-ai-bundle
Apr 30, 2025
Merged

MGMT-20237: Change tooltip for Openshift AI bundle#2943
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ammont82:MGMT-20237-change-tooltip-for-openshift-ai-bundle

Conversation

@ammont82
Copy link
Member

@ammont82 ammont82 commented Apr 30, 2025

Related with https://issues.redhat.com/browse/MGMT-20237

Captura desde 2025-04-30 11-45-53
Captura desde 2025-04-30 11-45-42

Summary by CodeRabbit

  • New Features

    • Introduced a unified 'openshift-ai' bundle that supports both NVIDIA and AMD GPUs, with automatic component installation based on detected hardware.
  • Improvements

    • Simplified the description for the 'openshift-ai' bundle, making requirements and compatibility clearer for users.
    • Removed separate 'openshift-ai-nvidia' and 'openshift-ai-amd' bundles for a more streamlined experience.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 30, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2025

@ammont82: This pull request references MGMT-20237 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Related with https://issues.redhat.com/browse/MGMT-20237

Captura desde 2025-04-30 11-45-53
Captura desde 2025-04-30 11-45-42

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link

coderabbitai bot commented Apr 30, 2025

Walkthrough

This change consolidates the previously separate 'openshift-ai-nvidia' and 'openshift-ai-amd' bundle specifications into a single 'openshift-ai' bundle within the bundleSpecs object. The new bundle removes mutual incompatibility settings and provides a simplified description, omitting specific hardware and configuration requirements. The external documentation link is also removed. No other bundles are altered.

Changes

File(s) Change Summary
libs/ui-lib/lib/ocm/components/clusterConfiguration/operators/bundleSpecs.tsx Consolidated 'openshift-ai-nvidia' and 'openshift-ai-amd' bundles into a single 'openshift-ai' bundle; removed incompatibilities and detailed requirements; eliminated external docs link.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant bundleSpecs

    User->>UI: Selects AI GPU bundle
    UI->>bundleSpecs: Retrieve 'openshift-ai' bundle specification
    bundleSpecs-->>UI: Returns consolidated bundle details
    UI-->>User: Displays unified 'openshift-ai' bundle description
Loading

Possibly related PRs

  • Do not allow virtualization bundle on SNO clusters #2933: Both PRs modify the bundleSpecs object in the same file by adjusting bundle specifications related to the noSNO property and bundle definitions, but the main PR consolidates AI GPU bundles while the retrieved PR adds noSNO to the virtualization bundle, indicating related changes to bundle configuration handling.

Suggested labels

lgtm, approved, size/XS

Suggested reviewers

  • batzionb

Poem

In the meadow of code where the bundles would roam,
Two GPU friends have now found one home.
No more splits between AMD and Nvidia's might—
Just one AI bundle, simple and bright!
Requirements are lighter, the docs link is gone,
This rabbit hops forward, the work is well done!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

libs/ui-lib/lib/ocm/components/clusterConfiguration/operators/bundleSpecs.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "@openshift-assisted/eslint-config" to extend from. Please check that the name of the config is correct.

The config "@openshift-assisted/eslint-config" was referenced from the config file in "/libs/ui-lib/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@openshift-ci openshift-ci bot requested review from celdrake and jgyselov April 30, 2025 09:47
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 30, 2025
@ammont82 ammont82 added this to the v2.40 milestone Apr 30, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2025

@ammont82: This pull request references MGMT-20237 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Related with https://issues.redhat.com/browse/MGMT-20237

Captura desde 2025-04-30 11-45-53
Captura desde 2025-04-30 11-45-42

Summary by CodeRabbit

  • New Features

  • Introduced a unified 'openshift-ai' bundle that supports both NVIDIA and AMD GPUs, with automatic component installation based on detected hardware.

  • Improvements

  • Simplified the description for the 'openshift-ai' bundle, making requirements and compatibility clearer for users.

  • Removed separate 'openshift-ai-nvidia' and 'openshift-ai-amd' bundles for a more streamlined experience.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
libs/ui-lib/lib/ocm/components/clusterConfiguration/operators/bundleSpecs.tsx (1)

31-31: Consider documenting the reasoning behind empty incompatible bundles

Previously, the NVIDIA and AMD bundles were likely mutually incompatible. With the new consolidated approach, you're setting incompatibleBundles: []. This makes sense for a unified bundle, but adding a code comment explaining this design decision might help future maintainers understand the rationale.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4bc6a50 and 5a2cc22.

📒 Files selected for processing (1)
  • libs/ui-lib/lib/ocm/components/clusterConfiguration/operators/bundleSpecs.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: circular-deps
  • GitHub Check: tests
  • GitHub Check: unit-tests
  • GitHub Check: format
  • GitHub Check: translation-files
  • GitHub Check: lint
🔇 Additional comments (2)
libs/ui-lib/lib/ocm/components/clusterConfiguration/operators/bundleSpecs.tsx (2)

29-40: Consolidated OpenShift AI bundle implementation looks good!

The consolidation of the previously separate hardware-specific bundles ('openshift-ai-nvidia' and 'openshift-ai-amd') into a single 'openshift-ai' bundle simplifies the user experience. The dynamic description that adapts based on discovered GPUs is a more flexible approach.


35-36: Review the wording of the description

The updated tooltip text is more succinct but consider if users would benefit from knowing:

  1. What specific capabilities each GPU type enables
  2. Any minimum hardware requirements that still apply
  3. Whether users need to take any action to enable the right modules

While the simplified text improves UX, some users might need more detailed guidance without the external documentation link that was previously available.

Copy link
Member

@rawagner rawagner left a comment

Choose a reason for hiding this comment

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

Looks great!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 30, 2025
@openshift-ci
Copy link

openshift-ci bot commented Apr 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, rawagner

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 91823a0 into openshift-assisted:master Apr 30, 2025
11 checks passed
ammont82 added a commit to ammont82/assisted-installer-ui that referenced this pull request Sep 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants