Hi,
I want to pass the variables in puppet manifests from text file. The text
file contains a list of values in different lines. I want to pass these
values to the variables defined in the manifest.
Thanks & regards,
Ankita
--
You received this message because you are subscribed to the Googl
Hi,
if this is a crucial package for correct Facter operation, and it's not
a hard dependency in the RHEL7 package, then this may be a bug.
Would either of you look through the tickets at
https://tickets.puppetlabs.com/ and open a new one if this is not being
tracked already?
Thanks,
Felix
On 0
Ah, okay this makes more sense for me. So I know that I can stick this in
the same file with the node definitions, but there's got to be a better
place for it to go. Where would the "proper" place be for it to go?
Many thanks for your responses. They've been very helpful.
On Sun, Jun 22, 2014 at
Felix,
I think you may be right and I'm thinking about opening a ticket.
AFAIK net-tools will be deprecated in future RHEL versions, so a solution
is necessary.
Regards,
Bas
Op maandag 23 juni 2014 09:55:49 UTC+2 schreef Felix.Frank:
>
> Hi,
>
> if this is a crucial package for correct Facter
On Saturday, June 21, 2014 3:56:43 AM UTC+5:30, Brian Mathis wrote:
>
> Summary: Do not try to control processes directly with Puppet and instead
> properly integrate your service into your operating system.
>
> -
>
> It sounds like you are misunderstanding how Puppet integrates into the
>
Hi Brian Mathis,
I followed your instructions and it is working fine.Thanks a lot for your
information.
Regards,
Sathish.
On Saturday, June 21, 2014 3:56:43 AM UTC+5:30, Brian Mathis wrote:
>
> Summary: Do not try to control processes directly with Puppet and instead
> properly integrate your s
On 2014-23-06 9:04, Ankita kumari wrote:
Hi,
I want to pass the variables in puppet manifests from text file. The
text file contains a list of values in different lines. I want to pass
these values to the variables defined in the manifest.
.pp files are text files ;-)
In older puppet versions
On Friday, June 20, 2014 9:44:59 AM UTC-5, Salty Old Cowdawg wrote:
>
> Just after upgrading one of my legacy systems with a new puppet agent I
> noticed the agent wasn't running any more.
>
> Running the agent in test mode I see:
>
> Error: Could not create resources for managing Puppet's files
On Mon, Jun 23, 2014 at 9:24 AM, jcbollinger
wrote:
>
>
> On Friday, June 20, 2014 9:44:59 AM UTC-5, Salty Old Cowdawg wrote:
>>
>>
>> You'll have to judge for yourself whether the work (probably not too
> much) is worth it for this system.
>
>
>
Considering my timeframe for decomming the machine
Hello, sorry to bring this back.
I just have a question, did you just changed the path of /usr/bin/ruby or
did you did something else to make it work?
Thanks in advance,
X.
On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote:
>
> On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons > w
Hello There, have you found a solution for this?
I'll appreciate your help.
Regards,
X.
On Friday, 31 May 2013 09:04:12 UTC+2, Thomas Dahlberg wrote:
>
> I found the solution. Dashboard does not play well with ruby 1.9.3.
> I will try the rails3 branch and see if it works better.
>
> /Thomas
>
>
On Sunday, June 22, 2014 12:43:20 AM UTC-5, treydock wrote:
>
> I'm attempting to use puppetlabs-apache with all my classes defined via
> Foreman (1.5.1) with Puppet 3.4.3. Servers are all CentOS 6.5.
>
> With puppetlabs-apache-1.0.1 when I applied both the apache class and
> apache::mod::ssl
Hi All,
So this was working on a Puppet Enterprise 3.2 puppet master but when
testing on a 3.4 Puppet Master I'm getting the following failure 'undefined
method `[]' for nil:NilClass' . So I know that this is telling me it's
failed to retrieve a value, but I'm wondering why I might be failing t
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to
point to ruby1.8 and everything looks good now on the Dashboard!
Thanks! :)
On Monday, 23 June 2014 15:37:59 UTC+2, Ximena Cardinali wrote:
>
> Hello, sorry to bring this back.
>
> I just have a question, did you just changed
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to
point to ruby1.8 and everything looks good now on the Dashboard!
Thanks! :)
On Monday, 23 June 2014 15:45:06 UTC+2, Ximena Cardinali wrote:
>
> Hello There, have you found a solution for this?
>
> I'll appreciate your help.
>
First of all, let me thank you, John, for replying to this post and giving
a sense to the discussion.
At times I wonder if PuppetLabs' guys read the forum and, if they do, why
they don't express an opinion on these matters.
I might be obsessive about modules, but I think that it's here where we
On Friday, June 20, 2014 8:01:49 PM UTC+2, Trevor Vaughan wrote:
>
> +1 to everything that John has said.
>
> While many Forge modules are not useful to me out of the box, I have had
> good luck modifying them to meet my needs at any given time.
>
Well, in my very personal opinion, if someone t
Hi,
I think you (example42) hit the nail in the head in the "rethinking
modules part 1" with one tiny exception... but that error was multiplied
by x100 in the second part of your dissertation.
The exception I am talking about is the desirability to pass a template
as a parameter: I agree you sho
On Tue, Jun 17, 2014 at 3:55 PM, Jim Ficarra wrote:
> Hey Rob,
>
> Thanks for the response!
>
> Yes - chocolatey version 0.9.8.23 is installed on both servers (found via
> choco version). They both respond to choco /?. This is a customized
> version that has had the install path modified and th
On Monday, June 23, 2014 6:49:00 PM UTC+2, pablo.f...@cscs.ch wrote:
>
> Hi,
>
> I think you (example42) hit the nail in the head in the "rethinking
> modules part 1" with one tiny exception... but that error was multiplied
> by x100 in the second part of your dissertation.
>
> The exception
It was installed on our puppet master which I don't control, so I'm not
100% sure - however this issue has been identified and fixed. The issue
boiled down to the PSModulePath system environment variable. It was
missing a semicolon between the stock path
(%SystemRoot%\system32\WindowsPowerShell\v
Perhaps read about modules? if you specify a class name (apache,
apache::vhosts) that class is automatically loaded from the relevant module.
Just like putting stuff directly in node definitions has correctly gone out of
style, so has defining classes/defines outside of modules.
http://docs.pup
Well, so I didn't know if it was "good form" to modify modules to hold
site-specific configuration items.
I think part of my frustration is that I haven't been able to find a doc,
or maybe one doesn't exist, that shows what a decent "production" Puppet
environment might look like. I think it'd be
I think the good form these days is to create generic modules and keep the
site-specific data in hiera (not that I'm good at keeping up with fashion).
Once you've gone through the Learning Puppet series of docs you'll probably
have more context to the roles/profiles pattern and other links.
htt
On 6/23/2014 4:05 AM, Ben Ruset wrote:
Ah, okay this makes more sense for me. So I know that I can stick this
in the same file with the node definitions, but there's got to be a
better place for it to go. Where would the "proper" place be for it to go?
Many thanks for your responses. They've bee
It's actually: yum-config-manager repos --enable
rhel-7-server-optional-rpms
:-)
Cheers!
On Friday, June 13, 2014 8:51:21 PM UTC+2, Arkandel wrote:
>
> Answering my own question. :)
>
> libselinux-ruby seems to not be distributed with libselinux. However it's
> found in the server-optional
26 matches
Mail list logo
