http://info.puppetlabs.com/puppetconf-video-registration.html
use that to get notified when the video / audio + slides becomes available.
All sessions, except I think the lab ones, were recorded and should be
available in the near future (this week I think, but soon for sure)
On Monday, Octobe
On Wednesday, September 19, 2012 4:52:46 PM UTC-5, Jason_s wrote:
>
> Hi,
>
> It sounds like you would like to reduce some of the boilerplate code
> around your testing? I happened to notice this article you may find useful:
>
> http://puppetlabs.com/blog/the-next-generation-of-puppet-module-tes
I'm in the process of trying to get automated testing for my modules, using
puppet-lint, rspec-puppet, puppetlabs_spec_helper and Jenkins.
Are there any automated, or semi-automated ways to ensure coverage on my
tests? At the moment I am writing tests for existing modules, but I also
need to be
I recently install dashboard (1.2.10) on my puppet master (2.7.19 on Ubuntu
10.04 LTS).
I setup the filebucket/viewer as per
http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html#enabling-the-filebucket-viewer.
The md5sums are now clickable links, but when I click them I just get a
All,
I am currently trying to find a better way to do change management for my
puppet code.
Currently we have a single Master with two environments (test and prod).
Each module has it's own git repo, as does our node defs and our hiera data
repository.
The 'test' environment is used to contro
On Tuesday, August 28, 2012 5:32:56 PM UTC-5, Matthaus Litteken wrote:
>
> We are happy to announce Hiera-Puppet 1.0.0.
>
>
That is good news, however, doesn't this rely on hiera 1.0.0?
Any word on when that will be out of RC and a final release will be ready?
> It includes Puppet functions
And this is fixed now...
Just had to move my storeconfigs settings from [main] to [master]
On Monday, August 27, 2012 11:00:48 AM UTC-5, llowder wrote:
>
> I've got a single puppet master (2.7.19 + facter 1.6.11) controlling a
> number of nodes (2.7.17 + facter 1.6.8-10). On all
I've got a single puppet master (2.7.19 + facter 1.6.11) controlling a
number of nodes (2.7.17 + facter 1.6.8-10). On all of thse, fact absed
variables work as expected (such as $::operatingsystem and $::fqdn).
However, on my puppet master, when I run 'puppet agent --test' all fact
based variab
I've got facter 1.6.4 + puppet 2.7.14 on an Ubuntu 10.04 (LTS, 64bit)
machine.
This is my puppet master.
When I run puppet agent on this machine, I am getting some weird behavior.
Namely, fact based variables are all showing up as empty strings.
When I run facter -p I see all the facts I expe
On Monday, August 20, 2012 12:24:59 PM UTC-5, Jakov Sosic wrote:
>
> Hi.
>
> I'm getting lots of warning like this one from puppet-lint:
>
> WARNING: line 67 has more than 80 characters
>
> Now, I don't like warnings, so any idea how should I rewrite this line
> for example, to void the warni
On Friday, August 17, 2012 4:36:13 PM UTC-5, jcbollinger wrote:
>
>
>
>
> Does that help?
>
>
I don't know how much it will help the OP, but this has been a great help
to me. I've never quite been able to figure out the create_resource thing,
but I think I understand it now and what I was doi
Got this fixed, seems the new box had an old version of rake installed and
when I did gem install rake, it did not update the system bin.
On Friday, August 17, 2012 11:16:28 AM UTC-5, llowder wrote:
>
>
>
> On Friday, August 17, 2012 10:58:40 AM UTC-5, Justin Stoller wrote:
>
On Friday, August 17, 2012 11:43:43 AM UTC-5, Douglas wrote:
>
> >
> > If variables are defined in ::config, does that cause any issues with
> scope?
>
> So... I just gave this a try, and variables I defined in ::config have
> gone out of scope in ::install. *sigh*
>
>
Of course they would..
On Friday, August 17, 2012 10:58:40 AM UTC-5, Justin Stoller wrote:
>
>
> This is RSpec using an old way of initializing Rake.
> see:
> http://stackoverflow.com/questions/6085610/ruby-on-rails-and-rake-problems-uninitialized-constant-rakedsl
>
> for more discussion and possible solutions.
>
I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems:
*** LOCAL GEMS ***
diff-lcs (1.1.3)
hiera (0.3.0)
hiera-puppet (0.3.0)
metaclass (0.0.1)
mocha (0.12.1)
puppet-lint (0.1.13)
puppetlabs_spec_helper (0.2.0)
rake (0.9.2.2)
rspec (2.11.0)
rspec-core (2.11.1)
rspec-expectation
On Friday, August 17, 2012 8:26:54 AM UTC-5, Axel Bock wrote:
>
> Hi Paul,
>
> thanks for the answer. I'm on SLES 11 SP2, and the RPM says "
> puppet-2.6.17-0.3.1".
> so, no, it should be reasonably new (even if too old for my personal taste
> ;)
>
> SuSE uses puppetd in the /etc/init.d script
On Tuesday, August 14, 2012 4:14:47 PM UTC-5, Jeff McCune wrote:
>
> On Mon, Aug 13, 2012 at 12:36 PM, llowder
> > wrote:
>
>> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
>>
>
> You should avoid using the import st
If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
what is the best practice? Is it better to have one node def per file, or
group the node defs by class (ie, all app servers in one file or all web
servers in one file) or some other layout?
Also, is there a way to have the n
All,
I am running Puppet 2.7.17 on Ubuntu 10.04 (64bit, server).
In some of my modules/files I have some broken symlinks (that once deployed
to the nodes are not broken) in directories that I manage via puppet.
When I run puppet doc, it errors out complaining about the target of
whatever symli
On Friday, August 10, 2012 3:52:42 PM UTC-5, Douglas wrote:
>
> On Fri, Aug 10, 2012 at 1:42 PM, llowder >
> wrote:
> >
> >
> > On Friday, August 10, 2012 3:28:33 PM UTC-5, Douglas wrote:
> >>
> >> So...
> >>
> >> I w
On Friday, August 10, 2012 3:28:33 PM UTC-5, Douglas wrote:
>
> So...
>
> I was just reading the new puppet scoping documentation at
> http://docs.puppetlabs.com/guides/scope_and_puppet.html.
>
> I don't get it. If I have this...
>
> class web_server {
> include common
> include web
On Tuesday, August 7, 2012 4:59:01 AM UTC-5, Yaniv Fine wrote:
>
> Thank you for your answer .
> any reson why Facter::Util::Resolution.
> exec not working .
> i don't see either when running factor on the client or on the puppet
> server yaml file any record of fact named yaniv ?
>
>
Have you d
As an update, I changed my site.pp to only include this nodedef and a
default, still nothing, even after restarting my master.
On Monday, August 6, 2012 2:27:50 PM UTC-5, llowder wrote:
>
> I'm testing puppet 3, trying to get my existing modules ready.
>
> However, I've ra
I'm testing puppet 3, trying to get my existing modules ready.
However, I've ran into a problem where I can't get it to apply my node def
(tried using both hostname and FQDN in the nodedef) - and it's not even
picking up my default one.
Did support for "import 'nodes/*.pp'" type manifests/site.
101 - 124 of 124 matches
Mail list logo
