Skip to content

feat: Add InferenceGraph resource #2361

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

israel-hdez
Copy link
Contributor

@israel-hdez israel-hdez commented Mar 27, 2025

Short description:

Add InferenceGraph resource

More details:

Add the InferenceGraph resource from the KServe project.

What this PR does / why we need it:

The new resource is going to be used for testing the InferenceGraph feature of Open Data Hub project.

Summary by CodeRabbit

  • New Features
    • Introduced a configurable inference graph resource, enabling enhanced deployment options for Kubernetes-based AI inference workloads with flexible scaling, resource allocation, and timeout settings.

Copy link

coderabbitai bot commented Mar 27, 2025

Walkthrough

The changes introduce a new class, InferenceGraph, in the ocp_resources/inference_graph.py file. This class is designed to represent an inference graph resource in a Kubernetes context and extends from NamespacedResource. It includes an initializer that accepts various optional parameters (e.g., affinity, max/min replicas, nodes, resources, scale parameters, and timeout) and a to_dict method that converts the instance to a dictionary representation. A check is implemented to ensure the nodes parameter is provided.

Changes

File Change Summary
ocp_resources/inference_graph.py Added new class InferenceGraph with a constructor accepting optional parameters (affinity, replicas, nodes, resources, scale settings, timeout) and a to_dict method that constructs a dictionary from the instance properties while checking that nodes is provided.
✨ 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

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.

@redhat-qe-bot
Copy link
Contributor

Report bugs in Issues

The following are automatically added:

  • Add reviewers from OWNER file (in the root of the repository) under reviewers section.
  • Set PR size label.
  • New issue is created for the PR. (Closed when PR is merged/closed)
  • Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

  • To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
  • To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.
    • Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
    • Cherry-pick will be started when PR is merged
  • To build and push container image command /build-and-push-container in the PR (tag will be the PR number).
    • You can add extra args to the Podman build command
      • Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>
  • To add a label by comment use /<label name>, to remove, use /<label name> cancel
  • To assign reviewers based on OWNERS file use /assign-reviewers
  • To check if PR can be merged use /check-can-merge
  • to assign reviewer to PR use /assign-reviewer @<reviewer>
Supported /retest check runs
  • /retest tox: Retest tox
  • /retest python-module-install: Retest python-module-install
  • /retest conventional-title: Retest conventional-title
  • /retest all: Retest all
Supported labels
  • hold
  • verified
  • wip
  • lgtm

@redhat-qe-bot redhat-qe-bot requested a review from myakove March 27, 2025 05:53
@israel-hdez israel-hdez changed the title Add InferenceGraph resource feat: Add InferenceGraph resource Mar 27, 2025
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: 2

🧹 Nitpick comments (3)
ocp_resources/inference_graph.py (3)

9-12: Update the class documentation with proper description.

The class docstring is currently a placeholder without any actual description of what an InferenceGraph resource is or how it should be used. Consider adding information about the purpose of this resource in KServe, its relationship to inference services, and any important characteristics that users should know.


16-57: Update parameter documentation with proper descriptions.

The docstrings for all parameters are currently placeholders. Consider consulting the KServe API documentation to add accurate descriptions for each parameter, explaining:

  • What affinity controls in the context of inference graphs
  • The purpose of max_replicas and min_replicas for scaling
  • What the required nodes parameter represents and its structure
  • What resources should contain
  • How scale_metric and scale_target affect scaling behavior
  • What the timeout parameter controls

This will significantly improve the usability of this class.


65-90: Consider using a utility function for snake_case to camelCase conversion.

The method manually converts snake_case parameter names to camelCase for the API (e.g., max_replicas to maxReplicas). This could be prone to errors if new parameters are added. Consider using a utility function for this conversion to improve maintainability.

Also, consider enhancing the structure building pattern to be more concise:

-            if self.affinity is not None:
-                _spec["affinity"] = self.affinity
-
-            if self.max_replicas is not None:
-                _spec["maxReplicas"] = self.max_replicas
-
-            if self.min_replicas is not None:
-                _spec["minReplicas"] = self.min_replicas
-
-            if self.resources is not None:
-                _spec["resources"] = self.resources
-
-            if self.scale_metric is not None:
-                _spec["scaleMetric"] = self.scale_metric
-
-            if self.scale_target is not None:
-                _spec["scaleTarget"] = self.scale_target
-
-            if self.timeout is not None:
-                _spec["timeout"] = self.timeout
+            # Map snake_case attributes to camelCase API fields
+            attr_to_field = {
+                "affinity": "affinity",
+                "max_replicas": "maxReplicas",
+                "min_replicas": "minReplicas",
+                "resources": "resources",
+                "scale_metric": "scaleMetric",
+                "scale_target": "scaleTarget",
+                "timeout": "timeout"
+            }
+            
+            for attr, field in attr_to_field.items():
+                value = getattr(self, attr)
+                if value is not None:
+                    _spec[field] = value
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2dc73c0 and 937b25b.

📒 Files selected for processing (1)
  • ocp_resources/inference_graph.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: tox
  • GitHub Check: python-module-install
  • GitHub Check: conventional-title
🔇 Additional comments (3)
ocp_resources/inference_graph.py (3)

14-14: LGTM! Correct API group set for KServe resource.

The API group is correctly set to the SERVING_KSERVE_IO constant from the parent class.


61-64: LGTM! Proper validation for required nodes parameter.

The code correctly checks if the required nodes parameter is provided and raises an appropriate error when it's missing.


59-59:

❌ Incorrect review comment

Missing return value from super().to_dict() call.

The parent method's return value is not being used. You should either capture the return value or check if the parent's implementation modifies self.res directly.


🏁 Script executed:

#!/bin/bash
# Check if the parent class's to_dict method returns a value or modifies self.res
rg -A 10 "def to_dict" --glob "ocp_resources/resource.py"

Length of output: 1300


Clarification on to_dict() Behavior

After verifying the parent implementation in ocp_resources/resource.py, it’s clear that the parent’s to_dict() method is designed to update the resource state (via _base_body()) rather than return a dictionary. The method’s signature explicitly indicates a return type of None, so capturing a return value isn’t necessary in this context.

Likely an incorrect or invalid review comment.

@myakove
Copy link
Collaborator

myakove commented Mar 27, 2025

/retest conventional-title

@myakove myakove merged commit d62ce3c into RedHatQE:main Mar 27, 2025
5 of 7 checks passed
@israel-hdez israel-hdez deleted the add-inference-graph branch March 27, 2025 15:25
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants