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.1.9b1.tar.gz (17.2 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.1.9b1-py2.7.egg (45.5 kB view details)

Uploaded Egg

File details

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

File metadata

File hashes

Hashes for salt-container-map-0.1.9b1.tar.gz
Algorithm Hash digest
SHA256 d10aa00905a3844e769cb1d3eac95f003a93e489a9573dc7b2f32a5e243b1cb5
MD5 e698f82447aa57f20ec7d9e872dd838f
BLAKE2b-256 ab82402accc8021a8737e1987711007839ec8f27461e0638c3b6090908a9bdb6

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for salt_container_map-0.1.9b1-py2.7.egg
Algorithm Hash digest
SHA256 6f542d405c706e7d163cb75042fac79098b0f45e7857870c46d67562a92d1afe
MD5 35fa3a3e22a4848c43b9d01b984678a8
BLAKE2b-256 1b5f985cb8c1cb9ed009e53c8076412837235077555116346646643fdb4509ae

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