bodgit / puppet-dbus Goto Github PK

View Code? Open in Web Editor NEW

0.0 3.0 4.0 156 KB

Puppet Module for managing D-Bus

Home Page: https://forge.puppetlabs.com/bodgit/dbus

License: Apache License 2.0

Ruby 72.00% Puppet 28.00%

puppet dbus

puppet-dbus's Introduction

dbus

Description
Setup - The basics of getting started with dbus
- Beginning with dbus
Usage - Configuration options and additional functionality
Reference - An under-the-hood peek at what the module is doing and how
Limitations - OS compatibility, etc.
Development - Guide for contributing to the module

Description

This module manages D-Bus.

RHEL/CentOS, Ubuntu, Debian and OpenBSD are supported using Puppet 5 or later.

Setup

Beginning with dbus

In the very simplest case, you can just include the following:

include dbus

Usage

To add the oddjob daemon to the system bus:

include dbus

dbus::system { 'oddjob':
  content => file('oddjob/oddjob.conf'),
}

Reference

The reference documentation is generated with puppet-strings and the latest version of the documentation is hosted at https://bodgit.github.io/puppet-dbus/ and available also in the REFERENCE.md.

Limitations

This module has been built on and tested against Puppet 5 and higher.

The module has been tested on:

Red Hat/CentOS Enterprise Linux 6/7/8
Ubuntu 16.04/18.04/20.04
Debian 9/10
OpenBSD 6.9

Development

The module relies on PDK and has both rspec-puppet and Litmus tests. Run them with:

$ bundle exec rake spec
$ bundle exec rake litmus:*

Please log issues or pull requests at github.

puppet-dbus's People

Contributors

Watchers

Forkers

bashton-ajenkins theosotr lsst-it teluq-pbrideau

puppet-dbus's Issues

dbus systemd unit is static

On platforms with systemd the unit managing dbus-daemon appears to always be static, therefore it can neither be disabled or enabled, leading to the following error:

Error: Could not enable messagebus: 
Error: /Stage[main]/Dbus::Service/Service[messagebus]/enable: change from false to true failed: Could not enable messagebus:

A simple fix would be to simply not try and manage the enable attribute on the service when on a platform with systemd.

Use `dbus` instead of `messagebus` on EL7

So despite EL7 having a dbus.service systemd unit with a messagebus.service symlink pointing to it, using the latter does not seem to work properly 100% of the time. Quite often I see the following:

# systemctl is-active messagebus
unknown
# systemctl is-active dbus
active

This behaviour causes the Puppet Service['messagebus'] resource to be started unnecessarily. Rather than try and pick apart why systemd is behaving this way, just use dbus as the default service name on EL7.

Drop old Puppet versions

Handle reloads better

So, systemd does define in the unit file how to reload dbus configuration without having to restart dbus-daemon which seems to cause some dbus services to not reconnect however it's triggered with a systemctl reload {dbus|messagebus}.service. Puppet doesn't (yet) support reloading a service as opposed to restarting it so it won't ever use that hook.

Instead, add a refresh-only exec resource that the configuration can notify and use this regardless of init system in use.

No need to manage the system default configuration

D-Bus now puts the default configuration at /usr/share/dbus-1/{session,system}.conf and /etc/dbus-1/{session,system}.conf are now "empty" files that tell you to put customisation in either {session,system}-local.conf files, or drop fragments as {session,system}.d/*.conf files.

So I can probably drop managing the horrible templated default files now as they're clearly designated as read-only and just manage the files under /etc/dbus-1.