Go to file
Ricardo Klein 45e3261e53 feat(vrrp_sync_group): added option for vrrp_sync_group
* Changed the template to include new config setting group
* Added example to pillar.example
* Included test (could be better if we check the entire section and
  ensure that it is in the correct format?)
2020-04-06 22:40:52 +02:00
bin ci: merge travis matrix, add salt-lint & rubocop to lint job 2019-10-09 05:17:37 +01:00
docs chore(release): 0.4.5 [skip ci] 2020-01-27 19:58:13 +00:00
keepalived feat(vrrp_sync_group): added option for vrrp_sync_group 2020-04-06 22:40:52 +02:00
test/integration/default feat(vrrp_sync_group): added option for vrrp_sync_group 2020-04-06 22:40:52 +02:00
.gitignore chore(gitignore): update from the template-formula [skip ci] 2020-02-14 22:28:43 +00:00
.rubocop.yml chore(rubocop): move LineLength cop from Metrics to Layout [skip ci] 2020-02-14 12:50:40 +00:00
.salt-lint ci(travis): update salt-lint config for v0.0.10 [skip ci] 2019-10-23 17:36:36 +01:00
.travis.yml ci(kitchen): avoid using bootstrap for master instances [skip ci] 2020-02-05 14:05:11 +00:00
.yamllint ci: merge travis matrix, add salt-lint & rubocop to lint job 2019-10-09 05:17:37 +01:00
AUTHORS.md chore(release): 0.4.5 [skip ci] 2020-01-27 19:58:13 +00:00
CHANGELOG.md chore(release): 0.4.5 [skip ci] 2020-01-27 19:58:13 +00:00
commitlint.config.js feat(semantic-release): implement an automated changelog 2019-05-13 16:16:29 +02:00
FORMULA chore(release): 0.4.5 [skip ci] 2020-01-27 19:58:13 +00:00
Gemfile ci(gemfile): restrict train gem version until upstream fix [skip ci] 2019-12-16 13:40:56 +00:00
kitchen.yml ci(kitchen): avoid using bootstrap for master instances [skip ci] 2020-02-05 14:05:11 +00:00
LICENSE feat(semantic-release): implement an automated changelog 2019-05-13 16:16:29 +02:00
pillar.example feat(vrrp_sync_group): added option for vrrp_sync_group 2020-04-06 22:40:52 +02:00
pre-commit_semantic-release.sh ci(travis): run shellcheck during lint job [skip ci] 2019-11-27 21:01:04 +00:00
release-rules.js feat(semantic-release): implement an automated changelog 2019-05-13 16:16:29 +02:00
release.config.js fix(release.config.js): use full commit hash in commit link [skip ci] 2019-10-31 10:33:18 +00:00

keepalived-formula

Travis CI Build Status Semantic Release

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.