On 18 Jun 2014 14:10, wrote:
>
>
> Hi,
>
> I still can make the ENC work on my puppet server.
>
> General:
> Puppet server: 3.3.1 Puppet agent: 2.7.25
> The server run Passenger on Apache, so the puppetmaster run from apache
and not by himself.
>
> I have in /etc/puppet/puppet.conf :
> [master]
>
Hi John,
Not at this time. It was added to the Windows support so hopefully Linux
isn't far behind!
Thanks,
Trevor
On Wed, Jun 18, 2014 at 4:44 PM, Dennis Miller
wrote:
> Is this still not natively available within Puppet?
>
> On Wednesday, September 28, 2011 8:23:52 AM UTC-5, jcbollinger wr
Spencer,
Thanks for the info. I can get the kernel versions from my facter
information, I do think it will be easier to upgrade those my self.
Thanks,
Again.
On Wednesday, June 18, 2014 2:06:16 PM UTC-5, Spencer Krum wrote:
>
> You can run 'apt-cache policy puppet' on your trusty nodes. If you
Is this still not natively available within Puppet?
On Wednesday, September 28, 2011 8:23:52 AM UTC-5, jcbollinger wrote:
>
>
>
> On Sep 27, 6:23 pm, Corey Osman wrote:
> > How do I go about using puppet to set an ACL on a file. I did not see
> ACL support under the file type.
> >
> > Has an
On Wed, Jun 18, 2014 at 6:11 AM, jcbollinger
wrote:
>
>
> On Wednesday, June 18, 2014 12:14:21 AM UTC-5, Torsten Kleiber wrote:
>>
>>
>>
>> Am Dienstag, 17. Juni 2014 15:03:20 UTC+2 schrieb jcbollinger:
>>
>>> You mean you have set these in your puppet.conf or in your environment?
>>> If the form
You can run 'apt-cache policy puppet' on your trusty nodes. If you have the
puppetlabs apt repo enabled you should see many old versions available.
As a last resort, you could install from ruby gems.
As for kernel versioning, if you can express that in a package name you can
do it in puppet. Of c
Or my other thought, can I ensure the kernel version through puppet? That
would solve some issue as well.
Eric
On Wednesday, June 18, 2014 9:56:56 AM UTC-5, Eric Speake wrote:
>
> I am not able to update my current puppet master at this exact time and I
> need to see if I can backport puppet 3
Hi Erik,
Yes, we will keep the Squeeze repos up at apt.puppetlabs.com. Once Squeeze
is announced EOL, we will begin the process of removing support, but we
will be sure to let users know before that happens.
On Mon, Jun 16, 2014 at 7:20 AM, Erik Dalén
wrote:
> Debian has announced a long term
On Wednesday, June 18, 2014 8:10:38 AM UTC-5, shlo@gmail.com wrote:
>
>
> Hi,
>
> I still can make the ENC work on my puppet server.
>
> General:
> Puppet server: 3.3.1 Puppet agent: 2.7.25
>
That's a potential problem, but not likely the one you're currently
fighting. The master provides
you will need to run the puppet agent with --verbose (or --test which
implied verbose) to actually display the output in the terminal.
On 18 June 2014 12:23, Malintha Adikari wrote:
> Hi,
>
> I am executing a shell script in the puppet agent side. If I execute the
> same shell script in my loca
Hello everyone,
I am using Puppet dashboard and I properly configured it to show bucketed
files:
Changed (1)
File[puppetlabs.list] (/etc/puppet/modules/apt/manifests/source.pp:35)
PropertyMessagecontentcontent changed
'{md5}9495858ce6c5ed7d5bdb098f13709ae2' to
'{md5}f572dd8d58abbc84a3fe28ebc3
Christopher, Felix, I got the idea. Thank you very much!
--
Best regards,
Sergey Arlashin
On Jun 18, 2014, at 7:04 PM, Felix Frank
wrote:
> Wow, Christopher gave an exhaustive answer :-)
>
> I'll try and Keep It Simple.
>
> On 06/18/2014 04:22 PM, Sergey Arlashin wrote:
>> I do need to ha
Wow, Christopher gave an exhaustive answer :-)
I'll try and Keep It Simple.
On 06/18/2014 04:22 PM, Sergey Arlashin wrote:
> I do need to have 2 separate modules. I need the class 'testmode' to run
> before class 'test mod::nginxtest'. And I need to restart service 'nginx'
> when I change '/tmp
Also see these for interesting ideas:
http://www.craigdunn.org/2012/05/239/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/
In your place, this is how I would arrange what you want, because I often cram
configs togeth
I am not able to update my current puppet master at this exact time and I
need to see if I can backport puppet 3.1.1 to ubuntu 14.04. I have looked
at the backports but I am not finding any puppet backports at all for 14.04.
Thank you,
Eric
--
You received this message because you are subscr
Another thing, JFYI: I think somewhere you said you are new the Puppet, so
get into the habit to follow the style-guide before it's too late,
especially for the quote: you are mixing up the double and single quotes.
Look at here: http://docs.puppetlabs.com/guides/style_guide.html
--
You receiv
Hi
Running puppet on port 443 might be a good move if you expect your laptops
to be using cafe hotel airport style wifi
sslh might be a suitable tool to proxy for puppet I've not tried it though.
Regards
Neil
On 18 Jun 2014 14:30, "jcbollinger" wrote:
>
>
> On Tuesday, June 17, 2014 12:19:08
I tried also just /usr/share/puppet-dashboard/bin/external_node it act the
same way.
I add node:, I hope I did it in the right way because I did not find it in
the document - also not work.
If I'm not adding any 'node: ', It should work for all the nodes the same.
Am I right? or it must appear
I think, you cannot: The manifest is first compiled on Puppet Master and
then the catalog (complied manifests) is sent to the agent, where that
command actually runs. You can try this instead to see if you get any thing
better
command=> '/pathToShellScript/myScript.sh 2>&1',
>
> logoutput
Hm, ok.
But when I use 'subscribe' instead of 'notify'
class testmod {
package { 'nginx': ensure => installed }
service { 'nginx':
ensure=> running,
enable=> true,
require => Package['nginx'],
subscribe => File['/tmp/nginx.test']
}
}
class testmod::nginxtest {
Thanks Rakesh!
But, as you probably can guess, that didn't change a thing; still getting
the same error. I'm not sure if PuppetDB look in the DNS record (as opposed
to hosts file), in that case it never gonna work. Best!!
--
You received this message because you are subscribed to the Google Gr
On 18 June 2014 14:10, wrote:
>
> Hi,
>
> I still can make the ENC work on my puppet server.
>
> General:
> Puppet server: 3.3.1 Puppet agent: 2.7.25
> The server run Passenger on Apache, so the puppetmaster run from apache
> and not by himself.
>
> I have in /etc/puppet/puppet.conf :
> [master]
Hi,
On 06/18/2014 03:51 PM, Sergey Arlashin wrote:
> Could you please help me figure out why this is happening ? It seems there is
> nothing in test mod whih requires testmod::nginxtest .
actually yes, there is.
file { '/tmp/nginx.test':
ensure => present,
notify => Service['nginx'];
I mentioned Pentaho (albeit spelled incorrectly) as an example, as I saw it
mentioned a number of times online due to its open source community variant
and full feature set. Thanks for the links, it appears that slurping data
into Pentaho via puppetdb's REST API or otherwise is quite possible if
Hi,
I have a weird dependency cycle issue. This is just a test module which I
created while trying to solve this issue:
modules/testmod/manifests/init.pp:
class testmod {
package { 'nginx': ensure => installed }
service { 'nginx':
ensure => running,
enable => true,
require =
On Tuesday, June 17, 2014 12:19:08 PM UTC-5, jmp242 wrote:
>
> I probably don't really understand much about how puppet connects to the
> clients, but is there a big security risk about opening it up to the
> internet so laptops can get their configuration... If it's "safe enough"
> for any va
On Wednesday, June 18, 2014 12:14:21 AM UTC-5, Torsten Kleiber wrote:
>
>
>
> Am Dienstag, 17. Juni 2014 15:03:20 UTC+2 schrieb jcbollinger:
>
>> You mean you have set these in your puppet.conf or in your environment?
>> If the former then which one (file system path) and which section? Are
Hi,
I still can make the ENC work on my puppet server.
General:
Puppet server: 3.3.1 Puppet agent: 2.7.25
The server run Passenger on Apache, so the puppetmaster run from apache and
not by himself.
I have in /etc/puppet/puppet.conf :
[master]
mode_terminus = exec
external_nodes = /us
Hi Josh,
On Tuesday, June 17, 2014 6:35:19 PM UTC+2, Joshua Partlow wrote:
> Is that the issue you are seeing?
>
Sorry for the confustion but I had the deprecation warning from the package
type; allow_virtual parameter.
Fixed it yesterday, had disable_warnings in the wrong location.
Stefan
Hi,
I am executing a shell script in the puppet agent side. If I execute the
same shell script in my local machine it will print several log messages to
terminal. But when I execute it in the puppet agent it does not print any
log into the agent terminal. How can I print the logs of the shell s
Santanu,. can you please try and update your jetti.ini as follows
[jetty]
host = 0.0.0.0
port = 8080
*ssl-host = 0.0.0.0*
ssl-port = 8081
ssl-key = /etc/puppetdb/ssl/private.pem
ssl-cert = /etc/puppetdb/ssl/public.pem
ssl-ca-cert = /etc/puppetdb/ssl/ca.pem
Restart puppetdb and verify...
On Wed,
Thanks John, your opinion is really helpful :)
El martes, 17 de junio de 2014 15:30:53 UTC+2, jcbollinger escribió:
>
>
>
> On Tuesday, June 17, 2014 3:45:57 AM UTC-5, Félix Barbeira wrote:
>>
>> I always heard that serve large files over puppet is a bad practice.
>> But...I guess it depends of w
32 matches
Mail list logo
