This file contains only general overview of the changes in the DebOps project. The detailed changelog can be seen using git log command.
You can read information about required changes between releases in the Upgrade notes documentation.
debops master - unreleased¶
New DebOps roles:
- debops.docker_registry role provides support for Docker Registry. The role can be used as standalone or as a backend for the GitLab Container Registry service, with debops.gitlab role.
- debops.ldap role sets up the system-wide LDAP configuration on
a host, and is used as the API to the LDAP directory by other Ansible
roles, playbooks, and users via Ansible inventory. The role is included in
common.ymlplaybook, but is disabled by default.
- debops.nslcd role can be used to configure LDAP lookups for NSS and PAM services on a Linux host.
- debops.pam_access role manages PAM access control files located in
/etc/security/directory. The role is designed to allow other Ansible roles to easily manage their own PAM access rules.
- debops.yadm role installs the Yet Another Dotfiles Manager script and ensures that additional shells are available. It can also mirror dotfiles locally. The role is included in the common playbook.
[debops.nginx] The role will automatically generate configuration which redirects short hostnames or subdomains to their FQDN equivalents. This allows HTTP clients to reach websites by specifying their short names via DNS suffixes from
/etc/resolv.conffile, or using
*.localdomain names managed by Avahi/mDNS to redirect HTTP clients to the correct FQDNs.
[debops.resources] Some lists can now configure ACL entries on the destination files or directories using the
item.aclparameter. Take a look to ACL support section to have the list of compatibles variables.
[debops.lxc] Users can now disable default route advertisement in the
lxc-netDHCP service. This is useful in cases where LXC containers have multiple network interfaces and the default route should go through a different gateway than the LXC host.
[debops.lxc] The lxc-new-unprivileged script will add missing network interface stanzas in the container's
/etc/network/interfacesfile, by default with DHCP configuration. This will happen only on the initialization of the new container, when a given LXC container has multiple network interfaces defined in its configuration file.
[debops.ansible_plugins] A new
ldap_attrsAnsible module has been added to the role. It's a replacement for the
ldap_attrcore Ansible module, that's more in line with the
ldap_entrymodule. Used by the debops.slapd and debops.ldap roles to manage the LDAP directory contents.
The DebOps project has been registered in the IANA Private Enterprise Numbers registry, with PEN number
53622. The project documentation contains an OID registry to track custom LDAP schemas, among other things.
bootstrap-ldap.ymlAnsible playbook can be used to bootstrap Debian/Ubuntu hosts with LDAP support enabled by default. The playbook will configure only the services required for secure LDAP access (PKI, SSH, PAM/NSS), the rest should be configured using the common playbook.
[debops.apt][debops.unattended_upgrades] Systems with the End of Life Debian releases (
wheezy) installed will be configured to use the Debian Archive repository as the main APT sources instead of the normal Debian repository mirrors. These releases have been moved out of the main repositories and are not fully available through normal means. The periodic updates of the APT archive repositories on these systems will be disabled since the EOL releases no longer receive updates.
The Debian LTS release (
jessie) APT repository sources will use only the main and security repositories, without updates or backports. See the information about the Debian LTS support for more details.
[debops.resources] New resources__commands variables can be used to define simple shell commands or scripts that will be executed at the end of the debops.resources role. Useful to start new services, but it shouldn't be used as a replacement for a fully-fledged Ansible roles.
[debops.sudo] The role is now integrated with the debops.ldap Ansible role and can configure the sudo service to read
sudoersconfiguration from the LDAP directory.
Updates of upstream application versions:
- [debops.gitlab] The role will install GitLab 11.7 on supported platforms (Debian Buster, Ubuntu Bionic), existing installations will be upgraded.
- [debops.phpipam] The relevant inventory variables have been renamed, check the Upgrade notes for details. The role now uses the upstream phpIPAM repository and it installs version 1.3.2.
- [debops.php] Because of the PHP 7.0 release status changed to End of life at the beginning of 2019, Ondřej Surý APT repository with PHP 7.2 packages will be enabled by default on Debian Jessie and Stretch as well as Ubuntu Trusty and Xenial. Existing debops.php installations shouldn't be affected, but the role will not try to upgrade the PHP version either. Users should consider upgrading the packages manually or reinstalling services from scratch with the newer version used by default.
- [debops.rstudio_server] The supported version has been updated to
v1.2.1335. The role no longer installs
libssl1.0.0from Debian Jessie on Debian Stretch, since the current version of the RStudio Server works in the default Stretch environment. The downloaded
.debpackage will be verified using the RStudio Inc. GPG signing key before installation.
[debops.lxc] The lxc-prepare-ssh script will read the public SSH keys from specific files (
rootkey file, and the
$SUDO_USERkey file) and will not accept any custom files to read from, to avoid possible security issues. Each public SSH key listed in the key files is validated before being added to the container's
The lxc-new-unprivileged script will similarly not accept any custom files as initial LXC container configuration to fix any potential security holes when used via sudo. The default LXC configuration file used by the script can be configured in
[debops.gitlab] The GitLab playbook will import the debops.docker_registry playbook to ensure that configuration related to Docker Registry defined in the GitLab service is properly applied during installation/management.
[debops.php] The PHP version detection has been redesigned to use the apt-cache madison command to find the available versions. The role will now check the current version of the
phpAPT package to select the available stable PHP version. This unfortunately breaks support for the
php5packages, but the
php5.6packages from Ondřej Surý APT repository work fine.
[debops.mariadb_server] The MariaDB user
rootis no longer dropped. This user is used for database maintenance and authenticates using the
unix_authplugin. However, DebOps still maintains and sets a password for the
rootUNIX account, stored in the
[debops.netbase] The role will be disabled by default in Docker containers. In this environment, the
/etc/hostsfile is managed by Docker and cannot be modified from inside of the container.
[debops.owncloud] The role will not perform any tasks related to occ command if the automatic setup is disabled in the
owncloud__autosetupvariable. In this mode, the occ tasks cannot be performed by the role because the ownCloud/Nextcloud installation is not finished. The users are expected to perform necessary tasks themselves if they decide to opt-out from the automatic configuration.
[debops.slapd] The role has been redesigned from the ground up, with support for N-Way Multi-Master replication, custom LDAP schemas, Password Policy and other functionality. The role uses custom
ldap_attrsAnsible module included in the debops.ansible_plugins role for OpenLDAP management.
The OpenLDAP configuration will definitely break on existing installations. It's best to set up a new OpenLDAP server (or replicated cluster) and import the LDAP directory to it afterwards. See role documentation for more details.
/etc/mailnameconfiguration file will contain the DNS domain of a host instead of the FQDN address. This will result in the mail senders that don't specify the domain part to have the DNS domain, instead of the full host address, added by the Mail Transport Agent. This configuration should work better in clustered environments, where there is a central mail hub/MX that receives the mail and redirects it.
[debops.root_account] If the debops.ldap Ansible role has been applied on a host, the debops.root_account role will use the UID/GID ranges defined by it, which include UIDs/GIDs used in the LDAP directory, to define subUID/subGID range of the
rootaccount. This allows usage of the LDAP directory as a source of UNIX accounts and groups in unprivileged containers. Existing systems will not be changed.
[debops.system_groups] If the LDAP support is enabled on a host via the debops.ldap role, the UNIX system groups created by the debops.system_groups role by default will use a
_prefix to make them separate from any LDAP-based groups of the same name. Existing installations should be unaffected, as long as the updated debops.system_groups role was applied before the debops.ldap role.
[debops.sshd] The access control based on UNIX groups defined in the
/etc/ssh/sshd_configfile has been removed. Instead, the OpenSSH server uses the PAM access control configuration, managed by the debops.pam_access Ansible role, to control access by users/groups/origins. OpenSSH service uses its own access control file, separate from the global
[debops.sshd] The role will enable client address resolving using DNS by setting the
UseDNS yesoption in OpenSSH server configuration. This parameter is disabled by default in Debian and upstream, however it is required for the domain-based access control rules to work as expected.
[debops.sshd] When the LDAP support is configured on a host by the debops.ldap role, the debops.sshd role will use the resulting infrastructure to connect to the LDAP directory and create the
sshdLDAP account object for each host, used for lookups of the SSH keys in the directory. The SSH host public keys will be automatically added or updated in the LDAP device object to allow for centralized generation of the
~/.ssh/known_hostsfiles based on the data stored in LDAP.
The role will no longer create a separate
sshd-lookupUNIX account to perform LDAP lookups; the existing
sshdUNIX account will be used instead. The ldapsearch command used for lookups will default to LDAP over TLS connections instead of LDAPS.
[deops.unattended_upgrades] The packages from the
stable-updatesAPT repository section will be automatically upgraded by default, the same as the packages from Debian Security repository. This should cover important non-security related upgrades, such as timezone changes, antivirus database changes, and similar.
[debops.php] The role will install the composer command from the upstream GitHub repository on older OS releases, including Debian Stretch (current Stable release). This is due to incompatibility of the
composerAPT package included in Debian Stretch and PHP 7.3.
[debops.users][debops.root_account] Management of the
rootdotfiles has been removed from the debops.users role and is now done in the debops.root_account role, using the yadm script. Users might need to clean out the existing dotfiles if they were managed as symlinks, otherwise yadm script will not be able to correctly deploy the new dotfiles.
The management of the user dotfiles in the debops.users role has been redesigned and now uses the yadm script to perform the actual deployment. See debops.yadm for details about installing the script and creating local dotfile mirrors. The users__accounts variable documentation contains examples of new dotfile definitions.
- [debops.auth] The
/etc/ldap/ldap.conffile configuration, nslcd service configuration and related variables have been removed from the debops.auth role. This functionality is now available in the debops.ldap and debops.nslcd roles, which manage the client-side LDAP support.
- [debops.rstudio_server] The role will no longer install the historical
libssl1.0.0APT package on Debian Stretch to support older RStudio Server releases. You should remove it on the existing installations after RStudio Server is upgraded to the newest release.
- [debops.redis_server] Use the
redis.conffile to lookup passwords via the redis-password script. This file has the
redis-authUNIX group and any accounts in this group should now be able to look up the Redis passwords correctly.
- [debops.slapd] The role will check if the X.509 certificate and the private key used for TLS communication were correctly configured in the OpenLDAP server. This fixes an issue where configuration of the private key and certificate was not performed at all, without any actual changes in the service, with subsequent task exiting with an error due to misconfiguration.
- [debops.lvm] Make sure a file system is created by default when the
mountparameter is defined in the
- [debops.lvm] Stop and disable
lvm2-lvmetad.socketsystemd unit when disabling
lvm__global_use_lvmetadto avoid warning message when invoking LVM commands.
- [debops.authorized_keys] Set the group for authorized_keys files to the primary group of the user instead of the group with the same name as the user. This is important because otherwise the readonly mode of the role does not work when the primary group of a user has a different name then the username.
debops v0.8.1 - 2019-02-02¶
New DebOps roles:
- debops.redis_server and debops.redis_sentinel roles, that
replace the existing
debops.redisAnsible role. The new roles support multiple Redis and Sentinel instances on a single host.
- debops.freeradius, an Ansible role that can be used to manage FreeRADIUS service, used in network management.
- debops.dhcp_probe, can be used to install and configure dhcp_probe service, which passively detects rogue DHCP servers.
- debops.mount, the role allows configuration of
/etc/fstabentries for local devices, bind mounts and can be used to create or modify directories, to permit access to resources by different applications. The role is included by default in the
- debops.redis_server and debops.redis_sentinel roles, that replace the existing
[debops.users] The role can now configure ACL entries of the user home directories using the
item.home_aclparameter. This can be used for more elaborate access restrictions.
[debops.root_account] The role will reserve a set of UID/GID ranges for subordinate UIDs/GIDs owned by the
rootaccount (they are not reserved by default). This can be used to create unprivileged LXC containers owned by
root. See the release notes for potential issues on existing systems.
[debops.root_account] You can now configure the state and contents of the
/root/.ssh/authorized_keysfile using the debops.root_account role, with support for global, per inventory group and per host SSH keys.
DebOps roles are now tagged with
skip::<role_name>Ansible tags. You can use these tags to skip roles without any side-effects; for example "<role_name>/env" sub-roles will still run so that roles that depend on them will work as expected.
[debops.ifupdown] The role will now generate configuration for the debops.sysctl role and use it in the playbook as a dependency, to configure kernel parameters related to packet forwarding on managed network interfaces. This functionality replaces centralized configuration of packet forwarding on all network interfaces done by the debops.ferm role.
[debops.lxc] New lxc-hwaddr-static script can be used to easily generate random but predictable MAC addresses for LXC containers.
The script can be run manually or executed as a "pre-start" LXC hook to configure static MAC addresses automatically - this usage is enabled by default via common LXC container configuration.
The lxc_ssh.py Ansible connection plugin is now included by default in DebOps. This connection plugin can be used to manage remote LXC containers with Ansible via SSH and the lxc-attach command. This requires connection to the LXC host and the LXC container via the
rootaccount directly, which is supported by the DebOps playbooks and roles.
[debops.lxc] The role can now manage LXC containers, again. This time the functionality is implemented using the
lxc_containerAnsible module instead of a series of shell tasks. By default unprivileged LXC containers will be created, but users can change all parameters supported by the module.
[debops.lxc] The role will now configure a
lxcbr0bridge with internal DNS/DHCP server for LXC containers, using the
lxc-netservice. With this change, use of the debops.ifupdown role to prepare a default bridge for LXC containers is not required anymore.
[debops.netbase] When a large number of hosts is defined for the
/etc/hostsdatabase, the role will switch to generating the file using the
templateAnsible module instead of managing individual lines using the
lineinfilemodule, to make the operation faster. As a result, custom modifications done by other tools in the host database will not be preserved.
[debops.netbase] The role can now configure the hostname in the
/etc/hostnamefile, as well as the local domain configuration in
Ansible roles included in DebOps are now checked using ansible-lint tool. All existing issues found by the script have been fixed.
The hosts managed by the DebOps Vagrant environment will now use Avahi to detect multiple cluster nodes and generate host records in the
/etc/hostsdatabase on these nodes. This allows usage of real DNS FQDNs and hostnames in the test environment without reliance on an external DHCP/DNS services.
[debops.php] The role will install the
composerAPT package on Debian Stretch, Ubuntu Xenial and their respective newer OS releases.
You can use the make versions command in the root of the DebOps monorepo to check currently "pinned" and upstream versions of third-party software installed and managed by DebOps, usually via git repositories. This requires the uscan command from the Debian
devscriptsAPT package to be present.
The debops.root_account role will be executed earlier in the
common.ymlAnsible playbook to ensure that the
rootUID/GID ranges are reserved without issues on the initial host configuration.
[debops.lxc] The role will configure the default subUIDs and subGIDs for unprivileged LXC containers based on the configured subordinate UID/GID ranges for the
[debops.gitlab] The role will now install GitLab 10.8 by default, on Debian Stretch and Ubuntu Xenial. The 11.x release now requires Ruby 2.4+, therefore it will only be installed on newer OS releases (Debian Buster, Ubuntu Bionic).
[debops.gitlab] The role has been updated to use Ansible local facts managed by the debops.redis_server Ansible role. Redis Server support has been removed from the GitLab playbook and needs to be explicitly enabled in the inventory for GitLab to be installed correctly. This will allow to select between local Server or Sentinel instance, to support clustered environments.
Check the Upgrade notes for issues with upgrading Redis Server support on existing GitLab hosts.
[debops.owncloud] The role will now use Ansible facts managed by the debops.redis_server role to configure Redis support.
[debops.lxc] The lxc-prepare-ssh script will now install SSH public keys from the user account that is running the script via sudo instead of the system's
rootaccount, which is usually what you want to do if other people manage their own LXC containers on a host.
Various filter and lookup Ansible plugins have been migrated from the playbook directory to the debops.ansible_plugins role. This role can be used as hard dependency in other Ansible roles that rely on these plugins.
[debops.grub] The GRUB configuration has been redesigned, role now uses merged variables to make configuration via Ansible inventory or dependent role variables easier. The GRUB configuration is now stored in the
/etc/default/grub.d/directory to allow for easier integration with other software. See the debops.grub documentation for more details.
[debops.grub] The user password storage path in
secret/directory has been changed to use the
inventory_hostnamevariable instead of the
ansible_fqdnvariable. This change will force regeneration of password hashes in existing installations, but shouldn't affect host access (passwords stay the same).
[debops.docker] If the Docker host uses a local nameserver, for example dnsmasq or unbound, Docker containers might have misconfigured DNS nameserver in
127.0.0.1. In these cases, the debops.docker role will configure Docker to use the upstream nameservers from the host, managed by the
If no upstream nameservers are available, the role will not configure any nameserver and search parameters, which will tell Docker to use the Google nameservers.
The test suite will now check POSIX shell scripts along with Bash scripts for any issues via the shellcheck linter. Outstanding issues found in existing scripts have been fixed.
[debops.librenms] The default dashboard in LibreNMS is changed from the
pages/front/tiles.phpwhich allows for better customization.
The order of the roles in the common playbook has been changed; the debops.users role will be applied before the debops.resources role to allow for resources owned by UNIX accounts/groups other than
[debops.gunicorn] The role depends on debops.python now to install the required packages. Please update your custom playbooks accordingly.
[debops.lxc] The LXC configuration managed by the role will use the systemd
lxc@.serviceinstances to manage the containers instead of using the lxc-* commands directly. This allows the containers to be shut down properly without hitting a timeout and forced killing of container processes.
[debops.ipxe] The role will no longer install non-free firmware by default. This is done to solve the connectivity issues with
The hostname and domain configuration during bootstrapping is now done by the debops.netbase Ansible role. The default for this role is to remove the
127.0.1.1host entry from the
/etc/hostsfile to ensure that domain resolution relies on DNS.
If you are using local domain configured in
/etc/hostsfile, you should define the
netbase__domainvariable in the Ansible inventory with your desired domain.
[debops.netbase] The role is redesigned to use list variables instead of YAML dictionaries for the
/etc/hostsdatabase. This allows for adding the host IPv4 and/or IPv6 addresses defined by Ansible facts when the custom local domain is enabled. See netbase__hosts for details. The role has also been included in the
common.ymlplaybook to ensure that the host database is up to date as soon as possible.
[debops.resources] Changed behaviour of used groups for templating. Now all groups the host is in, will be used to search for template files. Read the documentation about resources__templates for more details on templating with debops.
[debops.dnsmasq] The role has been redesigned from the ground up with new configuration pipeline, support for multiple subdomains and better default configuration. See the debops.dnsmasq role documentation as well as the Upgrade notes for more details.
[debops.owncloud] Drop support for Nextcloud 12.0 which is EOF. Add support for Nextcloud 14.0 and 15.0 and make Nextcloud 14.0 the default Nextcloud version.
debopsPython package has dropped the hard dependency on Ansible. This allows DebOps to be installed in a separate environment than Ansible, allowing for example to mix Homebrew Ansible with DebOps from PyPI on macOS. The installation instructions have also been updated to reflect the change.
The debops-init script will now generate new Ansible inventory files using the hostname as well as a host FQDN to better promote the use of DNS records in Ansible inventory.
- [debops.kmod] The role should now work correctly in Ansible
--checkmode before the Ansible local fact script is installed.
- [debops.sysctl] The role should correctly handle nested lists in role dependent variables, which are now flattened before being passed to the configuration filter.
- [debops.grub] The role should now correctly revert custom patch to allow user
/etc/grub.d/10_linuxscript, when the user list is empty.
debops.redisAnsible role has been removed. It has been replaced by the debops.redis_server and debops.redis_sentinel Ansible roles. The new roles use their own Ansible inventory groups, therefore they will need to be explicitly enabled to affect existing hosts.
You can use the debops.debops_legacy Ansible role to clean up old configuration files, directories and diversions of
debops.redisrole from remote hosts.
ldap_attrAnsible modules have been removed. They are now included in Ansible core, there's no need to keep a separate copy in the playbook.
[debops.ferm] Automated configuration of packet forwarding with
FORWARDchain rules and sysctl configuration has been removed from the role. Per-interface packet forwarding is now configurable using the debops.ifupdown role, and you can still use the debops.ferm and debops.sysctl roles to design custom forwarding configuration.
ansible_local.root.uuidlocal facts have been removed. They are replaced by
ansible_local.uuidlocal facts, respectively.
The hostname and domain configuration has been removed from the debops.bootstrap role. This functionality is now handled by the debops.netbase role, which has been included in the bootstrap playbook. The relevant inventory variables have been renamed, check the Upgrade notes for details.
resources__group_namevariable has been removed in favor of using all the groups the current hosts is in. This change has been reflected in the updated variable
debops v0.8.0 - 2018-08-06¶
- New DebOps roles:
- debops.netbase: manage local host and network database in
- debops.sudo: install and manage sudo configuration on
a host. The role is included in the
- debops.system_groups: configure UNIX system groups used on DebOps
hosts. The role is included in the
- debops.debops_legacy: clean up legacy files, directories, APT packages or dpkg-divert diversions created by DebOps but no longer used. This role needs to be executed manually, it's not included in the main playbook.
- debops.python: manage Python environment, with support for multiple
Python versions used at the same time. The role is included in the
- Icinga 2 support has been implemented with debops.icinga, debops.icinga_db and debops.icinga_web Ansible roles.
- debops.netbase: manage local host and network database in
- [debops.users] Selected UNIX accounts can now be configured to linger when
not logged in via the
item.lingerparameter. This allows these accounts to maintain long-running services when not logged in via their own private systemd instances.
- [debops.sudo] You can now manage configuration files located in the
/etc/sudoers.d/directory using sudo__*_sudoers inventory variables, with multiple level of conditional options.
- [debops.ntp] The OpenNTPD service will now properly integrate the ifupdown hook script with systemd. During boot, NTP daemon will be started once network interfaces are configured and will not restart multiple times on each network interface change.
- [debops.resources] The role can now generate custom files using templates, based on a directory structure. See resources__templates for more details.
- [debops.nginx] A
defaultset of SSL ciphers can be specified using the
nginx_default_ssl_ciphersvariable. This disables the
ssl_ciphersoption in the nginx configuration and forces the server to use the defaults provided by the OS.
- [debops.dhparam] The role will set up a systemd timer to regenerate Diffie-Hellman parameters periodically if it's available. The timer will use random delay time, up to 12h, to help with mass DHparam generation in multiple LXC containers/VMs.
- The DebOps installation now depends on the dnspython Python library. This
allows usage of the
digAnsible lookup plugin in DebOps roles to gather data via DNS SRV records.
- The DebOps installation now depends on the future Python library which provides compatibility between Python 2.7 and Python 3.x environments. It is currently used in the custom Ansible filter plugin provided by DebOps, but its use will be extended to other scripts in the future to make the code more readable.
- The editor alternative symlink configuration has been moved from
debops.consolerole to the debops.apt_install role which also installs vim by default.
- The configuration of automatic removal of APT packages installed via
Suggests:dependencies has been moved from the debops.apt role to the debops.apt_mark role which more closely reflects its intended purpose. Variable names and their default values changed; see the Upgrade notes for more details.
- [debops.owncloud] Support Nextcloud 13 and partially ownCloud 10. Nextcloud 11 and ownCloud 9.1 are EOL, you should update. The role can help you with the update to ensure that everything works smoothly with the new versions. Currently, the role can not do the update for you.
- [debops.sshd] The role will now check the debops.system_groups Ansible local facts to define what UNIX groups are allowed to connect to the host via the SSH service.
- [debops.nodejs] The NPM version installed by the role from GitHub is changed
latestwhich seems to be an equivalent of a stable branch.
- Some of the existing DebOps Policies and Guidelines have been reorganized and the concept of DebOps Enhancement Proposals (DEPs) is introduced, inspired by the Python Enhancement Proposals.
[debops.ifupdown] The debops.kmod role is added as a dependency. The debops.ifupdown role will generate modprobe configuration based on the type of configured network interfaces (bridges, VLANs, bonding) and the kernel modules will be automatically loaded if missing.
[debops.nodejs] Recent versions of NPM require NodeJS 6.0.0+ and don't work with other releases. Because of that the newest NPM release is not installable on hosts that use NodeJS packages from older OS releases.
The 'debops.nodejs' role will install NPM v5.10.0 version in this case to allow NPM to work correctly - on Debian Jessie, Stretch and Ubuntu Xenial. Otherwise, a NPM from the
latestbranch will be installed, as before.
[debops.nodejs] Instead of NodeJS 6.x release, the role will now install NodeJS 8.x release upstream APT packages by default. This is due to the NodeJS 6.x release switching to a Maintenance LTS mode. NodeJS 8.x will be supported as a LTS release until April 2019.
[debops.nodejs] The role will install upstream NodeSource APT packages by default. This is due to no security support in Debian Stable, therefore an upstream packages should be considered more secure. The upstream NodeJS packages include a compatible NPM release, therefore it won't be separately installed from GitHub.
The existing installations shouldn't be affected, since the role will select OS/upstream package versions based on existing Ansible local facts.
[debops.gitlab] Redesign the GitLab version management to read the versions of various components from the GitLab repository files instead of managing them manually in a YAML dictionary. The new
gitlab__releasevariable is used to specify desired GitLab version to install/manage.
[debops.gitlab] The gitaly service will be installed using the
gitUNIX account instead of
root. Existing installations might require additional manual cleanup; see the Upgrade notes for details.
[debops.gitlab] The role now supports installation of GitLab 10.7.
[debops.gitlab] The usage of
gitlab__fqdnvariable is revamped a bit - it's now used as the main variable that defines the GitLab installation FQDN. You might need to update the Ansible inventory if you changed the value of the
gitlab_domainvariable used previously for this purpose.
[debops.lxc] Redesign system-wide LXC configuration to use list of YAML dictionaries merged together instead of custom Jinja templates.
[debops.lxc] Add lxc-prepare-ssh script on the LXC hosts that can be used to install OpenSSH and add the user's SSH authorized keys inside of the LXC containers. This is a new way to prepare the LXC containers for Ansible/DebOps management that doesn't require custom LXC template scripts and can be used with different LXC container types.
[debops.core] The role will add any new administrator accounts to the list of existing admin accounts instead of replacing them in the Ansible local fact script. This should allow for multiple administrators to easily coexist and run the DebOps playbooks/roles from their own accounts without issues.
[debops.mariadb_server] [debops.mariadb] The MariaDB/MySQL server and client will now use the
utf8mb4encoding by default instead of the
utf8which is an internal MySQL character encoding. This might impact existing databases, see the Upgrade notes for details.
[debops.unattended_upgrades] On hosts without a domain set, the role enabled all upgrades, not just security updates. This will not happen anymore, the security updates are enabled everywhere by default, you need to enable all upgrades specifically via the
The debops script can now parse multiple playbook names specified in any order instead of just looking at the first argument passed to it.
- [debops.apt_install], [debops.auth]: don't install the
sudopackage by default, this is now done via a separate debops.sudo role to easily support switching to the
- [debops.console] Remove support for copying custom files from the role. This functionality is covered better by the debops.resources role.
- [debops.console] Remove support for managing entries in the
/etc/hostsdatabase. This is now covered by the debops.netbase Ansible role.
- [debops.auth] Remove configuration of UNIX system groups and accounts in the
adminsUNIX group. This is now done by the debops.system_groups Ansible role.
- [debops.bootstrap] The sudo configuration has been removed from
the debops.bootstrap role. The
bootstrap.ymlplaybook now includes the debops.sudo role which configures sudo service.
- [debops.bootstrap] The UNIX system group management has been removed from the
bootstrap.ymlplaybook now uses the debops.system_groups role to create the UNIX groups used by DebOps during bootstrapping.
- [debops.bootstrap] Remove management of Python packages from the role. The
bootstrap.ymlplaybook uses the debops.python role to configure Python support on the host.
- [debops.lxc] Remove support for direct LXC container management from the
role. This functionality is better suited for other tools like
lxc-* set of commands, or the Ansible
lxc_containermodule which should be used in custom playbooks. The 'debops.lxc' role focus should be configuration of LXC support on a host.
- [debops.lxc] Remove custom LXC template support. The LXC containers can be
created by the normal templates provided by the
lxcpackage, and then configured using DebOps roles as usual.
- [debops.postgresql_server] The tasks that modified the default
template1database and its schema have been removed to make the PostgreSQL installation more compatible with applications packaged in Debian that rely on the PostgreSQL service. See the relevant commit for more details. Existing installations shouldn't be affected.
debops v0.7.2 - 2018-03-28¶
- Add missing
python-ldapdependency as an APT package in the Dockerfile.
debops v0.7.1 - 2018-03-28¶
- New DebOps roles:
- debops.ansible: install Ansible on a Debian/Ubuntu host using Ansible. The debops.debops role now uses the new role to install Ansible instead of doing it directly.
- debops.apt_mark: set install state of APT packages (manual/auto) or
specify that particular packages should be held in their current state.
The role is included in the
- debops.kmod: manage kernel module configuration and module loading
at boot time. This role replaces the
debops-contrib.etckeeperrole has been integrated into DebOps as debops.etckeeper. The new role is included in the
- [debops.ifupdown] The role has new tasks that manage custom hooks in other services. First hook is The filter-dhcp-options hook which can be used to selectively apply DHCP options per network interface.
- [debops.lxc] The role will now generate the
lxc-debopsLXC template script from different templates, based on an OS release. This change should help fix the issues with LXC container creation on Debian Stretch.
- The test suite used on Travis-CI now checks the syntax of the YAML files, as well as Python and shell scripts included in the repository. The syntax is checked using the yamllint, pycodestyle and shellcheck scripts, respectively. Tests can also be invoked separately via the make command.
- [debops.etherpad] The role can now autodetect and use a PostgreSQL database as a backend database for Etherpad.
- [debops.pki] The X.509 certificate included in the default
domainPKI realm will now have a SubjectAltName wildcard entry for the host's FQDN. This should allow for easy usage of services related to a particular host in the cluster over encrypted connections, for example host monitoring, service discovery, etc. which can be now published in the DNS zone at
- [debops.pki] The role now supports Let's Encrypt ACMEv2 API via the acme-tiny Python script. The existing PKI realms will need to be re-created or updated for the new API to work, new PKI realms should work out of the box. Check the Upgrade notes for more details.
- [debops.proc_hidepid], [debops.lxc] The roles now use a static GID
procadminsgroup to synchronize the access permissions on a host and inside the LXC containers. You will need to remount the filesystems, restart services and LXC containers that rely on this functionality.
- [debops.sysctl] The configuration of the kernel parameters has been redesigned, instead of being based on YAML dictionaries, is now based on YAML lists of dictionaries and can be easily changed via Ansible inventory. You will need to update your inventory for the new changes to take effect, refer to the role documentation for details.
- [debops.ferm] The role should now correctly detect what Internet Protocols are available on a host (IPv4, IPv6) and configure firewall only for the protocols that are present.
- The debops command will now generate the
ansible.cfgconfiguration file with correct path to the Ansible roles provided with the DebOps Python package.
- [debops.nginx] Fix a long standing bug in the role with Ansible failing during welcome page template generation with Jinja2 >= 2.9.4. It was related to non-backwards compatible change in Jinja that modified how variables are processed in a loop.
debops-contrib.kernel_moduleAnsible role has been removed; it was replaced by the new debops.kmod Ansible role.
- [debops.ferm] The
ferm-forwardhook script in the
/etc/network/if-pre-up.d/directory has been removed (existing instances will be cleaned up). Recent changes in the debops.ferm role broke idempotency with the debops.ifupdown role, and it was determined that the functionality provided by the hook is no longer needed, recent OS releases should deal with it adequately.
debops v0.7.0 - 2018-02-11¶
New Ansible roles have been imported from the
x2go_server. They are not yet included in the main playbook and still need to be renamed to fit with the rest of the
New DebOps roles:
- debops.sysfs: configuration of the Linux kernel attributes through
/sysfilesystem. The role is not enabled by default.
- debops.locales: configure localization and internationalization on a given host or set of hosts.
- debops.machine: manage the
/etc/issuefile and a dynamic MOTD.
- debops.proc_hidepid: configure the
- debops.roundcube: manage RoundCube Webmail application
- debops.prosody: configure an xmpp server on a given host
- debops.sysnews: manage System News bulletin for UNIX accounts
- debops.sysfs: configuration of the Linux kernel attributes through the
You can now use Vagrant to create an Ansible Controller based on Debian Stretch and use it to manage itself or other hosts over the network.
You can now build an Ansible Controller with DebOps support as a Docker container. Official Docker image is also available, automatically rebuilt on every commit.
You can now install DebOps on Arch Linux using an included
Add new playbook,
agent.yml. This playbook is executed at the end of the main playbook, and contains applications or services which act as "agents" of other services. They may contact their parent applications to report about the state of the host they are executed on, therefore the agents are installed and configured at the end of the main playbook.
[debops.libvirtd] The role can now detect if nested KVM is enabled in a particular virtual machine and install KVM support.
DebOps roles and playbooks can now be tested using local or remote GitLab CI instance, with Vagrant, KVM and LXC technologies and some custom scripts.
DebOps roles and playbooks will be included in the Python packages released on PyPI. This will allow for easier installation of DebOps via pip (no need to download the roles and playbooks separately) as well as simple stable releases. The DebOps monorepo can still be installed separately.
[debops-tools] The debops-update script will now install or update the DebOps monorepo instead of separate
debops-playbooksand DebOps roles git repositories. Existing installations shouldn't be affected.
[debops-tools] The debops script will now include the DebOps monorepo roles and playbooks in the generated
ansible.cfgconfiguration. The monorepo roles and playbooks are preferred over the old
The script is backwards compatible and should work correctly with or without the
debops-playbooksrepository and roles installed.
The project repository is tested using pycodestyle for compliance with Python's PEP8 Style Guide.
npmpackage has been removed from Debian Stable. The role will now install NPM using the GitHub source, unless upstream NodeJS is enabled, which includes its own NPM version.
[debops.gunicorn] Update the role to work correctly on Debian Stretch and newer releases. The support for multiple gunicorn instances using custom Debian scripts has been removed in Debian Stretch, therefore the role replaces it with its own setup based on systemd instances.
[debops.gitlab_runner] The GitLab Runner playbook is moved to the
agent.ymlplaybook; it will be executed at the end of the main playbook and should that way include correct information about installed services.
Improved Python 3 support in the DebOps scripts and throughout the playbooks/roles. DebOps should now be compatible with both Python versions.
- [DebOps playbooks] Remove the
ipaddr.pyAnsible filter plugin, it is now included in the Ansible core distribution.
- [debops.console] Remove the
localesconfiguration from the 'debops.console' role, this functionality has been moved to the new 'debops.locales' role. You will need to update the Ansible inventory variables to reflect the changes.
- [debops.console] Remove management of the
/etc/motdfiles from the
debops.consolerole. That functionality is now available in the debops.machine role. You will need to update the Ansible inventory variables to reflect the changes.
- [debops.console] Management of the
hidepid=option has been moved to a new role, debops.proc_hidepid. You will need to update the Ansible inventory variables to reflect the changes.
- [debops.console] Management of the System News using the
sysnewsDebian package has been removed from the role; it's now available as a separate debops.sysnews Ansible role. You will need to update the Ansible inventory variables related to System News due to this changes.