I don't recommend using Puppet for anything to do with patching, even in
the distribution of the patches. (Actually, I'm not sure how Puppet would
be used to distribute patches even in principle.) Anyhow, sooner or later
you're going to want a tool that was actually designed for patch and
Hello there!
I'm running an AdHoc puppet master in my desktop. The class of the subject
exists and is running correctly. For some reason I intermittently receive
the error in the subject. Any Ideas? It was working fine until yesterday @
~14:00hs PST
*Here some more info:*
node's environment
For those following along at home, 0.5.rc1 has been pushed to rubygems and
can be installed with `gem install hiera-eyaml-gpg --pre` or `puppetserver
gem install hiera-eyaml-gpg --pre` :D
Thanks raphink!
-Hunter
On Mon, Feb 16, 2015 at 1:54 AM, Raphink raph...@gmail.com wrote:
For the
Problem solved with a
manage_config_file = false
Which mean the problem was indeed in the auto-generated my.cnf
:)
Le jeudi 12 mars 2015 02:57:52 UTC+1, Anthony Martinet a écrit :
Hi there,
I have the same issue here.
Still digging on how to make this work, so far when using
Error:
/Stage[main]/Our_unattended_upgrades/File[/etc/apt/apt.conf.d/20auto-upgrades]:
Could not evaluate: Could not retrieve file metadata for
puppet:///modules/our_unattended_upgrades/etc/apt/apt.conf.d/20auto-upgrades:
end of file reached
Wrapped exception:
end of file reached
Versions on the
On Wednesday, March 11, 2015 at 9:53:17 AM UTC-5, LinuxDan wrote:
Looking at developing a type/provider for RHSM.
Python API libraries exist, but not Ruby.
I found the RubyPython gem, but the idea of an imbeded Python interpreter
seems a bit scary.
That idea scares me, too.
Anyone
On Wednesday, March 11, 2015 at 10:02:08 PM UTC-5, Amos Shapira wrote:
On Thursday, 12 March 2015 00:39:53 UTC+11, jcbollinger wrote:
On Tuesday, March 10, 2015 at 10:30:48 PM UTC-5, Amos Shapira wrote:
Hi,
I'm running into the common issue of having to force an apt-get update
before
We've settled on a git repo per module, then using r10k (thinking about
moving to librarian-puppet) to pull modules from git onto our nodes.
This happens in the wrapper script that we run out of cron that also
executes the puppet apply.
The advantage here is that if you happen to break puppet,
I understand most of it, but why checkout as /etc/puppet_hash, and and not
simply as /etc/puppet, and just `git pull` when necessary?
I.e. What is the benefit of having to do clone from scratch on every run
(i.e. when something has changed)?
depesz
--
You received this message because you
On Wednesday, March 11, 2015 at 8:57:00 AM UTC-5, Christopher Wood wrote:
(Replying to two people in one email, hum.)
On Wed, Mar 11, 2015 at 06:01:39AM -0700, jcbollinger wrote:
On Tuesday, March 10, 2015 at 9:59:41 PM UTC-5, Bostjan Skufca wrote:
On Monday, 9 March 2015
The basic idea is this: you have a server to be configured using puppet. On
your machine, you have a git repository containing the puppet configuration,
plus some other scripts. The puppet configuration sets up /var/lib/git as the
home directory for user git, and a remote clone of your git
In my current scheme, I export the git repository, grab the puppet subdirectory
from the export, and move it to /etc/puppet_hash. I put it there instead of
/etc/puppet because I only want to update the files if there is a new commit.
To check this, I need to store the hash of the HEAD of the
While it's possible to do stuff like this in Puppet, this isn't really
configuration management you're doing; it's systems administration. If
your requirement is to have patches installed automatically, I would write
a 10 line shell script, and use puppet to install it as a cron job.
On
While it's possible to do stuff like this in Puppet, it's not really
configuration management that you're doing here; it's systems
administration. If your requirement is to have patches installed
automatically, I would write this as a 10 line shell script, and have
Puppet just take care of
On Thu, Mar 12, 2015 at 4:21 AM, James Green james.mk.gr...@gmail.com
wrote:
I was running puppet agent -t --noop repeatedly with this error.
Running again, this time omitting --noop, it succeeded. Not entirely clear
what this tells me...
On 12 March 2015 at 10:58, James Green
Thanks for the sanity check, John.
Next question: If I want to make a type/provider that depends on an external
script (Python in this case), does anyone know of a good example I can use as a
blueprint ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
Hi there,
I am going through this
tutorial:
http://projects.puppetlabs.com/projects/1/wiki/simplest_puppet_install_pattern
I am having trouble with Step two: Create a test manifests - specifially
the application of tests manifests with the noop flag
my current configuration is as follows:
Hi Greg,
This file, /etc/puppet/modules/transfer_contents/manifests/init.py, has a
file extension of .py. Puppet uses a file extension of .pp. Try
changing that and see if it resolves your issue.
On Thu, Mar 12, 2015 at 10:40 AM, Greg Heaphy heap...@gmail.com wrote:
Hi there,
I am going
Why more disk space use? There would still be one clone of the repo, it
just would be located in different place (not /etc/puppet_HASH, but
directly /etc/puppet).
I think i can see one benefit of doing it the way you did it - we have
guarantee that there will be no things in /etc/puppet that were
I don't have enough nodes to justify running my own patch repository, but
here is the manifest I use for patching our Debian-derived systems. First,
though, here is the facter called updates_already_running
Facter.add(:updates_already_running) do
confine :osfamily = Debian
setcode do
if
Hi All,
I am new to this group. I would like to call Puppet Node Classifier Rest
API from Java client. I couldn't find any document. Can someone please
provide steps or document.
I want to perform following tasks using java client.
Adding a class to a node group
Adding a child group
Deleting
If I understand your question, the reason I don't just export to /etc/puppet is
that the git repository contains files other than the puppet configuration, and
I prefer to keep those files out of the puppet directory.
Certainly one could clone the bare repository in /var/lib/git, and symlink
No; there would be two repositories on the server. The repository in
/var/lib/git is bare; recall that a bare git repository does not have a working
copy. It would be possible to make the server repository non-bare, but that's
generally a bad idea.
Charles
On Mar 12, 2015, at 3:35 PM,
I was running puppet agent -t --noop repeatedly with this error.
Running again, this time omitting --noop, it succeeded. Not entirely clear
what this tells me...
On 12 March 2015 at 10:58, James Green james.mk.gr...@gmail.com wrote:
Error:
Setting up percona server with puppet is a matter of changing the
package_name. Your package name however suggests you're trying to set up
galera cluster which is a very different beast altogether. For that, we
have created (and use) a galera module that works in conjunction with
Sure. I wasn't talking about what's in /var/lib/git.
In your approach there is bare in /var/lib/git/server, and checkout/clone
in /etc/puppet_HASH.
The situation I was asking about is where there is still bare in
/var/lib/git/server (or wherever I will decide to put it), and
checkout/clone in
I was able to install both packages using the local repository available on
the VM (/usr/src/forge/):
$ puppet module install /usr/src/forge/puppetlabs-stdlib-*.tar.gz
--ignore-dependencies
$ puppet module install /usr/src/forge/puppetlabs-concat-*.tar.gz
--ignore-dependencies
On Sunday, June
El 11/03/15 a las 14:26, Alessandro Franceschi escribió:
I agree with what you wrote.
Puppet is not the best tool to execute one-shot operations like patching
or deploying of applications.
It's good at maintaining the state of the resources of our systems, so
you can use it to configure what you
On 03/09/2015 05:59 PM, Sergiu Cornea wrote:
Hello guys,
I am trying to create a device files and I am not really sure if i'm
applying the right check.
exec { creates_random_file_for_${name}:
command = mknod -m 0444 ${dev_random} c 1 9,
path= '/usr/local/bin/:/bin/',
It does not currently have a keys_file_content parameter or anything, so
looks like no. You could use an additional file resource to manage that. A
PR to the ntp module to manage the keys would be nice too :)
-Hunter
On Tue, Mar 10, 2015 at 7:44 AM, Robert Poulson robpo...@gmail.com wrote:
It looks like the option is -install, not --install.
On Tue, Mar 10, 2015 at 12:28 PM, jdt jo.de.t...@gmail.com wrote:
Hello,
I'm trying to automate the installation of an HPOV agent on systems with
HP's oainstall.sh script.
When manually running the script with the options -install -agent
31 matches
Mail list logo
