Skip to content

saltstack-formulas/systemd-formula

Repository files navigation

systemd-formula

Travis CI Build Status Semantic Release

Formula to set up and configure systemd including
  • units
  • networkd
  • timesyncd
  • resolved
  • journald

See the full SaltStack Formulas installation and usage instructions.

If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.

If you want to use this formula, please pay attention to the FORMULA file and/or git tag, which contains the currently released version. This formula is versioned according to Semantic Versioning.

See Formula Versioning Section for more details.

Commit message formatting is significant!!

Please see How to contribute for more details.

Because systemd config files aren't easy to recreate in jinja based on multiple keys and different needs, I'm using TOFS.

Template Override and Files Switch (TOFS) pattern as described in the documentation file TOFS_pattern.md.

Note

See the full Salt Formulas doc.

Installs the systemd packages and libraries.

This state manages systemd-journald configuration

This state installs systemd-timesyncd and configures both NTP and timezone

This state installs systemd-timesyncd and adds the timesyncd.conf from pillar (see pillar.example)

This state installs systemd-networkd and recursively adds files per os_family/minion_id

This state installs systemd-networkd profile files from pillar (see pillar.example)

This state installs systemd-resolved and recursively adds files per os_family/minion_id

This state installs systemd-resolved and adds the resolved.conf from pillar (see pillar.example)

This formula provides a state to configure systemd units

Linux testing is done with kitchen-salt.

  • Ruby
  • Docker
$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]

Where [platform] is the platform name defined in kitchen.yml, e.g. debian-9-2019-2-py3.

Creates the docker instance and runs the systemd main state, ready for testing.

Runs the inspec tests on the actual instance.

Removes the docker instance.

Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.

Gives you SSH access to the instance for manual testing.