Changes for migration from @NVIDIA to @ai-dynamo#225
Merged
Conversation
…dynamo/grove/scheduler/client`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…amo/grove/scheduler/api`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…m/ai-dynamo/grove/scheduler/*`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…ynamo/grove/operator/client`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…mo/grove/operator/api`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…om/ai-dynamo/grove/operator/api`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
…rove/operator`. Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com>
unmarshall
previously approved these changes
Oct 22, 2025
Collaborator
|
For users of the Grove API and the Scheduler API the import paths need to also change. Please make sure that the consumers are well informed about this change so that they can also adapt quickly. If vendoring is used then we have some buffer but in case where there is no vendoring any further builds will fail. |
gflarity
requested changes
Oct 22, 2025
gflarity
left a comment
Contributor
There was a problem hiding this comment.
One small suggestion that makes it easier to test development forks using public images (and also works with the repo rename)
gflarity
previously approved these changes
Oct 22, 2025
This comment was marked as outdated.
This comment was marked as outdated.
bcc627b to
e12819b
Compare
Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com> --------- Signed-off-by: Saketh Kalaga <saketh.kalaga@sap.com> Co-authored-by: Geoff Flarity <gflarity@nvidia.com>
gflarity
approved these changes
Oct 22, 2025
sanjaychatterjee
approved these changes
Oct 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The repository is planned to be migrated from @NVIDIA to @ai-dynamo.
All corresponding changes in source which correspond to this migration are brought in by this PR:
^github\.com/NVIDIA/grove(?:/.*)?$to^github\.com/ai-dynamo/grove(?:/.*)?$.I've made changes module wise, and committed them individually to make it easy to review.
The changes are identical when the following is run on main at c2171c7 (other than miscellaneous changes in 601d17b):
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
DO NOT MERGE BEFORE MIGRATION.
Does this PR introduce a API change?
Additional documentation e.g., enhancement proposals, usage docs, etc.: