Entropy is a failure orchestration microservice for Docker platforms.
Entropy allows a user to define failure injection policies for containers or services running at a target Docker API endpoint. A failure injection policy describes a failure type, frequency/duration, probability, and container selector. Each policy is applied to all current and future containers matching the selector. Policies are manifest by the creation, scheduling, and lifecycle management of sidekick containers called injectors.
Entropy failures are pluggable, but by default there are four network failures available:
- Network Partition
- Packet Reordering
- Packet Loss
Policies are applied to all current and future containers at the target endpoint that match the provided selector. Currently selectors are limitied to a single label specification (as in Docker container labels). These may take the form: K, or K=V.
This is sufficient to create broad, cross-cutting, or specific failure injection policies for systems with healthy taxonomies.
State of the Project
The project is currently PoC quality with no tests and a crude software design. Most existing code will be replaced before a proper beta. Documentation is currently very light as so much will change before the next release. If you'd like to see how to use it, checkout the demo.
Checkout buildertools/entropy-demo for a demo guide.
A developer will almost always want a local build of the service running while they are developing. Rather than leave setup to contirbutors this project uses a simple Docker based development environment and iteration scaffold. The following set of commands will handle almost every development phase. This system automates the whole lifecycle on source change events. It also manages a fully tooled local runtime environment including time series database, dashboarding, and key-value stores.
Get the Code and Get Started
# Get the code git clone https://github.com/buildertools/entropy.git # Prepare the first time to get tooling cd entropy make prepare
# Start iterating make iterate # Do your work: # Use the running service: # open http://localhost:7890 # Watch the build logs: docker-compose logs entropy # Watch the functional / integration tests: docker-compose logs integ # Watch the service metrics: # open http://localhost:3000 # Stop working for the day: make stop
Updating Dependencies or Build System
make stop # Make your changes make iterate
# Produce a versioned release image make release
Hook developers should add service definitions for target endpoints to the development environment.