Displaying 20 results from an estimated 59 matches for "remotefiles".
Did you mean:
remotefile
2006 Nov 06
2
problem with remotefile definition
Hi,
I''m exploring Puppet and have hit a rather weird problem.
The puppetmaster server is running CentOS4, fully updated, with puppet
installed from the dlutter RPM repo, version 0.20.0-1.el4.
I tried adding the remotefile function definition from
http://reductivelabs.com/projects/puppet/documentation/installation.html
in /etc/puppet/manifests/utils/remotefile.pp but when I start
2007 Mar 07
8
Writing definitions to support changing defaults
What is the right way to write definition so that defaults can be overriden?
$puppetdir = "puppet://$server/files"
define remotefile($source, $owner = "root", $group = "root", $mode =
0644, $backup = false, $recurse = false) {
file { $name:
mode => $mode,
owner => $owner,
group => $group,
backup => $backup,
2006 Dec 18
1
$name causes weird behavior
I tried using $name in this manner:
remotefile { "/etc/auto_direct.local":
mode => 644,
source => "solall/$name"
}
(The remotefile function is handy, BTW)
When I use $name here, instead of specifying the actual path to the
file (solall/etc/auto_direct.local), puppetd ends up making
/etc/auto_direct.local an empty directory.
Shouldn''t $name
2006 Dec 21
7
Overriding types?
"Service and class definitions are scoped just as variable assignments are."
But what about types?
Here''s an example:
class solserver inherits server {
remotefile { "/etc/shadow":
mode => 400, group => staff,
source => "solall/etc/shadow.server"
}
Is it possible to just override the "/etc/shadow" definition for
2007 Jan 10
9
Definition specialization
There was a discussion a while ago about adding inheritance to
definitions. There is a need for a way to specialize parameters while
allowing passing other options. This comes up with remotefile where
it would be nice to have a default server location but not specify all
the parameters (and their defaults) in the definition.
Was there a change to the syntax? Is there a way to accomplish this?
2007 Mar 16
0
My updated remotefile
I recently update my remotefile definitions (others might have already done
so or have been using a better one than mine). I added an ensure parameter
so I could do overrides using remotefile rather than the underlying file:
define remotefile($owner = root, $ignore = ".svn", $group = root, $mode =
644, $source, $backup = false, $recurse = false, $ensure = file) {
$realsource =
2008 Jan 22
2
Could not set file on ensure: undefined method `[]'' for nil:NilClass
Hi,
I had a working puppet setup using version 0.22 until the ruby security
patch bit me. I tried upgrading server and clients to 0.24.1 however my
old manifests don''t seem to work anymore. When I run puppetd on the
client I see lots of messages like:
err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent
2007 Feb 15
2
use of $name
Hello
The following chunk is within a class definition. ${name} is being
exchanged with an empty string:
remotefile { "/${server_xml}":
owner => tomcat, group => tomcat, mode => 600,
source => "${ftoe_src_prefix_dev}${name}.jvm1"
}
However in the following chunk, lower down in the same class
definition, ${name} is being exchanged
2006 Dec 13
3
FreeBSD Ports, remotefile() problem
Howdy,
Found out about this project while looking for via ONLamp''s FreeBSD
build system article. After finding cfengine a tad arcane, this project
seems like a good fit for my setup. I''m still at the tinkering phase,
but I envision this thing bootstrapping and maintaining several FreeBSD
installs which have different CPU''s and packages.
The Good News:
2007 Feb 10
1
Multipe file sources...
Hi,
I''m trying to use several sources to pick from in a remotefile
statement:
remotefile { "/etc/sudoers":
mode => 0440,
source => [
"config/apps/sudo/sudoers.${host}",
"config/apps/sudo/sudoers"
],
sourceselect => first
}
But it doesn''t seem to work. I get an error like this:
"File source
2007 Feb 15
4
Component/type defaults for 0.22.x
Has the component/type defaults syntax changed for 0.22.x?
I have a component:
<snip>
define remotefile($owner=root, $group=root, $mode, $source,
$backup=false, $recurse=false, $groupname="default") {
file {
$name:
mode => $mode,
owner => $owner,
group => $group,
backup => $backup,
2007 Sep 04
1
Solaris ingores server variable
Hi everyone,
I got a basic puppetmaster setup, which works well for Linux.
I''ve setup a basic function:
define remotefile($owner = root, $group = root, $mode, $source, $backup =
false, $recurse = false) {
file {
$name:
mode => $mode,
owner => $owner,
group => $group,
backup => $backup,
2006 Aug 04
0
subscribed files sourced from puppet fileserver
...default: {
file { $name:
mode => $mode
}
}
}
}
Any changes I make to saslauthd.conf or saslauthd.init on the node
are moved aside as saslauthd.confcentral and saslauthd.initcentral -
this is not what I want, at least until I make the remotefiles
templates. In the meantime, how can I roll out initial copies from my
remotefiles location, then have puppet assure that they are there,
but not care about the contents?
RTS
--
Ryan Schwartz
Director of Systems Operations
Joyent, Inc.
TextDrive, Inc.
2007 Jan 25
4
Conditional exec
I am trying to write a definition that downloads and extracts a tar
file if the destination directory does not exist. The tar file won''t
change and does not need to be download and extracted if it changes.
The definition I am using now is:
define remote_tar($source, $directory) {
remotefile { "/tmp/$name.tgz":
source => $source,
}
exec {
2006 Oct 19
8
puppet 0.20.0: updated language syntax doesn''t work?
Hi,
I just upgraded to puppet 0.20.0 today after a short time playing with
0.19.3. The docs say to use the uppercase form for types but that
seems to break for me. When I updated the remotefile function to use
the new way, the puppet clients complain about objects not being
found. For example:
----- OLD WAY (works, just with deprecations) -----
define remotefile (...) {
file { $name :
2007 May 25
18
services do not get restarted
Hello List,
We are using puppet to manage a growing number of Debian Etch based
servers (currently 70). Since upgrading to 0.22.4 we encountered
a problem when services do not restarted on puppets request.
For example the Nagios remote plugin executor daemon (nrpe). It''s running
daemonized and its confiugration is located in /etc/nagios/nrpe.cfg. This
file is managed through puppet
2007 Feb 09
2
Use of variables in defines...
Hi,
I''m banging my head against the usage of variables i defines. Fx. I
have this defined to easily create new systemusers:
define systemuser($home = $home, $shell = "/bin/bash") {
group { $name:
ensure => present
}
user { $name:
ensure => present,
gid => $name,
home => $home,
shell =>
2007 Jan 17
11
scope issue after upgrade
I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think
are problems due to changes in scope rules.
In my site.pp manifest, I have the following:
import "classes/*"
node nfsserver {
include nfsserver
}
node webserver {
include webserver
}
class cluster1_sites {
website {
"example.com": ...;
"example2.com": ...;
}
}
node
2007 Nov 01
1
New Client Problems
I am having SSL difficulties setting up a new puppet client:
Client: fedora (rawhide) using 0.23.2
Server: centos 4.4 using 0.22.3
After initiating contact with puppetd --test
--server=puppet.myclient.com, I see the CSR on the server. After
signing it, and running puppet again, I get the signed certificate,
but also see:
err: Could not retrieve configuration: Certificates were not trusted:
2007 Jun 29
5
Installing a file only if a package is available
Hi,
is there a way to make sure a file is installed only if a certain
package is installed on the client?
e.g. I want to distribute the client key for NX via puppet. However I
only want to install these files if package ''freenx'' is installed on the
client.
I tried adding ''require => package["freenx"]'' but then puppetd complains
it