Objects matching the expression 'debian'

• #716 puppet 0.23 apt package provider fails to realize ensure => present, when ensure => latest works (0.23, apt, aptitude, debian, package, regression)
• #1060 services not disabled correctly on Debian (debian, service)
• #1161 service provider on Debian doesn't realize a service is disabled (debian, init)
• #1230 facts not (always) set in a puppet run (darwin, debian, facter)
• BootstrappingWithPuppet A functional example based around partial automatic installation and upgrading puppet to a functional version, primarily for Ubuntu but possibly adaptable to other Debian-based distributions. Requirements ------------ * A local apt repository * I use the reprepro package to manage my repository * A quick google found this tutorial http://ianlawrence.info/random-stuff/setting-up-a-personal-debian-repository * Backported packages for $lsbdistrelease, available in said repository. * Ubuntu has a package called prevu for automating the backporting process, take a look at https://wiki.ubuntu.com/Prevu * A trusted.gpg file containing the necessary GPG public keys for said repository, so that apt doesn't complain * A sources.list file containing said repository * The upgradepuppet class below (or similar, adapt as necessary) Usage ----- * Define a node in Puppet for your to-be-bootstrapped machine * Install your Ubuntu machine as per usual, with a preseed or without * Install Puppet from the official repositories (it'll be old, 0.22.something) * Note: These last two steps can be replaced if you can work out how to make a preseed disk with 0.22 installed already, although, why you'd put 0.22 on your disk instead of 0.24.1 beats me..) * Personally here I stop the puppetd daemon (apt-get install puppet && /etc/init.d/puppet stop) and run puppetd --test * Magical things will happen! Packages will be upgraded, Puppet will be started, then stopped and disabled. * Using a case statement in your node (see below) normal operations will continue. upgradepuppet class +++++++++++++++++++ This is the upgradepuppet class:: class upgradepuppet { file { "/etc/apt/sources.list": source (automatic, bootstrap, centos, cobbler, debian, epel, kickstart, recipe, repository, rhel, ubuntu)
• DebianUnstablePackages? (debian, installation, packages, unstable)
• PuppetDebian Running Puppet on Debian (debian, installation, packages, puppet, testing, unstable)
• PuppetWithRunit Puppet With Runit (debian, documentation, restart, runit, service, start, starting, stop)
• 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/Vim VIM recipe (debian, puppet, recipe, vim)
• StablePlatforms Puppet can work well under a broad range of operating systems and system configurations. Below is a brief list of configurations with reported successes. If you have an operational configuration that isn't listed here, please add it to the list: - CentOS 4/Linux 2.6 (x86_64, i386, VMWare ESX 32-bit) - CentOS 5/Linux 2.6 (athlon, i386, VMWare ESX 32-bit) - Darwin 8.9.1 (PowerPC, i386) - Debian 3.1/Linux 2.6 (i386, amd64) - Debian 4.0/Linux 2.6 (i386, xen686, amd64) - Fedora Core 2 (i386) - Fedora Core 3 (i386) - Fedora Core 4 (i386) - Fedora Core 5 (i386) - Fedora Core 6 (i386) - Fedora Core 7 (i386) - Fedora Core 8 (i386) - FreeBSD 4.7 (i386) - FreeBSD 6.0 (i386) - Gentoo Linux (x86_64) - Mandriva Corporate Server 4 (i586) - OpenBSD 4.1 (i386) - OpenBSD 4.2 (i386) - OpenBSD 4.3 (i386) - Oracle Linux 4 (x86_64) - RHEL 3 ES (VMWare ESX 32-bit) - RHEL 4 ES,AS (i386, x86_64) - RHEL 5 (i386, x86_64) - Sun Solaris 2.6 (i386, sparc) - Sun Solaris 7 (i386, sparc) - Sun Solaris 8 (i386, sparc) - Sun Solaris 9 (i386, sparc) - Sun Solaris 10 (i386, x86_64, sparc64) - SuSE Linux 8/Linux 2.4 (i386) - SuSE Linux Enterprise Desktop 10/Linux 2.6 (i586) - SuSE Linux Enterprise Server 10/Linux 2.6 (i586) - SuSE Linux Enterprise Server 9/Linux 2.6 (i586, x86_64) - Ubuntu 7.04 Feisty GNU/Linux 2.6 (i686, xen686) Platform-Specific Pages (compatibility, debian, os, osx, platform, redhat, suse, ubuntu)
• 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, server)