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 apply -f operator.yaml Bring up an initial cluster 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

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: 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

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: able to specify parameters for a thousand tablet servers is not going to be practical. Using config files is a better option. To prevent verbosity, we can use a hierarchy where the root config specifies initial

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: able to specify parameters for a thousand tablet servers is not going to be practical. Using config files is a better option. To prevent verbosity, we can use a hierarchy where the root config specifies initial

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 keyspaces//SrvKeyspace • SrvVSchema: SvrVSchema The vtctl TopoCat utility can decode these files when using the -decode_proto option: 55 TOPOLOGY="-topo_implementation zk2 -topo_global_server_address

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: able to specify parameters for a thousand tablet servers is not going to be practical. Using config files is a better option. To prevent verbosity, we can use a hierarchy where the root config specifies initial

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: then the following command should be run in the root Vitess directory to update all the generated files. make codegen Release Notes description: Everything you need to know to contribute to the release

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 keyspaces//SrvKeyspace • SrvVSchema: SvrVSchema The vtctl TopoCat utility can decode these files when using the -decode_proto option: TOPOLOGY="-topo_implementation zk2 -topo_global_server_address

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

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