Skip to content
This repository has been archived by the owner on Oct 19, 2023. It is now read-only.

Ansible libraries for automating Stonesoft FW Management

License

Notifications You must be signed in to change notification settings

gabstopper/ansible-stonesoft

Repository files navigation

ansible-stonesoft

Documentation Status

This repository provides Ansible modules for configuration and automation of Stonesoft Next Generation Firewall. It uses the smc-python for all operations between the ansible client and the Stonesoft Management Center.

Prerequisites

  • smc-python >= 0.6.0
  • Stonesoft Management Center 6.x
  • API client account with permissions

Installation

Using virtualenv (recommended)

pip install ansible
git clone https://github.com/gabstopper/ansible-stonesoft.git
cd ansible-stonesoft
pip install -r requirements.txt
  • Enable the SMC API within the management center

Once you have installed ansible and the stonesoft libraries, you can run the helper install.py which will copy the ansible library dependencies into your respective ansible paths (docs and module_utils).

Usage

Each ansible run will require a login event to the Stonesoft Management Center to perform it's operations. Since the ansible libraries use smc-python, the login process uses the same session logic.

  • You can provide url and api_key as task parameters
  • You can provide the smc_alt_filepath parameter in the task run to specify where to find the .smcrc file with your stored credentials

If neither of the two above are used, then:

  • Try to find ~.smcrc in users home directory
  • Use environment variables (SMC_ADDRESS, SMC_API_KEY, ...)

If none of the above succeed, the run will fail.

Running playbooks

Before running plays, it's best to explain the architecture used to make the administrative changes.

The Stonesoft Management Center is where modifications to all elements are performed.

Installing the ansible modules can therefore either be done on a client host machine remote from the SMC, or on the SMC itself.

If the ansible modules are installed on a controller that is remote from the SMC, set your inventory to use localhost for the connection.

For example, set your default inventory /etc/ansible/hosts:

localhost ansible_connection=local

Note that the host running the ansible client will still need to connect to the SMC through the smc-python API over the default port 8082/tcp.

The other option is to install the ansible libraries on the SMC server itself and make your ansible runs from the controller client. In this case, the SMC connection can then be done using an SMC url of 127.0.0.1.

More information

All modules provide doc snippets when run from the ansible client:

ansible-doc -s engine

Contributions

If you have requests for additional configuration functionality, please submit an issue request.

About

Ansible libraries for automating Stonesoft FW Management

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages