cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example:

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example:

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example:

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess committing. 19 • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp 23 System variable Handled long_query_time NoOp low_priority_updates committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example:

cell to be taken down and rebuilt as a unit. Vitess limits cross-cell traffic for both data and metadata. While it may be useful to also have the ability to route read traffic to individual cells, Vitess NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example:

We used the following sources for the threat modelling: ● Vitessʼs documentation including README files from the Vitess repository ● Vitessʼs source code at https://github.com/vitessio/vitess ● Feedback all transitive dependencies ⛔ Provenance - Includes reproducible info ⛔ Provenance - Includes metadata ⛔ ⛔ ⛔ ⛔ Common - Security Not defined by SLSA requirements Common - Access ✓ Common - Superusers

https://code.google.com/p/vitess/ • https://github.com/youtube/vitess • http://vitess.googlecode.com/files/Vitess_Percona_2012.pdf • http://vdisk.weibo.com/s/7JmTtKze0rn?from=page_100505_profile&wvr=6 Thank