Hallo!
paul matthews <[EMAIL PROTECTED]>:
>Like Matt I have been using "before=>" statements as opposed to "notify=>"
>to try and ensure dependency order. Could someone highlight the distinction
>as both seem to ensure a task is run and completed before the next step is
>called.
'before' and 'req
Simon,
Environment, as they are currently implemented, allow you to have different
definitions for the same classes per environment on the same puppetmaster.
What it looks like you are trying to do is have different puppetmasters for
each environment. You don't need environments to do that, just
Simon,
I'm not sure why you need to contact the server on a different port
for each environment. The master serves up a different configuration
(on the same port) just fine. What are you trying to accomplish?
--Paul
On Wed, Dec 10, 2008 at 6:53 PM, Simon Coggins <[EMAIL PROTECTED]> wrote:
>
> I
I read that as applying to the server which is fine for where it finds
it's modules and templates. I can see how only being able to change
the module and template paths on the client us useful.
Guess I will just do it manually via command line for the options I
want in each enveonment. Sham
In the documentation
(http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments)
you will see the following:
"Only certain parameters make sense to be configured per-environment,
and all of those parameters revolve around specifying what files to
use to compile a client's configuration.
Hi all,
I've been trying to change over to using environments now that I have
upgraded to 0.24.6. I have a puppet.conf file that looks like this:
---
[main]
environment = production
listen = true
runinterval = 1800
server = puppet.cqu.edu.au
report = true
factsync = t
Hi,
I've learned how to generate client certs on the master, and
distribute them to the client machine as part of the OS install
process, and added my learnings to the wiki,
see:
startup questions - Puppet Users | Google Groups
and
Certificates And Security - puppet - Trac
N
Paul,
'subscribe' and 'notify' are supersets of 'require' and 'before,'
respectively. While 'require' and 'before' simply insist that the
resource ordering occurs in a certain fashion, 'subscribe' and
'notify' make use of "events". An "event" occurs whenever a resource
changes, and some resources
Like Matt I have been using "before=>" statements as opposed to "notify=>"
to try and ensure dependency order. Could someone highlight the distinction
as both seem to ensure a task is run and completed before the next step is
called.
Thanks
Paul
2008/12/10 Paul Lathrop <[EMAIL PROTECTED]>
>
> Ma
Mat,
This should work (untested):
file { "/tmp/server_binary":
source => "puppet:///files/server_binary",
notify => Exec["stop-server"];
}
file { "/usr/local/sbin/server_binary":
source => "/tmp/server_binary",
require => Exec["stop-server"],
notify => Exec
On Thu, Dec 4, 2008 at 5:41 PM, Jeffrey Hulten <[EMAIL PROTECTED]> wrote:
>
> Is there a way, in a puppet config, to query the current nodes config
> elements and use them in a template? My specific case is a JBOSS
> configuration with multiple instances on one server installation. I
> have the s
As I understand it, refreshonly ensures the command will only run when a
dependent object is changed, hence only subscribe and notify trigger it, not
require. So I don't think either exec would be called in your manifest. I might
be missing something there though.
But regardless, I'm not sure
Thank you James
Sorry I was little busy to reply to you back
Thanks,
- AJay -
On Mon, Dec 1, 2008 at 5:53 PM, James Turnbull <[EMAIL PROTECTED]>wrote:
>
> [EMAIL PROTECTED] wrote:
> > Hi All,
> >
> > I want some important information for which I searched every where
> > and I'm not a
The problem seemed to be that I had separated puppet.conf and
puppetmasterd.conf. After fujin enlightened me, everything worked
just as it's supposed to.
Thanks!
On Dec 10, 12:43 am, Bill <[EMAIL PROTECTED]> wrote:
> I've been trying to migrate from webrick to a clustered mongrel
> implementati
I am reviewing puppet for suitability on a project that I'm working
on. In many regards, it looks perfect and I'm very pleased with the
overall feel thus far. For a proof-of-concept example, I've created a
manifest that ensures that the ntp package is installed on the client,
that it has the cor
I am reviewing puppet for suitability on a project that I'm working
on. In many regards, it looks perfect and I'm very pleased with the
overall feel thus far. For a proof-of-concept example, I've created a
manifest that ensures that the ntp package is installed on the client,
that it has the cor
Hi. I'm hoping that someone can help me with a simple example. We are
trying to use puppet to update a server binary to a group of machines.
Here's pseudocode for what I'm trying:
if (server_binary has changed) {
1) stop the old server
2) overwrite the old server binary by
Hi. I'm hoping that someone can help me with a simple example. We
are trying to use puppet to update a server binary to a group of
machines. Here's pseudocode for what I'm trying:
if (server_binary has changed) {
1) stop the old server
2) overwrite the old server binary by
I've been trying to migrate from webrick to a clustered mongrel
implementation. The problem I'm seeing is that puppetmasterd seems to
be insisting on trying to bind the servers on port 8140 even if I'm
explicitly instructing it not to.
([EMAIL PROTECTED]) conf.d > strace -o /tmp/suck puppetmaste
19 matches
Mail list logo
