TraceMachina / TraceMachina/nativelink

[Feature]: Rewrite ONTAP store as an S3 variant

Open
#2,779 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.6k
Forks
244
Avg merge
1d 16h
Merged PRs (30d)
54

Description

Problem statement

ONTAP store implementation is meant to be mostly S3, but it's drifted and doesn't have all the improvements of the core S3 implementation.

Proposed solution

Following on from the discussion in https://github.com/TraceMachina/nativelink/issues/2767 and with https://github.com/TraceMachina/nativelink/pull/2768 now merged, we should be able to rewrite the ONTAP store as a thin layer over S3, similarly to the R2 and OCI stores.

The one difficult item here is access to a real ONTAP instance, which we don't currently have. The original ONTAP work was done in collaboration with a client with a local ONTAP store they could test things with, and rewriting this will need access to actual ONTAP. There does appear to be an ONTAP simulator available for download, but it looks like it needs a NetApp client license to do so.

Alternatives considered

Sticking with the existing ONTAP setup which is believed working (but again, lack of ONTAP makes it hard to test)

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the R2 and OCI store implementations and the changes from merged PR #2768 first, then compare them with the existing ONTAP store. Done means ONTAP is a thin layer over the core S3 implementation and the result is validated against an actual ONTAP instance; arrange simulator or client access before relying on that validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.