Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

tigervnc

Puppet module for managing the installation and configuration of the tigervnc server.
Project URLRSS FeedReport issues

5,786 downloads

5,616 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.0.1 (latest)
  • 1.0.0
released Sep 1st 2018
This version is compatible with:
  • Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.7.0 < 6.0.0
  • ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'millerjl1701-tigervnc', '1.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add millerjl1701-tigervnc
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install millerjl1701-tigervnc --version 1.0.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

millerjl1701/tigervnc — version 1.0.1 Sep 1st 2018

tigervnc

master branch: Build Status

Table of Contents

  1. Module Description - What the module does and why it is useful
  2. Setup - The basics of getting started with tigervnc
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Module Description

This module installs, configures, and manages the tigervnc-server vncserver service.

By default, it will set the vnc session password for each user to the same password but allows for the user to change their own password as they choose. Alternatively, one can set different vnc session passwords per user. Either allows for the vncserver service(s) to startup correctly on the very first application of the module.

This module makes no assumptions for user authentication via XDMCP at this time.

This module assumes that you are not going to use xinetd for management of the service at this time.

If you prefer to use the xinetd/XDMCP method referenced in the documentation, please consider using the simp/vnc module.

For more details on the TigerVNC project, please see http://tigervnc.org/.

For reference, the tigervnc-server installation and configuration documentation for RedHat is located at:

This module is currently written to support CentOS/RedHat 6/7 operating systems. Other operating systems could be added if time permits (Pull requests are welcome. :)

Setup

What tigervnc affects

  • Package: tigervnc-server
  • File: /etc/sysconfig/vncservers (CentOS/RedHat 6)
  • File: /etc/systemd/system/vncserver@:displaynumber.service (CentOS/RedHat 7)
  • File: /home/username/.vnc (Managed by default. This can be disabled)
  • File: /home/username/.vnc/passwd (Managed by default. This can be disabled)
  • Service: vncserver (CentOS/RedHat 6)
  • Service: vncserver@:displaynumber.service (CentOS/RedHat 7)

Setup Requirements

The user(s) that the vncserver will be run as must exist on the system prior to the tigervnc class being called. However, no assumption is made on how that user is created on the system- just that it exists. For a puppet way of managing users, one could use the rberwald/accounts, and then you would likely want to setup in puppet code (site.pp or elsewhere) something similar to:

    Class['accounts'] -> Class['tigervnc']

to ensure proper resource ordering.

For CentOS/RedHat 7, this module depends on the camptocamp/systemd module for management of the systemd unit file and systemd daemon-reload process.

This module configures tigervnc-server using system service resources. If you prefer using xinetd for management of the vncserver processes, please consider using the simp/vnc module instead.

Beginning with tigervnc

To install, configure and manage the tigervnc-server vncserver service for a single user with the basic defaults, one would use the following puppet code:

  class { 'tigervnc':
    vncservers => {
      'user1' => {
        displaynumber => '1',
      },
    },
  }

which will launch a vncserver service process for the user "user1" listening at 0.0.0.0:5901.

Usage

All parameters to the main class may be passed via puppet code or hiera.

Note: the Puppet lookup function will by default create a merged hash from hiera data for the tigervnc::sysconfig_vncservers parameter. It is possible to override the merge behavior in your own hiera data; however, this has not been tested and could create unanticipated results.

Some futher examples that one could do with the class.

Disable the management of vncpasswd files per user

  class { 'tigervnc':
    manage_vncuser_passwords => false,
    vncservers               => {
      'user1' => {
        displaynumber => '1',
      },
    },
  }

Note: If one disables the class from managing the vncpasswd files, the vncserver service(s) will not start until the password file is created via other means.

Specify a default vncpasswd for all users

  class { 'tigervnc':
    vncuser_default_passwd => 'SuperDuperPassword',
    vncservers             => {
      'user1' => {
        displaynumber => '1',
      },
    },
  }

Note: While a default password will be created for a user, this module does not manage the vncpasswd file once created. This allows for the user to change their vncpasswd as they desire. If the vnc passwd file is removed at somepoint, the class will recreate a passwd fie with either the default or specified user password.

Specify multiple vnc users

  class { 'tigervnc':
    vncservers             => {
      'user1' => {
        displaynumber => '1',
      },
      'user2' => {
        displaynumber => '2',
      }
    },
  }

and what this looks like in hiera:

---

tigervnc::vncservers:
  user1:
    displaynumber: '1'
  user2:
    displaynumber: '2'

Specify vncserver arguments for a different resolution and to listen on localhost only

  class { 'tigervnc':
    vncservers             => {
      'user1' => {
        displaynumber => '1',
      },
      'user2' => {
        displaynumber => '2',
        'args'        => [
            'geometry 1280x1024',
            'localhost',
        ],
      },
    },
  }

and what this looks like in hiera:

---

tigervnc::vncservers:
  user1:
    displaynumber: '1'
  user2:
    displaynumber: '2'
    args:
      - 'geometry 1280x1024'
      - 'localhost'

Removing a systemd unit file and service (in this example for user2) on CentOS/RedHat 7

  class { 'tigervnc':
    vncservers             => {
      'user1' => {
        displaynumber => '1',
      },
      'user2' => {
        ensure        => 'absent',
        displaynumber => '2',
      }
    },
  }

Reference

Generated puppet strings documentation with examples is available from https://millerjl1701.github.io/millerjl1701-tigervnc.

The puppet strings documentation is also included in the /docs folder.

Public Class

  • tigervnc: Main class which installs, configures, and manages the vncserver service(s)

Private Classes

  • tigervnc::install: Class for installation of the tigervnc-server.
  • tigervnc::config: Class for setting configuration files for the vncserver process(es)
  • tigervnc::service: Class for managing the state of the vncserver process(es)

Limitations

This module currently supports CentOS/RedHat 6/7. In time, other operating systems may be added. Pull requests with tests are welcome!

Development

Please see the CONTRIBUTING document for information on how to get started developing code and submit a pull request for this module. While written in an opinionated fashion at the start, over time this can become less and less the case.

Contributors

To see who is involved with this module, see the GitHub list of contributors or the CONTRIBUTORS document.