Baton - Server Orchestration Tool
Baton is a general purpose server orchestration tool.
git clone firstname.lastname@example.org:digital-science/baton.git cd baton bundle install
bundle exec rspec
You can either:
gem install baton
Or, in your Gemfile:
How to use
Please check an existing extension, e.g. baton-ping, for more information about how to use and extend baton. Since baton was created as a base for other extensions, it doesn't do anything in particular by itself but provide the structure and a basic setup on top of RabbitMQ and EventMachine.
Submitting a Pull Request
- Fork the repository.
- Create a topic branch.
- Add specs for your unimplemented feature or bug fix.
bundle exec rake test. If your specs pass, return to step 3.
- Implement your feature or bug fix.
bundle exec rake test. If your specs fail, return to step 5.
open coverage/index.html. If your changes are not completely covered by your tests, return to step 3.
- Add documentation for your feature or bug fix.
- Add, commit, and push your changes.
- Submit a pull request.
Details and Building Extensions
Baton relies on EventMachine and AMQP for message passing. The gem defines a basic set of classes operating on top of RabbitMQ. The initial configuration will setup an input exchange and an output exchange.
On the input exchange, baton will wait for meaningful messages to perform actions (described by each service) and it will output messages to the output exchange.
This is the entry point for input messages. One should extend the API class and add meaningful methods that ultimately use
publish to publish messages to the input exchange. One example can be found here
Any baton extension should have an executable script that will start the extension service. Here is an example.
The Service is the starting point of any baton extension. The idea of the service is to setup consumers for the input messages arriving from the API. By implementing
setup_consumers one will allow the consumers to receive messages. Here is an example.
The service also handles daemonizing for an extension. It will properly detach the process and take care of managing pid files and optionally log files. The configuration for pid and log files is commented out in the sample config.
This class is an orchestration class that attaches observers to the consumers (like logger, etc), binds the input queues to the correct exchanges, dispatches the received messages to the consumers and updates the observers on changes. One doesn't need to extend this class unless one wants to change its behaviour.
This class must be extended in order to process each received message. One should implement
process_message at least, in order to give meaning to each received message. One can also override
routing_key in order to listen to specific messages. Here is an example of an implementation.
Like the consumer manager, this class doesn't need to be extended. It provides functionality to setup the exchanges and add consumers.
The observer class provides methods to notify observers. It is by default included in the consumers so that the output exchange (and possibly loggers, etc) receive the output messages.
You can easily extend baton to perform your own tasks. baton-ping provides what we consider to be a minimal extension to baton. One should note that there is an extra class on
baton-ping called monitor. This is a good example of what to do with output messages from a baton extension. Together with baton-ping-monitor, it provides a standard way of consuming output messages and do something relevant with them.
If you would like to create your own extension, simply install baton (
gem install baton) and run the following command:
batonize gem GEMNAME -b
This will create a basic gem structure with the necessary files to create a minimum viable baton extension.
Copyright (c) Digital Science. See LICENSE for details.