Maestro-ng

---------------

_December 12th, 2014_

This fix release introduces YAML file schema versioning, in particular
to ease the pain of the migration to Maestro >= 0.2.4. A new YAML
snippet can be added to your environment description file to specify the
version of the "schema" used to understand this YAML file by Maestro:

yaml
__maestro:
schema: 2


If you don't specify this information, Maestro will assume that you use
schema version 1, which in particular understands volume bindings the
"old way" (up to version 0.2.3).

-------------

_December 12th, 2014_

**Note:** this release introduces a breaking change that will require a
change in your YAML environment files. Volume bindings must now be
specified as `/on/the/host: /inside/the/container`. This is reversed to
what Maestro used to do until now, but makes it be the same "direction"
than what Docker and `docker-py` use. See 74 for more details.

* Display improvements:
- Fix completion output for the `pull` command when executed
standalone
- Simplified and colored port status in the detailed status output
- Allow for the ship column to slim down all the way to not being
displayed when the terminal is not wide enough
- Display container running/down time in the detailed status output
- Display each container's image tag in the output
* Added an `HttpRequestLifecycle` to implement lifecycle checks that
perform an HTTP request, valid when getting a 200 response code
* Added support for container restart policies
* Added TLS/SSL support
* Support for re-using existing containers when starting or restarting
them with the `--reuse` flag, as opposed to removing and recreating
the container (fixes 92)
* Support for per-container image repository override
* Added a `--only-if-changed` flag to the `restart` command that will
only restart the container if its image has changed after pulling it
(fixes 62)
* Added support for read-only volume bindings (74)

-------------

_September 12th, 2014_

* Docker Links support (21)
* Allow for forced colored output by setting the `ANSICON` environment
variable, even if the terminal is not a tty (72)
* New `pull` command that just performs the image pull/refresh without
affecting the running containers (71). Very useful in preparation of
a rolling upgrade as it can be done with maximum parallelism
* Introduce `ship_defaults` section to provide defaults for ship
attributes like `timeout` or SSH tunnel configuration (73)
* Scaffolding for ship providers, default one is the static list of
ships but more intelligent providers can be implemented, pulling from
EC2 APIs for example
* Variable column width for container and ship name if the terminal size
allows it
* Add support for docker -dns (59)
* Add support for docker -net (41)
* Add support for specifying a distinct ship endpoint address, used to
talk to the Docker daemon (67, 70)
* Fix bug in sleep lifecycle helper (69)

-------------

_July 22nd, 2014_

* Provide no-tty output without ANSI escape codes (output still looks a
bit funky, but at least it's not riddle with unreadable escape codes)
* Fix "time ago" calculation that shows hours as days
* Correctly bubble up orchestration errors and exit with a non-zero
returncode
* Fix install requirements when installing through setup.py (which pip
does by default)

-------------

_July 22nd, 2014_

* New pluggable audit trail functionality to send orchestration commands
and results notifications to audit trail targets. Currently supports
HipChat (via python-simple-hipchat) and log file
* Fix status orchestration play to not enforce dependency order as it's
useless and slows it down
* Show how long a container has been up or down for

-------------

_July 21st, 2014_

This release warrants jumping to the 0.2.x series as the extent of the
changes is significant and it contains some potentially breaking changes
in usage (not in the YAML format though).

* Major rework of the argument parser; each command now has its own
subparser with appropriate arguments; one downside is that Maestro can
now longer default to the 'status' command when no command is
specified
* Maestro no longer assumes dependencies should be included in an
orchestration play. Use `-d` or `--with-dependencies` to automatically
include the dependencies of the given services/containers (50)
* It is now possible to ignore the dependency order during an
orchestration play by passing `-i` or `--ignore-dependencies` to the
start, stop or restart commands
* Orchestration plays can now execute container operations in parallel,
respecting the dependency order as needed and/or as requested.
Additionally, a maximum concurrency limit can be specified with `-c`
or `--concurrency-limit` to restrict the number of containers that can
be acted upon at the same time. This can be used to implement rolling
restarts for example
* Add `-v` / `--version` flag to show Maestro version
* New `deptree` commands that shows the dependency tree of each provided
service or container (supports `-r` / `--recursive` to include
duplicate indirect dependencies)
* Removed `fullstatus` command, replaced with `status -F`.
* Compatibility improvements with docker-py mainline and Docker versions
* Dropped support for `docker_endpoint` in ship configuration
* SSH tunneling support via `bgtunnel` on-demand SSH tunnels (35, 44)
* Maestro now reads a maestro.yaml file from the current working
directory instead of stdin by default. `-f -` can still be used to
read from stdin (47)
* Include workaround for Python multiprocessing bug in Python < 2.7.5
(48)
* Implement simple 'sleep' lifecycle check that simply sleeps for the
given amount of time
* Changed `cmd` to `command` in YAML instance spec. `cmd` is still
accepted but deprecated and will be removed in the next release (part
of 39)