Hi Stefan,
On Nov 19, 9:49 pm, Stefan Schulte
wrote:
> So you want to remove a package and make sure that the service is
> stopped before that. I can think of a few options:
>
> - remove the service resource: When you remove a package there should be
> a pre_exec or something that stops your s
After upgraded to puppet-dashboard 1.04, when I click links to check
information of nodes or groups , such as http://localhost:3001/nodes/22,
it return a "We're sorry, but something went wrong." to me. Checking
the log, i got something as follows:
ActionView::TemplateError (undefined method `
Hi.
Puppetmaster server:
#hostname -f
puppet.config.site.ru
# puppetmasterd --version
2.6.1
Puppetd server:
#hostname -f
serv1.kzn.site.ru
# puppetd --version
2.6.1
I try send request for registration from puppetd server:
puppetd --verbose --no-daemonize --server puppet.config.site.ru --
waitforc
hi all ,
priorly , i deployed puppet as..
/etc/puppet/
--/puppet.conf
--/modules (all modules here)
--/manifests
i want to use environment option to select module according to
environment given.
now to use environment option , changerd puppet.c
> I just wonder if those work ? (syntax below)
no.
~pete
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr..
Hi,
So I was quietly cursing the Puppet DSL for making otherwise simple things
difficult, such as merging two arrays [1], and I was even starting to wonder if
I should look at alternatives like Chef more closely.
But then I had an idea - maybe someone has written a Ruby DSL like Chef's which
plug
> Although reading the release notes page [4], it looks like I can't rely on
> cross-version interoperability at all, so it's starting to look like I'm going
> to have to deploy from source to get the same version everywhere :(
Or you might want to build your own packages and deploy them. Which is
hi ,
i want to use absolute path as a source of file
like
file { "/var/lib/conf/Request.xsd":
owner => 'root',
source => '/etc/buildmodules/build1/modules/tomcat/files/
Request.xsd' ,
}
but it give following error ...
err: //tomcat/File[/var/lib/conf/Request.xsd]: Failed to retrieve
On Nov 19, 12:25 pm, Rudy Gevaert wrote:
> I'm trying to get around the following issue. I want to make sure if
> a service is stopped. I'm trying to do this is solaris but I don't
> think this is OS specific.
[...]
> when the software is not installed it can not check:
> info: Service[sendm
Hi All,
We're trying to get a hudson build working for our puppet modules by using
manitest.
So far we've had good progress but right now we're stumped.
We have a set of manifest/template combinations where the
manifest code uses the hostname fact to pick a specific template tied to a
particular
On Mon, Nov 22, 2010 at 3:15 AM, Nick wrote:
> Hi,
>
> So I was quietly cursing the Puppet DSL for making otherwise simple things
> difficult, such as merging two arrays [1], and I was even starting to wonder
> if
> I should look at alternatives like Chef more closely.
>
> But then I had an idea
On Mon, Nov 22, 2010 at 5:12 AM, sanjiv.singh
wrote:
> hi ,
> i want to use absolute path as a source of file
>
> like
>
> file { "/var/lib/conf/Request.xsd":
> owner => 'root',
> source => '/etc/buildmodules/build1/modules/tomcat/files/
> Request.xsd' ,
> }
>
> but it give following error
On Nov 19, 11:33 am, James Louis wrote:
> That's good to know. I originally installed on OpenSuse and it set up the
> sysconfig file automagically. Now I'm working on CentOS and what I'm hearing
> is I don't need to set up a sysconfig file (which I already have).
Some RHEL/CentOS packages also
Nick wrote:
> RHEL/CentOS 5 has nothing at all in base, and only v22.4 in RPMForge
You want to use EPEL for puppet in RHEL/CentOS, as the RPMForge
packages are way out of date. That said, we've stuck with 0.25.5 for
now in EPEL. But I have 2.6.x builds in my own repository to aid in
testing on R
On 22/11/10 15:22, Nigel Kersten wrote:
> Are those your three target platforms? Debian Lenny, Ubuntu Lucid and
> RHEL/CentOS 5 ?
Approximately. I'm evaluating Puppet personally, using my own machines, which
are either Debian or Ubuntu. I have a Debian Etch machine I want to replace
with a Debia
On Sun, Nov 21, 2010 at 7:55 AM, Nick wrote:
> Hi,
>
> A problem I've run into during my first attempts at writing manifests, is
> knowing what possible facts are available, and for a given fact, what values
> my
> manifest might encounter.
>
> A classic one is the possible values of $operatingsy
Nick wrote:
> - is there any more info anywhere, or anything in the pipeline?
> - will it work with older clients?
There isn't really a huge amount more information - it's a pretty new
feature. We'd love to see some modules, examples, more feedback.
It should work fine with older clients.
>
On Nov 20, 1:53 pm, "russell.fulton" wrote:
> one question can you have more than one instance of a parameterised
> module? I am guessing the answer is no. I could not find an explicit
> answer in the docs.
I think you're asking about parameterized *classes*, as the Puppet
terminology goes. T
On Nov 22, 12:18 pm, Nan Liu wrote:
> On Sun, Nov 21, 2010 at 7:55 AM, Nick wrote:
> > A problem I've run into during my first attempts at writing manifests, is
> > knowing what possible facts are available, and for a given fact, what
> > values my
> > manifest might encounter.
[...]
> It is
On Nov 22, 2010, at 10:21 AM, James Turnbull wrote:
>> Although reading the release notes page [4], it looks like I can't rely on
>> cross-version interoperability at all, so it's starting to look like I'm
>> going
>> to have to deploy from source to get the same version everywhere :(
>
> This
All,
Trying to install puppet-2.6.3 on CentOS 5.4 and I get the following.
[r...@stsdev-pri ~]# gem install puppet-2.6.3
ERROR: http://rubygems.org/ does not appear to be a repository
ERROR: Error installing puppet-2.6.3:
puppet requires facter (>= 1.5.1, runtime)
Facter is installed:
[
I thought there were issues with ruby versions > than 1.8.6 on
centos.
On Nov 22, 1:11 pm, rjl wrote:
> All,
> Trying to install puppet-2.6.3 on CentOS 5.4 and I get the following.
>
> [r...@stsdev-pri ~]# gem install puppet-2.6.3
> ERROR: http://rubygems.org/does not appear to be a repository
>
rjl wrote:
> Ruby is installed:
> [r...@stsdev-pri ~]# ruby --version
> ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linux]
>
Puppet is not yet compatible with Ruby 1.9.x.
Regards
James Turnbull
--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571
--
You received this message bec
Firstly thank you Daniel for your response on the scope stuff in
templates -- I had read that doc and missed it.
I am still struggling with this and I suspect that there may well be a
better way of doing what I need so as the subject says I am going back
to basics. In this post I will try and abst
Hmmm. I haven't tried puppet yet but I did finally get it installed.
In uninstalled the facter rpm and then installed the facter 1.8 gem and
then the puppet 2.6.3 gem without any issues.
-Original Message-
From: James Turnbull
Organization: Puppet Labs
Reply-To:
Date: Mon, 22 Nov 2010 1
Over the last few weeks I have several times felt the need to test out
some small snippets of puppet code without having to have them in my
live system.
At the moment I am doing all my testing by fiddling with file on the
puppet master and then invoking puppet on one of the clients. There
must be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Just a quick warning, I've found that 2.6.0 is too buggy to be useful, but
> anything higher worked well for me.
you should always use the latest minor version of a major version.
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Li
hello,
- Original Message -
> Over the last few weeks I have several times felt the need to test out
> some small snippets of puppet code without having to have them in my
> live system.
I've blogged a number of techniques at
http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
russell.fulton wrote:
> Over the last few weeks I have several times felt the need to test out
> some small snippets of puppet code without having to have them in my
> live system.
>
> At the moment I am doing all my testing by fiddling with file on t
"russell.fulton" writes:
> Firstly thank you Daniel for your response on the scope stuff in templates
> -- I had read that doc and missed it.
No worries - happy to help. As an incidental aside, if you actually continue
the same thread by replying to a previous message my mail client highlights
> }
>
> define sensor () {
> $rules = generate("/usr/local/sbin/get-rules-for ${fqdn} ${name}")
> # ...and that emits a single string with the right data.
>
It looks as if one can not pass variables into generators to protect
us from ourselves
"Generators can only contain alphanumerics,
"russell.fulton" writes:
>> }
>>
>> define sensor () {
>> $rules = generate("/usr/local/sbin/get-rules-for ${fqdn} ${name}")
>> # ...and that emits a single string with the right data.
>>
>
> It looks as if one can not pass variables into generators to protect
> us from ourselves
>
> "Gen
32 matches
Mail list logo
