On 12-02-06 02:53 AM, jkm89 wrote:
This is my configuration:
service { $nscasvc:
ensure = stopped,
enable = false,
pattern = $nscapattern,
require = Class[nsca::install],
}
If I add hasstatus = true work
Hi,
So I assume you have two class definitions like this, either in site.pp
or in modules:
class class1 {
...
}
class class2 {
...
}
You can then use a node definition in site.pp and include the
necessary classes like this:
node 'nodesSD' {
include class1
}
node
Hi,
On 02/04/2012 04:16 PM, eldorado554 wrote:
Any idea why controllernode.vps.net is not importing the
controllernode module?
your basic ideas are sound, but there is a conceptual misunderstanding:
You cannot include module. Instead, you have to include a *class*
from the module.
E.g.
Hi,
I had set up the puppet agent / master configuration. I have written
the site.pp in manifests. The catalog is running on the client with
some time intervals. I have observed that it took some 5 - 15 min for
running that manifest.
For immediate testing I have run the puppet agent using --test
Puppet Master / Agent is set up now. I have started the puppet master
and also started the puppet agent.
Puppet master command: puppet master
Puppet agent: puppet agent --server server --waitforcert=60
I have signed the certificate from the server.
I have written the site.pp in master machine
Hi All,
Recently my company has started hosting more random services in public
clouds to reduce costs, etc, etc. We use Puppet on our in-house servers
to varying degrees, in-house meaning physically located in our offices
or in secure data centres. We want the same level of management for our
I am working on setting up a Puppet configuration where some of the
data is stored on a DRBD volume. The modules and vardir are stored on
the drbd volume. The puppet.conf files point to the drbd volume for
vardir. I created a cert for a VIP puppet-master using the puppetca --
create command
I had
On Sun, Feb 5, 2012 at 2:12 PM, eper e...@eper.net wrote:
I have been working on this for several hours now and still seems not
to be working. I am unsure if its a bug or I am doing something wrong.
[master]
node_terminus = exec
external_nodes = /usr/share/puppet-dashboard/bin/external_node
Hello,
I have been playing around with this today and have managed to get it working.
It appears if you are using puppet-dashboard and use external nodes you do not
need to call extlookup() to access to variable, it is just globally available.
Example:
root@puppet01:/etc/puppet#
There's a couple of ways to do this, but I usually take the easy
route: assign a local variable that has the global's value in the
related manifest. In this case, in centrifydc's init.pp just set
$domain=$::domain. This will appear as a local variable in the
template and you don't have to change
I have found that using Puppet 2.6.2 on my master and running Puppet
2.6.12 on my clients seems to have resolved this issue, while 2.7 was
failing.
Perhaps Puppet defined resources have different semantics in 2.7?
-Clay
On Thu, 12 Jan 2012, Clay B. wrote:
Hello all,
The key issue is, if I
- Original Message -
There's a couple of ways to do this, but I usually take the easy
route: assign a local variable that has the global's value in the
related manifest. In this case, in centrifydc's init.pp just set
$domain=$::domain. This will appear as a local variable in the
you can set the client to update it's catalog w/ this parameter
runinterval = 3600
On Feb 6, 2:06 am, sateesh bbalasate...@gmail.com wrote:
Hi,
I had set up the puppet agent / master configuration. I have written
the site.pp in manifests. The catalog is running on the client with
some
On Feb 2, 2012, at 9:38 PM, sateesh wrote:
Hi Cody,
Thanks for your response.
As Specified by you I understood this way. Please correct me if I am
wrong.
1) I will be having a ready new VM with Ubuntu installed. So I dont
need to execute the step puppet node create --image
For posterity's sake I've resolved this. What looks to have happened
is the certs were signed and the puppet master used its host name,
rather than the VIP/Hostname pair that would fail between the nodes. I
had to recreate the ca, and certs. Then on the hosts had to clear out
all their certs and
On Feb 6, 2012, at 11:10 AM, Clay B. wrote:
I have found that using Puppet 2.6.2 on my master and running Puppet 2.6.12
on my clients seems to have resolved this issue, while 2.7 was failing.
Perhaps Puppet defined resources have different semantics in 2.7?
I can't answer that but
I am using puppet 2.6.11 and want to pass parameter for implementing
sudo for mulitple users. So here is my simple code, which I would like
to pass to hiera to specify user name lookup. Appreciate any help,
thanks in advance.
class sudo( $name) {
#Class:: sudo
#
#
package { sudo: ensure =
On Mon, Feb 6, 2012 at 2:23 PM, Gmoney greg.caldwe...@gmail.com wrote:
I am using puppet 2.6.11 and want to pass parameter for implementing
sudo for mulitple users. So here is my simple code, which I would like
to pass to hiera to specify user name lookup. Appreciate any help,
thanks in
Puppet Labs Operations will be doing maintenance on our Redmine ticket
tracker, projects.puppetlabs.com, on Wednesday evening. You can expect
the site to be unavailable for a couple hours while we transition the
site to a new system. We will begin the move at around 1730 PST. We
apologize for
As part of the Redmine Migration, we will also be redirecting
old traffic to a new URL for a few days while DNS propagates. This new URL
is transitory and will be removed once requests stop coming to the old
system.
--
Zach Leslie :: Puppet Labs http://puppetlabs.com :: 503.208.9791
--
You
I guess I'll find out on my own soon enough, but can I at least pre-
populate the stored configs database using some of the tables within
the inventory service? Do the host facts tables in the inventory
database mimic what you end up creating with stored configs? It would
be great if I could just
The fact data is the same, but copying it into the StoreConfigs
database won't make any different to initial performance getting it
populated.
The catalog data is not duplicated between the two, and is only in
StoreConfigs. That is the heavier part of the data, and you can't do
anything other
On Mon, 6 Feb 2012, Craig White wrote:
On Feb 6, 2012, at 11:10 AM, Clay B. wrote:
I have found that using Puppet 2.6.2 on my master and running Puppet 2.6.12 on
my clients seems to have resolved this issue, while 2.7 was failing.
Perhaps Puppet defined resources have different semantics in
Hi psychobyte,
Thanks for your reply.
I have installed the puppet 2.7.10 using gem. I observed that the
client is not at all hitting the server to get the catalog. I have
waited for an hour whether the new catalog will execute on the client.
But it doesn't. So I tried run the command with
24 matches
Mail list logo
