History

semantic-release-bot 143ee92d71 chore(release): 0.5.0 [skip ci] # [0.5.0](https://github.com/saltstack-formulas/keepalived-formula/compare/v0.4.5...v0.5.0) (2020-04-06) ### Bug Fixes * libtofs: “files_switch” mess up the variable exported by “map.jinja” [skip ci] ([`e01cd28`](`e01cd28115`)) ### Continuous Integration * kitchen: avoid using bootstrap for `master` instances [skip ci] ([`05a0959`](`05a095954d`)) ### Features * vrrp_sync_group: added option for vrrp_sync_group ([`45e3261`](`45e3261e53`))		2020-04-06 21:31:47 +00:00
..
AUTHORS.rst	chore(release): 0.5.0 [skip ci]	2020-04-06 21:31:47 +00:00
CHANGELOG.rst	chore(release): 0.5.0 [skip ci]	2020-04-06 21:31:47 +00:00
README.rst	docs(readme): update link to `CONTRIBUTING` [skip ci]	2019-10-14 11:36:37 +01:00
TOFS_pattern.rst	chore: use `semantic-release` cross-formula standard structure	2019-08-17 16:05:40 +01:00

README.rst

keepalived-formula

Formula to set up and configure keepalived

Table of Contents

General notes

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.

Contributing to this repo

Commit message formatting is significant!!

Please see How to contribute for more details.

Available states

`keepalived`

Installs and configures the keepalived package.

`keepalived.package`

Installs the keepalived package.

`keepalived.config`

This state manages the file keepalived.conf under /etc/keepalived (template found in "keepalived/files"). The configuration is populated by values in "keepalived/map.jinja" based on the package's default values (and RedHat, Debian, Suse and Arch family distribution specific values), which can then be overridden by values of the same name in pillar.

`keepalived.service`

This state ensures that keepalived service is running.

Testing

Linux testing is done with kitchen-salt.

Requirements

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.

`bin/kitchen converge`

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

`bin/kitchen verify`

Runs the inspec tests on the actual instance.

`bin/kitchen destroy`

Removes the docker instance.

`bin/kitchen test`

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

`bin/kitchen login`

Gives you SSH access to the instance for manual testing.