In order to accomplish this, smitty is continuously monitoring the +switch-master event, then it will update twemproxy configuration files and restart the resource.
A possible scenario:
You can get the latest release that includes a smitty binary, download and run it.
smitty needs to be configured through a YAML file specified by the -c command-line argument on process start. An example of configuration file, also included in conf/agent.yml could be this:
twemproxy_pool_name: "root" twemproxy_config_file: "conf/nutcracker.yml" sentinel_ip: "127.0.0.1" sentinel_port: "26379" restart_command: "/etc/init.d/twemproxy restart" log_file: "agent.log"
At 3scale, we're an absolute Futurama fanatics, and of course there isn't a better name for an agent that Smitty:
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request
Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0