Milestones
List view
See storj/storj#7378 for more details
No due date•11/11 issues closedRoadmap item: https://github.com/storj/roadmap/issues/47
Due by September 30, 2024•71/71 issues closed### Summary This milestone captures work to be done to better handle linkshare content that gets our domain flagged for malicious content
No due date•5/5 issues closedwork to be immediately done after the release of the linksharing tls MVP. Work under this milestone has been deemed necessary to complete to support and maintain the feature.
No due date•5/5 issues closed## MOVED TO INFRA REPO - KEEPING THIS AS PLACEHOLDER IN CASE WE NEED IT https://github.com/storj/infra/milestone/30 ### Summary We want to understand current scaling limitations for edge services (linksharing, s3 gateway, and associated applications such as auth service). Furthermore, we want to outline a plan for scaling edge services that we can begin to implement ASAP. ### Why Now We want to be able to proactively respond to capacity constraints before they become an issue. ### Goals **Answer the following key questions:** - How do we grow the baseline for expected growth (footprint)? - More locations - Higher capacity - How do we handle short term “surge”? - What is our current capacity for edge services? - With existing setup (firewall constraint)? - Assuming firewall issues are resolved? ### Key Stakeholders - Product - Engineering - Ops/Finance
Due by June 30, 2023•1/1 issues closed- No due date•1/1 issues closed
- No due date•9/9 issues closed
- No due date
Milestone to track https://github.com/storj/roadmap/issues/51 All details/requirements are on the roadmap item
No due date•1/1 issues closedThis milestone is https://github.com/storj/gateway-mt/issues/251, broken into several tasks.
No due date•2/2 issues closedOverview of feature here: storj/roadmap#39
No due date•5/5 issues closed### Objective (TBD). @storj/edge-team will be responsible for the work contained within this milestone. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is ... (TBD)**
No due date•3/3 issues closed### Objective (TBD). @storj/edge-team will be responsible for the work contained within this milestone. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is ... (TBD)**
No due date•10/10 issues closed### Objective (TBD). @storj/edge-team will be responsible for the work contained within this milestone. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is ... (TBD)**
No due date•2/2 issues closed### Objective TBD. @storj/edge-team will be responsible for the work contained within this milestone. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is .... (TBD)**
No due date•2/2 issues closed### Objective Conduct the necessary research to smoothly execute this project by having the required information up-front, and to reduce unknowns/blockers. @storj/edge-team will be responsible for the work contained within this milestone. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is to have conducted all necessary research to move forward with feature development**
No due date•6/6 issues closed### Objective Better understand our metrics around latency -- most notably "time to first byte" so that we can start to improve on the number. #### Key Outcomes 1. Understanding of current state metrics 2. Proposal for improving
No due date•2/2 issues closedThis milestone will capture the work needed to document our custom domain solution.
No due date•2/2 issues closed### Objective Have everything prepped and finalized to begin feature development. Investigate approach to supporting secure custom domains via Linksharing. Overview of feature here: https://github.com/storj/roadmap/issues/39 **The goal for completing this milestone is a proposal (or set of proposals) for the approach/implementation.**
No due date•4/4 issues closedIssues not directly related to the deployment and functionality of the new auth database.
No due date•11/11 issues closedWe've recently noticed that 1) the Minio V2/V4 auth tests are very specific, yet not correct [we suspect that S3 may have changed] and 2) the Ceph / Splunk tests catch many things Minio doesn't [we suspect there's lots more to catch]. Furthermore, each new test we run requires installing dependencies and is sort of annoying to run. It'd be nice to be able to capture the content of an 3rd party API test and play it back. One option here is a reliable capture format, another is to actually generate Go tests from HTTP captures. Tools that may help here include https://hurl.dev/ or https://awesomeopensource.com/project/buger/goreplay. Another similar item would be the ability to run "gold master" or comparative tests. In this case, we'd be testing Gateway against S3 directly, comparing the results of operations. This would also be useful to try against other clients, such as Ceph or Minio [now that we're using the latest Apache2 Minio, we can't look at Minio's code base for changes, but it'd be fine to look at its functionality]. Supporting the need to compare the "right answers" with "gold master" tests is the need to ask the right questions. I think there's a lot of room here to increase our use of "fuzz" testing, to be able to generate a variety of questions. It would be really nice to work toward multi-stage testing similar to QuickCheck. Instead of necessarily writing a state machine to track expected states, we could simply rely on Gold Master testing: does the result look like S3's result.
No due date•3/3 issues closedRoadmap Issue: https://github.com/storj/roadmap/issues/23
No due date•5/5 issues closedRoadmap Issue: https://github.com/storj/roadmap/issues/4
No due date•3/3 issues closedRoadmap Issue: https://github.com/storj/roadmap/issues/3
No due date•30/30 issues closed