4d68d23f51
We do mainatain set of systemd roles, that allow to easily provision extra services, mounts or even networks and used quite widely across roles. This way we can ease lives of deployers and need of maintaining external playbooks and roles that will do basically same. Feature for a way to create/manage internal networking was also asked for quite a while amoung users. Systemd-service role can also be used to define post/pre hooks for configured networks and systemd_mount can be usefull to setup a shared filesystems for image or volume conversion directories to avoid running out of diskspace on controllers. Change-Id: Ia13f7747696db5b7b7640df7532c6d55627bdd01
24 lines
1.1 KiB
YAML
24 lines
1.1 KiB
YAML
---
|
|
prelude: >
|
|
It is now possible to create and manage third-party services,
|
|
mount points and networks on hosts managed by OpenStack-Ansible.
|
|
This also inlcudes networks, that are required for OpenStack-Ansible
|
|
installation, like br-mgmt or br-storage.
|
|
In order to configure specific resources on selected set of hosts,
|
|
usage of group_vars or host_vars is appreciated.
|
|
features:
|
|
- |
|
|
Added new varaibles that allow users to configure extra systemd
|
|
services, networks or mounts on openstack hosts. While services and
|
|
mounts can be configured on any targeted hosts, networks will be created
|
|
only on bare metal nodes. In order to configure extra networks in
|
|
containers please reffer to ``openstack_user_config.yml`` documentation.
|
|
A list of new variables that were added:
|
|
|
|
* openstack_hosts_systemd_mounts
|
|
* openstack_hosts_systemd_networkd_devices
|
|
* openstack_hosts_systemd_networkd_networks
|
|
* openstack_hosts_systemd_networkd_prefix
|
|
* openstack_hosts_systemd_services
|
|
* openstack_hosts_systemd_slice
|