Hi,
I was curious if anyone out there could point me in the right direction to best
practices in writing (spec) tests for modules. My #{search provider}-fu is
failing this morning and I'd like to get beyond the basic pre/post commit hooks
of basic syntax checking.
Cheers,
Ryan
--
You receive
Yep. That is exactly what was going on. Once the clients were brought up
to the same rev, things went back to normal.
Cheers,
Ryan
On Mar 14, 2011 5:31 PM, "Peter Meier" wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm assuming this might be the clients running an older version?
l
Hey Folks,
I just updated my puppet master to 2.6.6. As part of the update, I moved my
puppet-master under Passenger.
ruby-1.8.7p249
rack-1.2.1
passenger-2.2.15
puppet-2.6.6 ( the clients are all 2.6.0 currently )
Ubuntu 10.04.{1,2} LTS
In doing so, I am now seeing the behavior outlined in:
Okay... that's very cool (and thanks for the github example repo for nodeless
puppet!). This plus the 'scaling puppet with git' [0] concepts I'll use here
at Lookout, Inc.
Cheers,
Ryan
[0] -
http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
On Feb 9, 2011, at 1:
This is exactly what we used schedules for. System software.was.only
updated at specific times to ensure that we got the maximum io from our
disks.
On Jan 17, 2011 6:50 PM, "Daniel Pittman" wrote:
On Mon, Jan 17, 2011 at 18:38, Nigel Kersten wrote:
> I'm trying to get a fee...
At my previous j
I'd be in favor of only maintaining one rev behind for compatibility (2.7.x
will support 2.6.x but not earlier).
Cheers,
Ryan
On Nov 24, 2010, at 4:57 PM, Nigel Kersten wrote:
> On Wed, Nov 24, 2010 at 4:35 PM, Daniel Pittman wrote:
>> Gary Law writes:
>>> On 24 November 2010 23:50, Nigel K
On 10/14/2010 3:47 AM, Michal Ludvig wrote:
> Hi guys,
>
> I'm installing Puppet on RHEL5 systems using KickStart but struggle
> with the first boot.
>
> Here's my situation:
> 1) kickstart installs the system, including puppet from our local repo
> 2) after reboot I have to login and set the hos
I've not actually tried but I would think you should be able to do
something like:
package {
"foo.i386": { ensure => latest ; }
}
I know yum understands the syntax of: yum install foo.i386 (or foo.x86_64).
Cheers,
Ryan
On 9/16/2010 6:05 AM, Geoff wrote:
> How do you do it with puppet?
> I'm
> And are you using --onetime to trigger these random runs, via cron or
> something?
> -Alan
>
We run puppet from cron via wrapper. The wrapper looks for a file that
signals "not to run" if we are in a maintenance mode.
Cheers,
Ryan
--
You received this message because you are subscribed to t
Howdy Alan,
On 7/21/2010 6:04 PM, Alan Sparks wrote:
> I have a custom schedule to apply changes to various classes (e.g.,
> "File { schedule => normal }"). This works fine for puppetd running as
> a daemon. However, I note that if I run puppetd with the --onetime
> option, it applies none of m
Awesome :)
On 7/9/2010 11:58 PM, James Turnbull wrote:
> Welcome back again to the Puppet release cycle with the long-awaited
> eleventy times better 2.6.0rc1 release!
>
> The 2.6.0 release is a major feature release and includes a huge variety
> of new features, fixes, updates and enhancements.
On 4/11/2010 8:58 PM, Luke Kanies wrote:
> We're very excited to announce that after years of being a critical
> contributor to Puppet, including writing the Puppet Book, James
> Turnbull is joining Puppet Labs as Director of Operations, where he'll
> be responsible for infrastructure, support, and
heh!
On Jan 25, 2010, at 5:01 PM, Allan Marcus wrote:
> re: font size.
>
> It looks fine to me on Safari 4 on the Mac.
>
> Note: for every year after 40 you need to press command-plus once :-)
>
> ---
> Thanks,
>
> Allan Marcus
> 505-667-5666
--
You received this message because you are sub
Agreed. Great collection of testing links.
Cheers,
Ryan
On Nov 13, 2009, at 1:15 PM, Christian Kauhaus wrote:
>
> Patrick Debois schrieb:
>> I've put my collection of infrastructure testing links online:
>> http://www.jedi.be/blog/2009/11/12/collection-of-test-driven-infrastructure-links/
>
I can get behind that. Nominated :)
On Nov 12, 2009, at 12:52 AM, Michael T. Halligan wrote:
>
> I just nominated Reductive Labs for a Crunchie in the "Best Enterprise
> Startup" category, if only because it's the kind of ridiculous SF startup
> popularity game that I think would annoy Luke
Chad Huneycutt wrote:
> I am not sure everyone is on the same page:
>
> 1. you don't want to have the root password (encrypted or not) showing
> up in the process listing of your clients.
Well, this is a policy/philosophy issue. The question is "what is an
acceptable risk for your environment?"
We sort of do this we set a global $password in our site.pp. That
$password is an MD5 string. My environment is currently all Linux.
Then, in our base module we have:
exec {
"set-root-password":
path => "/usr/sbin:/sbin"
command => "/bin/echo root:$password | /usr/sbin/chpasswd -e"
}
On 1/12/09 1:03 PM, Joe McDonagh wrote:
> I'm sure people are doing this, possibly even in significant numbers
> because it doesn't seem too complicated. What do you see (if anything)
> as being hurdles?
Environments of modules are your friend :)
Cheers,
Ryan
--~--~-~--~~---
Have you checked out the splay option?
Alternatively, I've since moved on from splay to use a cron job to run
puppetd. I have a meta package that pulls in puppet and drops in a root
cron job entry based on the mac address of the host's primary interface
during the post-install step of rpm.
C
Another good link for what you are asking for:
http://reductivelabs.com/trac/puppet/wiki/Recipes/LDAPClientNSSwitch
On Sat, Nov 22, 2008 at 8:06 PM, Ryan Dooley <[EMAIL PROTECTED]> wrote:
> Sorry for the late reply. Yes, you need to manage /etc/ldap.conf and
> probably /etc/ssl (or
ldap.conf file and a one or two files in
> /etc/pam.d?
>
> The "remotefile" resource type is new to me - is it available in puppet
> v.0.24.4?
>
>
> On 11/19/08, Ryan Dooley <[EMAIL PROTECTED]> wrote:
>>
>> Kenneth Holter wrote:
>> > Hi.
&
Kenneth Holter wrote:
> Hi.
>
>
> I need to configure our puppet nodes as LDAP clients, and were wondering
> if puppet has any build in support for this.
Easy enough (if I understand correctly). We do this here with a
'ldap_client' module that looks something like this:
class ldap_client
22 matches
Mail list logo
