CHANGELOG.md

ChangeLog

Maestro 0.2.6.1

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.

Maestro 0.2.6

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.

Maestro 0.2.5.1

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.

Maestro 0.2.5

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

Maestro 0.2.4.1

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:

__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).

Maestro 0.2.4

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)

Maestro 0.2.3

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)

Maestro 0.2.2

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)

Maestro 0.2.1

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

Maestro 0.2.0

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)

Maestro 0.1.8.1

May 30th, 2014

• Fixed link variable naming for port names containing dashes

Maestro 0.1.8

May 28th, 2014

• Support for custom image command
• Implement restart Maestro command
• Add support for "soft" dependencies through wants_info. Containers get the link environment variable, but the dependency has no impact on the start/stop orders
• Improve guestutils service matching by including a list of each service's instances as a <service_name>_INSTANCES environment variable

Maestro 0.1.7.1

April 28th, 2014

• Support for memory and cpu shares limits
• Fix image:tag parsing when custom registries are involved
• Improve Jinja2 setup to include filesystem loader and with extension for more flexible and complex Jinja2 templating capabalities

Maestro 0.1.7

April 9th, 2014

• Use docker-py 0.3.x
• Deep expend of environment variables list values
• Pre-processing of the YAML environment description through Jinja2 templating
• Correctly pass-in specified volumes to create_container() in case the image's Dockerfile didn't define them
• Support service-level environment variables that trickle down to all instances of the service
• Documentation improvements, flake8 and unit-test fixes
• Support for privileged containers
• Support for timeout on container stop

Maestro 0.1.6

January 30th, 2014

• Fullstatus output now shows port numbers
• Improved port specification syntax for more precise control about internal and exposed ports and interfaces
• Maestro extension for logstash-based logging scaffolding
• Docker and docker-py compatibility fixes (Id/ID, docker-py API tweaks)
• Show image being pulled when creating a container

Maestro 0.1.5

January 16th, 2014

• Fix download indicator for compatibility with Docker 0.7.x
• Renamed 'status' command to 'fullstatus', and implemented new, faster 'status' command that only looks at the state of the containers, not the services themselves
• Sort containers before building dependencies to try to keep them a bit more organized without breaking the dependency order
• Don't use white in commands output, just bold text
• Compatibility fixes with docker-py 0.2.3
• The 'logs' command now streams logs instead of dumping them, until you hit ^C to stop
• Implement registry login before pull, when needed and if possible
• Renamed 'scores' to 'plays', makes more sense
• Updates to the 'logs' command:
  • by default, the 'logs' command now dumps the full log and doesn't stream/follow
  • with the '-F' flag, logs will be followed
  • the new '-n N' flag will only show the last N lines of the log, but it doesn't work with streaming logs
• Setup for Travis-CI build with flake8 validation

Maestro 0.1.4

December 9th, 2013

• Optimize status score by not polling the service if the container is down (it can't be running then)
• Add guest helper function to retrieve the internal IP address of the container

Maestro 0.1.3

December 6th, 2013

• Download progress indicator when pulling an image
• Correctly exit with a non-zero exit code on error through better exception handling and reporting
• Removed the useless -v/--verbose option
• Bugfixes and code cleanups

Maestro 0.1.2

November 25th, 2013

• Seamless understanding of parameters as either containers or services for all operations
• Independent control of only the containers and/or services provided on the command-line without affecting dependencies or dependents with the new -o flag

Maestro 0.1.1

November 25th, 2013

• Improved output display
• Correctly show already up/already down containers when starting/stopping services and containers
• Add documentation for the guest utils functions
• Automatic pulling of missing images

Maestro 0.1.0

November 21st, 2013

Initial Maestro version with the basic orchestration features implemented. Environment description, dependency management and basic start/stop orchestration scores.

Maestro 0.1.0 is also the first version that provides the guestutils helper functions.