Skip to content

Forward-merge release/26.04 into main#1002

Merged
rgsl888prabhu merged 2 commits intomainfrom
release/26.04
Mar 31, 2026
Merged

Forward-merge release/26.04 into main#1002
rgsl888prabhu merged 2 commits intomainfrom
release/26.04

Conversation

@rapids-bot
Copy link
Copy Markdown
Contributor

@rapids-bot rapids-bot bot commented Mar 31, 2026

Forward-merge triggered by push to release/26.04 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

This change replaces the solve_lp_remote and solve_mip_remote stubs with real routines that use an embedded grpc client to communicate with a remote cuopt server.

There are two documents included, GRPC_ARCHITECTURE.md and SERVER_ARCHITECTURE.md that act as developer guides.

The server is built by build.sh and is called cuopt_grpc_server.

Remote execution is still enabled via env vars CUOPT_REMOTE_HOST and CUOPT_REMOTE_PORT

To try this feature, checkout the branch/PR and do the following:

$ build.sh
$ cuopt_grpc_server // defaults are fine, run with -h for help
$ CUOPT_REMOTE_HOST=localhost CUOPT_REMOTE_PORT=8765 cuopt_cli myproblem.mps

All cuopt APIs will pick up remote execution if the env vars are set. So cuopt_cli, the C API, the Python API, all will solve problems on the server if the env vars are set and the server is running. Just use cuopt tools and APIs as you normally would for a local solve.

Authors:
  - Trevor McKay (https://github.com/tmckayus)

Approvers:
  - Rajesh Gandham (https://github.com/rg20)
  - Ishika Roy (https://github.com/Iroy30)
  - Bradley Dice (https://github.com/bdice)

URL: #939
@rapids-bot rapids-bot bot requested review from a team as code owners March 31, 2026 01:24
@rapids-bot rapids-bot bot requested review from AyodeAwe and Iroy30 March 31, 2026 01:24
@rapids-bot
Copy link
Copy Markdown
Contributor Author

rapids-bot bot commented Mar 31, 2026

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@rapids-bot rapids-bot bot requested review from hlinsen and nguidotti March 31, 2026 01:24
@rgsl888prabhu rgsl888prabhu merged commit 335e936 into main Mar 31, 2026
83 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.

3 participants