Hi,
Here is my puppet.conf on the server side:
...
[master]
certname=s001ap38-test
...
The puppet.conf on the agent side is:
...
[master]
server=s001ap38-test
...
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group
The puppet manifest would simplify to :
class foo (
$services_to_stop = [],
) {
include 'stdlib'
if size($services_to_stop) > 0 {
service { $services_to_stop :
ensure => stopped,
enable => false,
On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Leroy Tennison wrote:
>
> Puppet v3.4.3
>
> What I was specifically hoping to do was:
>
> exec { 'test' :
>
> command => "%comspec% /c (a Windows command-line program with parameters)",
>
> }
>
>
> to avoid having to determine where Windows was insta
Hi Dan,
Thanks for hint. I am already using hiera, yes the code looks much cleaner
when using it.
Regards,
Vikas
On Monday, 12 October 2015 23:32:46 UTC+11, LinuxDan wrote:
>
> The puppet manifest would simplify to :
> class foo (
> $services_to_stop = [],
> ) {
>
> include 'stdlib'
>
> if size
On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Costya Regev wrote:
>
> Hi ,
> I have a question regarding managing puppet virtual Resource i have this
> code:
> class Carb::chocolatey {
> include chocolatey
> # [Make Chocolately default package provider]
> Package { provider => cho
On Monday, October 12, 2015 at 2:40:23 AM UTC-5, Wei Chen wrote:
>
> Hi,
>
> Here is my puppet.conf on the server side:
> ...
> [master]
> certname=s001ap38-test
> ...
>
> The puppet.conf on the agent side is:
> ...
> [master]
> server=s001ap38-test
> ...
>
>
The puppet agent does not use anythi
Given a site.pp that looks like this:
define test_type (
$value = [],
) {
$type = inline_template('<%= @value.class %>')
notify { "${title} => ${type}": }
}
@@test_type { $::fqdn:
value => [ $::fqdn ],
}
Test_type <<||>>
I get the odd result when run on icinga:
Notice: icinga.angel.net
Hi,
I have a foreman/puppet installation (done with foreman-installer) running
on ubuntu 14.
I was using it for a while already, with about 40 hosts, using the
'role/profile' approach to classify the nodes.
Which means that I have only one role per node, and the role calls
different profiles.
On Mon, Oct 12, 2015 at 5:54 AM, jcbollinger
wrote:
>
> On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Leroy Tennison wrote:
>>
>> Puppet v3.4.3
>>
>
At 3.4.3 your options are a bit more limited. For instance you are on 32
bit Puppet/Ruby b/c we didn't offer x64 Puppet/Ruby until 3.7.0. Or the
$
On Thu, Oct 8, 2015 at 12:44 AM, Fredrik Nilsson
wrote:
> Let's see if I can shed some light on this. Updated to Chocolatey
> 0.9.10-beta1 to see if this behaviour disappears, sadly it didn't. To
> puppet runs back to back will result in the file getting replaced both
> runs. There are no "manual
Thanks for the replies, learned more than I imagined.
On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Leroy Tennison wrote:
>
> Puppet v3.4.3
>
> What I was specifically hoping to do was:
>
> exec { 'test' :
>
> command => "%comspec% /c (a Windows command-line program with parameters)",
>
> }
>
>
You're encountering PDB-170 (https://tickets.puppetlabs.com/browse/PDB-170.)
It's a known bug, and last time I looked at it wasn't clear whether the
issue was Puppet or PDB, but I just tried it on Puppet 4.2.2/PuppetDB
3.1.0 and I can't reproduce:
https://gist.github.com/wkalt/83d8d8170d9f20a
On Sat, Oct 10, 2015 at 2:54 AM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:
> Same player shot again :
>
> https://tickets.puppetlabs.com/browse/PUP/fixforversion/14801/?selectedTab=com.atlassian.jira.plugins.jira-development-integration-plugin:release-report-tabpanel
>
> Version pupp
> Le 12 oct. 2015 à 18:01, Michael Stahnke a écrit :
> With transparency comes the ability to see things that are not perfect. We
> had a large conference last week where a very large portion of our employee
> base was in attendance. We shipped the bits because it fixed a bug that some
> peop
On Mon, Oct 12, 2015 at 9:51 AM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:
>
> > Le 12 oct. 2015 à 18:01, Michael Stahnke a
> écrit :
>
> > With transparency comes the ability to see things that are not perfect.
> We had a large conference last week where a very large portion of our
> Le 12 oct. 2015 à 19:12, Michael Stahnke a écrit :
>
>
>
> On Mon, Oct 12, 2015 at 9:51 AM, Fabrice Bacchella
> wrote:
>
> > Le 12 oct. 2015 à 18:01, Michael Stahnke a écrit :
>
> > With transparency comes the ability to see things that are not perfect. We
> > had a large conference las
I've just released version 2.0 of the puppetdbquery module. It uses the new
v4 API in PuppetDB, so version 3.x of PuppetDB is required.
The highlights are:
- v4 API support
- support for structured facts, example: system_uptime.days>209
- arbitrary subqueries using # sign, example:
#node.catalo
Puppet Agent 1.2.6 is out! This is a new minor release of the all-in-one
agent
bundle which contains no updated component code, but fixes bugs in
packaging
and service management.
* Includes a fix for an issue that could, in some cases, leave the puppet
and mcollective services stopped and unregis
Hey folks,
I'm using a pretty recent version of Gareth's module skeleton and the
included Rakefile. I can run "rake spec" fine but I don't seem to be able
to get the "rake covereage" task to work.
--
$ bundle exec rake coverage
rake aborted!
NoMethodError: undefined method `rcov=' for
#
Tasks:
Hello.
I wrote a custom report processor to work with a messaging bus (using
ampq). However, it seems inefficient to re-create connections after a
report has been submitted.
That being said, I have identified two approaches to solve this:
1 - Create an interface that keeps the ampq connections
20 matches
Mail list logo
