Ansible role to manage ATOS Hardware Security Module (HSM) client software
f5c86dff4e
With the latest setuptools release (61.0.0) ansible-role-atos-hsm's package build command (python3 setup.py sdist bdist_wheel) started to fail: error: Multiple top-level packages discovered in a flat-layout: ['defaults', 'handlers', 'templates', 'releasenotes']. This issue is mentioned in setuptools bug 3197 [1], and the suggested workaround is to disable auto-discovery by adding 'py_modules=[]' in setup.py. ansible-lint also released a new version (6.0.0), which has new rules that blocks the gate. As a workaround, this patch caps ansible-lint version <6.0.0 to unblock the gate. [1] https://github.com/pypa/setuptools/issues/3197 Change-Id: I3f827b3ed855ff46292dee7b21b74a622adc472d |
||
|---|---|---|
| defaults | ||
| handlers | ||
| releasenotes/notes | ||
| tasks | ||
| templates | ||
| zuul.d | ||
| .ansible-lint | ||
| .gitreview | ||
| AUTHORS | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| vars.yaml.sample | ||
atos-hsm
A role to manage ATOS Hardware Security Module (HSM) client software.
Role Variables
| Name | Default Value | Description |
|---|---|---|
| atos_client_working_dir | /tmp/atos_client_install | Working directory in the target host. |
| atos_client_iso_name | None | Filename for the ATOS Client Software ISO. |
| atos_client_iso_location | None | Full URL where a copy of ATOS Client ISO can be downloaded. |
| atos_client_cert_location | None | Full URL where the client certificate can be downloaded. |
| atos_client_key_location | None | Full URL where the client key can be downloaded. |
| atos_hsms | None | List of one or more HSM devices. |
Requirements
- ansible >= 2.4
Usage
You'll need to set up a temporary HTTP server somewhere that is accessible to the node where this role will be applied. The HTTP server should serve the following:
- ATOS Client Software ISO file.
- HSM Server Certificate file(s).
- HSM Client Certificate file.
- HSM Client Key file associated with the Client Certificate.
Due to the sensitive nature of the Certificate and Key files, you should use TLS encryption and username and passwords to access the HTTP server.
Use the hostname and user/password for your HTTP server for the full URL values that need to be set for this role. See vars.yaml.example.