I assume others have noticed this, but I haven't seen any chat about
it. I haven't gotten an email update from redmine in quite a while.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To p
On Tue, Jul 7, 2009 at 8:01 PM, Luke Kanies wrote:
> Oh, and to be clear -- I like the idea of using tokyo cabinet or
> something like it, but it's a good bit of work to switch, and some
> significant amount of that work is design rather than just
> implementation.
2 BILLION DOLLARS!!!
--~--~---
On Tue, Jul 7, 2009 at 7:13 PM, James Turnbull wrote:
> Yeah I have my doubts based on my experiences with a variety of
> platforms. I think that's a pretty optimistic outlook. :)
It is. :) But on the other hand, it's not like Ruby comes with Solaris
or HP-UX or any other non-freenix that isn't
On Tue, Jul 7, 2009 at 6:48 PM, James Turnbull wrote:
> On another note and being of a practical bent - what platforms is TC
> packaged for if we were to make it a dependency? Not extensive as far
> as I can see.
>
> I can find it on EPEL 5 - which covers those RH/Fedora/CentOS customers
> happy
On Tue, Jul 7, 2009 at 10:20 AM, James Turnbull wrote:
> Not being an expert on this and excuse me if this is a stupid question
> ... :) If this essentially replaced a back-end RDBMS - is it easy for
> people to query the data with other tools? For example, now I have my
> database of stored con
> Really, Storeconfigs builds hash-like structures (resources are a hash
> with arrays for values, effectively) into the db, which basically
> sucks: Every resource is at least two associations:
> has_many :param_names and has_many :param_values. This is slow and
> sucky, but unavoidable with a
On Fri, Jul 3, 2009 at 11:29 AM, Brice
Figureau wrote:
> That's our eldorado :-)
> But it isn't as easy as it sounds first, if you look to how puppet uses
> the database for collection, and storeconfigs.
> Then there's the issue of finding the proper storage engine.
I'll admit that I know next to
If attention is being paid to this section of the code, would any
consideration be made to moving away from RoR/RDBMS toward something
more suited to the task? Or even just augmenting the available
back-ends?
It seems like using an RDBMS for this data not only doesn't benefit
from RDBMS features,
I really appreciate it, guys. :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com
To unsubscribe from this group, send email
On Thu, Jun 18, 2009 at 1:51 AM, James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sam Rowe wrote:
> | Sorry if this info is somewhere...
> |
>
> Sam
>
> There will be another one. Probably early next month when the
> current ti
Sorry if this info is somewhere...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com
To unsubscribe from this group, send emai
On Mon, Jun 1, 2009 at 9:37 AM, James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Luke et al
>
> I came across two plug-ins for Redmine that might interest people:
>
> 1. An issue voting plug-in that allows you to vote for issues.
Bugzilla has voting. I asked a mozil
Bah. Didn't mean to send.
Puppet really needs a facility for this sort of thing. Space ship
operators, nagios types, etc... they all need to be more configurable
so that we don't have to do it "the puppet way."
--~--~-~--~~~---~--~~
You received this message becau
On Sat, May 23, 2009 at 8:06 PM, Kelsey Hightower
wrote:
>
> I can add a file param as long as its supported by tcpwrappers. From
> most docs I have read, the default location is /etc/hosts.allow and /
> etc/hosts.deny. Not sure if other types such as the "host" type allow
> this.
>
> Do you know
On Fri, May 22, 2009 at 11:26 PM, Kelsey Hightower
wrote:
>
> Puppet::Type.newtype(:tcpwrapper) do
> �...@doc = "Manages tcpwarppers hosts.allow and hosts.deny entries.
> The entry will be placed in /etc/host.allow when 'allow => true'
> or 'deny => false'
> The entry will be placed in /e
On Wed, May 20, 2009 at 8:23 PM, Mark Plaksin wrote:
> 1) There was an initial storeconfigs storm that hammered our
> puppetmaster and MySQL server (one and the same) fairly hard. Our MySQL
> stats make it look like most of the activity was DELETEs; Sam's guess is
> that a bunch of deduplicatio
heh, so I guess I should -1.
We had these facts on our HP-UX hosts for a while now and just this
morning figured out that because they can take longer than 5sec to
return data (display_manifest is a pig) they actually CRASH puppetd!
We can provide details on our support call (or where/whenever).
I talked with Luke on the phone about this and he suggested that this
code is acceptable.
On Fri, May 1, 2009 at 9:39 AM, Luke Kanies wrote:
>
> On Apr 27, 2009, at 7:10 PM, s...@samrowe.com wrote:
>
>>
>> From: Sam Rowe
>>
>> hardware model
>> serialnum
I aped the AIX one above it. :)
On Mon, Apr 27, 2009 at 1:32 PM, Peter Meier wrote:
>
> Hi
>
> I don't use hp-ux, so can't tell if this is the right code. However I'd
> like to do a comment on the "style":
>
>> +if Facter.value(:kernel) == "HP-UX"
>> + # no MemoryFree because hopefully there
On Thu, Mar 19, 2009 at 10:57 PM, Luke Kanies wrote:
> The queueing would only help with reducing client contention when the
> contention was caused by StoreConfigs, unfortunately.
>
> Although...
>
> I could see having a ping-back model, where a client sends a request
> for a compilation but the
On Thu, Mar 19, 2009 at 2:38 AM, James Turnbull wrote:
> I think we'll do:
>
> $operatingsystemrelease => 5.2
> $operatingsystemmajrelease => 5
Thanks!
Is there a good method for dealing with a case like this other than doubling up?
file { "whatever":
source => [
"$fileserver/whatever/what
On Wed, Mar 18, 2009 at 1:16 PM, Luke Kanies wrote:
>
> Hi all,
>
> As mentioned in an email yesterday, I'm working with someone to add a
> queueing service to Puppet so that some server-side operations are
> queued and executed as cpu time is available - generally those that
> aren't on the crit
So will there still be some value that will tell me 4 for RHEL4, 5 for
RHEL5, 9 for Solaris 9, and 10 for solaris 10? I don't care at all
about the minor number.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppe
On Tue, Mar 17, 2009 at 6:23 PM, Luke Kanies wrote:
> What about long-term consistency? Do you have concerns there?
>
> It's not exactly a forced upgrade - you'll only get the new format
> when you upgrade Facter, and it would be something like the 1.6
> release, which you'd expect to be a bit d
We also saw a ton of duped param_name.name entries and fact_name.name
entries :( after dropping the old tables and having puppet re-create
them.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" gro
On Wed, Mar 11, 2009 at 7:01 AM, James Turnbull wrote:
> That's fine. We just want to get rid of the inconsistency with the
> minimum amount of user pain.
>
> If we're going in the style of other facts we'd get:
>
> $operatingsystemrelease => 5.2
> $operatingsystemmajrelease => 5
>
> This is how
On Thu, May 8, 2008 at 12:39 PM, Luke Kanies <[EMAIL PROTECTED]> wrote:
> The bug tracker isn't that great, I must say.
Man am I glad to read that. I completely agree.
This seems like a separate issue though. What's being considered for
this? Bugzilla? It's the only one I've seen that doesn't su
27 matches
Mail list logo
