Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document supported storage backends #1953

Open
RJPercival opened this issue Nov 5, 2019 · 4 comments
Open

Document supported storage backends #1953

RJPercival opened this issue Nov 5, 2019 · 4 comments

Comments

@RJPercival
Copy link
Contributor

We have storage implementations for MySQL, Cloud Spanner and (partially) Postgres. However, we don't document whether we support deployments that use them. Some helpful things to document include:

  • Which storage backends do we support?
    • Do we support Cloud Spanner even though the storage implementation is marked "experimental"?
    • We presumably don't support Postgres, since the storage implementation is incomplete.
  • Which versions of storage backends do we support?
    • Do we support MySQL 8?
    • Do we support variants of MySQL, e.g. MariaDB, and if so, which ones?
@RJPercival
Copy link
Contributor Author

We should also document what it means for us to support a deployment (e.g. SLO on support requests only for supported deployments?).

@RJPercival
Copy link
Contributor Author

Also to consider: whether we only support specific configurations of some of these storage backends, e.g. only MySQL backed by SSD.

@mhutchinson
Copy link
Contributor

These are partially documented at https://github.com/google/trillian/blob/master/docs/Feature_Implementation_Matrix.md and this would benefit from fleshing out. See #1845 for an example of uncertainty and issues around specific versions of DB.

@RJPercival RJPercival removed their assignment Feb 26, 2020
@RJPercival RJPercival added this to Needs triage in Trillian via automation Feb 26, 2020
@paulmattei paulmattei moved this from Needs triage to Low priority in Trillian Mar 4, 2020
@paulmattei paulmattei moved this from Low priority to Backlog in Trillian Mar 4, 2020
@mhutchinson mhutchinson self-assigned this May 26, 2022
@mhutchinson
Copy link
Contributor

I'm going to tidy up the feature implementation matrix and call this done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Trillian
  
Backlog
Development

No branches or pull requests

3 participants