[Puppet Users] Re: How to setup database for Inventory Service

Actually I ended up creating manually the missing tables, but thanks for the info. On May 5, 1:31 am, James Turnbull wrote: > Alessandro Franceschi wrote: > > Thank you for the feedback. > > I've momentarily postponed theinventorysetupbut, for the chronicle, > > ju

[Puppet Users] Re: Red Hat Satellite Future : puppet and foreman

Great Ohad ! Nice to see that foreman and puppet are so deeply and explicitely integrated in the next satellite. grazie per il link yersinia :-) -- 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

Re: [Puppet Users] Global scope variables and erb templates in puppet 2.7

scope.lookupvar() works also on Puppet 2.6 and 0.25 and maybe earlier versions, and AFAIK will keep on working in future versions. Incidentally it has the benefit of not throwing an exception when the referred variables is not set (it just returns an empty field) I find it useful to refer to full

[Puppet Users] Re: A working firewall module

FYI I don't know it it may be useful , but I've done this: https://github.com/example42/puppet-modules/tree/master/iptables which can be used in 2 ways: - a "standard" iptable-save approach (set $iptables_config = "file" before to enable it) with rules file defined in https://github.com/example42

[Puppet Users] Re: Does Node Inheritance work for people?

I've ALWAYS used nodes inheritance and have NEVER had problems with them: - no scoping issues (well just at the beginning when I didn't realize what I'm going to write below) - no problems with resource defaults (I actually just set few general defaults without overriding them). I've always wonder

[Puppet Users] Re: Does Node Inheritance work for people?

