Skip to content

[oep] add multi cloud support proposal#93

Merged
slin1237 merged 1 commit into
mainfrom
slin/oep2
Jun 30, 2025
Merged

[oep] add multi cloud support proposal#93
slin1237 merged 1 commit into
mainfrom
slin/oep2

Conversation

@slin1237
Copy link
Copy Markdown
Collaborator

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

N/A

Fixes #
N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @slin1237, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a proposal (OEP) for adding multi-cloud support to OME. It outlines the motivation, goals, design details, and implementation plan for enabling OME to work with multiple cloud providers, including authentication and storage. The proposal aims to create a more flexible and adaptable architecture for OME.

Highlights

  • Multi-Cloud Support: This OEP proposes a multi-cloud architecture for OME, providing unified interfaces for authentication and storage operations across major cloud providers (OCI, AWS, GCP, Azure, GitHub).
  • Provider-Agnostic Interfaces: The design replaces existing OCI-specific implementations with provider-agnostic interfaces for authentication (pkg/auth) and storage (pkg/storage).
  • URI Specification: Introduces a consistent URI scheme across all providers (e.g., s3://bucket/object, gs://bucket/object).
  • Extensible Design: Implements an extensible factory pattern for easy registration of new providers without modifying core code.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

OEP-0002 introduces a multi-cloud storage and authentication proposal. The design is comprehensive, covering key aspects like motivation, architecture, and risks. The URI format should be more flexible, and the creation date in oep.yaml needs correction.

Comment thread oeps/0002-multi-cloud-support/README.md
Comment thread oeps/0002-multi-cloud-support/oep.yaml Outdated
@slin1237 slin1237 merged commit 365d7b7 into main Jun 30, 2025
23 checks passed
@slin1237 slin1237 deleted the slin/oep2 branch June 30, 2025 15:56
slin1237 added a commit that referenced this pull request Dec 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant