Hi Alex,
On 17 Feb 2014, at 22:05, Alex Scoble bloggingit...@gmail.com wrote:
Hi All,
We are currently transitioning from using the Puppet Enterprise (PE) ENC to
using hiera. Howevver, one piece of functionality that we lack with hiera is
the ability to group systems together based on
On Monday, February 17, 2014 3:49:30 PM UTC+1, jcbollinger wrote:
Yes, I believe the combination of two simple expressions into a complex
one via the and operator is what Felix was referring to. Despite the
docs, it might be worthwhile to play around a bit to test the outlines of
the
On Monday, February 17, 2014 9:40:22 PM UTC+1, Trevor Vaughan wrote:
Can you just have Class B 'include' class A and then have the appropriate
resources in Class B notify/require what you need from Class A?
Wouldn't this create a dependency cycle?
Class B, as I wrote, requires class A. I
Hello, I'm actually trying to install puppet-dashboard from the dashboard
manual http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.htmland
I can't see to go pass testing that dashboard is working
It seems that ./script/server doesn't exist
Does anyone have a video of that part, a
Hi Marco,
On Mon, Feb 17, 2014 at 03:41:14AM -0800, zerozerouno...@gmail.com wrote:
Hi,
I have this situation:
Class A: contains a File resource, and a Service resource which requires
the File resource (the service needs to be restarted when the file changes).
Class B: will be applied
Hi,
On 02/17/2014 12:41 PM, zerozerouno...@gmail.com wrote:
resources belonging to class B must be applied only after resources from
class A have been applied. Class B also contains some File resources,
and after they are applied also the _same_ service from class A needs to
be restarted.
On Tuesday, February 18, 2014 1:11:15 PM UTC+1, nikolavp wrote:
class A {
service {'myservice':
ensure = 'started',
}
file { '/etc/default/myservice.conf':
ensure = present,
notify = Service['myservice'],
template = '...',
}
}
On Tuesday, February 18, 2014 1:18:36 PM UTC+1, Felix.Frank wrote:
Can the service be moved to a class of its own, which is included and
notified by both A and B?
Indeed, maybe this is a clean and viable solution.
I'll look into it.
Thanks.
--
You received this message because you are
On Tue, Feb 18, 2014 at 04:25:43AM -0800, zerozerouno...@gmail.com wrote:
On Tuesday, February 18, 2014 1:11:15 PM UTC+1, nikolavp wrote:
class A {
service {'myservice':
ensure = 'started',
}
file { '/etc/default/myservice.conf':
ensure =
On Tuesday, February 18, 2014 6:25:43 AM UTC-6, zerozer...@gmail.com wrote:
On Tuesday, February 18, 2014 1:11:15 PM UTC+1, nikolavp wrote:
class A {
service {'myservice':
ensure = 'started',
}
file { '/etc/default/myservice.conf':
ensure = present,
On Mon, Feb 17, 2014 at 2:57 PM, Jay Benner longri...@gmail.com wrote:
I tried them in chocolatey.ps1, but that just seemed to break chocolatey.
On Monday, February 17, 2014 11:11:25 AM UTC-8, Jay Benner wrote:
If I am going to use the workarounds mentioned in the bug article you
On Mon, Feb 17, 2014 at 6:20 AM, jcbollinger john.bollin...@stjude.org wrote:
Well, I think the question that killed this thread the first time boils down
to would it really?. The speculation at the time was that parallel
execution would produce disappointing wall-time gains, based on the
ok thanks alot!
// Mikael
On Monday, February 10, 2014 10:41:28 PM UTC+1, jcbollinger wrote:
On Monday, February 10, 2014 6:26:56 AM UTC-6, Mikael Lindqvist wrote:
Hi,
Thanks for a great program!
I have one request though, and also wonder if there is some other way to
do this...
PS - This system that I am working on is very much a test system, so we can
try whatever we want on it. It is representative of a lot of other systems
on my network, though, so I do need to land on a semi-elegant solution at
some point.
On Tuesday, February 18, 2014 8:03:45 AM UTC-8, Rob
Hi Johan,
Thanks for the suggestion . it is working as peadmin user. But where I can
get all these information regarding mcollective in one place. Because it
took lot of time to resolve this issue. I didn't find anywhere that it
should be running as a pe-admin user.
Deep
On Tuesday,
On Tue, Feb 18, 2014 at 12:10 PM, Jay Benner longri...@gmail.com wrote:
PS - This system that I am working on is very much a test system, so we
can try whatever we want on it. It is representative of a lot of other
systems on my network, though, so I do need to land on a semi-elegant
Puppet 3.4.2, as specified. I've attached a log file.
On Friday, February 7, 2014 12:35:32 PM UTC-5, Rob Reynolds wrote:
First question - what version of puppet?
Second question - can you run puppet apply (or agent) with --trace --debug
--verbose and post the relevant results? We have
I've got a working puppet on apache / passenger on EL6.4. However, ever
since updating the puppet client on computers to 3.4.2, I get notices that
I'm using insecure YAML and should upgrade the server to 3.3 or newer. How
do I do this? rpm -qa puppet-server shows
Thats cutting it pretty close for me. I am preparing for a pretty high
profile demo to some execs next Wednesday. I'll need at least a day to
test it out. I don't think I'll be fired if I'm not ready to demo this
module, but it would really help me evangelize the product against a high
Is this the correct log file for the error you described?
On Tue, Feb 18, 2014 at 1:06 PM, jmp242 jp10...@gmail.com wrote:
Puppet 3.4.2, as specified. I've attached a log file.
On Friday, February 7, 2014 12:35:32 PM UTC-5, Rob Reynolds wrote:
First question - what version of puppet?
As far as I can tell. I'm on Windows, and it scrolls off the screen. It
didn't seem to capture much when I tried to redirect to a file.
On Tuesday, February 18, 2014 2:51:01 PM UTC-5, Rob Reynolds wrote:
Is this the correct log file for the error you described?
On Tue, Feb 18, 2014 at 1:06
I didn't see the error that you described (your log notes an issue with
forking), but have a look at
https://tickets.puppetlabs.com/browse/PUP-1389(which speaks of the
require_file issues you describe). We've recently
fixed that issue and it will be in the next release. I'm not sure these are
the
Here's another test where I just added --test to your command, and passed
to a log file. It should show my issue. Anyway, it does look very similar
an error, though I can't figure out why any of the string manipulation
would fail on openvpn.exe and not on fusion.exe ...
On Tuesday, February
Excellent catch, the error was indeed an improperly-formatted /etc/group
entry (on line 51). Thanks for your help! I've learned a lot about augeas
through this.
The old adage applies: garbage in, garbage out.
On Monday, February 17, 2014 10:18:46 AM UTC-6, Dominic Cleal wrote:
The fix that
I have some Windows systems that I need to configure a user's profile. The
user has to be logged into for the profile to be created. I came up with
the solution below but it seems kinda hacky. I assume there is a better way
to get the same effect without having a class inside a class? Is there
I am trying to get puppet to support HPUX better than it does now so it can
manage user accounts properly. I have already contributed changes to the
HPUX module to change passwords, but writing the rspec at the time was more
hack and guess than any real methodology. I did read the Learning
Just to expand a bit more here...
I am not talking about puppet .pp files, but the back-end Ruby source
files. I see a lot of things about puppet-lint, puppet-rspec and similar
tools, but from the best I can tell, these are for modules and
configuration of puppet operation and not puppet code
Just a bit more explanation...
When I was looking for references I was only finding puppet-lint and
rspec-puppet for testing manifests, but not finding anything for writing
the spec files to test module functionality or modifications to existing
modules such as the HPUX user management.
On 02/19/2014 02:03 AM, HPUX_PUPPET wrote:
Just a bit more explanation...
When I was looking for references I was only finding puppet-lint and
rspec-puppet for testing manifests, but not finding anything for
writing the spec files to test module functionality or modifications
to existing
Hi,
The Belgian Puppet User Group next Meetup is coming near.
We will have a round table where people will be talking about the how
and the why they have setup their puppet environment.
This event will take place on the 25th of February, and starts around 19:30
More information can be found
30 matches
Mail list logo
