A mass deployment tool for Docker fleets
MIT License
Bot releases are visible (Hide)
#193 Permit specifying an ssh_socket_heartbeat
for the SSH mechanism. This can alleviate stalled deploys in widely-threaded execution.
Published by intjonathan almost 6 years ago
#190 Lower logging level to DEBUG
for container inspect output during deploy. This prevents printing env vars in deployment logs, as those vars often contain secrets.
Published by intjonathan about 6 years ago
New in this release:
pid
namespacing mode on containers.Published by intjonathan about 6 years ago
New in this release:
#188 Environment variables may be sourced from lambdas, which are evaluated during deploy time. This permits calling functions to specify different environment variables per host.
Published by intjonathan over 6 years ago
SSH support is considered stable, as it has performed well for several months.
One new fix in this release: https://github.com/newrelic/centurion/pull/187 adds the unless-stopped
restart policy.
Published by intjonathan almost 7 years ago
This release adds beta SSH support for teams deploying to Docker hosts which do not expose their TCP sockets over the network.
Published by intjonathan over 7 years ago
Two fixs and one feature, for a balanced diet.
Fixed: #164 via #177 - containers in host networking mode may now define a public port to be used during healthchecks. The port mapping will be passed through to Docker, but it should be ignored by the server.
Fixed: #128 via #147 - manually set container names were not obeyed, now they are. If you have a name:
set in your deploy tasks, please read the notes on #147 to avoid having duplicate containers present after a deploy, especially in host networking mode. You should comment out the name:
directive until you're ready to manually intervene as containers may not be found during a stop operation.
Feature: #170 Container label support! You may now specify labels to be assigned to the containers Centurion creates. See the README for details.
Published by intjonathan almost 8 years ago
This fixes a bad behavior in 1.8.8 where setting a custom stop_timeout
caused Centurion to give up too soon waiting on the response from Docker. This would result in Excon timeouts during deploys.
The response timeout is now always 120 seconds longer than the Docker stop timeout.
See #171 and #175.
Published by intjonathan almost 8 years ago
Fixed in this release:
Published by dselans over 8 years ago
Minor bugfix release.
Published by dselans over 8 years ago
This is a minor release that includes a few readme/doc changes + ipc_mode addition to the dsl.
Changes: https://github.com/newrelic/centurion/compare/v1.8.5...v1.8.6
Published by dselans almost 9 years ago
This release includes a couple of minor updates/additions and a cgroup bugfix.
docker inspect
your running containers and verify that Memory
is not 0 or max possible memory; redeploy the container if it's incorrect.Changelog: https://github.com/newrelic/centurion/compare/v1.8.4...v1.8.5
Published by dselans almost 9 years ago
This is a minor bugfix release:
docker exec
'sChangelog: https://github.com/newrelic/centurion/compare/v1.8.3...v1.8.4
Published by dselans almost 9 years ago
Quick release that adds support for Docker 1.7 and 1.8 (and retains backwards compat with 1.5).
Changelog: https://github.com/newrelic/centurion/compare/v1.8.2...v1.8.3
Published by relistan about 9 years ago
This release fixes a bug in the rolling_deploy
code which was no longer waiting on the set timeout intervals. Additionally output is fixed to report proper hostname strings rather than objects.
Published by relistan about 9 years ago
This fixes a bug with host-based networking deployments.
Published by relistan about 9 years ago
A lot of minor updates went into this release, and the code is now stable on the major internal refactor that was done by @kremso. The major additions are support for capabilities, host-based networking, and support for restarting containers without a redeploy.
Published by relistan over 9 years ago
There is one notable change in this release. The container naming will no longer default to using the Docker server's hostname inside the container. It will leave it as the container ID which is the Docker default. You can supply an optional lambda or Proc
to name it as you see fit. The README
contains full details.