the noise over tcp blueprint had two unresolved questions:
* what do we do for IPv6?
* what do we do for UDP support?
this change punts those two questions for later and explicitly
rejects solving them as part of noise over TCP for now.
this change also punts renaming NodeURL to reduce codebase
churn.
Change-Id: Ib209942bae61716b2ff6cea852c336af072d8bc5
Add design for identifying and processing node events and sending
notifications to node operators.
github issue: https://github.com/storj/storj/issues/5039
Change-Id: I63341867207c28334bb025c6a104692ce2a16edd
Add document outlining the design and implementation steps for the paid
tier TLS feature.
https: //github.com/storj/storj/issues/5296
Change-Id: I51f68fc7890f816cef7bf2a319762ad701bac445
This change updates the automatic account freezing/unfreezing blueprint
to account for new feedback and changes in the implementation process.
Change-Id: If1a478d961b67aa4a946793168a7f525e06bb9e7
This blueprint describes a way to allow user accounts to be
automatically restricted after failing to pay and unrestricted after
payment has been collected.
Change-Id: I4b64eb8ef6bf83603be7ad7d7bcb78f2d885c2a4
and clarify some related implementation details.
Most notably, this change clarifies that the verification audit workers
and reverification audit workers are meant to live in a process or
processes separate from the satellite core, and outlines an extra queue
that will be used for communication with the core.
It's not entirely clear to me that this is the right approach; we would
save some fairly significant implementation time by leaving both types
of worker in the core. That would make it necessary to reconfigure and
restart the core when we wanted to change the number of verification
and/or reverification workers, and scaling would be limited to the
computational capacity of the core vm, but maybe those are acceptable
conditions.
Another option would be to leave the Verifier workers in the core, and
having a separate process for Reverifiers. That would be sort of a
middle way between the two above.
Change-Id: Ida12e423b94ef6088733b13d5cc58bdb78f2e93f
New blueprint describes a design which provides the satellite greater
control over sessions authorized to use the web app.
Change-Id: I5af227aef6d6b096167e2e8a60f1e8214c2cd71f
This change adds a blueprint outlining the renovation of the
current API system including guidelines for API code generation.
Change-Id: I5560cc8642eee44842829ecddf205886cd5b13f2
* docs: update graceful exit refactoring doc
Co-authored-by: paul cannon <thepaul@storj.io>
Co-authored-by: Jennifer Li Johnson <jennifer@storj.io>
Co-authored-by: Maximillian von Briesen <mobyvb@gmail.com>
Trusted Delegated Repair is performing repair on trusted servers outside
the network boundary of the satellite.
Change-Id: I13b0e6f53100cefcb89c0c77bd1421c549551ab7
This change adds two new tables to process orders as fast as we used
to but in an asynchronous manner and with hopefully less storage
usage. This should help scale on cockroach, but limits us to one
worker. It lays the groundwork for the order processing pipeline to
be queue rather than database driven.
For more details, see the added fast billing changes blueprint.
It also fixes the orders db so that all the timestamps that are
passed to columns that do not contain a time zone are converted to
UTC at the last possible opportunity, making it less likely to use
the APIs incorrectly. We really should migrate to include timezones
on all of our timestamp columns.
Change-Id: Ibfda8e7a3d5972b7798fb61b31ff56419c64ea35
This document describes a new state, suspension, which nodes will
be placed in if they respond to too many audits with "unknown" errors.
When in this state, node operators will have to fix their node within a
certain amount of time, or they will be disqualified. While nodes are
suspended, they will not be able to receive new data.
Change-Id: I543f27ada66d8b40fc52ca8ead8ecc8479326bad
- also updated ping chore to pick up trust changes
- fixed small typo in blueprint
- fixed flags for storj-sim
- wired up changes to testplanet
Change-Id: I02982f3a63a1b4150b82a009ee126b25ed51917d
* change satellite.Peer name to Core
* change to Core in testplanet
* missed a few places
* keep shared stuff in peer.go to stay consistent with storj/docs
