{"action":"opened","issue":{"url":"https://api.github.com/repos/geerlingguy/raspberry-pi-dramble/issues/78","repository_url":"https://api.github.com/repos/geerlingguy/raspberry-pi-dramble","labels_url":"https://api.github.com/repos/geerlingguy/raspberry-pi-dramble/issues/78/labels{/name}","comments_url":"https://api.github.com/repos/geerlingguy/raspberry-pi-dramble/issues/78/comments","events_url":"https://api.github.com/repos/geerlingguy/raspberry-pi-dramble/issues/78/events","html_url":"https://github.com/geerlingguy/raspberry-pi-dramble/issues/78","id":156563982,"number":78,"title":"Add a simple MySQL Failover playbook","user":{"login":"geerlingguy","id":481677,"avatar_url":"https://avatars.githubusercontent.com/u/481677?v=3","gravatar_id":"","url":"https://api.github.com/users/geerlingguy","html_url":"https://github.com/geerlingguy","followers_url":"https://api.github.com/users/geerlingguy/followers","following_url":"https://api.github.com/users/geerlingguy/following{/other_user}","gists_url":"https://api.github.com/users/geerlingguy/gists{/gist_id}","starred_url":"https://api.github.com/users/geerlingguy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geerlingguy/subscriptions","organizations_url":"https://api.github.com/users/geerlingguy/orgs","repos_url":"https://api.github.com/users/geerlingguy/repos","events_url":"https://api.github.com/users/geerlingguy/events{/privacy}","received_events_url":"https://api.github.com/users/geerlingguy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-24T17:26:13Z","updated_at":"2016-05-24T17:26:13Z","closed_at":null,"body":"Currently the MySQL servers get set up properly... but there's no simple way to failover automatically. I don't want to do any kind of monitoring-based failover, but I do want to show how Ansible can really make things like this (emergency nightmare) scenario fairly painless.\r\n\r\nTherefore I'm thinking I can add a `mysql-failover.yml` playbook in the drupal playbooks folder, and it will do the following:\r\n\r\n1. Run the `geerlingguy.mysql` role on the slave only, with the replication setup for 'master'.\r\n2. Run `STOP SLAVE` and `RESET SLAVE ALL` on the slave (now master).\r\n3. Update Drupal's settings.php to point to the slave (now master)."}}
{"actor":{"display_login":"geerlingguy"}}