Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Salt Container-Map

Configuration management and implicit dependency setup for Docker containers in SaltStack.

Project: https://github.com/merll/salt-container-map

Docs: Basic usage is provided in the state module. Details about container configurations are available in the docs for Docker-Map.

Overview

This package contains SaltStack modules for configuring Docker containers. They do not replace, but complement Salt’s built-in dockerio module in the following aspects:

  • Container dependencies that have to be followed during startup and shutdown do not have to be modelled via require or require_in. Instead, these are implicitly defined through their shared volumes and links.

  • For the purpose of sharing data between containers, virtual volumes can be created via a minimal runnable image (tianon/true obtained from the public Docker registry). These are considered during the dependency check and become adjusted with necessary file system permissions during startup.

  • When the configuration of a container is modified, the affected containers and their dependents can automatically be shut down and recreated.

  • Image updates can also result in an automated shutdown and recreation of containers and their dependents, without explicit watch or onchanges.

An example is documented in the state module.

Installation

Besides the usual package installation, a few simple post-installation steps are required. They are described in the docs.

Modules

Custom renderer

Container configurations can be set in both pillars and states. Pillars have the advantage that they are loaded automatically before any state (e.g. container_map.updated) or execution module uses it. Usually the disadvantage is that pillars cannot refer to other pillars. This package however provides a custom renderer lazy_yaml along with custom tags !pillar and !grain, which are resolved to their values on the minion just before the container maps and their configurations are instantiated.

By default, container maps are loaded from a pillar container_maps. This can be changed in the configuration by setting the configuration value container_map.pillar_name.

State and execution module

The modules distributed to the minions provide the functionality as outlined in the overview. A usage example is included in the state module documentation.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

salt-container-map-0.2.0b1.tar.gz (20.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

salt_container_map-0.2.0b1-py2.7.egg (51.7 kB view details)

Uploaded Egg

File details

Details for the file salt-container-map-0.2.0b1.tar.gz.

File metadata

File hashes

Hashes for salt-container-map-0.2.0b1.tar.gz
Algorithm Hash digest
SHA256 30a9643cda9975e6ab42cd21d93f0103c76294f5c3914675374c8891d965da8e
MD5 997f11b0e183f0e2291a7a54e20b56f5
BLAKE2b-256 b7fe2523d76b53cade03f3fdf431331ed7cc96e81692fe2eb04147a8d9f8b96c

See more details on using hashes here.

File details

Details for the file salt_container_map-0.2.0b1-py2.7.egg.

File metadata

File hashes

Hashes for salt_container_map-0.2.0b1-py2.7.egg
Algorithm Hash digest
SHA256 a7f4bb91f149c431961a8d93b7ec8aca4836dfba086e186ff56a7eafd6269e47
MD5 8540e36b6bb82f88b19d85b6b7ceafc7
BLAKE2b-256 3bfb0f127e3f3e52dcc0b3a1dababa19685b87b6b44a611d99da0efc7e65a9f6

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page