Forge Home

pakiti

Pakiti client as a Puppet module

9,887 downloads

9,147 latest version

2.4 quality score

Version information

  • 0.9.3 (latest)
  • 0.9.2
  • 0.9.1
  • 0.9.0
released Jan 29th 2015
This version is compatible with:
  • Puppet Enterprise 3.3.x
  • Puppet 3.3

Start using this module

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

Add this module to your Puppetfile:

mod 'ceritsc-pakiti', '0.9.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ceritsc-pakiti
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ceritsc-pakiti --version 0.9.3

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
Tags: pakiti

Documentation

ceritsc/pakiti — version 0.9.3 Jan 29th 2015

Puppet Pakiti module

This module gets list of installed software via supported package manager and sends them to your patch monitoring service Pakiti (old web http://pakiti.sourceforge.net/).

Requirements

Module has been tested on:

  • Puppet 3.4 and Facter 2.x (structured facts support is required!)
  • OS:
  • Debian 6,7
  • RHEL/CentOS 6
  • SLES/SLED 11 SP3

Required modules:

Note: basic functionality should be available on any platform and package manager supported by Puppet itself.

Quick Start

Setup client

include pakiti

Full configuration options:

class { 'perun':
  packages       => $::packages,  # hash with list of packages
  servers        => ['...'],      # list of Pakiti server names
  server_path    => '/feed/',     # server URL path
  host           => '...',        # reported hostname
  organization   => '...',        # reported organization (tag)
  site           => '...',        # reported site
  os             => '...',        # reported OS
  arch           => '...',        # reported architecture
  kernel         => '...',        # reported running kernel
  report         => false|true,   # report back vulnerable packages?
  stringify_fail => false|true,   # fail or err when $packages is not hash
  send_fail      => false|true,   # fail or err on send error
  debug          => false|true,   # debug send request
}

Example:

class { 'perun':
  servers   => ['pakiti.localdomain:443'],
  report    => false,
  send_fail => false,
}

Standalone run

puppet apply --no-stringify_facts -e "class {'pakiti': servers => ['pakiti.localdomain:443'] }"

Full example:

mkdir -p ~/.puppet/modules/
git clone https://github.com/puppetlabs/puppetlabs-stdlib.git ~/.puppet/modules/stdlib
git clone https://github.com/CERIT-SC/puppet-pakiti.git ~/.puppet/modules/pakiti
puppet apply --no-stringify_facts -e "class {'pakiti': servers => ['pakiti.localdomain:443'] }"

CERIT Scientific Cloud, support@cerit-sc.cz