Saltstack Official Galera Formula
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.rst 5.9KB

9 years ago
9 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216
  1. ======
  2. Galera
  3. ======
  4. Galera Cluster for MySQL is a true Multimaster Cluster based on synchronous replication. Galera Cluster is an easy-to-use, high-availability solution, which provides high system uptime, no data loss and scalability for future growth.
  5. Sample pillars
  6. ==============
  7. Galera cluster master node
  8. .. code-block:: yaml
  9. galera:
  10. master:
  11. enabled: true
  12. name: openstack
  13. bind:
  14. address: 192.168.0.1
  15. port: 3306
  16. members:
  17. - host: 192.168.0.1
  18. port: 4567
  19. - host: 192.168.0.2
  20. port: 4567
  21. admin:
  22. user: root
  23. password: pass
  24. database:
  25. name:
  26. encoding: 'utf8'
  27. users:
  28. - name: 'username'
  29. password: 'password'
  30. host: 'localhost'
  31. rights: 'all privileges'
  32. Galera cluster slave node
  33. .. code-block:: yaml
  34. galera:
  35. slave:
  36. enabled: true
  37. name: openstack
  38. bind:
  39. address: 192.168.0.2
  40. port: 3306
  41. members:
  42. - host: 192.168.0.1
  43. port: 4567
  44. - host: 192.168.0.2
  45. port: 4567
  46. admin:
  47. user: root
  48. password: pass
  49. Additional mysql users:
  50. .. code-block:: yaml
  51. mysql:
  52. server:
  53. users:
  54. - name: clustercheck
  55. password: clustercheck
  56. database: '*.*'
  57. grants: PROCESS
  58. grant_option: False
  59. - name: inspector
  60. host: 127.0.0.1
  61. password: password
  62. databases:
  63. mydb:
  64. - database: mydb
  65. - table: mytable
  66. - grant_option: False
  67. - grants:
  68. - all privileges
  69. Additional check params:
  70. mysql:
  71. server:
  72. clustercheck:
  73. - user: clustercheck
  74. - password: clustercheck
  75. - available_when_donor: 0
  76. - available_when_readonly: 1
  77. - enabled: True
  78. - xinetd_port 9200
  79. Usage
  80. =====
  81. MySQL Galera check sripts
  82. .. code-block:: bash
  83. mysql> SHOW STATUS LIKE 'wsrep%';
  84. mysql> SHOW STATUS LIKE 'wsrep_cluster_size' ;"
  85. Galera monitoring command, performed from extra server
  86. .. code-block:: bash
  87. garbd -a gcomm://ipaddrofone:4567 -g my_wsrep_cluster -l /tmp/1.out -d
  88. 1. salt-call state.sls mysql
  89. 2. Comment everything starting wsrep* (wsrep_provider, wsrep_cluster, wsrep_sst)
  90. 3. service mysql start
  91. 4. run on each node mysql_secure_install and filling root password.
  92. .. code-block:: bash
  93. Enter current password for root (enter for none):
  94. OK, successfully used password, moving on...
  95. Setting the root password ensures that nobody can log into the MySQL
  96. root user without the proper authorisation.
  97. Set root password? [Y/n] y
  98. New password:
  99. Re-enter new password:
  100. Password updated successfully!
  101. Reloading privilege tables..
  102. ... Success!
  103. By default, a MySQL installation has an anonymous user, allowing anyone
  104. to log into MySQL without having to have a user account created for
  105. them. This is intended only for testing, and to make the installation
  106. go a bit smoother. You should remove them before moving into a
  107. production environment.
  108. Remove anonymous users? [Y/n] y
  109. ... Success!
  110. Normally, root should only be allowed to connect from 'localhost'. This
  111. ensures that someone cannot guess at the root password from the network.
  112. Disallow root login remotely? [Y/n] n
  113. ... skipping.
  114. By default, MySQL comes with a database named 'test' that anyone can
  115. access. This is also intended only for testing, and should be removed
  116. before moving into a production environment.
  117. Remove test database and access to it? [Y/n] y
  118. - Dropping test database...
  119. ... Success!
  120. - Removing privileges on test database...
  121. ... Success!
  122. Reloading the privilege tables will ensure that all changes made so far
  123. will take effect immediately.
  124. Reload privilege tables now? [Y/n] y
  125. ... Success!
  126. Cleaning up...
  127. 5. service mysql stop
  128. 6. uncomment all wsrep* lines except first server, where leave only in my.cnf wsrep_cluster_address='gcomm://';
  129. 7. start first node
  130. 8. Start third node which is connected to first one
  131. 9. Start second node which is connected to third one
  132. 10. After starting cluster, it must be change cluster address at first starting node without restart database and change config my.cnf.
  133. .. code-block:: bash
  134. mysql> SET GLOBAL wsrep_cluster_address='gcomm://10.0.0.2';
  135. Read more
  136. =========
  137. * https://github.com/CaptTofu/ansible-galera
  138. * http://www.sebastien-han.fr/blog/2012/04/15/active-passive-failover-cluster-on-a-mysql-galera-cluster-with-haproxy-lsb-agent/
  139. * http://opentodo.net/2012/12/mysql-multi-master-replication-with-galera/
  140. * http://www.codership.com/wiki/doku.php
  141. * Best one: - http://www.sebastien-han.fr/blog/2012/04/01/mysql-multi-master-replication-with-galera/
  142. Documentation and Bugs
  143. ======================
  144. To learn how to install and update salt-formulas, consult the documentation
  145. available online at:
  146. http://salt-formulas.readthedocs.io/
  147. In the unfortunate event that bugs are discovered, they should be reported to
  148. the appropriate issue tracker. Use Github issue tracker for specific salt
  149. formula:
  150. https://github.com/salt-formulas/salt-formula-galera/issues
  151. For feature requests, bug reports or blueprints affecting entire ecosystem,
  152. use Launchpad salt-formulas project:
  153. https://launchpad.net/salt-formulas
  154. You can also join salt-formulas-users team and subscribe to mailing list:
  155. https://launchpad.net/~salt-formulas-users
  156. Developers wishing to work on the salt-formulas projects should always base
  157. their work on master branch and submit pull request against specific formula.
  158. https://github.com/salt-formulas/salt-formula-galera
  159. Any questions or feedback is always welcome so feel free to join our IRC
  160. channel:
  161. #salt-formulas @ irc.freenode.net