Hi,
I think you should be able to use the exported resource on both the remote
node, and the node that
exports it, by using collection both local and remote and overriding the
necessary attribute:
On host A:
@@host { $::hostname :
ensure = present,
ip = $secondary_ip,
}
Also on
[snip]
You will not be able to collect that resource on the node that exports it
(you would again -- and rightfully -- get a duplicate resource complaint),
but I think otherwise you should be ok.
The documentation for exported resources suggests otherwise:
Any node (including the node that
Hi,
you probably already tested this already, but how about:
onlyif = match *[spec = \${fs_dev}\] size == 0
Regards,
k
**
**
On Tue, Jul 30, 2013 at 3:54 PM, Sneha More snehamore...@gmail.com wrote:
Hi,
The solution which i have given you is nothing but the another form of
what you have
Hi,
[snip]
And given how puppet's variable scoping works, it makes most sense. But
this fully qualified class name syntax isn't present in the
documentation[1][2], so I'm wondering :
Is this the proper syntax?
Has this (or will this) become the best practice?
This behaviour, and the
[snip]
While it is easy to work around this by top-scoping the class, some form of
documented warning might prevent some hairpulling :)
Mostly for posterity, this behaviour is indeed considered buggy (a major
outstanding design issue) and is in fact documented:
*
Hi,
I bumped into the following this afternoon (on a 2.7.19 puppet master/agent
combo):
consider a class profile::tomcat in module profile with the following
content:
$ cat modules/profile/manifests/tomcat.pp
class profile::tomcat {
class { 'tomcat': }
notice('Class profile::tomcat in
Hi John,
I think the behavior you discovered is a natural and expected consequence
of Puppet's name scoping and resolution rules. The current namespace is
searched first for unqualified class names. Only if no matching class is
found there will other namespaces be considered.
The difference
Hi,
Issue:
1) I update my VERSION variable
2) the next puppet run and only updates the repo (no rpms are upgraded)
3) next puppet run updates the rpms.
There are no errors. but shouldn't my rpms update on the first run after
the variable change?
not sure if this causes it, but yum by
Hi,
On Thu, Aug 2, 2012 at 6:25 PM, Mike Reed mjohn.r...@gmail.com wrote:
Thank you all for the responses. I think the solution of scripting the
install and calling the script via puppet is an interesting thought.
Thanks as well for the suggested reading.
just my thoughts on this: if you
Hi,
I think you are hitting this issue:
https://projects.puppetlabs.com/issues/12127
Kind regards,
kristof
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from
Hi,
[snip]
node 'puppet-slave.test.net' {
include users::accounts
User | title=account |
}
Your virtual resource is not a user, but a define called
users::virtual::account.
So you need to realize it using:
Users::Virtual::Account | title == account |
Kind regards,
kristof
--
Hi,
[snip]
Very interesting that you should say that you created a Puppet master for
each environment ... it's the obvious way to accommodate the limits of RPM
packaging while retaining the ability to use Puppet in full agent mode.
Is this considered a best practice? What other
Hi,
[snip]
- Hack the RPM package names to include a version discriminator (e.g.
packageV1-1.0-noarch.rpm rather than package-1.0-noarch.rpm) to allow
them all to be installed on Puppet maste
This is a practice that is already used for the kernel, so it seems like a
legitimate way
[snip]
But that wouldn't work with puppet kick, right? I want to be able to have
a host reboot another host. :-)
That looks to me more like an orchestration issue, which is probably better
solved by a tool like mcollective, func, rundeck, ...
You are not changing state here, merely executing
Hi,
[snip]
Thanks. One question though. I'm not much of an Oracle expert, and I
guess this is more of an Oracle question, than a puppet one, but what
did you do to configure Oracle on the command line once it was
installed?
Oracle actually provides some stuff exactly for this. There is a
Hi,
[snip]
But the problem is that a certain module I include follows the principles of
Example42 's Puppet modules of splitting up resources in classes according
to the operating system.
[snip]
When I include this specific class in my developer-workstation module
below, the resource
[snip]
The hard part it turns out is getting some custom data into the SSL cert to
begin with. The CSR thats generated does not get generated with
'certdnsnames' embedded in it, thats done purely on the Signing side (aka,
your puppet ca). I had hoped I could set 'certdnsnames' on the client
[snip]
Below the relevant parts of my openssl.conf:
x509_extensions = usr_cert
[ usr_cert ]
basicConstraints= critical, CA:FALSE
keyUsage= digitalSignature, keyEncipherment
extendedKeyUsage= serverAuth, clientAuth, emailProtection
18 matches
Mail list logo
