openvpn-formula

Formula to install and configure openvpn server and client.

Table of Contents

• General notes
• Contributing to this repo
• Available states
  • openvpn
  • openvpn.config
  • openvpn.gui
  • openvpn.adapters
  • openvpn.ifconfig_pool_persist
  • openvpn.network_manager_networks
• Examples
• Notes
• Testing
  • Requirements
  • bin/kitchen converge
  • bin/kitchen verify
  • bin/kitchen destroy
  • bin/kitchen test
  • bin/kitchen login
• Testing with Vagrant
  • Requirements
  • Setup
  • Note
  • bin/kitchen converge
  • bin/kitchen verify
  • bin/kitchen destroy
  • bin/kitchen test
  • bin/kitchen login

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

• openvpn
• openvpn.config
• openvpn.gui
• openvpn.adapters
• openvpn.ifconfig_pool_persist
• openvpn.network_manager_networks

openvpn

Installs OpenVPN.

openvpn.config

Configures OpenVPN client and server. Multiple clients and servers are possible.

openvpn.gui

Configures OpenVPN GUI (Windows only). Sets global registry settings as described here.

openvpn.adapters

Manages TAP-Windows device adapters (Windows only). Ensures that any devices specified with dev_node in pillar exist.

openvpn.ifconfig_pool_persist

Installs and configures an ifconfig_pool_persist file. Used to assign host IPs.

openvpn.network_manager_networks

Don't setup a OpenVPN client service, but add ready-to-use NetworkManager configurations.

Examples

See openvpn/pillar.example.

Notes

This formula does can optionally deploy certificates and keys, but does not generate them. This must be done manually or with another formula.

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 openvpn 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.

Testing with Vagrant

Windows testing is done with kitchen-salt.

Requirements

• Ruby
• Virtualbox
• Vagrant

Setup

$ gem install bundler
$ bundle install --with=vagrant
$ bin/kitchen test [platform]

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

Note

When testing using Vagrant you must set the environment variable KITCHEN_LOCAL_YAML to kitchen.vagrant.yml. For example:

$ KITCHEN_LOCAL_YAML=kitchen.vagrant.yml bin/kitchen test      # Alternatively,
$ export KITCHEN_LOCAL_YAML=kitchen.vagrant.yml
$ bin/kitchen test

Then run the following commands as needed.

bin/kitchen converge

Creates the Vagrant instance and runs the openvpn main state, ready for testing.

bin/kitchen verify

Runs the inspec tests on the actual instance.

bin/kitchen destroy

Removes the Vagrant instance.

bin/kitchen test

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

bin/kitchen login

Gives you RDP access to the instance for manual testing.