similar to: Config files based on rpm version

I''m trying to write a script that runs command based on version of Redhat OS. For example, if the RHEL version is 6.0, it will run command. I was able to write file read script in ruby that would read file and execute but it didn''t seem to work in puppet script. Has anyone done something like this? $redhat_version_file = "/etc/redhat-release" $redhat_version =

Hi. I have the following facts available: # facter | grep oper operatingsystem => CentOS operatingsystemrelease => 6.2 Now, if I wish to use conditionals on these facts, I have to do it like this: case $operatingsystem {} case $::operatingsystemrelease {} I''m puzzled as to why can''t I just use $operatingsystemrelease, and what do these two semicolons mean? Thank

Hello, I am running puppet server version 0.25.4-2, and since Debian squeeze is the new stable release I would like to adapt some of my modules. I have a syslog-ng module, I would like to specify another template for my squeeze server. I changed my init.pp as follow : if ($operatingsystemrelease <= 5.0.8) { $syslog_template = "syslog/syslog-ng.conf.erb" } else {

Hi all, I''ve finally gotten around to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic

Hi all, I''m looking at changing the operatingsystemrelease fact for Red Hat. Linux currently just uses the kernel release as the operating system release, but I''ve got a client who wants the release to have both the specific distro (e.g., AS or EL) and the release (e.g., 3 or 4). Will this particularly annoy anyone? Anyone want to help make the release string work on

Currently, facter returns the kernel version as both the kernel and operatingsystemrelease facts. I would like to change that so that on Fedora, operatingsystemrelease is the release number (5,6,7 etc.) or ''Rawhide'' ... are there any objections to making that change ? David

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

Hello guys :), I''m kind of new to Puppet and stuck in defining a conditional statement. Here my problem: I want to provide different apt/source.list for different versions of Debian, 6.0.x and 7.0.x, which also run different versions of Puppet, 2.7.x and 3.2.x. My first idea was to use facters variable operatingsystemmajrelease and define like this: file {

From looking at the Facter code, it looks like the ''operatingsystemrelease'' fact is currently a mirror of the ''kernelrelease'' fact. I''d like to implement this fact so that it returns the major version of the operating system, eg: Debian Sarge: operatingsystemrelease => 3.1 Debian Etch: operatingsystemrelease => 4.0 RHEL3 update 8:

Hello All, How do I specify a variable that has a space in it? I''m trying to setup a yum repo that has two different baseurl''s based on the product name ($productname). Default goes one way, but if the product is "PowerEdge 2650" then is a different URL. The thing is, that is only picking up the default. How should I specify the value with the space in the

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

Hi all, I''m trying to work with hiera database in puppet and i''m having problems using %{variables} because they don''t get the values and i don''t know why. file hiera.yaml: cat hiera.yaml --- :backends: - yaml - puppet :hierarchy:- nodes/%{domain}/%{hostname} - os/%{operatingsystem}/%{operatingsystemrelease} -

I am writing my first module for ntp, I have a few different versions of Linux and also releases. The code worked when I only had one flavor of Linux but now I have four and possibly more flavors. My snippet that doesn''t work is as follows; ( I am not even sure this is the route I should be going if anyone has a better way please advise. Thank you in advance) $ntp_service = $ntpdaemon {

I''ve installed facter-1.6.0 and puppet-2.7.3 on a number of SLES 10 hardware nodes (HP DL580) running the Virtuozzo hosting software. Well, facter correctly identifies such a machine as a hardware node ("virtual => openvzhn") but somehow concludes that the hardware node is in fact virtual. ("is_virtual => true") This breaks some rather important logic. If

I am unable to get the #includedir function to work with sudo. This works just fine on all my CentOS 5.6 servers, but on 6 it is being ignored. I have this line in the file /etc/sudoers.d/zabbix-puppet zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet However sudo still requires a password. If I put that same line into /etc/sudoers file , there is no password prompt. At the end of my

Hi, i want to use Puppet to install all packages from a webserver (no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":}

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate

Hi All, In the example42 modules, I noticed the following is done: # Calculate OS version (without using lsb facts) $ossplit=split($operatingsystemrelease, ''[.]'') $osver=$ossplit[0] I''ve been using $lsbmajdistrelease in all my configs. Is there any particular reason why I might want to use the above instead? (apart from the dependency on redhat-lsb, which is

dears. I can not solved the problem: vzctl works. But how do I connect to Virtuozzo? Using the openvz >> > driver >> > it doesn't work out of the box: >> > virsh # connect openvz:///system >> > error: Failed to connect to the hypervisor >> > error: no connection driver available for openvz:///system Why can not I connect to the openvz??? please