Maestro-ng

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

_September 14th, 2015_

This release contains lots of improvements to keep Maestro moving
forward and compatible with Docker and its fast-moving pace! Starting
from this release the documentation has also moved to ReadTheDocs.org
and will progressively be updated to fit into their page structure.

* Display image tag of the running image for running containers.
* Add support for `cap_add` and `cap_drop` parameters.
* Lots of Python3 compatibility fixes; using MaestroNG with Python3
should now be possible.
* Use the same Jinja2 extensions and environment when reading an
environment file from STDIN than when reading from file, allowing for
the same references to environment variables and uses of includes.
* Rework auditing to track individual events (more verbose).
* Bump docker-py requirement to 1.3.0 and use a default Docker API
version of 1.15 (instead of 1.10, which is no longer supported by the
most recent versions of Docker).
* Control of the API version used when talking to a Docker daemon is now
possible via the `api_version` parameter to the Ship's constructor.
* Add support for Docker logging drivers via the support of the
`logconfig` parameters.
* Optimize `maestro logs` command, even continuing to follow the logs if
the underlying container gets restarted.
* Fix concurrent pulling of the same image on the same ship.

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

_May 26th, 2015_

This is the first MaestroNG release to be made available on the Python
Package Index. A few tweaks were made to make this possible:

* The pip package name was changed to `maestro-ng`. You might want to
uninstall and re-install Maestro instead of upgrading to avoid
conflicts.
* The package's README is now parsed and converted to reStructuredText
in the `setup.py` so it displays correctly on PyPI.

The following Maestro changes are also included in this small
point-release:

* Use yaml.CLoader to speed up YAML parsing, when possible
* Display image SHA in `status -F` output of running containers

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

_May 12th, 2015_

* guestutils: don't attempt to contact the Docker daemon running on the
host for get_container_internal_address(). It's not guaranteed that
the Docker daemon is available, or that it's even running on the
default port via TCP. Rely on the `netifaces` module instead.
* Fix lifecycle script check execution when container environment
contains non-string values.

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

_May 1st, 2015_

With this release, MaestroNG switches from the GNU GPLv3 to the Apache
Software License v2, with permissions from the various contributors.

* The official Docker port, 2375, is now the default port used by
Maestro.
* Improvements to the script execution as a lifecycle check; the script
is executed multiple times until success or until the maximum number
of attempts is reached, much like for TCP port pinging. The
environment of the script also contains the environment variables the
container would have when running.
* Fall back to looking up configured image registries by their FQDN
(93).
* Added support for `omit: true` on a service, which instructs Maestro
not to act on this service in "unspecified" commands, unless of course
the service is required for another one to run (108).
* Fix documentation on Maestro's use of authentication credentials
(65).
* Fix output of `status -F` command where port status wouldn't be shown.
* Remove container volumes when removing containers (122).
* Miscellanious flake8 and unit test fixups.

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

_February 23rd, 2015_

Simple point-fix release to include the separation of main() and
execute() in the module entrypoint to make building scripts that execute
MaestroNG easier.

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

_February 19th, 2015_

* Added support for specifying the container's work directory (111)
* Improvements to the pull task so it correctly reports errors (76)
* Improvements to error reporting by providing a meaningful traceback
* Allow connection to local Docker daemons via UNIX socket (106, 113)
* Added basic JSON-sending webhook auditor (118)
* Added support for `volumes_from` and container-only volumes (114)
* Set `DOCKER_IMAGE` and `DOCKER_TAG` environment variables inside the
started containers as running programs might find this information
useful