[Puppet Users] Re: puppet client 0.22.1-1 unable to communicate with master on 3.0.2-1
Million thanks, Nick .. That is enough pointers for me to consider .. Will come back with some feedback on what has worked (if any). rgds. On Saturday, 2 February 2013 01:51:03 UTC, Nick Fagerlund wrote: You're in a gnarly situation. DistroWatch is telling me that you're probably running Ruby 1.8.4, which, damn. I think your best bet is: * Find or build a newer Ruby, preferably 1.8.7. * Either install Puppet from source ( http://docs.puppetlabs.com/guides/from_source.html) or force apt to install a Puppet package meant for a newer distro. I... THINK the packages from the Puppet Labs repo ought to limp along just fine if the Ruby is new enough, but I've never heard of it being tried with Dapper. Good luck with that. On Friday, February 1, 2013 10:18:49 AM UTC-8, Chux wrote: Hi, I have a client that I cannot upgrade from ubuntu 6.06 (due to application dependency issues) ... I have been able to get puppet/facter installed on it, but it seems unable to make certificate requests .. #/usr/sbin/puppetd -d -t -v err: No certificate; running with reduced functionality. info: Creating a new certificate request for cofkedit.bodleian.ox.ac.uk info: Requesting certificate warning: peer certificate won't be verified in this SSL session err: Could not call puppetca.getcert: #RuntimeError: HTTP-Error: 400 Bad Request err: Could not request certificate: Certificate retrieval failed: HTTP-Error: 400 Bad Request == I have seem a few admonitions against using clients that are old, but I have no choice in this one if I hope to deploy puppet on it .. or are there work arounds I can attempt ? -- 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: Another function does not return a value problem
Yes, that was the reason perhaps. Thanks. On Sunday, February 3, 2013 10:32:32 PM UTC+2, R.I. Pienaar wrote: - Original Message - From: Andriy Yurchuk ayur...@gmail.com javascript: To: puppet...@googlegroups.com javascript: Sent: Sunday, February 3, 2013 9:28:58 PM Subject: [Puppet Users] Re: Another function does not return a value problem For some unknown reason it works after enabling PuppetDB. I guess you restarted the master while doing this? you have to restart it each time you change a function -- 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 client 0.22.1-1 unable to communicate with master on 3.0.2-1
Nick, This is not looking promising .. dapper is on ruby 1.8.4, and the nearest ubuntu version that could get me up to ruby 1.8.5 is feisty .. So, I modified apt preferences, to try and pull in the right versions of ruby from feisty (had to do the same for puppet and facter) .. However, the major show-stopper in this direction is glibc ... I need glibc = 2.5, but the highest possible for dapper (without risking bricking the system) is glibc 2.3.6 ... So, I am afraid this is a no go .. Thanks for the insight you have provided. best regards .. On Saturday, 2 February 2013 01:51:03 UTC, Nick Fagerlund wrote: You're in a gnarly situation. DistroWatch is telling me that you're probably running Ruby 1.8.4, which, damn. I think your best bet is: * Find or build a newer Ruby, preferably 1.8.7. * Either install Puppet from source ( http://docs.puppetlabs.com/guides/from_source.html) or force apt to install a Puppet package meant for a newer distro. I... THINK the packages from the Puppet Labs repo ought to limp along just fine if the Ruby is new enough, but I've never heard of it being tried with Dapper. Good luck with that. On Friday, February 1, 2013 10:18:49 AM UTC-8, Chux wrote: Hi, I have a client that I cannot upgrade from ubuntu 6.06 (due to application dependency issues) ... I have been able to get puppet/facter installed on it, but it seems unable to make certificate requests .. #/usr/sbin/puppetd -d -t -v err: No certificate; running with reduced functionality. info: Creating a new certificate request for cofkedit.bodleian.ox.ac.uk info: Requesting certificate warning: peer certificate won't be verified in this SSL session err: Could not call puppetca.getcert: #RuntimeError: HTTP-Error: 400 Bad Request err: Could not request certificate: Certificate retrieval failed: HTTP-Error: 400 Bad Request == I have seem a few admonitions against using clients that are old, but I have no choice in this one if I hope to deploy puppet on it .. or are there work arounds I can attempt ? -- 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 custom recursive directory synchronization
I'm trying to implement a custom recursive directory synchronization resource in Puppet. What I need to do is the following. I have a YAML file with the list of hostnames and the list of directories that should exist on each hostname inside, say, `/var/lib/my_app` directory (`deployment.yml`): host_1: - DIR_1 - DIR_5 host_5: - DIR_7 host_6: - DIR_2 - DIR_3 - DIR_9 On the master I have a directory that contains all of those `DIR_*` sub-directories. Each subdirectory contains some files. What I'm trying to achieve is to synchronize all the nodes according to the `deployment.yml`, so that `/var/lib/my_app` on `host_1` only contains `DIR_1` and `DIR_5`, but does not contain `DIR_7`, `DIR_2`, `DIR_3`, `DIR_9`, and so on. I tried to do this using the ignore variable for file type, but this does not remove the directories from the node if I remove them from deployment.yml. I tried to write a custom function to remove them afterwards, but it does not seem to work inside my manifest. I also wanted to implement a custom type, but it seems to be too complicated. I'd appreciate any help on this. -- 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 custom recursive directory synchronization
but this does not remove the directories from the node if I remove them from deployment.yml. maybe purge attribute can do this. On Monday, February 4, 2013 7:58:37 PM UTC+8, Andriy Yurchuk wrote: I'm trying to implement a custom recursive directory synchronization resource in Puppet. What I need to do is the following. I have a YAML file with the list of hostnames and the list of directories that should exist on each hostname inside, say, `/var/lib/my_app` directory (`deployment.yml`): host_1: - DIR_1 - DIR_5 host_5: - DIR_7 host_6: - DIR_2 - DIR_3 - DIR_9 On the master I have a directory that contains all of those `DIR_*` sub-directories. Each subdirectory contains some files. What I'm trying to achieve is to synchronize all the nodes according to the `deployment.yml`, so that `/var/lib/my_app` on `host_1` only contains `DIR_1` and `DIR_5`, but does not contain `DIR_7`, `DIR_2`, `DIR_3`, `DIR_9`, and so on. I tried to do this using the ignore variable for file type, but this does not remove the directories from the node if I remove them from deployment.yml. I tried to write a custom function to remove them afterwards, but it does not seem to work inside my manifest. I also wanted to implement a custom type, but it seems to be too complicated. I'd appreciate any help on this. -- 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] Integration testing infrastructure
Bryan Berry gave a talk at FOSDEM a couple of days ago about integration testing for infrastructure. He talked about a tool that's come out of the Chef community called Test Kitchen, and pointed out it should be possible to use it to test Puppet code too. I've put together a quick demo of doing that here: https://github.com/garethr/tk-demo-puppet Any feedback welcome. At the moment it's a proof of concept, but I'd like to see it exist for real - probably with Support for providing a Puppetfile. G -- Gareth Rushgrove @garethr devopsweekly.com morethanseven.net garethrushgrove.com -- 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] storeconfigs and exported resources?
Also your routes.yaml doesn't match the documentation I gave you either, nor should you be setting thin_storeconfigs any more as stated in another section. Yeah, but if I remove the section for catalog, I don't get replacing catalogs in puppetdb log... But since my initial problem was wrong section name in puppet.conf, maybe I can do without storing catalog cache in puppetdb? Because, things work as a charm now that [puppetmasterd] is renamed to [master] This should be the case, take a look here: https://gist.github.com/4706585 You can see without those lines in routes.yaml it still sends a replace catalog. You simply shouldn't need that part. If for some reason you do, then something isn't right, and we are probably better to drill into the 'why' now rather than later :-). Please, if you can take a second look, and try removing the lines to confirm that would be appreciated. I just simply cannot replicate your case. BTW documentation says that thin_storeconfigs must be set to false or removed, mine were set to false so that was OK I presume. Okay, fair enough. Thank you very very much... what a bad typo on my side :-/ No problemo :-). 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] Recent RoR Vulns and puppet 3x on RHEL 6?
Hello fellow Puppet users! I'm trying to perform due diligence to make sure that our Puppet installations aren't affected by all the RoR vulns in the news recently. (http://www.kalzumeus.com/2013/01/31/what-the-rails-security-issue-means-for-your-startup/) (http://www.informationweek.com/security/vulnerabilities/critical-ruby-on-rails-issue-threatens-2/240145891) I've been watching the PuppetLabs security (https://puppetlabs.com/security/) page, and the RedHat CVE DB (https://access.redhat.com/security/cve/) and haven't seen anything that appears to directly affect a typical Puppet3 installation on RHEL 6 running the latest RHEL6-supported Ruby (1.8.7.352-7). Is it safe to say that my platform is not affected? 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] creating file locations from hiera
On Friday, February 1, 2013 5:57:50 AM UTC-6, blalor wrote:
On Jan 25, 2013, at 9:25 AM, Peter De Cleyn pe...@decleyn.netjavascript:
wrote:
I ran again against a long standing bug / feature request but from a new
angle: creating directories with parents (
http://projects.puppetlabs.com/issues/86).
I was blown away when I saw that issue. It's been open for 7 years and
nobody can figure out how to create a directory tree? It's kinda
mind-boggling.
The issue is not about how to create a directory tree, of course. It's
about what resources Puppet is actually managing, and what their properties
are. If I write
file { '/path/to/myfile':
ensure = 'file',
content = '#not empty',
uid = 'someone',
gid = 'agroup',
mode = '0644',
create_parents = true
}
then what managed resource(s) does it actually declare? Certainly it
declares File['/path/to/myfile'], but does it also declare File['/path/to']
and File['/path']? If so, then what properties are declared for them?
What if they are also declared elsewhere? Is its meaning different when
the parent directory exists than when it doesn't?
I may not have said this in a while, and it bears repeating: Puppet is not
a script engine. Rather, it is a state management service, and as such it
is essential that the target state to which nodes are managed be clear, and
that it be consistent for consistent manifests, facts, and server-side
data. The point, then, is not that the above questions cannot be answered,
but rather that there isn't a *satisfactory* set of answers.
In any case, you can roll your own relatively easily to get something that
suits your particular desire-of-the-moment. For example, here's a reusable
definition that wraps an ordinary File resource with parent auto-creation:
define mymodule::file_with_parent (
$ensure = 'present',
$uid = undef,
$gid = undef,
$mode = undef,
$content = undef
# ...
) {
file { $name:
ensure = $ensure,
uid = $uid,
gid = $gid,
mode = $mode,
content = $content
# ...
}
$parent = regsubst($name, '/[^/]*/?$', '')
if ($parent != $name) and ($parent != '') {
exec { create parent directory $parent:
# mode? uid/gid? you decide...
command = /bin/mkdir -p $parent,
creates = $parent,
before = File[$name]
}
}
}
That will probably give you parent directories owned by root if the agent
has to create them, with permissions governed by whatever file mode
creation mask is in effect for the agent. Don't complain if you happen to
get root/root/0700 (because if you're doing it this way then you don't
care).
I wanted to create a module, where a path could be supplied with a class
parameter. The path would be used in a rsync configuration, so I would like
to be sure the path exists. As I want the module to be general and
completely separate code and data, I didn't want to configure a base path
in which all rsync modules would need to live. But there is AFAIK no mkdir
-p alternative in puppet, unless I'd go with an ugly exec.
Any ideas houw to realise this? I probably could define my path in hiera
as an hash and as such define all parent folders, but this is not that
elegant.
The real problem here is not with the absence of built-in parent directory
auto-creation in Puppet, it is with the module design. It should not be
the module's responsibility to create the entire parent directory tree, at
least not without more information than the path to the rsync target
directory. Configurability and proper scoping are essential aspects of
being general, as the OP desired his module to be. There are several
ways the problem could be approached that neither rely on Execs nor require
a module-wide base path, but they all require more data.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet custom recursive directory synchronization
To be able to do this with purge I need to pass the list of subdirectories I want to exist to source attribute, but I'm not sure I can do this On Monday, February 4, 2013 2:57:20 PM UTC+2, 刘长元 wrote: but this does not remove the directories from the node if I remove them from deployment.yml. maybe purge attribute can do this. On Monday, February 4, 2013 7:58:37 PM UTC+8, Andriy Yurchuk wrote: I'm trying to implement a custom recursive directory synchronization resource in Puppet. What I need to do is the following. I have a YAML file with the list of hostnames and the list of directories that should exist on each hostname inside, say, `/var/lib/my_app` directory (`deployment.yml`): host_1: - DIR_1 - DIR_5 host_5: - DIR_7 host_6: - DIR_2 - DIR_3 - DIR_9 On the master I have a directory that contains all of those `DIR_*` sub-directories. Each subdirectory contains some files. What I'm trying to achieve is to synchronize all the nodes according to the `deployment.yml`, so that `/var/lib/my_app` on `host_1` only contains `DIR_1` and `DIR_5`, but does not contain `DIR_7`, `DIR_2`, `DIR_3`, `DIR_9`, and so on. I tried to do this using the ignore variable for file type, but this does not remove the directories from the node if I remove them from deployment.yml. I tried to write a custom function to remove them afterwards, but it does not seem to work inside my manifest. I also wanted to implement a custom type, but it seems to be too complicated. I'd appreciate any help on this. -- 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: Possible to evaluate embedded variables?
On Saturday, February 2, 2013 12:55:56 PM UTC-6, Schofield wrote:
Given a variable that holds a class name is it possible to resolve the
value of a variable within that class?
Yes, via an inline_template, but it's a bad idea.
For example
class classes::myclass{
$install_dir = '/xyz'
}
class example($class_name='classes::myclass'){
file {/mylink :
ensure = link,
target = ${${class_name}::install_dir},
}
}
Right now it appears that the parser doesn't recognize the inner variable.
Currently running puppet v3.0.1.
I would like the target of the link to resolve to /xyz. Is this
possible?
Just to show that it can be done, you should be able to use
target = inline_template(%=
scope.lookupvar('${class_name}::install_dir') %)
But again, don't do that. It is fragile, and it is virtually guaranteed to
become a mess.
If you would like to discuss alternative approaches to the actual problem
you are trying to solve, then we would be pleased to do so.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Split node definition into multiple files
On Saturday, February 2, 2013 10:25:14 AM UTC-6, Jared Curtis wrote:
Couldn't you just add a new include to sites.pp called zones.pp then build
a class within it to include on your DNS nodes?
class myzones {
nsd::zone { ... }
.
}
node DNS {
include myzones
.
}
Moving the resources out of node blocks and into classes is certainly the
way to approach the problem. Sites.pp should have nothing to do with it,
however, and (separately) the new class(es) should go in a module.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] LogStash Book released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I've just released 'The LogStash Book' (http://www.logstashbook.com/). It's a new book designed for SysAdmins, Operations staff, Developers and DevOps who are interested in deploying a log management solution using the open source tool LogStash (http://www.logstash.net/). It's available for sale on the site a PDF or ePUB: http://www.logstashbook.com/ Or from Amazon.com as a Kindle ebook: http://www.amazon.com/gp/product/B00B9JQTCO/ref=as_li_ss_tl?ie=UTF8camp=1789creative=390957creativeASIN=B00B9JQTCOlinkCode=as2tag=puppet0e-20 Given the overlap between Puppet folks and LogStash users I thought it might interest people. Regards James - -- Author of: * The LogStash Book (http://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJRD9oQAAoJECFa/lDkFHAye0sH/RTxDbsWHWIhENwZNnpYjdJo G+wazhFEZ4Bs+siImxbBCJwlLU9y9EbkEBnooA4aWRiMIK58uGi0ptTGRbzPdW5d Tvk6ufqkxlV5DcuRm1iDBJQf6LTkLwd1igwcHC5tXydloW7MpZgiZUU69jL7Ldye UzStaGIYiSN8HR8hhRB9aaKoIrlR16hpYRkKIBDKfHvFvPa/zK/coZrklQLwl+et nuwaY7TYAyvtPPKnJeHPNjQqhLXxq0rYZnu1aEhwwWlViL5GQKWLEzvxbrb2geWp aYBDX+n3l9hqpWHrbY3SN1csOA/RoPY1YEoKaE0OYNjUOsZ58u+W7ZBNjNXtLV4= =8fTs -END PGP SIGNATURE- -- 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 Starting error
On Saturday, February 2, 2013 1:31:28 AM UTC-6, teste...@gmail.com wrote: Hello, I have got the following error while starting the puppet client, please find the following = root@epsilon [/usr/src]# /etc/init.d/puppet start Starting puppet: /usr/sbin/puppetd:159:in `require': no such file to load -- puppet/application/puppetd (LoadError) from /usr/sbin/puppetd:159 = I have checked ruby installation and it seems to be fine. Does any one see this error, please update? It looks like your initscript may be written toward a pretty old version of Puppet, as what used to be called puppetd has been puppet agent for at least the last three generations of Puppet. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] OS provisionning of physical server usinsg puppet ?
Hi all, I'm a newbie in puppet I read the documentation and according to me, puppet is a language to manage OS and to check compliance to OS template. I read that puppet enterprise can deploy Vmware vm template and Amazon EC2 VM. But it seem's that puppet core can't deploy physical server The only way I imagine is to build a pxe server, and images including puppet agent. Is it correct ? I'm looking for an open source tool supported tool by a company to deploy physical and VM servers, on Linux and Windows. Thank you ML. -- 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] All nodes are showing unresponsive
Hello That looks like a 500 error from Apache, which is a Internal server error. You need to have a look at the apache logs on the vm to see what the problem is. The logs *should* be in /var/log/httpd This is the centos guide to logs http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-logfiles.html I hope this helps. Mark On Monday, February 4, 2013 10:02:00 AM UTC, Mamta Garg wrote: Hi James, Thanks for reply! Yes, i am using learning puppet VM. and have ran both commands and able it run successfully . But even before running these command i started getting error while launching puppet dashboard. Please find attched acreenshot for dashboard error.Do you have clue about this error? Thanks, Mamta On Fri, Feb 1, 2013 at 8:44 PM, James Sweeny james@puppetlabs.comjavascript: wrote: Hi Mamta, Are you using the learning puppet VM (I assume so because of the domain name)? That comes with Puppet Enterprise installed, which uses different paths and service names. In PE, the master and console run under the pe-httpd service, and the agent runs under pe-puppet. Are you able to run the following commands? If not, please copy/paste the error text. /sbin/service pe-httpd start /sbin/service pe-puppet start If you are not using the learning puppet VM, and are not using Puppet Enterprise, the above instructions will not apply, and we will need more information about how you installed dashboard to troubleshoot further. Thanks, - James On Thu, Jan 31, 2013 at 5:03 AM, Mamta Garg itsmam...@gmail.comjavascript: wrote: Can anyone please help! On Wed, Jan 30, 2013 at 6:58 AM, Mamta Garg itsmam...@gmail.comjavascript: wrote: Hi , I have set the correct time on master and agent.But Not able to lauch puppet dashboard. Please guide? find attched screenshot. I thiugh because of servuce iam getting error ,I have tried to run below command ,getting error. puppet resource service puppet ensure=running enable=true Thanks, Mamta On Tue, Jan 29, 2013 at 11:38 PM, RAVI TEJ ravi...@gmail.comjavascript: wrote: Hi mamta, Could you please check the time on the server(which is hosting puppet-dashboard) ?? Make sure it is sync with the puppet master. -- 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. -- Thanks and Regards, Mamta Garg -- Thanks and Regards, Mamta Garg -- 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. -- James Sweeny Professional Services http://puppetlabs.com/ -- 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. -- Thanks and Regards, Mamta Garg -- 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 custom recursive directory synchronization
On Monday, February 4, 2013 9:40:41 AM UTC-6, Andriy Yurchuk wrote:
To be able to do this with purge I need to pass the list of subdirectories
I want to exist to source attribute, but I'm not sure I can do this
On Monday, February 4, 2013 2:57:20 PM UTC+2, 刘长元 wrote:
but this does not remove the directories from the node if I remove them
from deployment.yml. maybe purge attribute can do this.
On Monday, February 4, 2013 7:58:37 PM UTC+8, Andriy Yurchuk wrote:
I'm trying to implement a custom recursive directory synchronization
resource in Puppet. What I need to do is the following.
I have a YAML file with the list of hostnames and the list of
directories that should exist on each hostname inside, say,
`/var/lib/my_app` directory (`deployment.yml`):
host_1:
- DIR_1
- DIR_5
host_5:
- DIR_7
host_6:
- DIR_2
- DIR_3
- DIR_9
On the master I have a directory that contains all of those `DIR_*`
sub-directories. Each subdirectory contains some files. What I'm trying to
achieve is to synchronize all the nodes according to the `deployment.yml`,
so that `/var/lib/my_app` on `host_1` only contains `DIR_1` and `DIR_5`,
but does not contain `DIR_7`, `DIR_2`, `DIR_3`, `DIR_9`, and so on.
I tried to do this using the ignore variable for file type, but this
does not remove the directories from the node if I remove them from
deployment.yml. I tried to write a custom function to remove them
afterwards, but it does not seem to work inside my manifest. I also wanted
to implement a custom type, but it seems to be too complicated.
I'd appreciate any help on this.
One reasonably good way to approach this problem is to endow your manifests
with the knowledge of the full set of possible DIR_*. You could add that
as a separate datum, you could create it by merging all the per-host lists,
or you could perhaps create it by listing the server-side directory in
which they the master copies live. You can then generate appropriate File
resources for every one, specifying whether it should be present or absent.
Alternatively, you certainly can do this with an Exec'ed script. You
didn't say much about what you tried in that direction, but something along
these lines ought to do the trick:
# the join() function comes from the stdlib module:
$wanted_dirs_pattern = join($wanted_dirs, '|')
exec { 'clean unwanted myapp/ subdirs':
command = /bin/bash -c 'for d in /var/lib/my_app/*; do
case \$d in $wanted_dirs_pattern) ;; *) /bin/rm -rf \$d;; esac
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Installing Operating systems
Puppet doesn't do OS provisioning itself. You'd need a separate system to do that part, then hand off to puppet after a minimal install has been completed. You can use a tool like Foreman (http://theforeman.org/). It will handle the provisioning of the systems and also integrates with puppet to assign classes and handle ssl certs. On Monday, February 4, 2013 4:28:53 AM UTC-7, Manish Singh wrote: Hello All, I am new to puppet and was trying to figure out whether puppet can handle the requirement I had. The requirement is to reinstall an OS (Windows, distributions of Linux) on slave machines before a job is executed. This is needed as we need a clean OS before executing the jobs on the nodes.. Is there a way using puppet that I plugin a machine to the puppet network, I can install a OS of my choice on the node and then that node gets added as a puppet node for further job execution? -Manish -- 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: Installing Operating systems
There is also razor (https://puppetlabs.com/solutions/next-generation-provisioning/). It is only for provisioning (not assigning classes) and is the future of provisioning and puppet. On Monday, February 4, 2013 11:29:33 AM UTC-7, joe wrote: Puppet doesn't do OS provisioning itself. You'd need a separate system to do that part, then hand off to puppet after a minimal install has been completed. You can use a tool like Foreman (http://theforeman.org/). It will handle the provisioning of the systems and also integrates with puppet to assign classes and handle ssl certs. On Monday, February 4, 2013 4:28:53 AM UTC-7, Manish Singh wrote: Hello All, I am new to puppet and was trying to figure out whether puppet can handle the requirement I had. The requirement is to reinstall an OS (Windows, distributions of Linux) on slave machines before a job is executed. This is needed as we need a clean OS before executing the jobs on the nodes.. Is there a way using puppet that I plugin a machine to the puppet network, I can install a OS of my choice on the node and then that node gets added as a puppet node for further job execution? -Manish -- 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: Debugging a facter problem
On Friday, February 1, 2013 8:16:12 AM UTC-6, Bernhard Schmidt wrote:
---
require 'facter'
require 'facter/util/ip'
if not FileTest.exists?(/usr/sbin/lldpctl)
nil
end
That last bit probably doesn't do what you want. That is to say, it
evaluates to nil in every case (implicitly when the condition is not
satisfied), and has no effect on anything else in the fact implementation.
Perhaps you meant to put the rest of the body in an 'else' clause? Or,
reverse the sense of the test and put everything else inside the condition?
config = Hash[]
output = Facter::Util::Resolution.exec(/usr/sbin/lldpctl -f keyvalue)
if output ==
nil
end
Again, a not-what-you-intended conditional statement. In this case, it's
probably altogether unnecessary.
for line in output.split(\n) do
# Drop Multiline
if line =~ /^lldp/
key, value = line.split('=')
prefix, int, key2 = key.split('.', 3)
if not config.has_key?(int)
config[int] = Hash[]
end
config[int][key2] = value
end
end
More idiomatic Ruby might be:
# This hash automatically creates appropriate new
# entries as needed:
config = Hash.new { |h, k| h[k] = Hash.new }
output.lines.grep(/^lldp/).each do |line|
# note the 'chomp':
key, value = line.chomp.split('=')
prefix, int, key2 = key.split('.', 3)
config[int][key2] = value
end
Other than the chomp, however, I don't think that will change the results.
for interface in config.keys do
Facter.add(lldp_neighbor_ + Facter::Util::IP.alphafy(interface)) do
setcode do
device = config[interface].fetch('chassis.name', )
ifdescr = config[interface].fetch('port.descr', )
ifalias = config[interface].fetch('port.ifalias', )
if device !=
if ifalias !=
device + + ifalias
else
device ++ ifdescr
end
end
end
end
end
More idiomatic:
config.each_pair do | interface, props |
Facter.add(lldp_neighbor_ + Facter::Util::IP.alphafy(interface)) do
setcode do
device = props.fetch('chassis.name', )
if device !=
# note: although clean and concise, this is not 100%
# equivalent to the original if 'port.ifalias' can be present but
# empty:
device + ' ' + props.fetch('port.ifalias', props['port.descr'])
else
# default value when device is empty
'no config'
end
end
end
end
I think that might solve your problem, too. Here's what I think is
happening to you: your 'for' loop runs, setting variable 'interface' in
turn to each key of the 'config' hash. At each iteration, it creates a
block of code that Facter will execute (later) to determine the value of
one fact. Ruby blocks are closures, so where yours later reference the
value of 'interface' they are getting the then-current value in the context
where the block was created. By that time, that's the value after the
iteration is done (apparently the last key iterated).
I think the rewritten version will solve that problem because at each
iteration, the values of the key and (inner) hash are captured as distinct
local variables ('interface' and 'props'), very much as if the block passed
to 'each_pair' were an independent function. This is a Ruby subtlety, so
you have chosen a good example to attempt to expand your understanding of
Ruby.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Installing Operating systems
Razor is still pretty experimental, so I wouldn't recommend it unless you are comfortable with alpha software. It does integrate with provisioning, in the sense that it will hand off through a broker to Puppet (or Chef, or other tools), so it should have a smooth transition between provisioning and configuration. If you are interested there is a Razor mailing list, puppet-ra...@googlegroups.com, where you would be welcome to join us. We would love more feedback on if, and how, Razor helps solve your problems - or how it falls short! On Mon, Feb 4, 2013 at 10:32 AM, joe lava...@gmail.com wrote: There is also razor (https://puppetlabs.com/solutions/next-generation-provisioning/). It is only for provisioning (not assigning classes) and is the future of provisioning and puppet. On Monday, February 4, 2013 11:29:33 AM UTC-7, joe wrote: Puppet doesn't do OS provisioning itself. You'd need a separate system to do that part, then hand off to puppet after a minimal install has been completed. You can use a tool like Foreman (http://theforeman.org/). It will handle the provisioning of the systems and also integrates with puppet to assign classes and handle ssl certs. On Monday, February 4, 2013 4:28:53 AM UTC-7, Manish Singh wrote: Hello All, I am new to puppet and was trying to figure out whether puppet can handle the requirement I had. The requirement is to reinstall an OS (Windows, distributions of Linux) on slave machines before a job is executed. This is needed as we need a clean OS before executing the jobs on the nodes.. Is there a way using puppet that I plugin a machine to the puppet network, I can install a OS of my choice on the node and then that node gets added as a puppet node for further job execution? -Manish -- 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. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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] OS provisionning of physical server usinsg puppet ?
On Mon, Feb 4, 2013 at 5:59 PM, ml mldmld1...@gmail.com wrote: Hi all, I'm a newbie in puppet I read the documentation and according to me, puppet is a language to manage OS and to check compliance to OS template. I read that puppet enterprise can deploy Vmware vm template and Amazon EC2 VM. But it seem's that puppet core can't deploy physical server The only way I imagine is to build a pxe server, and images including puppet agent. Is it correct ? I'm looking for an open source tool supported tool by a company to deploy physical and VM servers, on Linux and Windows. Checkout http://theforeman.org Ohad Thank you ML. -- 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] Announce: PuppetDB 1.1.1 Available!
PuppetDB 1.1.1 is now available for download! This is a bug-fix release of PuppetDB. For details on the new features in PuppetDB 1.1.x, check out the blog post at https://puppetlabs.com/blog/announcing-puppetdb-1-1-do-more-with-your-data/ = ### Downloads### = Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.3 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello == ### 1.1.1 Release Notes ### == Many thanks to the following people who contributed patches to this release: * Chris Price * Nick Fagerlund * Nick Lewis Fixes: * (#18934) Dashboard Inventory Service returns 404 Version 1.1.0 of the PuppetDB terminus package contained a faulty URL for retrieving fact data for the inventory service. This issue is fixed and we've added better testing to ensure that this doesn't break again in the future. * (#18879) PuppetDB terminus 1.0.5 is incompatible with PuppetDB 1.1.0 Version 1.1.0 of the PuppetDB server package contained some API changes that were not entirely backward-compatible with version 1.0.5 of the PuppetDB terminus; this caused failures for some users if they upgraded the server to 1.1.0 without simultaneously upgrading the terminus package. Version 1.1.1 of the server is backward-compatible with terminus 1.0.5, allowing an easier upgrade path for 1.0.x users. -- 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] Announce: Puppet 3.1.0 Available
Puppet 3.1.0 is a feature release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.1.0 version in our issue tracker at: https://projects.puppetlabs.com/versions/288 This is the first minor release in the Puppet 3 series. It introduces some new functionality and fixes a number of bugs, but is intended to be completely backwards-compatible with 3.0. There will be no further 3.0.x point releases, so any current Puppet 3 users should upgrade to 3.1.0. For users upgrading from a 2.x series release, please read through the [long-form Puppet 3 release notes](http://docs.puppetlabs.com/puppet/3/reference/release_notes.html) for a full list of new features, deprecations, and backwards-incompatible changes. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.1.0.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.1.0.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.1.0.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.1.0.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.1.0: https://projects.puppetlabs.com/projects/puppet/ ## Puppet 3.1.0 Contributors ## Aaron Hicks, Andrew Parker, Branan Purvine-Riley, Chris Barker, Dave Dash, Dustin J. Mitchell, Eric Sorenson, Erik Dalén, Henrik Lindberg, Jeff McCune, Joachim de Groot, John Julien, Josh Cooper, Lauri Tirkkonen, Matthaus Owens, Michael Hall, Moses Mendoza, Nick Fagerlund, Nick Lewis, Patrick Carlisle, Paul Morgan, Peter Eisentraut, Rahul Gopinath, Ryan Uber, Stefan Schulte, Steven Lindberg, mruzicka = ## Puppet 3.1.0 Release Notes ## = ### Ruby DSL Deprecated, new Puppet Ruby DSL removed We introduced deprecation warnings for the (not-well-documented, mostly-unused) Ruby DSL; if you are using the Ruby DSL in production we want to hear from you to learn what you're doing with it -- please reply to this message on puppet-...@googlegroups.com! Additionally, after testing the revamped Ruby DSL that was in RC1, we made the call not to ship it. This was a tough decision, but the number and severity of issues that came up in exploratory testing led us to the conclusion that it was not supportable code. Again, if there are issues you run into with the Puppet DSL that you wanted to solve with the Ruby DSL, we want to hear about this on the puppet-dev mailing list. ## Headline Features ### Improvements When Loading Ruby Code A major area of focus for this release was loading extension code. As people wrote and distributed Faces (new puppet subcommands that extend Puppet's capabilities), bugs like [#7316](https://projects.puppetlabs.com/issues/7316) started biting them. Additionally, seemingly simple things like retrieving configuration file settings quickly got complicated, causing problems both for Puppet Labs' code like Cloud Provisioner as well as third-party integrations like Foreman. The upshot is that it's now possible to fully initialize puppet when using it as a library, loading Ruby code from Forge modules works correctly, and tools like puppetlabs_spec_helper now work correctly. ### YARD API Documentation To go along with the improved usability of Puppet as a library, we've added [YARD documentation](http://yardoc.org) throughout the codebase. YARD generates browsable code documentation based on in-line comments. This is a first pass through the codebase but about half of it's covered now. To use the YARD docs, simply run `gem install yard` then `yard server --nocache` from inside a puppet source code checkout (the directory containing `lib/puppet`). ### YAML Node Cache Restored on Master In 3.0.0, we inadvertently removed functionality that people relied upon to get a list of all the nodes checking into a particular puppet master. This had actually flip-flopped a few times but now it's enabled for good, added to the test harness, and available for use as: # shell snippet export CLIENTYAML=`puppet master --configprint yamldir` puppet node search * --node_terminus yaml --clientyamldir $CLIENTYAML ### Other bugfixes and improvements In addition to the headline features, Puppet 3.1 includes a number of improvements and bugfixes, many of which were community-contributed -- many thanks to the community members who submitted documentation, test, and code improvements. Some of the more interesting ones follow. * The Solaris package manager now supports the `holdable` feature
Re: [Puppet Users] Is it possible to enable SSL tracing on the master and agent?
If you are running the master under mod_passenger then you can set 'LogLevel debug'. On 3 February 2013 04:29, Schofield dbschofi...@gmail.com wrote: I would like to see the SSL handshake between the master and agent. How do I enable this? -- 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: Split node definition into multiple files
Hi
thank you for your inputs.
Am 04.02.2013 16:53, schrieb jcbollinger:
On Saturday, February 2, 2013 10:25:14 AM UTC-6, Jared Curtis wrote:
Couldn't you just add a new include to sites.pp called zones.pp
then build a class within it to include on your DNS nodes?
and (separately) the new class(es) should go in a module.
I've done that now and grouped the entries using child classes:
class myzones {
include myzones::customer1
}
class myzones::customer1 {
nsd::zone { ... }
}
etc..
That's more or less what I was looking for.
Is there a way to automatically include child classes? Something like
include myzones::* :-)
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.
Re: [Puppet Users] Recent RoR Vulns and puppet 3x on RHEL 6?
Unless you've elected to use legacy storeconfigs (with activerecord), you are correct, your system should not be vulnerable. stahnma On Mon, Feb 4, 2013 at 6:15 AM, Kodiak Firesmith kfiresm...@gmail.com wrote: Hello fellow Puppet users! I'm trying to perform due diligence to make sure that our Puppet installations aren't affected by all the RoR vulns in the news recently. (http://www.kalzumeus.com/2013/01/31/what-the-rails-security-issue-means-for-your-startup/) (http://www.informationweek.com/security/vulnerabilities/critical-ruby-on-rails-issue-threatens-2/240145891) I've been watching the PuppetLabs security (https://puppetlabs.com/security/) page, and the RedHat CVE DB (https://access.redhat.com/security/cve/) and haven't seen anything that appears to directly affect a typical Puppet3 installation on RHEL 6 running the latest RHEL6-supported Ruby (1.8.7.352-7). Is it safe to say that my platform is not affected? 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. -- 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] How do I generate a sequence number in a template
I'm trying to puppetize my PgPool install. PgPool uses the convention: backend_hostname0 = backend_port0 = backend_weight0 = backend_data_directory0 = backend_flag0 = I'm using exported resources and concat to auto-detect postgres instances. My template for this chunk looks like: % Array(ipaddress).zip(Array(pgport)).each do |ipaddress,port| -% % backend = 0 % backend_hostname%= backend -% = %= ipaddress % backend_port%= backend -% = %= port % backend_weight%= backend -% = 1 backend_data_directory%= backend -% = '/db/pg' backend_flag%= backend -% = 'ALLOW_TO_FAILOVER' % backend += 1 % % end % I assumed that the backend = 0 / backend += 1 would work like a counter as this .each loop was iterated over. However what I end up with is two stanza's with backend_hostname0 ...etc... backend_hostname0 ...etc... any ideas on how to make this happen? 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: Announce: Puppet 3.1.0 Available
On Mon, Feb 4, 2013 at 12:07 PM, Matthaus Owens matth...@puppetlabs.comwrote: Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet 3.1.0 is in the main repository that is enabled by default and not the pre-release repository, right? For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos To get Puppet 3.1.0 you don't need to enable the pre-release repo. This is the real deal! If you have our repository configured you should simply need to upgrade the packages you already have installed. -Jeff -- 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] hiera query yaml parameters
Thanks, Steven.
I will try it out
On Feb 3, 2013, at 10:21 PM, Steven Nemetz wrote:
You can read the hash directly, create_resource is not needed (may or may not
be desired)
$user_defs = hiera('os_users') will give you the full hash
What I tend to do for this type of data structure is:
$user_defs = hiera('os_users')
$user_keys = keys($user_defs)
if is_array($user_keys) {
process_users { $user_keys:; }
}
define process_users {
# Do whatever you want for each element of the hash
# $name will be the hash key
# $user_defs[$name] is the hash of the current item
# $user_defs[$name]['comment'] to access the user's comment field
}
Steven
From: y...@comcast.net
Subject: Re: [Puppet Users] hiera query yaml parameters
Date: Sun, 3 Feb 2013 19:19:25 -0500
To: puppet-users@googlegroups.com
Could you show your solution, please ?
I would like to see how you did it.
On Feb 3, 2013, at 6:46 PM, roadtest wrote:
I figure out the solution.
Using the create_resource to convert YAML to a hash array, then I can query
retrieve every individual value. If there is better way, feel free to share
with group.
carl
On Saturday, February 2, 2013 3:25:33 PM UTC-5, roadtest wrote:
Hello,
I have a yaml data file containing user account with following information.
#more users.yaml
---
os_users:
user1:
locked: false
comment: System Operator
uid: '700'
gid: '700'
groups:
- admin
- sudonopw
sshkeys:
- ssh-rsa
B3NzaC1yc2EBIwAAAQEAwLBhQefRiXHSbVNZYKu2o8VWJjZJ/B4LqICXuxhiiNSCmL8j+5zE/VLPIMeDqNQt8L
user2:
locked: true
comment: Test Locked Account
uid: '701'
gid: '701'
groups:
- admin
- sudonopw
sshkeys:
- ssh-rsa
B3NzaC1yc2EBIwAAAQEAwLBhQefRiXHSbVNZYKu2o8VWJjZJ/B4LqICXuxhiiNSCm
I can search os_users information like following:
#hiera -c /etc/hiera.yaml os_users
{user1={groups=[admin, sudonopw], locked=false,
comment=System Operator, uid=700, sshkeys=[ssh-rsa
B3NzaC1yc2EBIwAAAQEAwLBhQefRiXHSbVNZYKu2o8VWJjZJ/B4LqICXuxhiiNSCmL8j+5zE/VLPIMeDqNQt8L],
gid=700}, user2={groups=[admin, sudonopw], locked=true,
comment=Test Locked Account, uid=701, sshkeys=[ssh-rsa
B3NzaC1yc2EBIwAAAQEAwLBhQefRiXHSbVNZYKu2o8VWJjZJ/B4LqICXuxhiiNSCm],
gid=701}}
My question is how I can get value of os_users - user1 - sshkeys. I tried:
#hiera -c /etc/hiera.yaml os_users[user1[sshkeys]]
nil
Could you please advise whether this is doable or direct me to some document?
Thanks in advance,
carl
--
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] Re: Announce: Puppet 3.1.0 Available
Absolutely right. Apologies. That was a copy/paste error on my part from a previous 3.1.0-rc release email. Thanks for catching that Jeff! On Mon, Feb 4, 2013 at 5:47 PM, Jeff McCune j...@puppetlabs.com wrote: On Mon, Feb 4, 2013 at 12:07 PM, Matthaus Owens matth...@puppetlabs.com wrote: Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet 3.1.0 is in the main repository that is enabled by default and not the pre-release repository, right? For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos To get Puppet 3.1.0 you don't need to enable the pre-release repo. This is the real deal! If you have our repository configured you should simply need to upgrade the packages you already have installed. -Jeff -- 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. -- Matthaus Owens Release Manager, Puppet Labs -- 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] Is it possible to generate a sequence in a template?
Howdy! Is it possible to generate a sequence in a loop in a puppet template? I'm trying something like: % @foo = 0 % % Array(bar).each do |flan| -% value %= @foo % % @foo += 1 % % end % But that's not working. (i just get a bunch of 0's) Any ideas? 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] How do I generate a sequence number in a template
On Mon, Feb 4, 2013 at 5:41 PM, David Kerr ker...@gmail.com wrote: My template for this chunk looks like: % Array(ipaddress).zip(Array(pgport)).each do |ipaddress,port| -% % backend = 0 % backend_hostname%= backend -% = %= ipaddress % backend_port%= backend -% = %= port % backend_weight%= backend -% = 1 backend_data_directory%= backend -% = '/db/pg' backend_flag%= backend -% = 'ALLOW_TO_FAILOVER' % backend += 1 % % end % I think your problem is you are re-initializing the 'backend' variable each iteration of the loop. Try: % backend = 0 -% % Array(ipaddress).zip(Array(pgport)).each do |ipaddress,port| -% backend_hostname%= backend -% = %= ipaddress % backend_port%= backend -% = %= port % backend_weight%= backend -% = 1 backend_data_directory%= backend -% = '/db/pg' backend_flag%= backend -% = 'ALLOW_TO_FAILOVER' % backend += 1 -% % end % Cheers, Aaron Russo IST Infrastructure Services, Unix Group UC Berkeley --- Desk: 510-643-5550Mobile: 510-206-1532 IM: aru...@berkeley.edu (XMPP/Jabber) -- 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] Is it possible to generate a sequence in a template?
On Mon, Feb 4, 2013 at 7:37 PM, David Kerr ker...@gmail.com wrote: % @foo = 0 % % Array(bar).each do |flan| -% value %= @foo % % @foo += 1 % % end % This code worked for me. I just used an inline template, but otherwise I had exactly what you had: link: https://gist.github.com/arusso23/4712284 (I'm on 3.0.1 btw) Cheers, Aaron Russo IST Infrastructure Services, Unix Group UC Berkeley --- Desk: 510-643-5550Mobile: 510-206-1532 IM: aru...@berkeley.edu (XMPP/Jabber) -- 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] Is it possible to generate a sequence in a template?
On Monday, February 4, 2013 9:07:49 PM UTC-8, Aaron Russo wrote: On Mon, Feb 4, 2013 at 7:37 PM, David Kerr ker...@gmail.com javascript: wrote: % @foo = 0 % % Array(bar).each do |flan| -% value %= @foo % % @foo += 1 % % end % This code worked for me. I just used an inline template, but otherwise I had exactly what you had: link: https://gist.github.com/arusso23/4712284 (I'm on 3.0.1 btw) hmm, ok thanks, good to know it SHOULD work =) I believe my problem is that i'm using concat and my expectations of how that works are incorrect. Now i have to figure out how to do what I'm doing w/o concat. 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] How do I generate a sequence number in a template
yeah, i saw that, and fixed it, but still no good. i had thought/hoped that i deleted this post and posted my next one which you also kindly answered. On Monday, February 4, 2013 9:05:24 PM UTC-8, Aaron Russo wrote: On Mon, Feb 4, 2013 at 5:41 PM, David Kerr ker...@gmail.com javascript: wrote: My template for this chunk looks like: % Array(ipaddress).zip(Array(pgport)).each do |ipaddress,port| -% % backend = 0 % backend_hostname%= backend -% = %= ipaddress % backend_port%= backend -% = %= port % backend_weight%= backend -% = 1 backend_data_directory%= backend -% = '/db/pg' backend_flag%= backend -% = 'ALLOW_TO_FAILOVER' % backend += 1 % % end % I think your problem is you are re-initializing the 'backend' variable each iteration of the loop. Try: % backend = 0 -% % Array(ipaddress).zip(Array(pgport)).each do |ipaddress,port| -% backend_hostname%= backend -% = %= ipaddress % backend_port%= backend -% = %= port % backend_weight%= backend -% = 1 backend_data_directory%= backend -% = '/db/pg' backend_flag%= backend -% = 'ALLOW_TO_FAILOVER' % backend += 1 -% % end % Cheers, Aaron Russo IST Infrastructure Services, Unix Group UC Berkeley --- Desk: 510-643-5550Mobile: 510-206-1532 IM: aru...@berkeley.edu javascript: (XMPP/Jabber) -- 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: Installing Operating systems
We did a presentation about razor on puppetcamp ghent last friday. (kind of an introduction and a small demo). https://puppetlabs.com/community/puppet-camp/#previous video will be online soon The video and slides will be available soon. Grt johan On 02/04/2013 07:40 PM, Daniel Pittman wrote: Razor is still pretty experimental, so I wouldn't recommend it unless you are comfortable with alpha software. It does integrate with provisioning, in the sense that it will hand off through a broker to Puppet (or Chef, or other tools), so it should have a smooth transition between provisioning and configuration. If you are interested there is a Razor mailing list, puppet-ra...@googlegroups.com, where you would be welcome to join us. We would love more feedback on if, and how, Razor helps solve your problems - or how it falls short! On Mon, Feb 4, 2013 at 10:32 AM, joe lava...@gmail.com wrote: There is also razor (https://puppetlabs.com/solutions/next-generation-provisioning/). It is only for provisioning (not assigning classes) and is the future of provisioning and puppet. On Monday, February 4, 2013 11:29:33 AM UTC-7, joe wrote: Puppet doesn't do OS provisioning itself. You'd need a separate system to do that part, then hand off to puppet after a minimal install has been completed. You can use a tool like Foreman (http://theforeman.org/). It will handle the provisioning of the systems and also integrates with puppet to assign classes and handle ssl certs. On Monday, February 4, 2013 4:28:53 AM UTC-7, Manish Singh wrote: Hello All, I am new to puppet and was trying to figure out whether puppet can handle the requirement I had. The requirement is to reinstall an OS (Windows, distributions of Linux) on slave machines before a job is executed. This is needed as we need a clean OS before executing the jobs on the nodes.. Is there a way using puppet that I plugin a machine to the puppet network, I can install a OS of my choice on the node and then that node gets added as a puppet node for further job execution? -Manish -- 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. -- Johan De Wit Open Source Consultant Red Hat Certified Engineer(805008667232363) Puppet Certified Professional 2013 (PCP006) _ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile +32 (0)474/42 40 73 BELGIUM http://www.open-future.be _ -- 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] All nodes are showing unresponsive
Hi Mark, Thanks for reply! Now internal server error issue has been resolved but still showing all nodes as unresponsive under puppet dashboard. All the task are showing pending. Thanks, Mamta On Mon, Feb 4, 2013 at 9:18 PM, Mark Whaite wha...@gmail.com wrote: Hello That looks like a 500 error from Apache, which is a Internal server error. You need to have a look at the apache logs on the vm to see what the problem is. The logs *should* be in /var/log/httpd This is the centos guide to logs http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-logfiles.html I hope this helps. Mark On Monday, February 4, 2013 10:02:00 AM UTC, Mamta Garg wrote: Hi James, Thanks for reply! Yes, i am using learning puppet VM. and have ran both commands and able it run successfully . But even before running these command i started getting error while launching puppet dashboard. Please find attched acreenshot for dashboard error.Do you have clue about this error? Thanks, Mamta On Fri, Feb 1, 2013 at 8:44 PM, James Sweeny james@puppetlabs.comwrote: Hi Mamta, Are you using the learning puppet VM (I assume so because of the domain name)? That comes with Puppet Enterprise installed, which uses different paths and service names. In PE, the master and console run under the pe-httpd service, and the agent runs under pe-puppet. Are you able to run the following commands? If not, please copy/paste the error text. /sbin/service pe-httpd start /sbin/service pe-puppet start If you are not using the learning puppet VM, and are not using Puppet Enterprise, the above instructions will not apply, and we will need more information about how you installed dashboard to troubleshoot further. Thanks, - James On Thu, Jan 31, 2013 at 5:03 AM, Mamta Garg itsmam...@gmail.com wrote: Can anyone please help! On Wed, Jan 30, 2013 at 6:58 AM, Mamta Garg itsmam...@gmail.comwrote: Hi , I have set the correct time on master and agent.But Not able to lauch puppet dashboard. Please guide? find attched screenshot. I thiugh because of servuce iam getting error ,I have tried to run below command ,getting error. puppet resource service puppet ensure=running enable=true Thanks, Mamta On Tue, Jan 29, 2013 at 11:38 PM, RAVI TEJ ravi...@gmail.com wrote: Hi mamta, Could you please check the time on the server(which is hosting puppet-dashboard) ?? Make sure it is sync with the puppet master. -- 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=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Thanks and Regards, Mamta Garg -- Thanks and Regards, Mamta Garg -- 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=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- James Sweeny Professional Services http://puppetlabs.com/ -- 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=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Thanks and Regards, Mamta Garg -- 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. -- Thanks and Regards, Mamta Garg -- 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
