Objects matching the expression 'puppet'

• #526 [PATCH] null schedule, a schedule that will never run. (puppet, schedules)
• #595 puppet choke on non english LANG settings (facter, lang, puppet)
• #704 schedule failing in 0.23.0 (puppet)
• #1010 puppet/puppetmaster randomly corrupts file{} resources, seemingly after leaking RAM for some time (corrupt, file, puppet, puppetmaster)
• #1073 --show_diff is not implied by --noop (noop, puppet, show_diff)
• #1240 Graphing does not work with puppet (as opposed to puppetd) (graph, graphing, puppet)
• AptKeys? (puppet, recipe)
• BracketEditor The Bracket Editor (design, proposal, puppet)
• CodeNames Puppet code names (development, documentation, download, package, planned, puppet)
• CompleteConfiguration Complete Configuration (complete, configuration, module, modules, puppet, recipe)
• CookBook (cookbook, puppet)
• DevelopmentLifecycle The Puppet Development Life Cycle (buildbot, cycle, development, git, lifecycle, puppet, repository, tickets)
• DocumentationStart Puppet Documentation (documentation, index, puppet, start.)
• DownloadingPuppet (documentation, download, install, puppet, source)
• FrequentlyAskedQuestions Puppet is an open-source next-generation server automation tool. It is composed of a declarative language for expressing system configuration, a client and server for distributing it, and a library for realizing the configuration. The primary design goal of Puppet is that it have an expressive enough language backed by a powerful enough library that you can write your own server automation applications in just a few lines of code. With Puppet, you can express the configuration of your entire network in one program capable of realizing the configuration. The fact that Puppet has open source combined with how easily it can be extended means that you can add whatever functionality you think is missing and then contribute it back to the main project if you desire. For more about the capabilities of Puppet, take a look at the documentation_. [back_] Who maintains this FAQ and where can I find an updated version? (asked, certificates, configuration, docs, facter, faq, frequently, gpl, graphing, installation, manifests, puppet, questions, tls)
• IrcChannel Pasting configuration files (IRC, documentation, puppet, support)
• Lab42Infrastructure Lab42 Puppet Infrastructure (infrastructure, lab42, module, modules, puppet, recipe)
• ManagedByPuppet (applications, apps, managed, modules, puppet, recipes, software, solutions)
• MultipleCertificateAuthorities NOTE (SSL, certificates, documentation, puppet, security)
• PuppetBookErrata (book, errata, james, pulling, puppet, strings, turnbull)
• PuppetDebian Running Puppet on Debian (debian, installation, packages, puppet, testing, unstable)
• PuppetIntroduction Introduction to Puppet (documentation, introduction, puppet)
• PuppetMacOSX Puppet on Mac OS X (documentation, osx, package, provider, puppet)
• PuppetPresentations (luke, presentation, puppet, slides, video)
• PuppetRecipes Recipes for configuring Puppet (puppet)
• PuppetRedHatCentos A lot of work has gone into support of these highly popular platforms. Since yum appears to be the wave of the future, community member David Lutterkort maintains a yum repository_ for users of Red Hat?, CentOS and other compatible strains of UNIX. This repository is kept up-to-date, so the version available there should be sufficient for most purposes. If you find that a newer version than what is available from the _unstable tree is required, please refer to the instructions_ for building Puppet from the Git repository. Compatability (centos, installation, os, puppet, redhat, rhel)
• PuppetScalability Puppet Scalability Notes (performance, puppet, puppetmasterd, recipe, scalability, speed.)
• PuppetScripts? (puppet, ruby)
• PuppetVersioning Major ----- Any revision which: * adds major functionality Minor ----- Any revision which: * adds minor functionality evident to the user * adds major functionality not evident to the user Release ------- Any revision which: * adds/removes/modifies parameters * deprecates parameters or syntax, or * changes file formats Build ----- Every change committed to Git has a unique ID. Scheme B: MAJOR.MINOR.RELEASE (0.22.4) (development, puppet, version, versioning)
• Recipes/AmazonWebService Amazon Web Service Recipes (Amazon, puppet, recipe)
• Recipes/AptKeys Recipe for managing apt gpg keys (apt, aptkets, keys, puppet, recipe, recipes)
• Recipes/Apt_Repositories Recipe for Mixing In Multiple apt Repositories (puppet, recipe)
• Recipes/AqueosShorewall Aqueos Shorewall Recipe (aqueos, puppet, recipe, shorewall)
• Recipes/Asterisk This is mode for installing asterisk, libpri, zaptel and app_rxfax/app_txfax. It is very Debian specific, since it has to build the zaptel kernel module. It also requires small ruby function_ to get the kernel version without the architecture for the linux-kbuild package. $libdir/parser/functions/kernelversion.rb:: module Puppet::Parser::Functions newfunction(:kernelversion, :type (Asterisk, puppet, recipe)
• Recipes/Authorized_keys Authorized_keys Recipe (authorized_keys, puppet, recipe, ssh)
• Recipes/Autofs AutoFS Recipe (autofs, puppet, recipe)
• Recipes/CentralizedSudoers Centralised sudoers recipe (puppet, recipe, sudo, sudoers)
• Recipes/ClamAV ClamAV Antivirus Recipe (ClamAV, puppet, recipe)
• Recipes/Debian Operating System Release Management (Debian, puppet, recipe)
• Recipes/DebianApache2Recipe Recipe for Apache2 on Debian (Etch) (apache2, components, debian, puppet, recipe)
• Recipes/DebianPreseed Managing Debian packages using debconf preseed (debian, linux, package, preseed, puppet, recipe)
• Recipes/DownloadFileRecipe Download 1 or more Files (download, file, puppet, recipe)
• Recipes/FilePermissionCheck File Permissions Check Recipe (file, permissions, puppet, recipe)
• Recipes/FirmwarePassword Working with Passwords and other sensitive data with exec (password, passwords, puppet, recipe)
• Recipes/Fonts Font Installation Recipe (fonts, puppet, recipe)
• Recipes/HighAvailability High Availability Recipe (availability, puppet, recipe)
• Recipes/KernelModules Kernel Modules (kernel, linux, modules, puppet, recipe)
• Recipes/LDAPClientNSSwitch LDAP Client NSSwitch recipe (LDAP, nsswitch, puppet, recipe)
• Recipes/ModuleIptables The iptables module illustrated will help administer iptables rules. There are essentially three parts: the module manifest_, which declares an iptables class and a defined-type for adding fragments, the rebuild-iptables_ script that rebuilds the iptables rules when a fragment is added or removed, and an area for fragments_. .. _module manifest: modules/iptables/manifests/init.pp :: # Handles iptables concerns. See also ipt_fragment definition define ipt_fragment($ensure) { case $ensure { absent: { file { "/etc/iptables.d/$name": ensure (iptables, network, puppet, recipe)
• Recipes/MutualRestart Mutual Restart Recipe (puppet, recipe, restart)
• Recipes/MySQLServer Install MySQL server and set root password (MySQL, database, puppet, recipe)
• Recipes/MySQLStoredConfiguration MySQL Server Recipe for Stored Configuraton (MySQL, configuration, database, puppet, recipe, stored)
• Recipes/NFS Purpose (NFS, file, puppet, recipe, recipes)
• Recipes/Nagios This module contains two classes, one for an NRPE client (set up for Debian and FreeBSD), and one for the Nagios server (Debian): modules/nagios/manifest/init.pp:: class nagios-nrpe { case $operatingsystem { "freebsd": { $nrpeservice (nagios, nrpe, puppet, recipe)
• Recipes/OpenNTPD OpenNTPD Recipe (NTP, openntpd, puppet, recipe)
• Recipes/PasswordManagement Password Management (password, passwords, puppet, recipe)
• Recipes/Pkgsync Pkgsync (pkgsync, puppet, recipe)
• Recipes/RailsMongrelApacheProxybalancer Rails stack recipe (apache, mongrel, puppet, rails, recipe)
• Recipes/RdiffBackup rdiff-backup recipe (puppet, rdiff-backup, recipe)
• Recipes/ResolvConf resolv.conf recipe (network, puppet, recipe, resolv.conf)
• Recipes/ShowNodeObjects This script accepts a host name and produces a list of objects in manifest syntax associated with that host. It is meant to be run on the puppetmaster host. By default only the 'hostname' fact is supplied but other facts can be specified by using the '--fact` option (multiple times if needed). If the argument to '--fact' does not contain a ' (node, nodes, puppet, recipe)
• Recipes/SimpleText Simple Text edits (puppet, recipe, text)
• Recipes/Solaris_cde-login Solaris CDE login recipe (CDE, login, puppet, recipe, solaris)
• Recipes/SubversionIntegration I have published my code for creating and checking out Subversion repositories as a module_. It's pretty easy to use:: import 'subversion/svnrepo' # Creates the repository at /var/lib/svn/puppet svnrepo { puppet: path (puppet, recipe, subversion)
• Recipes/SubversionWorkingCopy Manage a Subversion Working Copy (puppet, recipe, subversion)
• Recipes/Sudo Improved sudo recipe (puppet, recipe, sudo, sudoers)
• Recipes/TemplateValidationFunction args[0] checkscript (puppet, recipe, template, validation)
• Recipes/Timezone Timezone Recipe (puppet, recipe, timezone)
• Recipes/TracIntegration I have been managing my trac_ installations with Puppet for a long time, and I've recently converted my code to a module_. Here's how I use it at my site:: import 'trac' Trac { alt (puppet, recipe, trac)
• Recipes/UpdateFromSubversionRepo This is a script/daemon that updates a set of puppetmaster directories(manifests,files,etc) from a subversion repository, and will push those updates to additional puppetmasters via rsync+ssh. It expects the subversion repository to setup in a trunk/tag format(though that's not necessary here, it's just the way that I use it). For instance:: /puppet /puppet/trunk /puppet/trunk/files /puppet/trunk/manifests .... /puppet/tags /puppet/tags/prod-YYYYMMDDHHmmss For the script below to work, /puppet-dev and /puppet-prod must have an initial check done ahead of time. It'll do a "lite" query every 5 seconds, and perform updates if it detects something. This script is most useful if you can't trigger an update via a commit hook. puprepod --------- :: #!/usr/bin/env ruby CHECKFREQ (puppet, recipe, repo, subversion)
• Recipes/UserAndHomedirRecipe Adding a User and their Home directory (homedir, puppet, recipe, user)
• Recipes/VMWareGuest VMware (facter, puppet, recipe, vmware)
• Recipes/Vim VIM recipe (debian, puppet, recipe, vim)
• Recipes/VirtualMachine Virtual Machine Fact (puppet, recipe, virtual, vmware)
• Recipes/WorkstationInheritance Workstation Inheritance Recipe (inheritance, puppet, recipe, workstation)
• Recipes/YumServerBuild Yum Server Build Recipe (puppet, recipe, repo, repos, yum)
• Recipes/ZabbixAgent Zabbix Agent recipe (puppet, recipe, zabbix)
• Recipes/syslog-ng syslog-ng recipe (puppet, recipe, syslog-ng)
• RubySSL-2007-006 2007-006-RubySSL Security Patch (bug, certificates, documentation, faq, puppet)
• SimplestPuppetInstallRecipe Using Puppet is largely about developing the Puppet manifests, which describe the configuration of your system. Once you have Puppet installed (see Installation Guide_ ) on at least one server (the Puppetmaster), and at least one client, you're ready to set up a minimal configuration and get started using Puppet. A Simple Manifest: Managing Ownership of a File (certificates, certs, configuration, puppet, puppetmaster, recipe, ssl, sudo, tutorial)
• SolarisPuppetClientInstallationGuide (install, installation, ldapnodes, puppet, solaris)
• UsingMongrel Alternatively, see: UsingMongrelOnDebian_ UsingMongrelPound_ UsingMongrelNginx_ .. _UsingMongrelOnDebian: Using Mongrel OnDebian .. _UsingMongrelPound: Using Mongrel Pound .. _UsingMongrelNginx: Using Mongrel Nginx Puppet daemons default to using WEBrick for http serving, but puppetmasterd can be used with Mongrel instead. This requires setting up a web proxy in front of Mongrel to handle the SSL connections, and then you can start as many puppetmasterd instances as you need. Note that Puppet uses Mongrel differently than most -- usually, you would have a mongrel_cluster command that managed multiple Mongrel instances. I planned to implement it this way, but it ended up being easier in the short term to stick with puppetmasterd. Please contact me (Luke) if you want to work on getting mongrel_cluster to work with Puppet, as it could be used to manage multiple Mongrel instances at once. See the following diagram which shows how it works: http://reductivelabs.com/trac/puppet/attachment/wiki/UsingMongrel/puppetmaster-mongrel.png Version 0.23.1 or higher of puppetmasterd is required. (Earlier versions couldn't do certificate signing because they didn't support the X-Client-Verify header.) This document only describes setting up Apache as a proxy in front of Mongrel. Any other http proxy should work, as long as it supports validating client certificates. Why You'd Do This ----------------- Mongrel scales much better than WEBrick, at least partially because it allows you to run multiple processes serving the same pool of clients on the same host. WEBrick only uses Ruby's threading, which does not scale beyond one processor, and it appears that WEBrick starts dropping connections beyond about 2 concurrent connections. If you're getting connection-reset or End-of-file errors, you should try Mongrel. As more people try it and it proves to be stable, it will eventually become the preferred serving platform for the master. Apache Configuration -------------------- Here is a complete apache configuration, intended for use only with puppet:: # Jeff Mc Cune? <mccune@math.ohio-state.edu> # 2007-09-14 # # Minimal Apache Configuration for Apache+Mongrel+Puppetmaster # # Host System Setup and Configuration: # - Add puppet/puppet user/group # - Use the following configuration file. # - /Library/Puppet/Generated/Server is owned by puppet/puppet # # - If you have a system which doens't provide Apache 2.2.X packages: # Apache may be built with: # # ./configure --enable-so \ # --enable-ssl (http, mongrel, puppet, puppetmasterd, server)
• UsingMongrelOnDebian This is a complete step-by-step configuration for using Mongrel instead of Webrick on Debian Etch. It uses the Debian Apache2 recipe_ and creates a stand-alone apache server on port 8140 for puppetmaster. You need: 1. The mongrel and libdaemons-ruby1.8 packages from etch-backports_ 2. A stand-alone apache2 configuration for puppetmaster only: Apache Configuration_ 3. An init script for stand-alone apache: Apache init script_ 4. A puppetmaster init script, which starts 10 mongrel processes: Puppetmasterd init script_ 5. And finally, a module called puppet to tie this all together. The module's init.pp file is listed below:: class puppetmaster inherits apache2 { $certname (debian, http, mongrel, puppet, puppetmasterd, recipe, server)
• VersionControlPuppet Keep your Puppet manifests under version control (puppet, recipe, subversion, svn)
• WhosUsingPuppet Organizations using Puppet (people, puppet, testimonials, user)
• WikiStart (documentation, puppet)