wrote: > On Mon, Aug 08, 2011 at 06:25:20AM -0700, Alessandro Franceschi wrote: > > NEVER include a class in the inheritance tree (well you can if you > > don't redefine variables used in that class but still is not > > necessary). > > In a nodes inheritance layout BEFO

[Puppet Users] Re: Custom Facts

Btw, Rip or anyone, any suggestion on how to sort alphabetically the scope variables so that the generated yaml doesn't change at (almost) every puppet run? content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s =~ /(uptime_seconds|timestamp|free)/ }.to_yaml %>") On 2 Set, 20:26, "R

[Puppet Users] Re: Deployment of applications

You might be interested in Puppi, which is a Puppet module and a bash command that i've written exactly for this reason. Code: https://github.com/example42/puppi More info: http://www.example42.com (now terribly slow) or http://puppetlabs.com/blog/deploying-applications-and-bringing-puppet-informat

[Puppet Users] Re: qualified variables in templates

Use something like <%= scope.lookupvar('hostname') %> On Sep 20, 11:06 am, Arnau Bria wrote: > Hi all, > > is there a way for qualifying variables inside a template? > I've tried : > > Name = <%= "${::hostname}" %> > > but the var gets "${::hostname}" value. > > thinking in version 2.8, is it >

[Puppet Users] How to access to all the parameters of a parametrized class or a define

trized class or a define (something like: openssh::*.to_yaml ) The point is to have a quick and generic way to pass Puppet knowledge (the variables defined/used) about a class, to a local file, that can be used in various interesting ways. If there's no way to do that, does anyone find

[Puppet Users] Re: How to access to all the parameters of a parametrized class or a define

returns a hash - which you could then convert to a yaml document if you > like. > > ken. > > > > > > > > On Tue, Oct 25, 2011 at 11:25 PM, Alessandro Franceschi wrote: > > Dear all, > > is there a way to access in a template to all the p

[Puppet Users] Request for comments: new foo module template

To who may be interested, I'm working on the default template of the next generation of Example42 modules. In http://github.com/example42/puppet-foo2 there's the foo sample module. All the "first generation" Example42 modules ( http://github.com/example42/puppet-modules ) which are more or less

[Puppet Users] Dynamically create arguments for a define (or parametrized class)

Maybe I'm asking too much, but is there a way to dynamically add resources in a define/parametrized class based on a variable (or hash) passed to a containing class/define? Something that when I call boo { "bah": options => { "optiona" => "valuea", "optionb" => "valueb",

Re: [Puppet Users] Dynamically create arguments for a define (or parametrized class)

On Thursday, October 27, 2011 4:03:42 PM UTC+1, Henrik Lindberg wrote: > > Did you try something like: > > define boo($a="a", $b="b", $c="c") { > bar { $title: >a => $a, >b => $b, >c => $c, > } > } > > boo { 'the title' : a => "a value", c => "c value" } > Thanks

[Puppet Users] Re: Dynamically create arguments for a define (or parametrized class)

Thanks for the link. I fear that this function doesn't exactly apply to my case (it creates dynamically resources, not arguments for a resource) but I should give it a deeper look and consider if I can work around it. al -- You received this message because you are subscribed to the Google Gro

[Puppet Users] How to show in a template all the variables of a define or parametrized class

Hi all, is there a quick and elegant way to place, possibly as yaml file, all the variables defined in a parametrized class (and a define?) Something like: file { "debug_openssh": path=> "${settings::vardir}/debug-openssh", mode=> "0640", owner => "root", gro

[Puppet Users] Re: Recommendation for general practice for application deployment?

Puppi (more info here download from here) is a Puppet module made exactly for application deployments. You can deploy war files with a define

Re: [Puppet Users] Re: Best practice for module params in foo::params

Note that you can use hiera to gather and define variables at top level scope and keep the usage of ::vars on your params class. This has the advantage that if you will ever need to change the method you use to give values to the top scope variable, you just have to change the references at top

[Puppet Users] Re: How to setup database for Inventory Service

Actually that is the good way to do that on a fresh installation I suppose, but I wonder, and ask, if there's a way to create the needed schema for the Inventory service without destroying the current database. My case is that I've a Puppet Master with storeconfigs activated and a lot of data a

[Puppet Users] Re: How to setup database for Inventory Service

ou shouldn't need to migrate anything, the data will be populated > when the clients check in. > > On Apr 11, 10:07 am, Alessandro Franceschi wrote: > > > > > > > > > Actually that is the good way to do that on a fresh installation I suppose, > >

[Puppet Users] Re: How to setup database for Inventory Service

Thank you for the feedback. I've momentarily postponed the inventory setup but, for the chronicle, just inserting the query you posted didn't work out of the box. I'll get back on this when sorted out other things. Al On Tuesday, April 12, 2011 1:16:07 PM UTC+2, Greg Sutcliffe wrote: > > Heya, >

[Puppet Users] Puppet-rspec suggestions

Good afternoon all, I've played a bit with rspec puppet lately trying to use it in a sane way, checking if the module's logic is correctly applied rather than if Puppet does what it's supposed to do. But I'm really new to rspec and might miss some important points. My efforts are for the moment

[Puppet Users] Re: Using foo::params, inheritance, and parameterized classes simultaneously?

Gary has already given a good reply, let me just add some of the motivations that have driven this approach in my new modules (example42): - I want all the variables used in a Puppet class to be visible to the system (in my case Puppi, so that I can do interesting things with them): Puppet know

Re: [Puppet Users] Re: Using foo::params, inheritance, and parameterized classes simultaneously?

On Sunday, January 15, 2012 12:41:50 AM UTC+1, Nigel Kersten wrote: > > > > What would it take for you to just have one source of truth for data > Alessandro? > > e.g. what would we have to change about Puppet for us to simply use Hiera > ? > > We're looking to integrate Hiera into Puppet fo

Re: [Puppet Users] Re: Using foo::params, inheritance, and parameterized classes simultaneously?

On Sunday, January 15, 2012 9:30:02 PM UTC+1, Nigel Kersten wrote: > > > > On Sun, Jan 15, 2012 at 12:42 AM, Alessandro Franceschi wrote: > >> >> So, to reply to your question, Nigel, something like a hiera backend or a >> Puppet function that does what is w

[Puppet Users] Re: params.pp class with parametrized class support?

Look here at how I do this: https://github.com/example42/puppet-openssh -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Fw_KNwipuDgJ. To post to this group,

[Puppet Users] Re: params.pp class with parametrized class support?

But, well, 2 years ago I was doing the opposite... Sorry for lack of definitive answers but I'm still exploring and trying to find out if the approach I use is usable and fitting for others. my2c al > On Jan 18, 1:58 am, Alessandro Franceschi wrote: > > Look here at how I do this:https

[Puppet Users] Re: How to handle multiple modules requiring the same packages

I add my 2 cents. The alternatives proposed in the replies are ok for me, just would like to express an alternative approach that I''ve used in some situations. It's due to different factors: - Many packages to manage (but not necessarily) - Option to include a module in an existing module set, wh

[Puppet Users] Re: node inheritance

Just a quick note, not strictly related to your question Be careful when including classes with nodes' inheritance: if you set a variable, for example, in the node "web" that is used by classes included in the baseline class, that variable' value will be ignored. It's a typical "variables scoping

Re: [Puppet Users] Re: node inheritance

an alternative, and will probably be the "right thing" when is incorporated in the next version, but it has its own cons, imho. my2c al On Tuesday, March 20, 2012 3:57:17 PM UTC+1, Garrett Honeycutt wrote: > > On 3/19/12 3:55 PM, Alessandro Franceschi wrote: > > Just a quick not

[Puppet Users] Is there a way to upload modules releases to the Forge via CLI?

In order to contribute to the Forge in a sane and quick way I think it's needed a way to upload new releases in a scriptable way. There's a (long lasting) ticket open for that: http://projects.puppetlabs.com/issues/3790 but in the meantime I wonder if someone has managed to find a way to obtain

[Puppet Users] Re: Announce: PuppetDB 0.9.0 (first release) is available

Wow, these are great news! I've just installed it on an Ubuntu 12.04 and it was really painless. For whoever might be interested I made an instant module for this: https://github.com/example42/puppet-puppetdb with default Example42 NextGen layout (so it still misses puppetdb specific resources a

Re: [Puppet Users] Re: Announce: PuppetDB 0.9.0 (first release) is available

If I can add my coins to the discussion I'd say that installing and running PostgreSQL is really easy (I actually really never used it before and have been "forced" by PuppetDB) and, even if I don't feel myself at ease with it too, I don't think it is going to be a real pain to mantain. But, mo

Re: [Puppet Users] JBOSS installation and Configuration through puppet

, find the updated version on GitHub: https://github.com/example42/puppet-jboss Please let me know if there are other issues you find with the module. For quicker replies on problems with Example42 modules I suggest to open issues via GitHub. Best regards Alessandro Franceschi / Example42 Il

Re: [Puppet Users] Windows Puppet Agent Hangs on Run

Issue should have been fixed now. Thanks for the github bug report. On Monday, January 14, 2013 3:47:38 PM UTC+1, phundisk wrote: > > Thank you for the information! That resolved the issue. I have posted a > bug report on puppi's github > https://github.com/example42/puppi/issues/45 > > On Satu

[Puppet Users] Re: Can someone provide more clarity on Puppi

at the documentation is not good and somehow scattered on different places (what have you seen? the README on the git repo?) I'm at disposal to answer to any question about it and eventually to suggest you the possible Puppet code you can write to manage an application deployment you may need.

[Puppet Users] Re: Can someone provide more clarity on Puppi

your nodes)... you just need it in your modulepath to pluginsync its lib dir. al On Thursday, January 17, 2013 10:58:20 PM UTC+1, Alessandro Franceschi wrote: > > Hi, > Puppi is a shell tool, installed and configured bythe omonimous Puppet > module, that has basically 2 functions:

Re: [Puppet Users] JBOSS installation and Configuration through puppet

in 49.37 seconds > > my node manifest is > > node 'ABC' { > class { 'jboss': > } > > Currently I am trying the module on centos but will need it immediately > for suse/ubuntu and rhel as well > > please help.. > > Thanks in advance... &g

Re: [Puppet Users] JBOSS installation and Configuration through puppet

rest all has been fixed. > > Also there issues if unzip or wget are not installed on the client machine. > > Thanks & Regards, > > Rakesh K. > > On Thu, Jan 24, 2013 at 6:54 PM, Alessandro Franceschi > > > wrote: > >> Hi Rakesh, >> I just wo

[Puppet Users] Re: Can someone provide more clarity on Puppi

l node definitions in my Puppet manifest each serving > different purpose, I want to use Puppi to deploy to all those hosts but not > at the same time. > > Any help will be appreciated. > > Thanks in advance, > Krishna Murthy > > On Thursday, 17 January 2013 22:02:25 UTC, A

[Puppet Users] Re: Can someone provide more clarity on Puppi

ame > server, which means same 'deploy_root' but two 'war' files and I don't > think I can use two 'source' two times. > > Any suggestions will be much appreciated. > > Thanks & Regards, > Krishna Murthy > > On Friday, 22 February 2013

[Puppet Users] Re: Can someone provide more clarity on Puppi

in > '/puppet/modules/puppi/manifests/'? because I tried doing both but no luck. > > Any help on above points will be much appreciated as I am not getting much > help from google. > > Thanks & Regards, > Krishna Murthy > > > On Friday, 22 February 20

[Puppet Users] Re: Can someone provide more clarity on Puppi

to do 'puppi deploy' and 'puppi rollback' from one central > system (Puppetmaster) and I understand that we can do that using puppi's > Mcollective plugin, so any help on how to install puppi mcollective plugin > will be very helpful to me. > > Thanks &

[Puppet Users] Re: example42 mcollective - setting version produces an error

On Wednesday, April 10, 2013 5:27:20 PM UTC+2, Larry Fast wrote: > > When I define the mcollective_version variable using hiera I get the > following error. There is no indication where the problem has occurred. > > Error: Failed to apply catalog: You cannot specify more than one of > content,

Re: [Puppet Users] example42 puppet-squid

I confirm. That Squid module is very old and is part of the "old generation" of Example42 Puppet modules, it was done before the release of Puppet 2.6 and doesn't support parameters (that's why you see errors when trying to pass parameters to it). As author of the Example42 module I suggest to u

[Puppet Users] Re: removing hosts from puppet-monitor (example42)

Hi Andreas, to remove a node you can run: puppet node deactivate on the PuppetMaster. To be sure to have quicker answers about Example42 modules, please use: https://groups.google.com/forum/?fromgroups#!forum/example42-puppet-modules Ciao Alessandro On Sunday, April 28, 2013 1:34:12 PM UTC+2, A

Re: [Puppet Users] puppet pull code from svn

You may also find this useful: https://github.com/example42/puppet-svn/blob/master/manifests/reposync.pp it creates a command that can be used either via Puppet or via cron or directly via shell to pull code from a subversion repository. A similar alter-ego for git is: https://github.com/example4

[Puppet Users] The handy Grail of Modules Standards

27;s your general idea on the proposed naming standards, if you have better ideas on naming and approach. Let's grab this handy Grail :-) Alessandro Franceschi Example42 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscr

Re: [Puppet Users] The handy Grail of Modules Standards

On Monday, June 17, 2013 1:17:45 PM UTC+2, Matthias Saou wrote: > > Hi, > > First off... is these some pun I'm not getting, or was it supposed to > be "Holy Grail"? Just wondering :-) > It's holy but is also handy, as I think it's just at hands reach. > > Also, when I read "Puppet Modules

Re: [Puppet Users] The handy Grail of Modules Standards

On Tuesday, June 18, 2013 11:16:15 AM UTC+2, Matthias Saou wrote: > > On Mon, 17 Jun 2013 07:32:36 -0700 (PDT) > Alessandro Franceschi > wrote: > > > Thanks for your opinion, even if I don't fully agree with it. > > Puppet is a language and so people do the sa

Re: [Puppet Users] The handy Grail of Modules Standards

Some personal notes among the lines... On Tuesday, June 18, 2013 6:35:18 PM UTC+2, Ken Barber wrote: > > > Although I agree that to be reusable, modules need to provide certain > types > > of levers, knobs, and switches, as appropriate for their scopes, I think > the > > case is weak for those

Re: [Puppet Users] The handy Grail of Modules Standards

On Wednesday, June 19, 2013 5:03:41 PM UTC+2, jcbollinger wrote: > > > > On Tuesday, June 18, 2013 1:19:32 PM UTC-5, Alessandro Franceschi wrote: >> >> Some personal notes among the lines... >> >> On Tuesday, June 18, 2013 6:35:18 PM UTC+2, Ken Barber wrote: &

Re: [Puppet Users] The handy Grail of Modules Standards

On Thursday, June 20, 2013 4:12:46 PM UTC+2, jcbollinger wrote: > > > > On Wednesday, June 19, 2013 5:34:58 PM UTC-5, Alessandro Franceschi wrote: >> >> >> >> On Wednesday, June 19, 2013 5:03:41 PM UTC+2, jcbollinger wrote: >>> >>> >&g

Re: [Puppet Users] The handy Grail of Modules Standards

On Friday, June 21, 2013 5:05:20 PM UTC+2, jcbollinger wrote: > > > > On Thursday, June 20, 2013 10:14:09 AM UTC-5, Alessandro Franceschi wrote: >> >> >> >> On Thursday, June 20, 2013 4:12:46 PM UTC+2, jcbollinger wrote: >>> >>> >>&g

Re: [Puppet Users] The handy Grail of Modules Standards

On Saturday, June 22, 2013 11:47:13 AM UTC+2, Wolf Noble wrote: > > > I'd like to say I really like the intent behind this. > > Yes, a name is important. So is continuity. I believe the underlying goal > is to provide a collection of reference material. Once the skeleton of this > material is

Re: [Puppet Users] The handy Grail of Modules Standards

On Monday, June 24, 2013 3:57:55 PM UTC+2, jcbollinger wrote: > > > > On Friday, June 21, 2013 6:21:22 PM UTC-5, Alessandro Franceschi wrote: >> >> >> >> On Friday, June 21, 2013 5:05:20 PM UTC+2, jcbollinger wrote: >>> >>> Anything you

Re: [Puppet Users] PuppetLabs Module Toolkit

You might find this useful: https://github.com/example42/Example42-templates On Monday, June 24, 2013 7:30:38 PM UTC+2, Eric Aiken wrote: > > Thanks for the insight. Reading the puppet lab doc didn't really answer > the question of what tools, rather it explained the end goal. However it > did

Re: [Puppet Users] The handy Grail of Modules Standards

On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote: > > > > On Monday, June 24, 2013 9:12:17 AM UTC-5, Alessandro Franceschi wrote: >> >> >> >> On Monday, June 24, 2013 3:57:55 PM UTC+2, jcbollinger wrote: >>> >>> >>> Non

Re: [Puppet Users] The handy Grail of Modules Standards

On Tuesday, June 25, 2013 10:10:13 PM UTC+2, Ygor wrote: > > I have been watching this thread grow and metastasize and I would like to > offer my opinions: > > "The wonderful thing about standards is that there are so many of them to > choose from." Grace Hopper (maybe) > > There are at least

Re: [Puppet Users] The handy Grail of Modules Standards

On Tuesday, June 25, 2013 11:49:49 PM UTC+2, Alessandro Franceschi wrote: > > > > On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote: >> >> >> >> On Monday, June 24, 2013 9:12:17 AM UTC-5, Alessandro Franceschi wrote: >>> >>

Re: [Puppet Users] The handy Grail of Modules Standards

On Wednesday, June 26, 2013 3:37:10 PM UTC+2, jcbollinger wrote: > > > > On Tuesday, June 25, 2013 4:49:49 PM UTC-5, Alessandro Franceschi wrote: >> >> >> >> On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote: >>> >>> &g

Re: [Puppet Users] The handy Grail of Modules Standards

e forgive me > though, my product manager wired brain wants to pause at this point and > discuss it a bit first before I offer my opinions on the doc. > On Tue, Jun 18, 2013 at 11:19 AM, Alessandro Franceschi > > wrote: > >> For me a module is reusable when: >&g

[Puppet Users] Re: Puppi parameters in command line

Hi Il giorno mercoledì 26 giugno 2013 00:29:26 UTC+2, NewUser5 ha scritto: > > Hi , > I am a new puppet user. As i am not used yet to ruby and puppet I've > decided to use the puppi module to deploy web applications in my company. > I ve created some specific define , scripts etc and I saw r

Re: [Puppet Users] Fwd: [Module team] Much ado about modules

On Saturday, July 6, 2013 1:30:15 AM UTC+2, Nan Liu wrote: > > On Fri, Jul 5, 2013 at 11:05 AM, Ashley Penney > > > wrote: > >> Now that Puppetlabs has a module team we thought we should start trying >> to keep the community informed as to what we're doing and why on earth >> we're doing it.

Re: [Puppet Users] Fwd: [Module team] Much ado about modules

itHub organization, it can be moved anywhere, eventually under PuppetLabs organization, and, once completed, remain a reference for naming standards) On Monday, July 8, 2013 6:02:25 PM UTC+2, Ashley Penney wrote: > > On Mon, Jul 8, 2013 at 11:12 AM, Alessandro Franceschi > > >

Re: [Puppet Users] Fwd: [Module team] Much ado about modules

Given that https://github.com/stdmod/puppet-modules/blob/master/Parameters_List.md is based on the same resource_argument pattern can we make a step further and define names that can be used for any module and call them "suggested standards"? Restricting the discussion to PuppetLabs modules only is

[Puppet Users] Re: The handy Grail of Modules Standards

://github.com/stdmod/puppet-elasticsearch the latter, in particular, even if not complete, I think is a good example of the reusability and interoperability options that these naming standard suggest. al On Monday, June 17, 2013 11:37:50 AM UTC+2, Alessandro Franceschi wrote: > > Dear al

Re: [Puppet Users] Fwd: [Module team] Much ado about modules

On Tuesday, July 9, 2013 6:23:39 PM UTC+2, jcbollinger wrote: > > > > On Monday, July 8, 2013 11:02:25 AM UTC-5, Ashley Penney wrote: >> >> >> This is definitely something we want to do and need to do. I've been a >> little hesitant to wade down into the whole "these are the specific >> parame

[Puppet Users] Re: Module team update: 2013-07-07 - 2013-07-12

I insist on the question since I've not had answers previously: Any hope the redesign of the PuppetLabs modules will consider the suggested standards discussed here: https://github.com/stdmod/puppet-modules/blob/master/Parameters_List.md ? On Saturday, July 13, 2013 12:24:46 AM UTC+2, Ashley Penn

Re: [Puppet Users] Re: Module team update: 2013-07-07 - 2013-07-12

On Saturday, July 13, 2013 2:47:36 PM UTC+2, Ashley Penney wrote: > > On Sat, Jul 13, 2013 at 6:16 AM, Alessandro Franceschi > > > wrote: > >> I insist on the question since I've not had answers previously: >> Any hope the redesign of the PuppetLabs modu

Re: [Puppet Users] The handy Grail of Modules Standards

as a way to keep the discussion alive. On Saturday, July 13, 2013 6:04:34 PM UTC+2, Ryan Coleman wrote: > > Hey Al, sorry. I went on holiday and then had to unbury myself. I guess > it's time I get my opinion out there. > > > On Mon, Jul 1, 2013 at 2:33 AM, Alessan

[Puppet Users] Re: Changes to allowed function calls in Puppet 3.0

ass/define arguments list (which might be considered somehow a border case)? Any info is welcomed. Best regards Alessandro Franceschi Example42.com On Friday, September 14, 2012 8:22:59 PM UTC+2, Andy Parker wrote: > > This is a heads up to anyone who has written code that calls custom &

Re: [Puppet Users] Module critique

of the resources parameters using class inheritance (yes, the more you avoid class inheritance and the better, but if your module doesn't provide a way to (re)define the behaviour of most of the resources defined in these classes, trying to change them without changing the module becomes almo

[Puppet Users] Re: Run Stages for Particular Modules

It feels like you're overusing a bit too much run stages... Read here for usage recommendations (and limitations): http://docs.puppetlabs.com/puppet/2.7/reference/lang_run_stages.html You can more easily manage relationships inside a class (all the mysql steps can be managed inside the same mysql

[Puppet Users] Re: How to recursively ship files while keeping their modes

Have you tried to add: mode => undef, it might work (not tested). On Wednesday, September 12, 2012 9:43:58 PM UTC+2, Marc Haber wrote: > > Hi, > > I have defined a resource like this: > > file { "/etc/foo/conf.d" : > ensure => directory, > recurse =>

[Puppet Users] Re: How do design next-gen modules, any guidelines ? a question for gurus...

Hi Thomas and John, just bumped in this thread so sorry for replying so late... On Monday, October 22, 2012 6:17:50 PM UTC+2, jcbollinger wrote: > > > > On Monday, October 22, 2012 2:33:18 AM UTC-5, Thomas Guthmann wrote: >> >> Hi, >> >> My dilemma is how should I write my module to be "next-gen

Re: [Puppet Users] The handy Grail of Modules Standards

e works. On Monday, August 5, 2013 11:01:08 PM UTC+2, Jakov Sosic wrote: > > On 06/26/2013 07:27 PM, Alessandro Franceschi wrote: > > Good point. > > In the doc I placed some possible examples on where to assign names, but > > more (or remarks on the ones listed) c

Re: [Puppet Users] The handy Grail of Modules Standards

On Thursday, August 8, 2013 1:45:44 AM UTC+2, Jakov Sosic wrote: > > On 08/06/2013 01:17 AM, Alessandro Franceschi wrote: > > > That's quite nice, I like the reduced verbosity of the code and > > essentiality of an all in one (init.pp) location for resources.

Re: [Puppet Users] The handy Grail of Modules Standards

On Friday, August 9, 2013 9:22:54 PM UTC+2, Jakov Sosic wrote: > > On 08/08/2013 09:10 PM, Alessandro Franceschi wrote: > > natural to use two different parameters, like service_ensure and > > service_enable rather than one like service_status. > > Oh, I see. Simpler f

Re: [Puppet Users] The handy Grail of Modules Standards

te: > > On 2013-08-09 22:56, Alessandro Franceschi wrote: > > > > > > On Friday, August 9, 2013 9:22:54 PM UTC+2, Jakov Sosic wrote: > > > > On 08/08/2013 09:10 PM, Alessandro Franceschi wrote: > > > natural to use two different parameters, li

Re: [Puppet Users] params pattern when writing modules

A small note on params.pp, even if I've largely used it in the Example42 modules there are cases where it's totally uneffective, for example when you've to define there a parameters whose value may change according to another parameter the user may pass to init.pp An example is here: https://gi

[Puppet Users] Re: Custom Function that uses powershell

Functions are executed on the PuppetMaster when compiling the catalog. I don't think you can. You may try some workaround calling a powershell command from a custom fact and use the fact value to manage your logic. On Thursday, September 5, 2013 6:32:21 PM UTC+2, carllindelof wrote: > > Hi All, >

Re: [Puppet Users] The handy Grail of Modules Standards

An update on the stdmod works, which are going on slowly, but still moving. We are getting near to define a basic set of names for modules parameters. In particular there's a pull request where various discussions are ongoing on some basic naming patterns: https://github.com/stdmod/puppet-modules

[Puppet Users] Re: [Puppet-dev] Status of Data in modules

Thanks for the update Eric, very useful to understand the ongoing works on data in modules. On Friday, October 11, 2013 9:01:19 PM UTC+2, Dan Bode wrote: > > > > > On Fri, Oct 11, 2013 at 11:09 AM, Eric Sorenson > > > wrote: > >> >> Thanks to everyone who kicked the tires on the experimental da

[Puppet Users] Re: [Puppet-dev] Status of Data in modules

On Monday, October 14, 2013 9:19:10 AM UTC+2, Erik Dalén wrote: > > > > > On 13 October 2013 12:40, Alessandro Franceschi > > wrote: > >> Thanks for the update Eric, very useful to understand the ongoing works >> on data in modules. >> >> On Fri

[Puppet Users] A standard way to manage monitoring/firewalling in modules

During the works on stdmod naming conventions I wondered if we could find a non intrusive and standard way to allow management of monitoring and firewalling for modules. Since there's not a single solution to that and it would be quite hard to find a shared approach in a reasonable time I though

Re: [Puppet Users] Re: Status of Data in modules

On Tuesday, October 15, 2013 3:35:00 PM UTC+2, R.I. Pienaar wrote: > > > > - Original Message - > > From: "jcbollinger" > > To: puppet...@googlegroups.com > > Sent: Tuesday, October 15, 2013 2:08:10 PM > > Subject: Re: [Puppet Users] Re: Status of Data in modules > > > > > > > >

Re: [Puppet Users] Re: Status of Data in modules

Il giorno mercoledì 16 ottobre 2013 12:14:12 UTC+2, R.I. Pienaar ha scritto: > > > > - Original Message - > > From: "Alessandro Franceschi" > > > To: puppet...@googlegroups.com > > Sent: Wednesday, October 16, 2013 10:54:14 AM > >

[Puppet Users] Re: A note on upcoming module metadata improvements

Il giorno mercoledì 16 ottobre 2013 18:07:57 UTC+2, Ryan Coleman ha scritto: > > We've been working hard to reduce the complexity involved in publishing > modules to the Forge and make it simpler to find great modules. I'm writing > today to give you some background on the problems we're workin

[Puppet Users] Re: A standard way to manage monitoring/firewalling in modules

lly different parameters, occupying the namespace), the name of the parameters. It's basically what is currently done in ex42 modules, where there's a standard, but it's a example42-only standard and does not work with outer modules. I'd pay for having shared and common st

Re: [Puppet Users] Re: Status of Data in modules

Wow, this looks promising: sane, plain and easy to use. Going to test it soon. Looking at things in perspective, how do you think this approach will go along with the one implemented in Puppet 3.3 ? al On Sunday, December 8, 2013 11:19:37 PM UTC+1, R.I. Pienaar wrote: > > > > - Original Mes

[Puppet Users] References on Puppet performance tuning and profiling

Hi all, I'd like to collect some info about Puppet performances, more specifically what are the factors and the relevant "weights" involved in: - catalog compilation times (number of resources, number of relations among resources, number of parameters in classes...) - catalog application times (

Re: [Puppet Users] Puppet module template mentioned at contributor summit

Craig, Not sure to have understood the difference between a defaults.pp pattern and a params.pp pattern, given that I suppose that if there were parameters in the main module class of Gareth's example they would inherit values in params.pp exactly as the defaults example you've written. Can be e

Re: [Puppet Users] Puppet module template mentioned at contributor summit

data mapping. > > It's not that different, but allows for more flexibility and tighter hiera > integration > > Craig > > > > On Wed, Feb 26, 2014 at 2:43 PM, Alessandro Franceschi > > > wrote: > >> Craig, >> Not sure to have understood the diff

[Puppet Users] Re: Problems in Ch. 4 of Pro Puppet 2nd Edition

Hei Jon, your text correction and errors hunting skills are impressive. I'm writing a book about Puppet too and am definitively in time to correct it before printing. There are already technical reviewers doing a great work, but I think you can add great value to the contents and their correctnes

Re: [Puppet Users] Re: Problems in Ch. 4 of Pro Puppet 2nd Edition

On Friday, March 7, 2014 5:16:41 AM UTC+1, Jon Forrest wrote: > > On 3/5/2014 1:26 PM, Alessandro Franceschi wrote: > > Hei Jon, > > your text correction and errors hunting skills are impressive. > > Thanks. I try. > > > I'm writing a book about Pup

[Puppet Users] Re: 3.5 breaks yumrepo resource

Confirm. On Friday, April 4, 2014 7:56:24 AM UTC+2, Jo wrote: > > 3.5 breaks yum repos using mirrorurl and no baseurl. > https://tickets.puppetlabs.com/browse/PUP-2155 > > On Apr 3, 2014, at 2:32 PM, Eric Sorenson > > > wrote: > > Puppet 3.5.0 is now available as an official release.

[Puppet Users] Re: Is there a puppet module for tomcat and apache

I expect this to work: https://github.com/example42/puppet-tomcat even if not in all the different possible tomcat versions / OS combinations, The tomcat::instance define is in production in various Ubuntu/Debian environments. https://github.com/example42/puppet-tomcat/blob/master/manifests/inst

[Puppet Users] Rethinking Puppet modules

Hi all, I've written a blog post with my opinions on the current modules ecosystem: http://www.example42.com/2014/05/31/rethinking-modules-part-1/ The post talks about : What are the reusability features a module should have, imho The distinction between application (component) modules and higher

[Puppet Users] Re: Rethinking Puppet modules

s here where we play the most important game on user code reusability. On Friday, June 20, 2014 5:04:28 PM UTC+2, jcbollinger wrote: > > > > On Thursday, June 19, 2014 11:09:22 AM UTC-5, Alessandro Franceschi wrote: >> >> Hi all, >> I've written a blog post wit

  1   2   >