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.0b2.tar.gz (21.0 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.0b2-py2.7.egg (51.9 kB view details)

Uploaded Egg

File details

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

File metadata

File hashes

Hashes for salt-container-map-0.2.0b2.tar.gz
Algorithm Hash digest
SHA256 0f28c23917fa6cc4adfcbaf89826f200465921ffc3bb59857ad20b6d670f7530
MD5 36ee33826e77f646213b7db206b3b54a
BLAKE2b-256 0d681838bef0670e2a59fd65ca579f736a5fc203447c1a139d15f5df0855535b

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for salt_container_map-0.2.0b2-py2.7.egg
Algorithm Hash digest
SHA256 8e187f9753a82c9432383a418c872d70ba4238a5277b5066d203e3e3ba61a2fe
MD5 4724de6748a96c56f309c53da1c4dc7d
BLAKE2b-256 ec63ed4c3ee7c060d29b2db34249505f92b72580afdd4862a75618435ed88ffb

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 Sentry Error logging StatusPage Status page