$ curl -sLO \
http://yum.puppetlabs.com/base/puppet-dashboard-1.0.0-3.noarch.rpm
&&
rpm -qip puppet-dashboard-1.0.0-3.noarch.rpm | grep Signature
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because you are s
On 5 May 2010, at 5:26 PM, James Turnbull wrote:
I've fixed it now and added some further fixes to the spec file
provided by Todd Zullinger.
Thanks, both.
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because yo
ce default is in scope). 'yum clean expire-cache' is the cheapest way to
ensure an updated view of your yum repos, without deleting too much metadata
which may need re-downloading in case the repos are unchanged. Note that this
clean would happen on every Puppet run, of course, and that ma
nships could be extremely powerful and useful. Has anybody
> managed to get anything like this working, or does anybody know a
> reason why this shouldn't work?
You may be running across something as simple as a slight variation on bug
#4560:
https://projects.puppetlabs.co
efault. (You may also want to parameterize
on the $environment fact, &c.)
Incidentally, we (the Stanford University Libraries) adopted this
modules/services distinction from the other, larger Puppet deployment here at
Stanford, and it's worked very well for us.
--
Ian Ward Comfort
Syst
promotion to stable.
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To un
0 added to the Puppet
Labs yum repository in the near future? We've been running the official 1.0.4
RPM quite successfully, and it would be great to get those new features through
the same channel.
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
ray = ['a','b','c']
$var = myfunction('first arg', $array)
$empty_array = []
$other_var = myfunction($empty_array)
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because y
ck down this issue (and should probably do
so in the 0.25 beta, anyway), but I wonder if anyone else has seen this.
--
Ian Ward Comfort
System Administrator, Student Computing, Stanford University
--~--~-~--~~~---~--~~
You received this message because you ar
On 28 Jul 2009, at 11:00 PM, David Schmitt wrote:
> Ian Ward Comfort wrote:
>> For me, the killer app for storeconfigs is exported SSH host keys.
>> That's information that my puppetmaster *doesn't* have in its
>> manifests, and needs to collect f
especially if your flight is on time and
you make the 11:31 southbound from Millbrae. See:
http://flysfo.com/web/page/atsfo/airtrain/map/index.html
http://www.caltrain.com/timetable.html#weekday-southbound
--
Ian Ward Comfort
System Administrator, Student Computing,
$iface") }
N.B. due to the way Facter alphafies interface names, there's an
unavoidable limitation when working with network facts that the
interfaces eth0.1 and eth0:1 are indistinguishable. (Actually, I'm
not even sure how Facter behaves in this case.)
--
Ian Ward Comfort
the systems so I can generate a
> configuration file (loop through each processor number).
>> <% for cpu in (0..processorcount) %>
Try:
<% for cpu in (0 .. processorcount.to_i) %>
--
Ian Ward Comfort
Systems Team Lead, Student Computing, Stanford University
--
On 23 Nov 2009, at 7:33 AM, Christopher Johnston wrote:
> Its definitely there.. I even put a <%= processorcount %> to make
> sure the variable is set.
>
> <% processorcount.to_i-1 %>
> <% for cpu in (0..processorcount) %>
Try:
<% for cpu in (0 .. p
different name? (Say, openssl-yoursite?) We avoid
building our own packages with the same name as official distro
packages to avoid this and similar problems.
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because yo
}
class puppet::server {
include puppet::client::disabled
}
Now it's safe to apply puppet::client to all your nodes, including
your puppetmaster, because the ::disabled class will override the
management of puppet.conf on the puppetmaster (which presumably
On 21 Jan 2010, at 7:47 AM, Rob McBroom wrote:
On Jan 20, 2010, at 6:29 PM, Ian Ward Comfort wrote:
I think a lot of shops do this by creating special "disabling"
classes for those one-off systems. To use your puppetmaster
example (untested pseudocode ahead):
class pupp
17 matches
Mail list logo
