Out of curiosity, how are people using parameterized classes in a way that is
distinct from defined-types?
--
Digant C Kasundra
Infrastructure Systems Software Developer, ITS:IDG, Stanford University
--
You received this message because you are subscribed to the Google Groups
"Puppet
Is anyone else noticing slowness with 2.7.1? When I run puppet on my 2.6.8
box, it takes 11 seconds. On my second box with exactly the same catalog, it
takes 35 seconds.
--
Digant C Kasundra
Infrastructure Systems Software Developer, ITS:IDG, Stanford University
--
You received this
- Original Message -
> On Tue, 2011-08-23 at 11:00 -0700, Digant C Kasundra wrote:
> > Is anyone else noticing slowness with 2.7.1? When I run puppet on my
> > 2.6.8 box, it takes 11 seconds. On my second box with exactly the
> > same catalog, it takes 35 seconds
- Original Message -
> On Aug 23, 1:00 pm, Digant C Kasundra wrote:
> > Out of curiosity, how are people using parameterized classes in a
> > way that is distinct from defined-types?
>
> I am _using_ defined types, that's how.
>
> Although I disfavor
re subscribed to the Google
> Groups "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
>
table and move servers over to using this environment as the
departments approve of the change.
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
plexity of how and when classes are interpreted, aren't
variables often a tricky thing to play with if you are planning to change their
values in later scopes?
* Lastly, perhaps this is still my OCD, but I'm still a fan of the style guide.
Without it, I dont' think our manifests
e management processes and vetting required from multiple stakeholders in
different departments, making fullscale migration difficult. I'll see if i can
draft something up.
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~--
ues in later scopes".
>
I agree.
> > * Lastly, perhaps this is still my OCD, but I'm still a fan of the
> > style guide. Without it, I dont' think our manifests would be as
> > clean and legible as they currently are.
>
>
- "Eric2" wrote:
> Hi,
>
> err: Could not retrieve catalog: Could not find class parent
> apache::package at /home/puppet/modules/apache/manifests/debian.pp:11
> on node ns0.mysite.org
>
> vi /home/puppet/modules/apache/manifests/debian.pp
> ### debian
> class apache::debian inherits apa
> I sketched a schema describing the use of multiple environments and
> git
> submodules for Puppet development.
>
> It's available on the wiki both in both OpenOffice Draw format and
> PDF.
>
> http://reductivelabs.com/trac/puppet/attachment/wiki/PuppetVersionControl/puppetmaster-git-submodule
Hello everyone,
We're pondering moving to git for our version control system for Puppet
manifests. However, since we have 4 puppetmasters, we're wondering how to deal
with timestamps. Since git doesn't preserve the timestamps, and instead, sets
the current timestamp to every file it modifies
- "Nigel Kersten" wrote:
> On Thu, Aug 20, 2009 at 10:39 AM, Digant C
> Kasundra wrote:
> >
> > Hello everyone,
> >
> > We're pondering moving to git for our version control system for
> Puppet manifests. However, since we have 4 p
be terrible. Having two different paths for the same
namespace is confusing and will easily lead to problems.
However, the example you give is correct: you can't have the same module name
in two modulepaths and usually want to prefix the classnames to avoid name
collisions.
--
Digant C
> If anyone feels up to grabbing this document and running with it,
> please feel free.
As the original author, I suppose I should take over. Can you send me what you
had?
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford Univ
l our work back in-house so can we preserve
these documents since they are still very much part of what our team uses.
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~~---~--~~
You received this message b
tion with large amount of classes
and large difference and ties to external entities like a CMDB. So well
defined patterns can be good, but how to write them and more importantly, how
to present them in a common area can be difficult, especially where there are
multiple solutions to a give
- "lyric" wrote:
> Hello Puppet Friends,
>
> wouldn't it be nice to have a Puppet expert directory with profiles
> and services they offer.
>
> I want to use Puppet but I am not an administration expert, so it
> would be nice to be able to contact local Puppet experts (in my case
> expert
- "Trevor Vaughan" wrote:
> All,
>
> I'm looking for a way to obtain information about the managed
> services
> on a given client system.
>
> Basically, some way to know what services have been enabled by Puppet
> from the client.
>
> I'm hoping to implement something like 'purge' for se
I uncovered the aforementioned issue before but cannot
for the life of me replicate it now. Anyone else know what I'm talking about?
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
--
You received this message because you are subscribed to the Google G
uppetclient puppetd[16163]: Starting catalog run
> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
> 133.44 seconds
>
> I've not been able to look on what is causing it, I belive it's coming
> after we change the environment the puppetclient is pointing to,
e and functional class but only a fragment. Such a
naming convention might call for something like foo::_files or foo::inc::files.
I would like to open this topic up to discussion to the greater community (you
guys) and see what you think.
--
Digant C Kasundra <[EMAIL PROTECTED]>
Technical Lea
CTED]>
To: puppet-users@googlegroups.com
Sent: Tuesday, September 16, 2008 12:40:09 PM GMT -08:00 US/Canada Pacific
Subject: [Puppet Users] Re: Module Standards
2008/9/16 Digant C Kasundra <[EMAIL PROTECTED]>:
> So my proposal is if there is need or want to break up large classes, the
ta resources created as
native types in puppet or (b) through an external node tool.
That's the basic jist of it. I'd love to hear from interested parties or
parties doing something similar.
--
Digant C Kasundra <[EMAIL PROTECTED]>
Technical Lead, ITS Unix Systems a
overrides would come in. The amavis module would have classes
that inherit and override the MTA classes. But how to do so in a manner such
that the MTA in use can be anything and that the amavis module doesn't need to
know about the MTA specifics is a challenge and one that isn't qui
itely along the times of functional role, like
LDAP, mailers, etc.
--
Digant C Kasundra <[EMAIL PROTECTED]>
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~~---~--~~
You received this message because you are subscribed
n type is like sort of like "what you do to a system." So, things like
"install this file" or "install this package." Functional role is things like
"manage openldap" or "ensure these users are present" which would in turn
include actions like installi
to standard for all Puppet Common Modules, it's about making a
> *start* in "code".
>
> - module or class extensions that everyone uses
>
> because these often-used extensions should go *in* the module
> (upstream,
> upstream, upstream is my motto), and such ca
n which servers had
which kind of issues and trouble tickets, blah blah blah. Things I don't
necessarily care about but I do know that I'm expected to feed data into it and
I don't want to duplicate data I already have based on facter and puppet.
--
know about my systems and what the upper
pay grades want (i.e. an ITIL CMDB). I'll likely end up drafting a proposal of
the solution and what it might look like and work on the interconnects in an
open source, collaborative fashion.
--
Digant C Kasundra
collecting these facts. I'd love to try out this solution here and see how it
performs.
--
Digant C Kasundra <[EMAIL PROTECTED]>
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~~---~--~~
You received this message be
extensions that everyone uses
>
> because these often-used extensions should go *in* the module
> (upstream,
> upstream, upstream is my motto), and such can only be done when there
> is
> an upstream module to begin with.
>
> Thanks in advance for review/comments,
>
&
- "Jeroen van Meeuwen" <[EMAIL PROTECTED]> wrote:
> Digant C Kasundra wrote:
> > There is a lot to digest here but a quick correction on:
> >
> > # Red Hat / CentOS has puppet-0.24.4 and does not do the import
> magic. It could do the imports, but
d
> >> "functional role?"
>
> > An action type is like sort of like "what you do to a system." So,
> things like "install this file" or "install this package." Functional
> role is things like "manage openldap" or &qu
p files. I was just curious if there
was an example on the Wiki that we hadn't updated or might want to revisit.
--
Digant C Kasundra <[EMAIL PROTECTED]>
Technical Lead, ITS Unix Systems and Applications, Stanford University
--~--~-~--~~~---~--~~
You rec
sible solution is to somehow share those state files
> between servers. This may or may not be feasible in your environment
> (no pun intended...)
How can the state files be shared between servers?
--
Digant C Kasundra
Technical Lead, ITS Unix Systems and Applications, Stanford University
> > How can the state files be shared between servers?
>
> DRBD.
Considering a load-balanced environment, it seems this might not be optimal.
Perhaps the puppetmaster need the ability to store the state information in a
database.
--
Digant C Kasundra
Technical Lead, ITS Unix
37 matches
Mail list logo
