Re: [Puppet Users] Re: PuppetDB queue problem
Hey Mike,
Thanks for the suggestions, but we already checked the IO rates, and they
seemed fine. And yes, PuppetDB and Postgres are on the same machine for
now, but we plan to change that sometime in the future.
Cheers,
ak0ska
On Tuesday, March 5, 2013 12:51:16 AM UTC+1, Mike wrote:
Is puppetdb and postgres on the same server?
How many node does your environment have?
I had a similar issue and it was linked to I/O. Can you look at that?
Mike { Thanks = always }
On Mar 4, 2013, at 4:55 PM, Ken Barber k...@puppetlabs.com javascript:
wrote:
Any progress today?
On Fri, Mar 1, 2013 at 9:00 AM, ak0ska akos@gmail.com javascript:
wrote:
Yes, maybe not. The next step will be to recreate it from scratch.
On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote:
Well, I don't think a vacuum will help you - I imagine something is
wrong with the schema right now or some data migration failed during
upgrade. Esp. if you had migration issues from your custom PuppetDB.
Of course I can't prove this with so little knowledge - but it
certainly does raise a red flag.
The only other option is to compare the schemas with a known good one,
and compare the database data to try and find the fault. This however
is prone to error and might be time-consuming. Recreating the database
sounds like a far more reliable option with a lot more guarantees
around it.
ken.
--
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...@googlegroups.com javascript:.
To post to this group, send email to
puppet...@googlegroups.comjavascript:.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
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...@googlegroups.com javascript:.
To post to this group, send email to
puppet...@googlegroups.comjavascript:.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet MySQL Module
Hi all,
I'm using the MySQL module
https://forge.puppetlabs.com/puppetlabs/mysql and I can't find the way
to give certain permission to a secondary user over an already created
DB (which has it own user):
mysql::db { 'galaxy':
user = 'galaxy',
password = 'XX',
host = 'localhost',
grant= ['all'],
}
Now I would like to give select privileges on galaxy DB to user arnau,
but I can't find the way for doing so.
Could someone give a hand?
TIA,
Arnau
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet MySQL Module
You can use the database_grant resource type. Here is an example:
database_grant { ${user}@${::hostname}/${db}:
privileges = ['select'], # anything you want
require= Database_user[${user}@${::hostname}],
}
set the $user and $db variables to what you want ;)
More information can be found on the github README file for module.
--
Nikola
On Tue, Mar 05, 2013 at 09:21:28AM +0100, Arnau Bria wrote:
Hi all,
I'm using the MySQL module
https://forge.puppetlabs.com/puppetlabs/mysql and I can't find the way
to give certain permission to a secondary user over an already created
DB (which has it own user):
mysql::db { 'galaxy':
user = 'galaxy',
password = 'XX',
host = 'localhost',
grant= ['all'],
}
Now I would like to give select privileges on galaxy DB to user arnau,
but I can't find the way for doing so.
Could someone give a hand?
TIA,
Arnau
--
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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet MySQL Module
On Tue, 5 Mar 2013 10:48:16 +0200
Nikola Petrov wrote:
Hi Nikola,
You can use the database_grant resource type. Here is an example:
database_grant { ${user}@${::hostname}/${db}:
privileges = ['select'], # anything you want
require= Database_user[${user}@${::hostname}],
}
set the $user and $db variables to what you want ;)
More information can be found on the github README file for module.
thanks alot, I already had one database_grant but I've realized that I
had a typo in the dtaabses (well, I was refering to antoher...
galaxytest, for that reason it was not working.
thanks a lot,
Cheers,
Arnau
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet MySQL Module
On Tue, 5 Mar 2013 10:48:16 +0200 Nikola Petrov wrote: You can use the database_grant resource type. Here is an example: But how may I set its password? (it's working cause my user was correctly created and I set its passwd before). *Sorry, I did reply too early.. Cheers, Arnau -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Struggling to get Hiera to work
Hi chaps, thanks for your responses.
Running puppetmaster in debug mode fixed the problem, as a side effect.
I hadn't appreciated that after editing /etc/puppet/hiera.yaml
puppetmaster needs to be restarted - I thought that file would be read
each time hiera grabs a variable.
TL;DR: I turned it off and on again ;)
Cheers,
Jonathan
On 05/03/13 07:34, Denmat wrote:
Hi,
You can run the master in debug mode and it will show you where puppet is
looking for the hiera files.
Give it a whirl,
Den
On 04/03/2013, at 22:49, Jonathan Gazeley jonathan.gaze...@bristol.ac.uk
wrote:
I'm setting up Hiera in my multi-environment puppetmaster for the first time.
I've written /etc/puppet/hiera.yaml, defined the hierarchies and created a
couple of data files with sample data in them. When queried from the
commandline, it works:
[jg4461@puppet ~]$ hiera -d -c /etc/puppet/hiera.yaml motd::banner
environment=netops_jg4461
DEBUG: Mon Mar 04 11:42:29 + 2013: Hiera YAML backend starting
DEBUG: Mon Mar 04 11:42:29 + 2013: Looking up motd::banner in YAML backend
DEBUG: Mon Mar 04 11:42:29 + 2013: Looking for data source netops_jg4461
DEBUG: Mon Mar 04 11:42:29 + 2013: Found motd::banner in netops_jg4461
MOTD BANNER for NETOPS
However, when I try to reference this variable in a manifest with syntax like
this:
class motd {
file { 'motd':
name= '/etc/motd',
mode= '0644',
owner = 'root',
group = 'root',
content = hiera('motd::banner'),
}
}
It fails with this error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item motd::banner in any Hiera data file and no default
supplied at
/home/jg4461/PUPPETROOT/environments/common/modules/motd/manifests/init.pp:7 on
node **.bris.ac.uk
My hiera.yaml points to the right location (the puppet dev environment is being
served from my homedir on the puppetmaster but all hiera data is stored in
/etc/puppet/hiera, with the production puppet environment).
What kind of things should I be looking for here?
Thanks,
Jonathan
--
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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet to copy file instead of symlink
hi, I want to have puppet copy a file, but I can only reference the file within the puppet configuration from the symlink. Have tried file = true and other options but puppet only copies the symlink. Is this possible? many thanks, David. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Package(Java.ActiveMQ etc..) Manual Installation Issues.
Hi All,
I am trying to install Java or ActiveMQ manually into my agent server from
master, Installation is working fine for me, but the issues which I am
facing is whenever I run *puppet agent -t* in my agent ActiveMQ installing
again and again,basically ActiveMQ installation is not checking in my
manifests.
1.) How we can check custom service running using manifest? 2) How we can
achieve this with conditional(if,else...) statement?
Please find my code below..
class activemq {
include wget::gxactivemq
exec { 'ActiveMQExe':
command = /bin/tar xzf
/gx/mnt/software/ESB/apache-activemq-5.5.1-bin.tar.gz,
cwd = /gx/mnt/software/ESB/,
require = [wget::fetch[activemqDownload]],
logoutput = true,
}
file { '/gx/logical/ESB/':
ensure = link,
owner = ubuntu,
group = ubuntu,
target = '/gx/mnt/software/ESB/',
require = [Exec[ActiveMQExe]],
}
file { '/gx/logical/ESB/apache-activemq-5.5.1':
ensure = directory,
owner = ubuntu,
group = ubuntu,
recurse = true,
require = [Exec[ActiveMQExe],File[/gx/logical/ESB/]],
}
file { '/gx/logical/ESB/apache-activemq-5.5.1/conf':
ensure = directory,
owner = ubuntu,
group = ubuntu,
mode = 777,
recurse = true,
require = [Exec[ActiveMQExe],File[/gx/logical/ESB/]],
}
}
Thanks,
Jithin
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problem while Installing software (agent) from puppetmaster to clients
Hi,
there's a number of problems with your approach. Have you done any
simple deployment tasks using puppet to get you started? I advise to get
very familiar with the basics before trying a more involved management
operation such as newrelic installation.
On 03/04/2013 08:22 AM, guptasachin1112...@gmail.com wrote:
I had installed puppet master and client on two different machines.
machine A has puppet master and machine B has client. both are centos6
64 bit machines.
Machine B (client) is successfully connected to master (machine A). My
aim is to install New Relic agent (server monitorinig tool) on different
clients. I had installed new relic agent on machine A and trying to
build a module so that I can deploy new relic agent remotely to my
clients. right now I have only one client but there can be n number of
clients.
This is fine so far.
steps carried out on puppetmaster Machine A
a) I had created a new module mcollective under /etc/puppet/modules
directory.
Why is the module called mcollective? Should it not be called newrelic
instead?
under manifests, I had created a init.pp with the follwoing contents
#Module: mcollective
#
# Class: mcollective
# Description:
# This class does it all.
#
# Files:
# /etc/yum.repos.d/newrelic.repo
#
#
class mcollective {
$my_repo = 'newrelic_repo'
if $my_repo { include mcollective::${my_repo} }
$my_install = 'install'
if $my_install { include mcollective::${my_install} }
}
Putting the class names into variables does not strike me as really
benefitting. And it does break the KISS principle.
class mcollective::newrelic_repo {
file { '/etc/yum.repos.d/newrelic.repo':
owner = root,
group = root,
mode = 644,
source = 'puppet:///modules/mcollective/newrelic.repo',
}
}
That's all right.
class mcollective::install {
exec { 'Installing newrelic-repo':
command = 'yum -y install newrelic-repo*',
timeout = 600,
}
}
With puppet, you should use exec as little as possible. Instead, try
package { newrelic-sysmond: ensure = installed }
This won't work until the repo has been created, so tell puppet about
the order:
package { newrelic-sysmond:
ensure = installed,
require = Class[newrelic::repo],
}
b) I had also copied newrelic.repo from /etc/yum.repos.d/newrelic.repo
to /etc/puppet/modules/manifests
This won't work. If you want to make a file available using file { name:
source = ... }, it needs to be put into an appropriate files tree, such
as /etc/puppet/modules/newrelic/files/...
c) under files diretcory, I had created sites.pp as
Now this one should be under manifests!
import 'mcollective'
Importing modules is deprecated. I advise to not even bother with the
import statement.
node 'basenode' {
include mcollective
include mcollective::newrelic_repo
include mcollective::install
}
That's fine.
node 'WA19487ORACLE01' inherits basenode {
license_key = 'd15ff577e5f27e071fe9b2d6809b9f2950fe87d1',
!!! Please get a new license key. You just shared your key with the
internet. !!!
}
d) here I have called module and passed the license_key for the node.
No. No, you haven't.
For one thing, the above is a syntax error. In a node block, there can
only be resource declarations such as
include newrelic
host { localhost: ... }
file { /etc/motd: ... }
etc.
I think what you are thinking of is a construct such as this:
node 'WA19487ORACLE01' inherits basenode {
class { newrelic::install:
license_key = ...;
}
}
e) I had restarted my puppetmaster(machine A) and puppet (machine B).
when I checked /varlog/messages/ of machine A and machine B, new reliec
agent is not getting deployed on machine B (clinet).
When developing puppet manifest, use these commands on your client node:
puppet agent --test --noop
If the output is satisfactory, follow that up with
puppet agent --test
to make puppet apply the necessary changes.
f) my client is not able to retervie the catalog from puppet master. it
throws following error when i run puppet agent --test on clinet I am
getting the result as
[root@WA19487ORACLE01 ~]# puppet agent --test
notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources
using 'eval_generate': hostname was not match with the server certificate
err: /File[/var/lib/puppet/lib]: Could not evaluate: hostname was not
match with the server certificate Could not retrieve file metadata for
puppet://WA19487PUPPET01/plugins: hostname was not match with the server
certificate
err: Could not retrieve catalog from remote server: hostname was not
match with the server certificate
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Time:
Last run: 1362381429
err: Could not send report: hostname was not match with the server
certificate
please post your suggestions to help me out.
What is in your /etc/puppet/puppet.conf on the client node?
What is
Re: [Puppet Users] Auto remove certificate from puppet master host
Hi, I disbelieve that there is such a facility yet. One probably needs to rig something that greps through the master log and invokes puppet ca accordingly (to get rid of stale certificates). HTH, Felix On 03/04/2013 11:04 AM, Roman Alekseev wrote: Hi, Does anybody know how to perform auto removing certificate of host which is unreachable some period? 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] load puppet report from file
Hi,
disclaimer: I know next to nothing about ruby, and have not dabbled in
many parts of the puppet code base. However :-)
Since you YAML::loaded the serialized object, in your report variable is
a perfectly fine instance of Puppet::Reports, for you to inspect and
deal with as you please.
What more would you like the puppet code to do with that?
Cheers,
Felix
On 03/05/2013 04:49 AM, cblum...@gmail.com wrote:
This is more of a ruby programming question I think but here goes.
I would like to load a report from a file for some processing that does
not happen on the puppet master:
#!/usr/bin/env ruby
require 'yaml'
require 'puppet'
report =
YAML::load(File.open('/var/lib/puppet/state/last_run_report.yaml', 'r'))
Puppet::Reports.register_report(:myreport) do
def process
if self.status == 'failed'
msg = failed puppet run for #{self.host} #{self.status}
else
msg = puppet run for #{self.host} #{self.status}
end
end
end
I am not sure that using the register report method is the proper way to
go as this is how you do custom reporting from the master. I have been
looking around in the puppet code for a way to get the report yaml into
the puppet reports class. What is the class and method that I cannot find?
Chris
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Auto remove certificate from puppet master host
Thanks, will try to find how to resolve this by myself. вторник, 5 марта 2013 г., 16:16:03 UTC+4 пользователь Felix.Frank написал: Hi, I disbelieve that there is such a facility yet. One probably needs to rig something that greps through the master log and invokes puppet ca accordingly (to get rid of stale certificates). HTH, Felix On 03/04/2013 11:04 AM, Roman Alekseev wrote: Hi, Does anybody know how to perform auto removing certificate of host which is unreachable some period? 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: PuppetDB queue problem
What are the I/O stats? Can I just peak at them?
Mike { Thanks = always }
On Mar 5, 2013, at 3:00 AM, ak0ska akos.he...@gmail.com wrote:
Hey Mike,
Thanks for the suggestions, but we already checked the IO rates, and they
seemed fine. And yes, PuppetDB and Postgres are on the same machine for now,
but we plan to change that sometime in the future.
Cheers,
ak0ska
On Tuesday, March 5, 2013 12:51:16 AM UTC+1, Mike wrote:
Is puppetdb and postgres on the same server?
How many node does your environment have?
I had a similar issue and it was linked to I/O. Can you look at that?
Mike { Thanks = always }
On Mar 4, 2013, at 4:55 PM, Ken Barber k...@puppetlabs.com wrote:
Any progress today?
On Fri, Mar 1, 2013 at 9:00 AM, ak0ska akos@gmail.com wrote:
Yes, maybe not. The next step will be to recreate it from scratch.
On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote:
Well, I don't think a vacuum will help you - I imagine something is
wrong with the schema right now or some data migration failed during
upgrade. Esp. if you had migration issues from your custom PuppetDB.
Of course I can't prove this with so little knowledge - but it
certainly does raise a red flag.
The only other option is to compare the schemas with a known good one,
and compare the database data to try and find the fault. This however
is prone to error and might be time-consuming. Recreating the database
sounds like a far more reliable option with a lot more guarantees
around it.
ken.
--
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...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
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...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Windows Firewall Question
Hi Adam,
I would be interested in seeing an example of a firewall config managed by
the registry module. Is that possible?
Thanks,
David.
On Friday, February 15, 2013 5:13:04 AM UTC, ad wrote:
Hey Jim,
As someone who generally hates using execs unless I absolutely have to, I
would recommend using the Puppet Labs registry module. I can dig out some
examples tomorrow if you like.
Adam
On Thursday, February 14, 2013 9:29:52 AM UTC-6, jim wrote:
Hello all,
I'm currently running 2.7.19 (Puppet Enterprise 2.7.0)
I want to use puppet to add / amend or delete windows firewall rules, is
there a tidy way of doing this
exec { Check_MK_Firewall_Rule_create:
command = 'C:\Windows\System32\netsh.exe advfirewall firewall add rule
name=Check_MK dir=in action=allow protocol=TCP localport=6556',
unless = 'C:\Windows\System32\netsh.exe advfirewall firewall show rule
name=Check_MK',
}
## If I remove the unless statement, it will keep add the same rule over
and over again, which will make the firewall rule list un-manageable
exec { Check_MK_Firewall_Rule_enable:
command = 'C:\Windows\System32\netsh.exe advfirewall firewall set rule
name=Check_MK new enable=Yes',
}
## When I do a puppet run it keeps running this, is there a way to only
run if disabled ???
Hope this make sense
regards
James
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Package and unless
Hello guys, Thanks for the tips you all sent me! I'll write my own facter, sound the better way to solve this. About duplicating work, I agree with you. The big problem is: The company was compiled in all machines the nrpe and nagios-plugins to /opt, and now I'm suffering to try to control this. New machines will be raised with rpm/deb packages that I made, but I can't break the production environment :) On Monday, March 4, 2013 11:41:24 AM UTC-3, jcbollinger wrote: Also, you should consider whether you are making unnecessary work for yourself. It may be that you are duplicating work that your package management system would be happy to do for you. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet autoami problem
Hi, Im using Puppet v3.0.2. Im trying to test puppet autoami module, but after installing it using #*puppet module install ccaum-autoami* and doing *puppet help* im getting the following: Error: Could not autoload puppet/face/node/cloudscale: no such file to load -- puppet/cloudscale Error: Could not autoload puppet/face/node_aws/cloudscale: no such file to load -- puppet/cloudscale ! node! Subcommand unavailable due to error. Check error logs. ! node_aws! Subcommand unavailable due to error. Check error logs. When uninstalling the module everything get back to normal: # puppet help node View and manage node definitions. node_aws View and manage Amazon AWS EC2 nodes. [root@puppetmaster modules]# puppet help node_aws USAGE: puppet node_aws action This subcommand provides a command line interface to work with Amazon EC2 machine instances. The goal of these actions is to easily create new machines, install Puppet onto them, and tear them down when they're no longer required. OPTIONS: --render-as FORMAT - The rendering format to use. --verbose - Whether to log verbosely. --debug- Whether to log debug information. ACTIONS: bootstrapCreate and initialize an EC2 instance using Puppet. create Create a new EC2 machine instance. fingerprint Make a best effort to securely obtain the SSH host key fingerprint. list List AWS EC2 machine instances. list_keynamesList available AWS EC2 key names. terminateTerminate an EC2 machine instance. See 'puppet man node_aws' or 'man puppet-node_aws' for full help. Has anybody any idea how to fix this? Regards -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Weird Scope Fun
[Puppet v3.1.0 both on the master and client (debian squeeze)]
So, I'm porting a pretty monolithic module over from our 2.6.x puppet
environment to a new puppet 3.1.0 environment and ran into some
notifications in syslog from the puppetmaster.
I have a module/class that instantiates numerous parameterized subclasses.
class my_class {
class {my_class::some_implementation::parameterized_subclass:
somevariable = true,
}
...
}
and...
class my_class::some_implementation::parameterized_subclass ($somevariable
= false) {
#do stuff
}
So, all works fine, but I get scope qualified variable notifications on
the puppetmaster. If I change my_class::parameterized_subclass to the
following, it goes away.
class my_class::some_implementation::parameterized_subclass
($my_class::parameterized_subclass::some_implementation::parameterized_subclass::somevariable
= false) { }
That seems a bit bizarre to me (and annoying). Is there a scope behavior
I'm missing that would prevent this type of class layout? Any ideas?
Think of a layout like:
base::security::ossec
base::monitoring::rsyslog
base::monitoring::munin
etc...
Regards,
-Matt
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Discover SO of my nodes
Hello all! Using puppet 2.7.9 and Dashboard, I can see the hostname of my nodes. With some selects against MySQL, I can also discover their IP address. But that is any way to discover more details, like, with OS is running on that node? Thanks a lot!! Tiago C. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet autoami problem
On Mar 5, 2013, at 3:43 AM, emzvarg...@gmail.com wrote: Hi, Im using Puppet v3.0.2. Im trying to test puppet autoami module, but after installing it using #puppet module install ccaum-autoami and doing puppet help im getting the following: Error: Could not autoload puppet/face/node/cloudscale: no such file to load -- puppet/cloudscale Error: Could not autoload puppet/face/node_aws/cloudscale: no such file to load -- puppet/cloudscale ! node! Subcommand unavailable due to error. Check error logs. ! node_aws! Subcommand unavailable due to error. Check error logs. When uninstalling the module everything get back to normal: # puppet help node View and manage node definitions. node_aws View and manage Amazon AWS EC2 nodes. [root@puppetmaster modules]# puppet help node_aws USAGE: puppet node_aws action This subcommand provides a command line interface to work with Amazon EC2 machine instances. The goal of these actions is to easily create new machines, install Puppet onto them, and tear them down when they're no longer required. OPTIONS: --render-as FORMAT - The rendering format to use. --verbose - Whether to log verbosely. --debug- Whether to log debug information. ACTIONS: bootstrapCreate and initialize an EC2 instance using Puppet. create Create a new EC2 machine instance. fingerprint Make a best effort to securely obtain the SSH host key fingerprint. list List AWS EC2 machine instances. list_keynamesList available AWS EC2 key names. terminateTerminate an EC2 machine instance. See 'puppet man node_aws' or 'man puppet-node_aws' for full help. Has anybody any idea how to fix this? Regards -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. This should be fixed in puppet 3.1, see issue #7316. Josh -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Using Puppet with Windows MSIs
Hi Nathan, On Mar 4, 2013, at 8:57 AM, Nathan Shirlberg nathan...@gmail.com wrote: I want to use Puppet to manage deployment of internal .Net software. The CI build can generate a versioned MSI file and push that out to Puppet. I am creating an MSI with the same name, but different versions for each release. Puppet detects the missing Package and properly installs the new Package from MSI. However, Puppet does not detect that a new MSI needs to replace the already installed package. My problem seems to be the same as this closed issue. I am running 3.1.0. My plan for deployment has been to have each CI build create the appropriately versioned MSI files and deploy them to Puppet as desired. Then, let Puppet compare the MSI versions to the versions already installed and install the new MSI if necessary. Do I have a simple bug in my implementation or do I have a bad strategy. I am considering the following: 1) Modify puppet windows package source to compare versions installed to the version of the MSI. 2) Abort the MSI strategy and have each build generate a manifest that uses the windows resources directly to complete the install (file, service, scheduled task, IIS, etc). I think I will need to create an Assembly resource that can install dlls to the GAC. 3) Put the version number as part of the package name. Thus forcing Puppet to manage each version as a separate package. I'd rather not do this because it will mean generating quite a bit of manifest code as part of the build to ensure that previous versions are uninstalled and adding the new version to the manifest. Thanks, Nathan -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. You can specify the MSI PackageCode as the name of the package resource to ensure that particular version is installed. If you don't know what the PackageCode is (since it's supposed to be unique for each MSI build), you can use read it from the MSI in ruby. Search this list for more information. Josh -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] PuppetDB: Upgraded to 1.1.1, Dashboard empty
I'm running PuppetDB installed from yum on CentOS 6, with a Postgres backend. After upgrading from 1.0.5 to 1.1.1, my dashboard (http://puppetdb/dashboard/index.html) is full of question marks with empty graphs, and the top right displays PuppetDB (unknown version). Other than that the upgrade was fine, and I didn't see any other errors in nodes applying their catalogs, so I didn't pay it much attention. It's bugging me, though, as it'd be nice to see some stats and at least know everything's healthy. Any insights? On a related note, I'd like to run Nagios checks against PuppetDB, but what should I be checking? Is there a Puppet Face for querying PuppetDB's status? -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Long puppet catalog run times on certain nodes after using pson is called
I am not seeing any queueing, but perhaps I am not looking in the right place. At most I am seeing 1 pending task, but typically all systems go is the only thing the registers in Dashboard. Also in dashboard I occasionally see this - /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/validations.rb:1101:in `save_without_dirty!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in `save_without_transactions!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in `transaction' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in `rollback_active_record_state!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/app/models/report.rb:117:in `create_from_yaml' /usr/share/puppet-dashboard/app/models/report.rb:90:in `create_from_yaml_file' But I haven't mentioned it because I assumed it was unrelated and another thing I needed to look at it later (still might be). Should I be looking in other places on the master to show long queues? I'll Wireshark next on the clients and see if I that adds anything. Thanks, Rob On Tuesday, February 26, 2013 11:32:33 AM UTC-7, r.yeo wrote: Running the agent in debug mode on a some clients and I am seeing long run times such as this, but only after the using pson lines : Tue Feb 26 10:57:38 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 10:58:53 2013: Info: /Stage[main]/Vpn::Config/File[/opt/cisco/vpn/.anyconnect_global]: Evaluated in 75.03 seconds Tue Feb 26 10:58:53 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 11:00:08 2013: Info: /Stage[main]/Amadeuspro/File[/etc/puppet/tmp/com.HairerSoft.AmadeusPro.plist]: Evaluated in 74.78 seconds Tue Feb 26 11:00:08 2013: Info: /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Starting to evaluate the resource Tue Feb 26 11:00:08 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 11:01:23 2013: Info: /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Evaluated in 75.00 seconds Tue Feb 26 11:01:23 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 11:02:38 2013: Info: /Stage[main]/Puppet::Snow/File[/etc/hooks/ cleanpup.pl]: Evaluated in 75.01 seconds This catalog took 921.02 to complete : Tue Feb 26 11:02:38 2013: Notice: Finished catalog run in 916.78 seconds Tue Feb 26 11:02:38 2013: Changes: Tue Feb 26 11:02:38 2013: Events: Tue Feb 26 11:02:38 2013: Resources: Tue Feb 26 11:02:38 2013: Total: 55 Tue Feb 26 11:02:38 2013: Skipped: 6 Tue Feb 26 11:02:38 2013: Time: Tue Feb 26 11:02:38 2013:Filebucket: 0.00 Tue Feb 26 11:02:38 2013: Package: 0.00 Tue Feb 26 11:02:38 2013:Ssh authorized key: 0.00 Tue Feb 26 11:02:38 2013: User: 0.06 Tue Feb 26 11:02:38 2013: Group: 0.11 Tue Feb 26 11:02:38 2013: Exec: 0.59 Tue Feb 26 11:02:38 2013:Config retrieval: 13.28 Tue Feb 26 11:02:38 2013: Last run: 1361901758 Tue Feb 26 11:02:38 2013: File: 906.98 Tue Feb 26 11:02:38 2013: Total: 921.02 Tue Feb 26 11:02:38 2013: Version: Tue Feb 26 11:02:38 2013:Config: 1361893868 Tue Feb 26 11:02:38 2013:Puppet: 3.1.0 Also, this isn't global as I have nodes getting identical complete configs in 7 seconds and run times are just fine after the using pson lines. Example of a fast node : Tue Feb 26 11:22:57 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 11:22:58 2013: Info: /Stage[main]/Amadeuspro/File[/etc/puppet/tmp/com.HairerSoft.AmadeusPro.plist]: Evaluated in 0.15 seconds Tue Feb 26 11:22:58 2013: Info: /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Starting to evaluate the resource Tue Feb 26 11:22:58 2013: Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Tue Feb 26 11:22:58 2013: Info: /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Evaluated in 0.07 seconds Puppet master and clients are 3.1 with Dashboard 1.2.22 and also using PuppetDB. Any thoughts why I'd have trouble and long run times on select nodes when pson is called? Thanks! -- You received this message because you are
Re: [Puppet Users] Pattern for managing software versions?
If you want to be able to install multiple versions of some piece of software, then you should obtain or create packages that allow it. For example, RedHat-family JDK packages (java-version-openjdk) support this, whereas Oracle's JDK packages for RedHat family systems do not. Agreed, had to repackage the oracle JDK's to play nice:) Configuration files are a separate question, but I don't see why your scenario would constitute a special case for them. Do you imagine a specific problem in that area? Not really a specific problem because obviously people are successfully using this pattern. I'm really trying to explore the difference between the different patterns and understand why you would chose one over the other. The current pattern that is working successfully for me is the role/profile pattern. Here I use a profile to associate a specific jdk version with the appserver version. It gives me one place to update the version of the jdk for all deployments of the app server. The problem that I can imagine (or rather what I don't fully understand yet) is how to manage the jdk version in hiera when the jdk version is dependent on the version of the app server and not facts on the node. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Long puppet catalog run times on certain nodes after using pson is called
On 03/05/2013 05:34 PM, r.yeo wrote: Should I be looking in other places on the master to show long queues? Do the most simple thing: Raise the Passenger workers to 30 and see what happens :-) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] PuppetDB: Upgraded to 1.1.1, Dashboard empty
It sounds like the dashboard Javascript can't access the HTTP end-points which is strange. The way it works is that it hits a series of REST end-points on the web server. As the dashboard is updated using background Javascript, it can still keep trying to access backend data even though the web server is down or not accessible. Are you sure the web-server is still listening publicly on port 8080 still? What does your jetty.ini look like? What do you see in your puppetdb.log when you try to hit the dashboard? In your browser if you enable the javascript console - do you get any errors that might be helpful? ken. On Tue, Mar 5, 2013 at 8:31 AM, Stephen Price ste...@gmail.com wrote: I'm running PuppetDB installed from yum on CentOS 6, with a Postgres backend. After upgrading from 1.0.5 to 1.1.1, my dashboard (http://puppetdb/dashboard/index.html) is full of question marks with empty graphs, and the top right displays PuppetDB (unknown version). Other than that the upgrade was fine, and I didn't see any other errors in nodes applying their catalogs, so I didn't pay it much attention. It's bugging me, though, as it'd be nice to see some stats and at least know everything's healthy. Any insights? On a related note, I'd like to run Nagios checks against PuppetDB, but what should I be checking? Is there a Puppet Face for querying PuppetDB's status? -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Long puppet catalog run times on certain nodes after using pson is called
On 5 March 2013 17:34, r.yeo rob.q...@gmail.com wrote: I am not seeing any queueing, but perhaps I am not looking in the right place. At most I am seeing 1 pending task, but typically all systems go is the only thing the registers in Dashboard. Also in dashboard I occasionally see this - /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/validations.rb:1101:in `save_without_dirty!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in `save_without_transactions!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in `transaction' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in `rollback_active_record_state!' /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /usr/share/puppet-dashboard/app/models/report.rb:117:in `create_from_yaml' /usr/share/puppet-dashboard/app/models/report.rb:90:in `create_from_yaml_file' But I haven't mentioned it because I assumed it was unrelated and another thing I needed to look at it later (still might be). Should I be looking in other places on the master to show long queues? You should probably check using the command passenger-status instead of looking at the pending tasks in dashboard, that will show very different things. Pending tasks in dashboard is not really relevant for this. -- Erik Dalén -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] PuppetDB: Upgraded to 1.1.1, Dashboard empty
Sorry, I should have done some more digging. I'm using nginx as the front end, and I had specific location rules to forbid invalid requests. I allowed GET on this location: location ~ ^/(facts|resources|dashboard|nodes|status|metrics|version) I should have read the 1.1 release notes more closely. It's now: location ~ ^/(v2\/)?(facts|resources|dashboard|nodes|status|metrics|version|experimental) Not sure if it's necessary to have the (v2/) optional, but I'd rather keep it backwards-compatible for now. As soon as I made that change, the dashboard started working just fine. Thanks for the tips! On Tuesday, March 5, 2013 10:44:48 AM UTC-8, Ken Barber wrote: It sounds like the dashboard Javascript can't access the HTTP end-points which is strange. The way it works is that it hits a series of REST end-points on the web server. As the dashboard is updated using background Javascript, it can still keep trying to access backend data even though the web server is down or not accessible. Are you sure the web-server is still listening publicly on port 8080 still? What does your jetty.ini look like? What do you see in your puppetdb.log when you try to hit the dashboard? In your browser if you enable the javascript console - do you get any errors that might be helpful? ken. On Tue, Mar 5, 2013 at 8:31 AM, Stephen Price ste...@gmail.comjavascript: wrote: I'm running PuppetDB installed from yum on CentOS 6, with a Postgres backend. After upgrading from 1.0.5 to 1.1.1, my dashboard (http://puppetdb/dashboard/index.html) is full of question marks with empty graphs, and the top right displays PuppetDB (unknown version). Other than that the upgrade was fine, and I didn't see any other errors in nodes applying their catalogs, so I didn't pay it much attention. It's bugging me, though, as it'd be nice to see some stats and at least know everything's healthy. Any insights? On a related note, I'd like to run Nagios checks against PuppetDB, but what should I be checking? Is there a Puppet Face for querying PuppetDB's status? -- 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...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/puppet-users?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] use of parameterized classes
Hi,
I have been following this new type of style, using parameterized classes but I
have a question.
Say I have the following:
class java-app-profile {
class {'java-app':
app-name = my_first_app1,
app-dir = '/opt/company/my_first_app1',
}
class {'java-app':
app-name = my_first_app2,
app-dir = '/opt/company/my_first_app1',
}
class {'java-app':
app-name = my_first_app3,
app-dir = '/opt/company/my_first_app1',
}
}
Can I declare multiple parameterized classes of the same type within a single
class?
Reference: http://docs.puppetlabs.com/guides/parameterized_classes.html
Thanks,
Corey Osman
co...@logicminds.biz
Green IT and Data Center Automation Specialist
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet to copy file instead of symlink
On Tue, 2013-03-05 at 03:53 -0800, david.har...@struq.com wrote: hi, I want to have puppet copy a file, but I can only reference the file within the puppet configuration from the symlink. Have tried file = true and other options but puppet only copies the symlink. Is this possible? many thanks, David. When you read the fine documentation located at: http://docs.puppetlabs.com/references/latest/type.html#file You will note that there is a links parameter on the file resource that can be used to set the behaviour with regards to symlinks. -- Calvin Walton calvin.wal...@kepstin.ca -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet 3.1 slow to compile in Windows (standalone mode)
I too and learning puppet for the first time. I attempted my first
manifest run launch puppet from command line but it cannot find my file.
puppet apply C:\test.pp
I get Error: Could not run: Could not find file C:\test.pp
How did you run your script. I'm interested in anything this group might
have to offer and hopefully soon I can contribute.
On Tuesday, February 12, 2013 3:05:42 AM UTC-5, Styme wrote:
I'm trying to learn Puppet (v.3.1) and I've noticed that in Windows it
takes Puppet quite a bit of time to process a manifest compared to the
experience I had with the Learning VM.
I mean a simple manifest like this:
file {
'C:\testfile.txt':
ensure = 'present',
content = 'This is a text file',
}
will take Puppet roughly 30 seconds from start to finish to process in
Windows. It says it completed the catalog run in less than a second, so I'm
assuming it's the compilation that is slow. While on the Learning VM, it
takes a mere few seconds from start to finish. Is this just a Windows
thing? Or are there extra configuration/setup I must do in Windows (I'm
interested in standalone mode)?
I appreciate the help/advice.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: use of parameterized classes
On Tuesday, March 5, 2013 1:07:37 PM UTC-6, Corey Osman wrote:
Hi,
I have been following this new type of style, using parameterized classes
but I have a question.
Say I have the following:
class java-app-profile { class {'java-app': app-name = my_first_app1,
app-dir = '/opt/company/my_first_app1', }
class {'java-app':
app-name = my_first_app2, app-dir = '/opt/company/my_first_app1',
}
class {'java-app':
app-name = my_first_app3, app-dir = '/opt/company/my_first_app1',
}
}
Can I declare multiple parameterized classes of the same type within a
single class?
No, classes are singletons, they can only be declared once.
In this situation, you should be using a defined type
- http://docs.puppetlabs.com/puppet/3/reference/lang_defined_types.html
They look like paramaterized classes, but are more like the built in types
(user, file, package etc)
Reference: http://docs.puppetlabs.com/guides/parameterized_classes.html
Thanks,
Corey Osman
co...@logicminds.biz javascript:
Green IT and Data Center Automation Specialist
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Boolean in hiera... problems again
Hi...
I've been trying to set up boolean values in Hiera, but with no luck.
For example, I'm using puppetlabs-haproxy module, and this is a code
snippet:
class haproxy (
$manage_service = true,
...
) inherits haproxy::params {
...
if $manage_service {
}
}
Now, this is how I set up values in hiera:
haproxy::manage_service: false
But, it seems that $manage_service is always true... I tried by single
quoting 'false', capital letter False, but nothing helps...
Only thing so far I've found out is to change the manifest code to look
like this:
if $manage_service == 'true' {
}
Any ideas?
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: PuppetDB queue problem
Vacuum full was running for the whole weekend, so we didn't yet have time to
rebuild indexes, because that would require more downtime, and we're not
sure how long it would take. The size of the database didn't drop that much,
it's now ~370Gb.
Wow. Thats still way too large for the amount of nodes. I imagine
re-indexing might help, we can check first. Can you display how big
each of your relations are? A query like this might help:
SELECT nspname || '.' || relname AS relation,
pg_size_pretty(pg_relation_size(C.oid)) AS size
FROM pg_class C
LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)
WHERE nspname NOT IN ('pg_catalog', 'information_schema')
ORDER BY pg_relation_size(C.oid) DESC
LIMIT 20;
Also - what are the row counts for each of your tables btw?
If you run this for each table it will get you a row count:
select count(*) from table_name;
I'd be curious to see if any of these are higher than what they should
be based on your node count, maybe some of the space is just large
tables perhaps?
We already see some improvements. The queue doesn't get insanely large, in
fact the highest peak we saw since Monday morning was about 20, but mostly
it's between 0 and 3. That's good. :) One strange benefit is that we now see
Resources and Resource duplication values on the Dashboard, those were
previously just question marks, as you can see on my previous screenshots.
Perhaps the queries were just timing out on the dashboard?
However, we still get the constraint violations, steadily 2 violations per
hour. They appear as Retried commands on the dashboard. But if the queue
reaches the size 0, then does this mean these commands get written to the
database eventually? The violations seem to happen shortly after puppetdb
starts garbage collection.
You can see it here: http://pastebin.com/B6VR67LW
This should be evident in your puppetdb.log if you trace the uuid of a
command. If commands 'fail' completely, they end up in the DQL located
here:
/var/lib/puppetdb/mq/discarded/
ken.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Mcollective/Puppet Connector
When attempting to execute the mcollective puppet plugin: # mco puppet runonce -v aixl : execution expired aixj : execution expired I get an error, 'execution expired' on some hosts. However, these hosts respond via mco ping and, I have verified the date/time on the servers. The puppet agent is also working fine with the puppetmaster. Can anyone shed any light on this? Thanks! Bee -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
- Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:26:06 PM Subject: [Puppet Users] Mcollective/Puppet Connector When attempting to execute the mcollective puppet plugin: # mco puppet runonce -v aixl : execution expired aixj : execution expired for whatever reason it took more than 5 seconds to just get puppet started - it daemonizes and dissociates from mcollectived on run so this really should not take 5 seconds unless your machines are very very slow etc? did you change any of the mco puppet agent configuration? -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
Ahh... We do not run the puppet agents as daemons, we just call the agent manually when needed. Is there a way I can increase this timeout? Thanks! On Tue, Mar 5, 2013 at 4:28 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:26:06 PM Subject: [Puppet Users] Mcollective/Puppet Connector When attempting to execute the mcollective puppet plugin: # mco puppet runonce -v aixl : execution expired aixj : execution expired for whatever reason it took more than 5 seconds to just get puppet started - it daemonizes and dissociates from mcollectived on run so this really should not take 5 seconds unless your machines are very very slow etc? did you change any of the mco puppet agent configuration? -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
- Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:31:10 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ahh... We do not run the puppet agents as daemons, we just call the agent manually when needed. that's what the mco agent does too - so back to the questions, are your machines particularly slow/busy? did you change the config in server.cfg or /etc/mcollective/plugin.d/puppet.cfg? Is there a way I can increase this timeout? you'd need to adjust the DDL files everywhere, best to find out what the cause is -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
Ok, thanks. I did not change anything in the config files other than to add the required settings for the connector in server.cfg #Puppet Plugin plugin.puppet.command = /opt/puppet/bin/puppet agent --test plugin.puppet.splay = false plugin.puppet.daemonize = true plugin.puppet.splaylimit = 30 plugin.puppet.config = /etc/puppet/puppet.conf connector = stomp plugin.stomp.host = puppet05 plugin.stomp.port = 61613 plugin.stomp.user = mcollective plugin.stomp.password = secret I do not even have this file :/etc/mcollective/plugin.d/puppet.cfg I do not think my servers are particularly slow, but then again, I have other servers that are answering just fine... Thanks SO MUCH! On Tue, Mar 5, 2013 at 4:35 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:31:10 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ahh... We do not run the puppet agents as daemons, we just call the agent manually when needed. that's what the mco agent does too - so back to the questions, are your machines particularly slow/busy? did you change the config in server.cfg or /etc/mcollective/plugin.d/puppet.cfg? Is there a way I can increase this timeout? you'd need to adjust the DDL files everywhere, best to find out what the cause is -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
Am I looking at the wrong Configuration Guide? http://docs.puppetlabs.com/mcollective/reference/basic/configuration.html I do not see anything about the puppet.cfg file. Also, my puppetmaster and my ActiveMQ are on seperate boxes... On Tue, Mar 5, 2013 at 4:35 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:31:10 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ahh... We do not run the puppet agents as daemons, we just call the agent manually when needed. that's what the mco agent does too - so back to the questions, are your machines particularly slow/busy? did you change the config in server.cfg or /etc/mcollective/plugin.d/puppet.cfg? Is there a way I can increase this timeout? you'd need to adjust the DDL files everywhere, best to find out what the cause is -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
- Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:40:58 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks. I did not change anything in the config files other than to add the required settings for the connector in server.cfg #Puppet Plugin plugin.puppet.command = /opt/puppet/bin/puppet agent --test plugin.puppet.splay = false plugin.puppet.daemonize = true plugin.puppet.splaylimit = 30 plugin.puppet.config = /etc/puppet/puppet.conf these are not required parameters for the connector :) You're specifically changing the way puppet is being run to use --test thus causing it to not daemonize and dissociate from the running mcollectived. Take away your plugin.puppet.command setting -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
Ok, thanks! I also found this... #plugin.puppet.timeout = 20 Will this increase the period of time it waits for execution against the puppetmaster? On Tue, Mar 5, 2013 at 4:51 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:40:58 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks. I did not change anything in the config files other than to add the required settings for the connector in server.cfg #Puppet Plugin plugin.puppet.command = /opt/puppet/bin/puppet agent --test plugin.puppet.splay = false plugin.puppet.daemonize = true plugin.puppet.splaylimit = 30 plugin.puppet.config = /etc/puppet/puppet.conf these are not required parameters for the connector :) You're specifically changing the way puppet is being run to use --test thus causing it to not daemonize and dissociate from the running mcollectived. Take away your plugin.puppet.command setting -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
- Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 10:02:37 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks! I also found this... #plugin.puppet.timeout = 20 Will this increase the period of time it waits for execution against the puppetmaster? no, you have to not set it to use --test, for any reasons, just dont do it. On Tue, Mar 5, 2013 at 4:51 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:40:58 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks. I did not change anything in the config files other than to add the required settings for the connector in server.cfg #Puppet Plugin plugin.puppet.command = /opt/puppet/bin/puppet agent --test plugin.puppet.splay = false plugin.puppet.daemonize = true plugin.puppet.splaylimit = 30 plugin.puppet.config = /etc/puppet/puppet.conf these are not required parameters for the connector :) You're specifically changing the way puppet is being run to use --test thus causing it to not daemonize and dissociate from the running mcollectived. Take away your plugin.puppet.command setting -- 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?hl=en. 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Mcollective/Puppet Connector
Ok, Thanks!!! :) On Tue, Mar 5, 2013 at 5:05 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 10:02:37 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks! I also found this... #plugin.puppet.timeout = 20 Will this increase the period of time it waits for execution against the puppetmaster? no, you have to not set it to use --test, for any reasons, just dont do it. On Tue, Mar 5, 2013 at 4:51 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Worker Bee beeworke...@gmail.com To: puppet-users@googlegroups.com Sent: Tuesday, March 5, 2013 9:40:58 PM Subject: Re: [Puppet Users] Mcollective/Puppet Connector Ok, thanks. I did not change anything in the config files other than to add the required settings for the connector in server.cfg #Puppet Plugin plugin.puppet.command = /opt/puppet/bin/puppet agent --test plugin.puppet.splay = false plugin.puppet.daemonize = true plugin.puppet.splaylimit = 30 plugin.puppet.config = /etc/puppet/puppet.conf these are not required parameters for the connector :) You're specifically changing the way puppet is being run to use --test thus causing it to not daemonize and dissociate from the running mcollectived. Take away your plugin.puppet.command setting -- 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?hl=en. 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?hl=en. 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Boolean in hiera... problems again
Getting booleans from hiera to puppet is not currently not functioning like
you would expect.
There is a bug reported for it and they are working on it but it's still in
progress last I looked.
On 6 March 2013 06:08, Jakov Sosic jso...@srce.hr wrote:
Hi...
I've been trying to set up boolean values in Hiera, but with no luck.
For example, I'm using puppetlabs-haproxy module, and this is a code
snippet:
class haproxy (
$manage_service = true,
...
) inherits haproxy::params {
...
if $manage_service {
}
}
Now, this is how I set up values in hiera:
haproxy::manage_service: false
But, it seems that $manage_service is always true... I tried by single
quoting 'false', capital letter False, but nothing helps...
Only thing so far I've found out is to change the manifest code to look
like this:
if $manage_service == 'true' {
}
Any ideas?
--
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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] multi-line content= construct for puppet resource file command
Hello all,
How does one enter multi-line content using 'puppet resource file ...'
at the command line?
For example, I am trying to create a file called /tmp/hw.txt with two
lines of content:
$ cat /tmp/hw.txt
hello
world
This does not work:
$ puppet resource file hello_world \
path=/tmp/hw.txt \
ensure=file \
content=hello\nworld\n
This does, but use puppet apply :
cat eof | puppet apply
file { hello_world:
path = /tmp/hw.txt,
ensure = file,
content = hello\nworld\n,
}
eof
Does anyone have any pointers on how to construct the content= line so
that I can get two lines of text?
Regards,
- Robert
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
