[Puppet Users] Creating multiple redis instances
Hello guys,
I'm creating a module to manage redis, and facing just a little problem
with that.
I have the following init.pp
class redis {
include redis::install
include redis::service
include redis::params # redis:: params also import
# redis::config and
# redis::monitoring
}
My params class receive some parameters from a define called redisInstance:
class redis::params {
define redisInstance ($redis_port = 6379, $redis_host = "127.0.0.1",
$slaveof = false, $master_port = false) {
include redis::config, redis::monitoring
}
}
Into redisInstance I have two includes to both, configure and monitoring
redis, with I do based on the given parameters.
The problem is that I'm not able to create a second instance just like this:
redis::params::redisInstance {
"redis_6379": redis_port=> "6379", redis_host=>
"192.168.100.97", slaveof => "127.0.0.1", master_port => "6872";
"redis_6380": redis_port=> "6380", redis_host=>
"192.168.100.98", slaveof => "127.0.0.1", master_port => "6880";
}
Finally, the part which should configure multiple instances is on config.pp
and is the following:
file { "/etc/redis/redis_${redis_port}.conf":
ensure => file,
content => template("redis/config/redis.conf.erb"),
mode=> 0644,
notify => Class["redis::service"];
}
My question is, why the "define" redisInstance cannot create multiple
instances when I use the "include" directive, but when I call the "file"
directive into the define it create as many instances as I want ?
For example, If I use the include directive and call de define as the
following:
redis::params::redisInstance {
"redis_6379": redis_port=> "6379", redis_host=>
"192.168.100.97", slaveof => "127.0.0.1", master_port => "6872";
"redis_6380": redis_port=> "6380", redis_host=>
"192.168.100.98", slaveof => "127.0.0.1", master_port => "6880";
}
It just creats a single instance(6379) and not the second one(6380).
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] 3.3.0 bug? Could not prefetch package provider/UTF-8
When I ran into this, what bit me was funky characters hiding in comments in the manifests. On Tue, Sep 17, 2013 at 3:42 PM, Robin Lee Powell < rlpow...@digitalkingdom.org> wrote: > > As of upgrading master and clients to 3.3.0, some of my servers are > saying: > > Error: Could not prefetch package provider 'yum': invalid byte sequence in > UTF-8 > Error: Could not prefetch package provider 'rpm': invalid byte sequence in > UTF-8 > > I can't tell whether this actually stops them from *doing* anything > or not, but I don't think so. > > I have tried various things with LANG and LC_ALL to no effect. > > Ideas? > > -Robin > > -- > http://intelligence.org/ : Our last, best hope for a fantastic future. > .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e > lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e > lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni > li'u > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] 3.3.0 bug? Could not prefetch package provider/UTF-8
As of upgrading master and clients to 3.3.0, some of my servers are saying: Error: Could not prefetch package provider 'yum': invalid byte sequence in UTF-8 Error: Could not prefetch package provider 'rpm': invalid byte sequence in UTF-8 I can't tell whether this actually stops them from *doing* anything or not, but I don't think so. I have tried various things with LANG and LC_ALL to no effect. Ideas? -Robin -- http://intelligence.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: b64_zlib_yaml errros after server upgrade to
Well, In case anyone is interested, after a rollback with yum to puppet-server-3.2.4-1.el6.noarch, it works again, with no errors. It also seems to work well with 3.3.0 clients. Thanks. On Tue, Sep 17, 2013 at 4:20 PM, Andrei-Florian Staicu < andrei.sta...@gmail.com> wrote: > Again, sorry for lots of emails. > > After updating the client to puppet-3.3.0-1.el6.noarch, i now get the > following: > puppet agent --test --noop > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not intern from pson: source '%7B%22timestamp%22%3' not in PSON! > this message sometimes changes into > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not intern from pson: source '%7B%22expiration%22%' not in PSON! > or > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not intern from pson: source '%7B%22values%22%3A%7' not in PSON! > > After some searching around, i found this: cd > /usr/share/puppet-dashboard/config/ ; rake db:migrate , but did not help > (and it shouldn't do anything, since the puppetdb was not upgraded). > > Thanks for any pointers. > > > > On Tue, Sep 17, 2013 at 3:29 PM, Andrei-Florian Staicu < > andrei.sta...@gmail.com> wrote: > >> Sorry, I pasted the wrong message. These are the errors: >> puppet agent --test --noop >> Error: Could not retrieve catalog from remote server: Error 400 on >> SERVER: Could not intern from b64_zlib_yaml: invalid code lengths set >> >> puppet agent --test --noop --debug >> Error: Could not retrieve catalog from remote server: Error 400 on >> SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat >> >> > > > -- > Beware of programmers who carry screwdrivers! > -- Beware of programmers who carry screwdrivers! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Dashboard not working (406 Not Acceptable)
I ran into the same issue, and this resolved it. Thanks!
On Thursday, June 21, 2012 8:04:13 AM UTC-5, James Tan wrote:
>
> Old thread, but I ran into the same problem so figured I'll post my
> solution here. In my case, I added more verbose logging which pointed me to
> the missing "spool" directory. Running the following commands fixed it:
>
> mkdir -p /usr/share/puppet-dashboard/spool
> chown puppet-dashboard:puppet-dashboard spool
>
> Regards,
> James T.
>
> On Monday, November 21, 2011 2:13:27 PM UTC+1, Galed Friedmann wrote:
>>
>> Anybody? Any ideas?
>>
>> Thanks again
>>
>> On Sun, Nov 13, 2011 at 2:45 PM, Galed Friedmann
>>
>> > wrote:
>>
>>> Hi all,
>>> I've created a replication of my puppet environment in order to set it
>>> up in a new location.
>>> I've created an exact replication of my master server which is running
>>> the puppet master, dashboard server, and mysql.
>>>
>>> Everything is working fine except for the dashboard. The master is
>>> configured to send reports to dashboard and indeed is sending them, but
>>> looking at production.log in dashboard I see this:
>>>
>>> Processing ReportsController#upload (for 127.0.0.1 at 2011-11-13
>>> 12:43:26) [POST]
>>> Parameters: {"action"=>"upload", "controller"=>"reports"}
>>> Completed in 1ms (View: 0, DB: 0) | 406 Not Acceptable [
>>> http://localhost/reports/upload]
>>>
>>> For every attempt of the master to send a report.
>>> This is a working configuration so I guess I missed something when I
>>> changed the setting of the new server, any idea what might be wrong here?
>>>
>>> puppet master configuration:
>>> [master]
>>> storeconfigs = true
>>> dbadapter = mysql
>>> dbuser = ...
>>> dbpassword = ...
>>> dbserver = localhost
>>> dbsocket = /var/run/mysqld/mysqld.sock
>>>
>>> reports = store, http
>>> reporturl = http://localhost:3000/reports/upload
>>>
>>> Thanks!
>>>
>>> --
>>> 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/-/mGPKjqlxWY0J.
>>> To post to this group, send email to puppet...@googlegroups.com
>>> .
>>> To unsubscribe from this group, send email to
>>> puppet-users...@googlegroups.com .
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Fail/stop after a step fails?
Is it possible to get puppet to just *give up* if a particular step fails? Thousands upon thousands of "Skipping because of failed dependencies" gets really old. -Robin -- http://intelligence.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] rspec-puppet require syntax
Can someone tell me the correct way to specify the following require
statement in an rspec-puppet test?
*require =>
[Class['ssl'],Class['pcre3'],Staging::Extract["nginx-${version}.tar.gz"]]*
I tried this: *'require' =>
"[Class['ssl'],Class['pcre3'],Staging::Extract['nginx-1.4.1.tar.gz']]"* but
got the following error:
*Failure/Error: )
*
*expected that the catalogue would contain Exec[install_nginx] with require
set to
`"[Class['ssl'],Class['pcre3'],Staging::Extract['nginx-1.4.1.tar.gz']]"`
but it is set to `[Class[Ssl]{:name=>"Ssl"}, Class[Pcre3]{:name=>"Pcre3"},
Staging::Extract[nginx-1.4.1.tar.gz]{:name=>"nginx-1.4.1.tar.gz"}]` in the
catalogue*
I've tried every combination of different quotes, removing the inner
quotes, capitalising the resource titles, and even just copying and pasting
what the error above says the catalogue is reporting, but it just doesn't
work. I thought I had the syntax for requires figured out, but apparently
not.
Thanks,
Guy
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Fail/stop after a step fails?
On Tue, Sep 17, 2013 at 12:35:15PM -0700, Robin Lee Powell wrote: > > Is it possible to get puppet to just *give up* if a particular > step fails? Thousands upon thousands of "Skipping because of > failed dependencies" gets really old. Or, indeed, have it stop after a particular step *succeeds* would be fine too. -Robin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] fact_values id
Hello, We seem to have run out of values for our id field in the fact_values table – how big should we be making the field? (we're using mysql) - should we make it an unsigned bigint? Thanks, -Roy -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Configuring a Windows Domain Controller (DC) using puppet
Hi Rich dcpromo.exe with an answers file is a great idea. Thanks for that ! This will give me a machine with DC and DNS (but not a DHCP server). Since I am working with a test environment, I will be having DHCP, DNS and DC on the same 2008 R2 machine. Do you have references I can use to add a DHCP role too? I am not too familiar with dism. Thanks Harsh On Friday, September 6, 2013 6:48:35 AM UTC-7, Rich Siegel wrote: > > I wrote this for managing dns. > https://github.com/rismoney/puppet-windns > > If you want to build a dc, dcpromo creates and uses a scripted unattended > file.http://technet.microsoft.com/en-us/library/cc732887.aspx > > You could easily use an exec resource to run dcpromo. Use an unless > param script to see if target is a dc already. > > Dhcp shouldn't be colo on a dc, but you could add roles with dism module > and leverage powershell module to do anything you want. In 2012 dcpromo is > powershell... > > HTH, > Rich > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: /var/opt/lib/pe-puppet/reports/$hostname yaml files not recent
By default, reports are not stored on the individual nodes, but sent to the master. There are some situations where local files get created, mostly involving the node running standalone. Not sure if PE has different defaults, but normally you should find all reports on the master, in the directory specified by reportdir. http://docs.puppetlabs.com/references/latest/configuration.html#reports You should check all the report* parameters on that page for correctness in your environment. Details on the report formats is on this page. http://docs.puppetlabs.com/references/latest/report.html An option to 'reports' that is oddly not mentioned on that page is the puppetdb option, which is to store reports in puppetdb, and is described on this page. http://docs.puppetlabs.com/puppetdb/1.4/connect_puppet_master.html On Monday, September 16, 2013 9:10:05 AM UTC-7, root wrote: > > Still cannot figure out why I have such a variety of dates for the yaml > files that exist in /var/opt/lib/pe-puppet/reports/`hostname` on each node. > Each node is configured with "report = true", and the reports are > supposedly being sent to the Master. Not sure at all why sometimes I get a > local yaml file, and sometimes I don't. > > Anyway, I'm using Puppet Enterprise, and my reading of the docs tells me > the Master is storing the info from each run in PuppetDB. Anyone have any > luck extracting info from PuppetDB? Again, what I'm looking for is what > Puppet changed or wants to change on each node. Thanks. > > On Saturday, September 14, 2013 3:16:35 PM UTC-4, root wrote: > >> Cross-posted from Puppet Enterprise Users: >> >> Is Puppet Enterprise (3.0) supposed to create a yaml file in >> /var/opt/lib/pe-puppet/reports/$hostname every time it runs? Because the >> files in this directory on all my nodes are not very consistent and they >> are not recent. If I do a puppet run on the node either through >> the Console or manually on the the node, it does not create a new yaml >> report file. >> >> My bigger need is to generate my own custom reports from Puppet runs. I >> thought these yaml files would be easier to parse than the log messages >> sent to syslog. The information I want to display is a summary of what >> Puppet found to change for particular class/modules. >> >> Thanks. >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: The security of the puppet master
On Tue, Sep 17, 2013 at 06:18:48AM -0700, jcbollinger wrote:
>
>
> On Tuesday, September 17, 2013 1:20:40 AM UTC-5, huangm...@gmail.com wrote:
> >
> > I want the puppetmaster can sign the manifest. avoid some guys publish
> > dangerous manifest to agent. like exec{"foo": command=>"rm / -rf";}
> >
> >
> Sure, but signed manifest code also just verifies (with reasonable
> confidence but not absolute certainty) that the manifests were signed by a
> particular authority. It's not qualitatively different in that respect;
> it's just a question of how great your trust in the signer can or should be.
>
Ahh, but many is the time I wished we had a signing mechanism for forge
modules.
--
-ashley
Did you try poking at it with a stick?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Need help with defining same package resource in two modules
On Tuesday, September 17, 2013 1:59:02 AM UTC-5, Martin Alfke wrote: > > > On Sep 17, 2013, at 8:18 AM, Rahul Khengare > > wrote: > > > Hi Mani, > > > > Case2: A=true, when B runs it fails > > Error 400 on SERVER: > > Duplicate definition: Package[pkg1] is already defined in > > file A at line ; cannot redefine at > > > > How do i overcome this issue to complete the workflow of module B in > both cases (where A is enabled or disabled) > > > > If module A get enable then re-declaration of package[pkg1] resource is > happening. Here you can disable the module B. > > > > Make your package resource virtual and realise the resource in both > modules. > > > And to be clear, the virtual package declaration needs to be factored out of the two classes you presented into a separate one that each class that realizes it will declare. That class could be in module A or B, or it could as easily be in any other module, but there can still be only one declaration of each resource, whether concrete or virtual. In that case, however, you could also just put a concrete declaration of pkg1 into that third class, and then including that class would be sufficient -- you wouldn't need to realize any virtual package resource. Virtual resources make sense in this sort of scheme mainly when their declaring class doesn't know whether the resource will be wanted or not for any given node. The most canonical example I know is system users: you can have a class that declares virtual User resources for all of the members of a (smallish) organization, which is included on all nodes. Then on a node-by-node basis, the appropriate users for each node are realized. If the main purpose of a class is to declare a specific resource, however, then it doesn't usually make sense for the resource to be declared virtually. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: b64_zlib_yaml errros after server upgrade to
Again, sorry for lots of emails. After updating the client to puppet-3.3.0-1.el6.noarch, i now get the following: puppet agent --test --noop Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from pson: source '%7B%22timestamp%22%3' not in PSON! this message sometimes changes into Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from pson: source '%7B%22expiration%22%' not in PSON! or Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from pson: source '%7B%22values%22%3A%7' not in PSON! After some searching around, i found this: cd /usr/share/puppet-dashboard/config/ ; rake db:migrate , but did not help (and it shouldn't do anything, since the puppetdb was not upgraded). Thanks for any pointers. On Tue, Sep 17, 2013 at 3:29 PM, Andrei-Florian Staicu < andrei.sta...@gmail.com> wrote: > Sorry, I pasted the wrong message. These are the errors: > puppet agent --test --noop > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not intern from b64_zlib_yaml: invalid code lengths set > > puppet agent --test --noop --debug > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not intern from b64_zlib_yaml: invalid bit length repeat > > -- Beware of programmers who carry screwdrivers! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: The security of the puppet master
On Tuesday, September 17, 2013 1:20:40 AM UTC-5, huangm...@gmail.com wrote:
>
> I want the puppetmaster can sign the manifest. avoid some guys publish
> dangerous manifest to agent. like exec{"foo": command=>"rm / -rf";}
>
> there is a software named samhain. it's a integrity checker and host
> intrusion detection system . when compile the source code of the software,
> you can configure a cert with it.
> when the software running. it's only read the cert signed configure file.
>
> any way, agent use https connect master . the ssl connect just let the
> connecting is safe, but not the manifest code .
>
>
Sure, but signed manifest code also just verifies (with reasonable
confidence but not absolute certainty) that the manifests were signed by a
particular authority. It's not qualitatively different in that respect;
it's just a question of how great your trust in the signer can or should be.
In fact, if Puppet manifests are developed on systems that do have network
connections before being passed through your disconnected signing
authority, then there is an opportunity for an attacker to compromise the
development systems and modify manifests before they are signed. That
reduces the security of your approach to no better than a standard master /
agent arrangement, except that it also exposes configuration secrets to
every single machine under management, as I discussed before.
There can be no question that Puppet manifests are security-sensitive
resources, but digitally signing them and handing them to clients in that
form is not inherently more secure than Puppet's standard approach, and in
some ways it is less so. Information security is all about who you trust,
about what, and to what extent. You can move around the pieces to change
your exposure profile -- which is what you have done -- but it's very
difficult to genuinely improve security without introducing fundamentally
new technology or architecture, which you have not done.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet agent and puppet master
Thanks !!
:)
On Monday, September 16, 2013 4:12:44 PM UTC+2, jcbollinger wrote:
>
>
>
> On Monday, September 16, 2013 7:40:35 AM UTC-5, Adeel Bhatti wrote:
>>
>> Thanks for your reply !
>> This would be really cool if the agent can look and identify the manifect
>> changes !
>> I have a service restart in my class, so I want to execute that only if
>> there is some change in the configuration/manifest !
>> Regards
>> Adeel
>>
>>
>
> Puppet can do that. See below.
>
> In answer to your original question, it is usual for each Puppet client to
> run the agent on a regular schedule, either using its built-in daemon mode
> (i.e. running it as a service) or via an external scheduler, such as cron.
> That way there is no need to touch individual clients to roll out
> configuration changes -- it is sufficient to change the manifests and/or
> data on the master.
>
> It is important to understand that Puppet is a state management service,
> not a script engine. The distinction shows up here in that the Puppet
> agent's normal behavior is to check the properties of each managed
> resource, and to apply only those changes needed to put it into the target
> state. Resources that are already in the target state are not changed in
> any way.
>
> Thus, whenever the agent modifies a resource, such as a service's
> configuration file, it constitutes a genuine change. Puppet has a
> mechanism for notifying resources about such changes in other resources,
> and it is particularly well supported for exactly the situation you
> describe: restarting services when their configuration changes. It can
> look like this:
>
> file { '/etc/myservice.conf':
> ensure => 'file',
> content => template('myservice.conf.tmpl'),
> # ...
> }
>
> service { 'myservice':
> enable => true,
> ensure => running,
> subscribe => File['/etc/myservice.conf']
> }
>
> The magic is in the 'subscribe' parameter. It says that the service needs
> to be "refreshed" if the agent applies any changes to the referenced file
> resource. The meaning of "refresh" varies by resource type, but for
> services it means to restart the service.
>
>
> John
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Using Puppet for downgrading Varnish (circular dependency)
Hello! Help me please how do I get puppet to downgrade several packages at the same time? I want to downgrade to samba 3.6.9 to 3.5.10 for this I am writing yum downgrade samba-winbind-3.5.10, samba-common-3.5.10, samba-common-clients-3.5.10 and how do I get puppet to do the same? is it possible? Thank you! On Monday, July 1, 2013 2:45:26 PM UTC+4, Stefan Pommerening wrote: > > Hi Wolf, > > indeed that 'exec' solution is what I've found when searching for a > solution. > In my situation this won't help - unfortunately. > > Nevertheless I tracked down the main problem to be caused by different > usage scenarios for yum. > > When upgrading I have to specify only the main varnish package 'varnish'. > When downgrading I have to specify both the 'varnish' and the > 'varnish-libs' > package for yum. > > As long as puppet does not support both options we will have to use work- > arounds. ;-) > > Stefan > > > > -- ;; -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: b64_zlib_yaml errros after server upgrade to
Sorry, I pasted the wrong message. These are the errors: puppet agent --test --noop Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid code lengths set puppet agent --test --noop --debug Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: puppet-chocolatey error
I am using the puppet-chocolatey module. The forge page linked here to submit
issues. Perhaps the link is not correct?
Nate
On Tue, Sep 17, 2013 at 8:23 AM, Sneha More
wrote:
> Hi Nate,
>install_options is an array of additional options to pass when
> installing a package. so you can not pass 'latest' parameter to it, instead
> you can try this for latest version installation
> package { 'Teamspeak3' :
> ensure => latest,
> provider=> 'chocolatey',
> }
> Thanks & Regards
> Sneha More,
> NTT DATA GTS, OSS Center, India (pune)
> On Tuesday, September 17, 2013 8:11:04 AM UTC+5:30, Nate Walck wrote:
>>
>> I started using chocolatey today and when trying to install an app
>> (Teamspeak3 in this case), I got the following error:
>>
>> Info: Applying configuration version '1379384597'
>> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line
>> ==no version
>> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line
>> ==no version
>> Notice:
>> /Stage[main]/Gaming_desktop::Applications/Package[Teamspeak3]/ensure: created
>> Notice: Finished catalog run in 6.96 seconds
>> Press any key to continue . . .
>>
>> I ran it again, same exact error.
>>
>> The config for it was:
>>
>> package { 'Teamspeak3' :
>> ensure => installed,
>> provider=> 'chocolatey',
>> install_options => 'latest',
>> }
>>
>> I noticed when I changed it to:
>>
>> package { 'Teamspeak3' :
>> ensure => installed,
>> provider=> 'chocolatey',
>> }
>>
>> It gave me the same error found here:
>>
>> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line
>> ==no version
>> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line
>> ==no version
>>
>> But it actually stared downloading the software rather than saying it
>> installed (which it hadn't previously).
>>
>> Am I using 'latest' incorrectly, or is something else going on here?
>>
>> Thanks,
>>
>> Nate
>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-chocolatey error
Hi Nate,
install_options is an array of additional options to pass when
installing a package. so you can not pass 'latest' parameter to it, instead
you can try this for latest version installation
package { 'Teamspeak3' :
ensure => latest,
provider=> 'chocolatey',
}
Thanks & Regards
Sneha More,
NTT DATA GTS, OSS Center, India (pune)
On Tuesday, September 17, 2013 8:11:04 AM UTC+5:30, Nate Walck wrote:
>
> I started using chocolatey today and when trying to install an app
> (Teamspeak3 in this case), I got the following error:
>
> Info: Applying configuration version '1379384597'
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Notice: /Stage[main]/Gaming_desktop::Applications/Package[Teamspeak3]/ensure:
> created
> Notice: Finished catalog run in 6.96 seconds
> Press any key to continue . . .
>
> I ran it again, same exact error.
>
> The config for it was:
>
> package { 'Teamspeak3' :
> ensure => installed,
> provider=> 'chocolatey',
> install_options => 'latest',
> }
>
> I noticed when I changed it to:
>
> package { 'Teamspeak3' :
> ensure => installed,
> provider=> 'chocolatey',
> }
>
> It gave me the same error found here:
>
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
>
> But it actually stared downloading the software rather than saying it
> installed (which it hadn't previously).
>
> Am I using 'latest' incorrectly, or is something else going on here?
>
> Thanks,
>
> Nate
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet ignores schedules
Hello,
the following small code works, but the file /tmp/test will never be
created because the schedule is skipped because running on an host.
1. site.pp:
2. test::test_define {hallo:
3. }
4. include test
5.
6. test/init.pp:
7. class test {
8. }
9. test/test_define.pp
10. define test::test_define {
11. schedule {$name:
12. period => daily,
13. range => '2-4',
14. repeat => 1;
15. }
16.
17. file {'/tmp/test':
18. ensure => present,
19. schedule => $name;
20. }
21. }
22.
23. Debug Log:
24.
25.
26. Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml;
using pson
27. Info: Caching catalog for test2.zdkwh.mlrbw.net
28. Debug: Creating default schedules
29. Debug: Loaded state in 0.07 seconds
30. Info: Applying configuration version '1379405805'
31. Debug: /Schedule[daily]: Skipping device resources because running
on a host
32. Debug: /Schedule[monthly]: Skipping device resources because running
on a host
33. Debug: /Schedule[hourly]: Skipping device resources because running
on a host
34. Debug: /Schedule[never]: Skipping device resources because running
on a host
35. *Debug:
/Stage[main]//Node[default]/Test::Test_define[hallo]/File[/tmp/test]: Not
scheduled*
36. *Debug:
/Stage[main]//Node[default]/Test::Test_define[hallo]/Schedule[hallo]:
Skipping device resources because running on a host*
37. Debug: /Schedule[weekly]: Skipping device resources because running
on a host
38. Debug: /Schedule[puppet]: Skipping device resources because running
on a host
39. Debug: Finishing transaction 70022790653200
40. Debug: Storing state
41. Debug: Stored state in 0.17 seconds
42. Notice: Finished catalog run in 0.26 seconds
43. Debug: report supports formats: b64_zlib_yaml pson raw yaml; using
pson
Thanks in advance!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Run a custom function through the ruby debugger
Hallo, I'm developing a custom function that is exhibiting some odd behavior, so I would like to debug it. How do I load it in the ruby shell in a way that lets me execute it? I have tried the steps on the documentation: irb(main):001:0> require 'puppet' > > => true > > irb(main):002:0> require 'phash2text.rb' > > => true > > irb(main):003:0> Puppet::Parser::Functions.function(:hash2text) > > => "function_hash2text" > > irb(main):004:0> function_hash2text > > NameError: undefined local variable or method `function_hash2text' for >> main:Object > > from (irb):4 > > from :0 > > But how can I actually execute the function? Thanks, Andrea -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-chocolatey error
> >I think puppet does not provide the support for "chocolatey". Not out-of-the-box, but https://github.com/chocolatey/puppet-chocolatey adds that support. Cheers, Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-chocolatey error
Hi Nate,
I think puppet does not provide the support for "chocolatey".
See
http://docs.puppetlabs.com/references/latest/type.html#package-attribute-provider
for
list of available provider which is supported by puppet.
Thanks and Regards,
Rahul Khengare,
NTT DATA OSS Center, Pune, India.
On Tuesday, September 17, 2013 8:11:04 AM UTC+5:30, Nate Walck wrote:
>
> I started using chocolatey today and when trying to install an app
> (Teamspeak3 in this case), I got the following error:
>
> Info: Applying configuration version '1379384597'
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Notice: /Stage[main]/Gaming_desktop::Applications/Package[Teamspeak3]/ensure:
> created
> Notice: Finished catalog run in 6.96 seconds
> Press any key to continue . . .
>
> I ran it again, same exact error.
>
> The config for it was:
>
> package { 'Teamspeak3' :
> ensure => installed,
> provider=> 'chocolatey',
> install_options => 'latest',
> }
>
> I noticed when I changed it to:
>
> package { 'Teamspeak3' :
> ensure => installed,
> provider=> 'chocolatey',
> }
>
> It gave me the same error found here:
>
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
> Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
> version
>
> But it actually stared downloading the software rather than saying it
> installed (which it hadn't previously).
>
> Am I using 'latest' incorrectly, or is something else going on here?
>
> Thanks,
>
> Nate
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] SSH configuration Question
This is all going to depend on the criteria on which you will decide which ports gets used where. You can make a standard puppet configuration and have code in the template (ERB file) to decide what port to bind sshd on depending on facts from facter. If the default facter you are working with does not provide the facts that you would like to have, it is possible to easily add other facts. Another way you can do this is to make a puppet define with the port number as parameter that you can then use in a template file. You can then specify the configuration you want on a per-host basis. Hope this helps, Antoine Le 2013-09-16 05:00, John.1209 a écrit : > I'm somewhat new to puppet and I have this issue with SSH. > > Let's say I have 6 different SSH configurations. How do I get puppet to install or upgrade SSH based on the configurations? Assume the O/S and SSHD versions are all the same. > > So let's say I have different configurations that run SSHD with the following ports: > > Port 22 > Port > Port 1000, and so on. > > How can I write or modify the puppet openssh module to update the different configurations? > > Thanks in advance. > > John > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users [1]. > For more options, visit https://groups.google.com/groups/opt_out [2]. Links: -- [1] http://groups.google.com/group/puppet-users [2] https://groups.google.com/groups/opt_out -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet-chocolatey error
I started using chocolatey today and when trying to install an app
(Teamspeak3 in this case), I got the following error:
Info: Applying configuration version '1379384597'
Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
version
Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
version
Notice: /Stage[main]/Gaming_desktop::Applications/Package[Teamspeak3]/ensure:
created
Notice: Finished catalog run in 6.96 seconds
Press any key to continue . . .
I ran it again, same exact error.
The config for it was:
package { 'Teamspeak3' :
ensure => installed,
provider=> 'chocolatey',
install_options => 'latest',
}
I noticed when I changed it to:
package { 'Teamspeak3' :
ensure => installed,
provider=> 'chocolatey',
}
It gave me the same error found here:
Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
version
Warning: Puppet::Type::Package::ProviderChocolatey: Failed to match line ==no
version
But it actually stared downloading the software rather than saying it installed
(which it hadn't previously).
Am I using 'latest' incorrectly, or is something else going on here?
Thanks,
Nate
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Need help with defining same package resource in two modules
Refer http://docs.puppetlabs.com/puppet/2.7/reference/lang_virtual.html this for creating and realizing the virtual resource. Thanks and Regards, Rahul Khengare NTT DATA OSS Center, Pune, India. On Tue, Sep 17, 2013 at 12:29 PM, Martin Alfke wrote: > > On Sep 17, 2013, at 8:18 AM, Rahul Khengare wrote: > > > Hi Mani, > > > > Case2: A=true, when B runs it fails > > Error 400 on SERVER: > > Duplicate definition: Package[pkg1] is already defined in > > file A at line ; cannot redefine at > > > > How do i overcome this issue to complete the workflow of module B in > both cases (where A is enabled or disabled) > > > > If module A get enable then re-declaration of package[pkg1] resource is > happening. Here you can disable the module B. > > > > Make your package resource virtual and realise the resource in both > modules. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/mOHDwWzINdc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] b64_zlib_yaml errros after server upgrade to
Hi, After upgrading the puppet server to puppet-server-3.3.0-1.el6.noarch, I get the following on a puppet-3.2.2-1.el6.noarch client: puppet agent --test --noop Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run However, the erros look different with debug: puppet agent --test --noop --debug Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run And with trace: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:185:in `is_http_200?' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:100:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:197:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:351:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:350:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in `prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:353:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:327:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:456:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:504:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:132:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:86:in `execute' /usr/bin/puppet:4 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Any idea if this is a recognized bug? Thanks. -- Beware of programmers who carry screwdrivers! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
