or as part of
your release process. Thanks.
On Oct 20, 5:06 pm, Michael Stahnke wrote:
> On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass wrote:
> > Is this going to make it into the yum repo? Thanks.
>
> What is "this" in this context? Dashboard 1.2.2 is avail
Is this going to make it into the yum repo? Thanks.
On Oct 10, 2:33 pm, Michael Stahnke wrote:
> This is a maintenance release of Puppet Dashboard 1.2.2.
>
> This release is available for download
> at:http://downloads.puppetlabs.com/dashboard/
>
> We have included Debian and RPM packages as we
To be a little more explicit about what Nan said, if you use a
parameterized class, any parameters you passed into the class will
also be available in the template. The same things goes for a define.
On Oct 17, 5:58 pm, Matt Zagrabelny wrote:
> Hi,
>
> Is it possible to pass parameters to use in
I've been working on building the Fedora 15 rails 3 RPMs for EL6. I'd
be interested in doing that for EPEL, I'll have to look into how to
become a maintainer.
On Oct 17, 4:05 pm, Todd Zullinger wrote:
> robert.morti...@gmail.com wrote:
> > I am having no joy installing Puppet Server with MySQL s
Hi Matt,
How to accomplish what you describe is going to be highly dependent on
the site's security policy, since you are dealing with sensitive
information. I didn't want to put this info in the main git repo that
controls my puppet masters, since it is available to lots of people.
What I ended
While testing puppet 2.7, I found that one of my manifests broke
because of the following quoted string:
"http://$yumserver/repos/vmware-$esxversion-rhel6-64";
Everything in the resulting string after "vmware-" was blank. After
some experiments I found that puppet 2.7 allows dashes in variable
n
You just need to include a $ in front of those parameter variables:
define config_file($owner = named, $group = named, ...
On Oct 5, 12:19 pm, "liam.j.bennett" wrote:
> Can some explain to me how to fix the following warning:
>
> warning: Deprecation notice: must now include '$' in prototype
>
>
So I've just started testing these repos and I ran into problems.
First, many of the EL6 RPMs are not signed, so they fail to install
with my standard yum config. In the EL6 products repo, for example,
only 3 of 12 RPMs are signed. The other issue is that the new puppet
dashboard 1.2.1 package is
Michael, thanks very much for these packages, they are quite helpful.
Curious question - is there any coordination with tmz to push these
packages into EPEL?
On Sep 12, 5:36 pm, Michael Stahnke wrote:
> I've had a vision of having packages for Puppet, Dashboard,
> mcollective, facter, et al, avai
Hi folks, sorry about this unusual email but I wasn't sure where else
to send this.
I just attended PuppetConf 2011 in Portland. On the last day near the
end of the conference, I found a pair of sunglasses in the main
auditorium. I stowed them in my backpack intending to find out if
there was a
Peter, are you using run stages? Your cyclical reference is probably
related to the fact that every single file resource that installs a
root-owned file has an implicit dependency on the root user. If
you've got any root-owned files installed by stages that happen before
the stage where you decla
Peter, I'm not sure about your specific question but there is a much
easier way of doing what you are trying to do.
<%= hosts.join(',') %>
That will replace your entire example template. :)
On Sep 24, 2:33 pm, Peter Berghold wrote:
> I thought I read in some documentation somewhere that for ar
Sav,
Maybe I'm confused about what you are trying to do, but why not just
do "import nodes/*" from site.pp instead of using find commands? The
only catch is that if you add or remove a node, you have to do a
"touch" command on site.pp to get puppet to re-read the import
statement and pick up the
13 matches
Mail list logo
