Saltstack Official Galera Formula
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.

README.rst 5.1KB

9 år sedan
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  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. Usage
  50. =====
  51. MySQL Galera check sripts
  52. .. code-block:: bash
  53. mysql> SHOW STATUS LIKE 'wsrep%';
  54. mysql> SHOW STATUS LIKE 'wsrep_cluster_size' ;"
  55. Galera monitoring command, performed from extra server
  56. .. code-block:: bash
  57. garbd -a gcomm://ipaddrofone:4567 -g my_wsrep_cluster -l /tmp/1.out -d
  58. 1. salt-call state.sls mysql
  59. 2. Comment everything starting wsrep* (wsrep_provider, wsrep_cluster, wsrep_sst)
  60. 3. service mysql start
  61. 4. run on each node mysql_secure_install and filling root password.
  62. .. code-block:: bash
  63. Enter current password for root (enter for none):
  64. OK, successfully used password, moving on...
  65. Setting the root password ensures that nobody can log into the MySQL
  66. root user without the proper authorisation.
  67. Set root password? [Y/n] y
  68. New password:
  69. Re-enter new password:
  70. Password updated successfully!
  71. Reloading privilege tables..
  72. ... Success!
  73. By default, a MySQL installation has an anonymous user, allowing anyone
  74. to log into MySQL without having to have a user account created for
  75. them. This is intended only for testing, and to make the installation
  76. go a bit smoother. You should remove them before moving into a
  77. production environment.
  78. Remove anonymous users? [Y/n] y
  79. ... Success!
  80. Normally, root should only be allowed to connect from 'localhost'. This
  81. ensures that someone cannot guess at the root password from the network.
  82. Disallow root login remotely? [Y/n] n
  83. ... skipping.
  84. By default, MySQL comes with a database named 'test' that anyone can
  85. access. This is also intended only for testing, and should be removed
  86. before moving into a production environment.
  87. Remove test database and access to it? [Y/n] y
  88. - Dropping test database...
  89. ... Success!
  90. - Removing privileges on test database...
  91. ... Success!
  92. Reloading the privilege tables will ensure that all changes made so far
  93. will take effect immediately.
  94. Reload privilege tables now? [Y/n] y
  95. ... Success!
  96. Cleaning up...
  97. 5. service mysql stop
  98. 6. uncomment all wsrep* lines except first server, where leave only in my.cnf wsrep_cluster_address='gcomm://';
  99. 7. start first node
  100. 8. Start third node which is connected to first one
  101. 9. Start second node which is connected to third one
  102. 10. After starting cluster, it must be change cluster address at first starting node without restart database and change config my.cnf.
  103. .. code-block:: bash
  104. mysql> SET GLOBAL wsrep_cluster_address='gcomm://10.0.0.2';
  105. Read more
  106. =========
  107. * https://github.com/CaptTofu/ansible-galera
  108. * http://www.sebastien-han.fr/blog/2012/04/15/active-passive-failover-cluster-on-a-mysql-galera-cluster-with-haproxy-lsb-agent/
  109. * http://opentodo.net/2012/12/mysql-multi-master-replication-with-galera/
  110. * http://www.codership.com/wiki/doku.php
  111. * Best one: - http://www.sebastien-han.fr/blog/2012/04/01/mysql-multi-master-replication-with-galera/
  112. Documentation and Bugs
  113. ======================
  114. To learn how to install and update salt-formulas, consult the documentation
  115. available online at:
  116. http://salt-formulas.readthedocs.io/
  117. In the unfortunate event that bugs are discovered, they should be reported to
  118. the appropriate issue tracker. Use Github issue tracker for specific salt
  119. formula:
  120. https://github.com/salt-formulas/salt-formula-galera/issues
  121. For feature requests, bug reports or blueprints affecting entire ecosystem,
  122. use Launchpad salt-formulas project:
  123. https://launchpad.net/salt-formulas
  124. You can also join salt-formulas-users team and subscribe to mailing list:
  125. https://launchpad.net/~salt-formulas-users
  126. Developers wishing to work on the salt-formulas projects should always base
  127. their work on master branch and submit pull request against specific formula.
  128. https://github.com/salt-formulas/salt-formula-galera
  129. Any questions or feedback is always welcome so feel free to join our IRC
  130. channel:
  131. #salt-formulas @ irc.freenode.net