>> I was just testing the host config file from puppetdb coupled with the
>> documentation on the beaker documentation.
>
> Those docs honestly look old, they are still mentioning blimpy which I
> effectively deprecated/superseded with the aws_sdk driver.
>
>> I was actually going to omit the erro
Hi there,
I'm pretty new to puppet and have a general question.
I will have multiple (vagrant) machines wich i want to manage via puppet.
The "problem" is that all the machines will have the same name because they
are development machines wich are run by different developers. Is it a
problem f
I did an rpm query and could find the .c file but not the .so file. In the
end I copied it from somewhere else and continued, but so many more
(different) problems after that, I decided it was taking too long
and switched to the enterprise version of puppet that sorts all that out.
Thanks for
El lunes, 6 de octubre de 2014 20:29:05 UTC-3, Henrik Lindberg escribió:
>
> On 2014-06-10 20:47, Ciro Iriarte wrote:
> >
> >
> > El lunes, 6 de octubre de 2014 10:52:05 UTC-3, jcbollinger escribió:
> >
> >
> >
> > On Sunday, October 5, 2014 5:55:55 PM UTC-5, Ciro Iriarte wrote:
> >
>
On Monday, October 6, 2014 6:14:39 AM UTC-5, Vincent Miszczak wrote:
>
> Hello,
> I need to export concat::fragment on some nodes and gather the results on
> some other.
>
> To create the export I do something like :
> @@concat::fragment{"/myfile-$fqdn":
>target=>"/myfile"
> }
>
> but on the
On Monday, October 6, 2014 1:47:31 PM UTC-5, Ciro Iriarte wrote:
> Trying this approach I get "Detail: undefined method `each_pair' for
> #" using this code:
>
>
> <% if (@ospfconfig.is_a?(Hash)) and (@ospfconfig.count > 0) -%>
> <% @ospfconfig.sort.each do |instance,instparam| -%>
> protocol
Is it possible to make a module simply not be applied at all if it
encounters an OS it does not support?
Currently doing a check for the OS and outputting a "fail" is standard
amongst modules but this ends the Puppet run for the client if it has a
module assigned that does this.
The use case i
Hey guys,
I kept getting this annoying warning in the output of my puppet runs:
Warning: The package type's allow_virtual parameter will be changing its
default value from false to true in a future release. If you do not want to
allow virtual packages, please explicitly set allow_virtual to fal
That's great Ken.
I'll have a look. My .fog file was correct but I was missing that
ec2.yaml.
I get the user experience thing, it'll evolve and I'll help if I can.
Would I be right to assume you built your images with packer?
Thanks!
On Tuesday, 7 October 2014 04:37:43 UTC-6, Ken
> That's great Ken.
>
> I'll have a look. My .fog file was correct but I was missing that
> ec2.yaml.
>
> I get the user experience thing, it'll evolve and I'll help if I can.
>
> Would I be right to assume you built your images with packer?
All of those images predate packer, but we're using pa
So I have the following puppet rule. Pasted below. The problem is,
sometimes, I see it looks like it is running the File before it sets the
variable $sendmail_file in the case statement above. The reason I believe
this, is because of the error message that it reports. Which is
Error Message:
er
Where appropriate, I enjoy using file_line to edit files from the
puppetlabs/stdlib module, but I would like to keep a copy of the file
before it gets changed by file_line. Is there a way to have file_line use
the filebucket in the same way files controlled with the 'file' type do?
--
You rece
Hi,
making modules into noop is a fairly dangerous design, because your
manifest can and will just silently fail.
If you really *need* to assign dysfunctional features to your nodes, let
your profiles module take care of sorting them out based on facts.
profile::cool_linux_only_app {
if $ker
(ok - terrribly unprofessional title.. I get it).
I'm trying to 'do the right thing' and move from the embedded DB to
Postgres. Following the instructions I figured I would dump out the
contents of the embedded DB and import this into Postgres.
So I start 'puppetdb export --outfile '.
Pour so
Hey JonY,
Sounds interesting. What version of PuppetDB are you using? Do you have
reports, facts, and catalogs, or only some of those? Can you paste your
config.ini?
Also can you give the output of
ps aux |grep java
top -n1
free
in a gist maybe?
Wyatt
On Tue, Oct 7, 2014 at 8:30 AM, Jon
On Tue, Oct 7, 2014 at 7:26 AM, Tim Dunphy wrote:
> Hey guys,
>
> I kept getting this annoying warning in the output of my puppet runs:
>
>
> Warning: The package type's allow_virtual parameter will be changing its
> default value from false to true in a future release. If you do not want to
> a
I have an EXEC command that has an onlyif condition. When I have my puppet
service running as the correct user account, all goes well.
When the puppet agent is running under an inadequately privileged account,
some operations fail silently.
During a maintenance action, another staff member tried
Hi,
I have a text file where i get all the java version.
*cat java.txt*
*/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/bin/java -version*
*/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java -version*
*/opt/oracle/agent12c/core/12.1.0.4.0/jdk/bin/java -version*
*/opt/oracle/agent12c
https://gist.github.com/ce60c590a0531c0b09cd.git
# rpm -qa | grep puppet
puppet-server-3.7.1-1.el6.noarch
puppetlabs-release-6-11.noarch
puppetdb-terminus-2.2.0-1.el6.noarch
puppet-3.7.1-1.el6.noarch
vim-puppet-2.7.20-1.el6.rf.noarch
puppetdb-2.2.0-1.el6.noarch
Am storing 30 days of data. Yes -
We're excited to announce the release of Puppet Strings 0.1.0! This is a
preliminary release of the new documentation module. Our goal is to get it
into the hands of users so that we can get feedback on what direction we
should take this. The long-term goal is to have this tool eventually
replace t
>
> What's the 2.2 error?
> Also FYI we're doing zero testing with ruby 2.2 at this time.
Hi Kaylo,
The error that I'm getting is this one:
err: Failed to apply catalog: Invalid parameter allow_virtual at
/etc/puppet/environments/production/modules/puppet/manifests/install.pp:5
And zero test
RHEL 6.5
Puppet 3.7.1
puppetlabs-stdlib-4.3.2
Local hardening guidelines say that /usr/local and /var/log/audit have to be
separate partitions.
OK, so I make "mount" resources.
Now the problem: The order of the mount points in /etc/fstab makes a
difference.
I had /usr/local before /usr, and a
On 10/07/2014 09:55 PM, Dan White wrote:
> |Local hardening guidelines say that /usr/local and /var/log/audit
> have to be separate partitions.
> OK, so I make "mount" resources.
>
> Now the problem: The order of the mount points in /etc/fstab makes a
> difference.
> I had /usr/local before /usr,
Nice. I'll look out for your packer project. I've been using it to build
our vagrant boxes, but haven't yet built any for vSphere or external cloud.
I'm getting this error:
ruby/2.1.0/gems/aws-sdk-1.42.0/lib/aws/core/resource.rb:238:in `rescue in
block in define_attribute_getter': unable to
Thanks Jony.
I've loaded up an embedded database to comparable capacity and while export
isn't quick, it's not nearly as slow as you're experiencing.
Fro your process list the PDB appears to be running with a max heap size
(Xmx) of 1024m. Perhaps increasing this could make a difference?
The exp
On 10/7/14 1:17 PM, Felix Frank wrote:
On 10/07/2014 09:55 PM, Dan White wrote:
|Local hardening guidelines say that /usr/local and /var/log/audit
have to be separate partitions.
OK, so I make "mount" resources.
Now the problem: The order of the mount points in /etc/fstab makes a
difference.
I
Running for 7 hours now. Has exported ~15-20% of the data.
I'm intrigued to see what I end up with.
On Tuesday, October 7, 2014 1:19:04 PM UTC-7, Wyatt Alt wrote:
>
> Thanks Jony.
>
> I've loaded up an embedded database to comparable capacity and while
> export isn't quick, it's not nearly as s
> Nice. I'll look out for your packer project. I've been using it to build
> our vagrant boxes, but haven't yet built any for vSphere or external cloud.
Its not my project, its a private project we have. So I can't speak
around if we'll release it or not - just to be clear :-).
> I'm getting th
Hmmm. I'm pretty sure the puppelabs_spec_helper gave me a beaker target
Brett
Sent from my iPhone
On Oct 7, 2014, at 15:15, Ken Barber wrote:
>> Nice. I'll look out for your packer project. I've been using it to build
>> our vagrant boxes, but haven't yet built any for vSphere or ext
Hi all,
We have a puppetmaster installation (CentOS, Puppet 3.4.3) in production,
and as the scope and complexity of our installation grows, the manifest
processing has been getting slower and slower. I looked into it today, and
realized that caching wasn't working. So I put some config option
>>> Using your sample project, if I include the puppetlabs_spec_helper in the
>>> Gemfile, it doesn't error but completes rather quickly saying there are no
>>> tests (obviously). But it doesn't bawk on any ec2 configuration.
>>
>> So puppetlabs_spec_helper assists with the unit testing side of t
The default.yaml is in the gist I supplied. I used the el6 and centos6 64 from
your sample project.
An Ami search on aws by the name or Ami ID didn't turn up any results which is
why I thought they were private.
I'll try building an Ami with packer.Are there any conventions that need
On Tue, Oct 7, 2014 at 12:31 PM, Tim Dunphy wrote:
> What's the 2.2 error?
>> Also FYI we're doing zero testing with ruby 2.2 at this time.
>
>
>
> Hi Kaylo,
>
> The error that I'm getting is this one:
>
> err: Failed to apply catalog: Invalid parameter allow_virtual at
> /etc/puppet/environment
>
> Hmm, my OS X 10.9.5 reports:
> ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]
> While I believe ruby 2.2 is still in preview:
> https://www.ruby-lang.org/en/news/2014/09/18/ruby-2-2-0-preview1-released/
> Kylo
Yeah it's interesting that Mac OS X includes a preview ver
First, congratulations this is awesome and will make a lot of people very
happy!
Second, typo in the README: puppet strings serever, that's one 'e' too many.
Third, is there an example module annotated with yard-style documentation
to give a people an idea of how to get this going? Some example
> On Oct 7, 2014, at 4:17 PM, Felix Frank
> wrote:
>
>> On 10/07/2014 09:55 PM, Dan White wrote:
>> Local hardening guidelines say that /usr/local and /var/log/audit have to be
>> separate partitions.
>> OK, so I make "mount" resources.
>>
>> Now the problem: The order of the mount points
Hi,
I created a example repository and README documentation around how to unit test
your site.pp file. Most puppet unit testing documents seem to only cover
module testing and I felt like site.pp was left out. I have not had a chance
to share a lot of my knowledge until recently and here it
On Tue, Oct 7, 2014 at 7:06 PM, Daniele Sluijters <
daniele.sluijt...@gmail.com> wrote:
> First, congratulations this is awesome and will make a lot of people very
> happy!
>
Thanks, that's great to hear!
>
> Second, typo in the README: puppet strings serever, that's one 'e' too
> many.
>
Quite
Hi Tim,
Some people are working around the first issue by doing a:
if verscmp($::puppetversion, 3.6.0) {
Package { allow_virtual => true,
}
You could do that, and possibly a comparison to the rubyversion fact as
well.
Thanks,
Spencer
On Tue, Oct 7, 2014 at 5:45 PM, Tim Dunphy wrote:
> H
Hi,
that depends on your manifest and if they need to talk to a puppet master
or you are just doing a puppet apply (masterless).
Have a look at the Vagrantfile docs on puppet provisioners and you may get
inspired. Also you can pass in 'puppet_node' names and facts at run time
(with a puppet maste
40 matches
Mail list logo
