Summary
OCI would like to create an official integration path in NeMo Agent Toolkit similar to the existing first-class cloud provider integrations already present in the project.
This request is based on the work proposed in PR #1804, which adds an oci LLM provider/config in nvidia_nat_core, a LangChain wrapper in nvidia_nat_langchain, OCI documentation, and OCI-focused test coverage.
Motivation
Today NAT has explicit integration paths for other cloud providers such as AWS Bedrock and Azure OpenAI. OCI would like to have the same kind of official, maintainable path for OCI-hosted workflows rather than relying on one-off or purely custom integrations.
From the PR context, the intended OCI support includes:
- a first-class
oci provider/config in NAT core
- LangChain workflow-layer support via
langchain-oci
- documentation and installation guidance for OCI users
- test coverage for OCI-hosted workflows, including OCI-hosted Nemotron validation
Goal
Track maintainer discussion and alignment on whether NAT should support OCI as an official cloud-provider path, and if so, what the supported scope should be for an initial integration.
Reference
Summary
OCI would like to create an official integration path in NeMo Agent Toolkit similar to the existing first-class cloud provider integrations already present in the project.
This request is based on the work proposed in PR #1804, which adds an
ociLLM provider/config innvidia_nat_core, a LangChain wrapper innvidia_nat_langchain, OCI documentation, and OCI-focused test coverage.Motivation
Today NAT has explicit integration paths for other cloud providers such as AWS Bedrock and Azure OpenAI. OCI would like to have the same kind of official, maintainable path for OCI-hosted workflows rather than relying on one-off or purely custom integrations.
From the PR context, the intended OCI support includes:
ociprovider/config in NAT corelangchain-ociGoal
Track maintainer discussion and alignment on whether NAT should support OCI as an official cloud-provider path, and if so, what the supported scope should be for an initial integration.
Reference