Hi everyone,
Now that I am starting to move from a primarily Hiera/YAML data backend to
using Foreman smart parameters, I am encountering an issue that I'd like to
see if anyone has dealt with. In Hiera, I use RI Pienaar's module_data
module so that I can build a data structure in every module,
This gist has the debug output:
https://gist.github.com/touchdown/190fe8eca878b82fc71b
I realize that it came from running the postgresql setup in puppetdb
module. I am running both postgresql locally so i simply declare both
classes with default params.
On Monday, April 28, 2014 8:51:35 AM UTC
In the past I've worked around this by creating a stub version of
dmidecode. facter is happy.
On Monday, April 28, 2014 11:59:52 AM UTC-7, Matthaus Litteken wrote:
>
> This issue is being tracked at
> https://tickets.puppetlabs.com/browse/CPR-5. The core of the problem
> is that facter is not a
On 4/28/14, 5:06 PM, mike wrote:
> Hi everyone,
> I learning Hiera for my Puppet configuration but I've the error when i
> execute the node connection.
>
> []
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find data item apache_package
Hi everyone,
I learning Hiera for my Puppet configuration but I've the error when i
execute the node connection.
[]
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item apache_package in any Hiera data file and no
default suppli
Sorry, this is what happens when I'm too tired. I see all the pieces now.
The types module is using create_resources() as well as the hiera_hash()
function.
I'll read the collectors documentation again.
Any idea why R.I. Pienaar thinks that it's a bad idea to use the
create_resources() functio
Not ab augeas expert but IIRC what I did in a similar situation is force
puppet/augeas to point to only one file.
Try adding "context," "incl," and "lens" to your augeas definition, like
the example below. By specifying the lens, I think it helps speed up the
augeas type also. At least I read th
I think I get it now.
The types module is actually a wrapper for tying hiera hash data to the
three built in types, but this pattern could also be used with a defined
type perhaps?
Thanks,
Alex
On Monday, April 28, 2014 1:05:55 PM UTC-7, Alex Scoble wrote:
>
> Hi Garrett,
>
> Thanks for the r
Hi Garrett,
Thanks for the response. The module you posted does indeed help as it shows
how to deal with hashes of hiera data without using the create_resources()
function.
Thanks,
Alex
>
> Hi,
>
> The create_resources() function allows you to have a data driven design.
> This gives you th
I hope this is an appropriate place for this question; if not, any
redirection to a more appropriate place is appreciated.
So: I'm trying to set up puppet + augeas on an opensolaris system. There
are certain files I have that are under RCS version control--this is not
all my doing, so some of
On 4/28/14, 3:34 PM, Alex Scoble wrote:
> Hi All,
>
> I'm working on a module that builds KVM/libvirt hosts and populates them
> with predefined VMs.
>
> So far I have the module to where it can create any number of virtual
> nets, storage pools and volumes using virsh, but it isn't pretty.
>
>
By the way, if it's not clear, my ultimate goal is to automate everything
so that bare metal servers pxe boot to a razor server, get their CentOS
install ISO and kickstart from razor, get installed, boot up, get their
network interfaces and logical volumes set up, get all the necessary
libvirt
Hi All,
I'm working on a module that builds KVM/libvirt hosts and populates them
with predefined VMs.
So far I have the module to where it can create any number of virtual nets,
storage pools and volumes using virsh, but it isn't pretty.
I've read on various threads here that create_resources
This issue is being tracked at
https://tickets.puppetlabs.com/browse/CPR-5. The core of the problem
is that facter is not an all arch package. It depends on dmidecode,
which is not available for all architectures. Because of this, facter
is an arch dependent package and there is no all package for
2014-04-28 17:50 GMT+02:00 Ádám Sándor :
> Viewing the process tree doesn't show anything new, it doesn't look like
> puppet is forking any new processes. It's just using more and more memory
> and 94% of CPU. This happens even if I run the provisioning after everything
> is set up so it doesn't ev
Viewing the process tree doesn't show anything new, it doesn't look like
puppet is forking any new processes. It's just using more and more memory
and 94% of CPU. This happens even if I run the provisioning after
everything is set up so it doesn't even have to do much.
Something I left out from
To the build-czars at puppet labs: could you please include a "*_all.deb"
version of facter in your build cycle? It doesn't appear to have been
created since v 1.6.18.
My clients are almost exclusively ARM based and can't upgrade without this
being available.
Humbly yours, me.
--
You receiv
>>> I don't really know much about the internals of PuppetDB, so can anyone
>>> shed
>>> any light on the possible cause of these crashes, and what I can do to
>>> mitigate them?
>>
>> I'd be interested to see what is happening your postgresql.log when
>> this occurs. Connections must be closing fo
Thanks for the reply. It seems that the Killed message is coming from the
vserver manager (or whatever it's called, I don't know much about the
technology), because the process is using too much memory. Which is a
problem because it means that puppet is using more memory then the
application ac
On Sunday, April 27, 2014 9:38:52 AM UTC-5, Remi Ferrand wrote:
>
> Hi everyone,
>
> thanks all for your answers but i'm starting to think that there is way to
> pass puppet "undef" value from a rspec test...
> If anybody has the solution to fix this test suite (
> https://github.com/riton/puppe
On Sunday, April 27, 2014, Lito K wrote:
> Hi everyone,
> I have the following scenario:
> I have an app.war file that needs to be expanded in tomcat, this war file
> creates a new directory at /app/{data,config,profile}.
> I need to change a file in /app/config/server.properties after the war
>
Can you paste the full error in a gist (with surrounding content as
well) instead of just putting it in a subject line?
If you can run the failing component with --debug so we can see more
verbose output next to the error that might be also useful. If this
error is being logged by your master, you
Look at the creates => option, I use that to drop an initial /etc/my.cnf,
but then it can be modified and not regressed by puppet.
On Mon, Apr 28, 2014 at 3:41 AM, Paul Tötterman wrote:
> For files in user's home directories I would manage the skeleton files
>> using puppet and then when the use
> I'm using Puppet with PuppetDB running on the same machine, but with the
> Postgresql database on an external server. Several times a day, PuppetDB
> seems to crash with errors like the one below. Nodes are then unable to
> check in, although Puppet will restart its own PuppetDB service on its
>
Sorry, its your agents that need to be upgraded not your master. Are
they all running 3.4.3 or greater?
On Sat, Apr 26, 2014 at 7:08 PM, JonY wrote:
>
>
> On Saturday, April 26, 2014 11:05:50 AM UTC-7, JonY wrote:
>>
>> I think I'm past that version already:
>>
>> # rpm -qa | grep puppet
>> puppe
Hi everyone,
I have the following scenario:
I have an app.war file that needs to be expanded in tomcat, this war file
creates a new directory at /app/{data,config,profile}.
I need to change a file in /app/config/server.properties after the war
expansion.
I need to restart tomcat to refresh the co
Hi folks,
I'm using Puppet with PuppetDB running on the same machine, but with the
Postgresql database on an external server. Several times a day, PuppetDB
seems to crash with errors like the one below. Nodes are then unable to
check in, although Puppet will restart its own PuppetDB service on
Hi,
On 04/26/2014 07:41 PM, Schorschi Decker wrote:
>
> Actually looking at that page and other examples via Google is what
> suggested the 'test' directory should exist. There seems to be a quite
> a few examples of how to install razor that all point to the same step,
> that does not appear to
Hi,
this is really, really meta (http://xkcd.com/917/).
I'm a little cautious of building something like this:
http://thedailywtf.com/Articles/The_Enterprise_Rules_Engine.aspx
I'd have to play with your module though in order to get a feel about
wether it is rather useful or over the top.
One r
I actually just had a revelation and thought of a better way:
$dir = inline_template('<%=ENV["HOME"]%>') # again, just to make testing
> using puppet apply easier
> file { "$dir/foo":
> source => ["file://$dir/foo.local", 'file:///etc/motd'] # the latter
> would typically be a puppet:/// UR
>
> For files in user's home directories I would manage the skeleton files
> using puppet and then when the user account is created they'll be copied
> into their home directory. That obviously only works for new users though.
> It won't account for existing users or for updating the file if it
On 25/04/14 12:23, myself3...@googlemail.com wrote:
> Hi there,
>
> I am new to foreman and just installed version 1.2
I'd recommend using Foreman 1.4 or even 1.5 if you're doing a new
installation. 1.2 is a little old.
> Then I installed some puppet modules to my puppet environment production.
32 matches
Mail list logo
