Matthew, we are using the module in a limited proof of concept. You can see
where the defaults are set in
https://github.com/dj-wasabi/puppet-zabbix/blob/master/manifests/params.pp.
It's a little confusing after there. Where you're looking, those variables
are not used. They are set in two places
Possibly. If an agent has stdlib 1.0.0 already synced and the master has
1.0.2, there may be files added, removed, or changed. It does seem unlikely
that the node would have synced files on a first run, but it is possible
depending on who the agent was packaged and installed. Can you provide a
Thanks Francois, that works as well!
On Thu, Apr 14, 2016 at 4:20 AM, Francois Lafont <
francois.lafont.1...@gmail.com> wrote:
> Hello,
>
> Try this in your template:
>
> HWADDR is <%=
> scope.lookupvar('::networking')['interfaces']['eth0']['mac'] %>
>
> or this:
>
> HWADDR is <%=
>
Hi,
So it is normal to see files that are removed on the client the first time
it connects to the master with a config that uses stdlib?
On Thursday, April 14, 2016 at 5:23:39 PM UTC-4, Rob Nelson wrote:
>
> Yes, all modules in an environment would be pluginsynced.
>
>
> Rob Nelson
>
My bad, I gave a naive read through and didn't see that 2015->2016 is not
yet supported. Nothing to see here...
On Thursday, April 14, 2016, Brett Swift wrote:
> That's if you're moving from a PE 3.8 infrastructure as per the 2016.1.1
> docs though. Unless I'm reading that
That's if you're moving from a PE 3.8 infrastructure as per the 2016.1.1
docs though. Unless I'm reading that wrong.
>From a 2015.2.x to 2016 it suggests pe_repo if it's in a puppet enterprise
installation.
Did I miss something here?
On Thu, Apr 14, 2016 at 15:26 Rob Nelson
Wondering if anyone uses this module? I think it does a fantastic job but
did have a few questions around some of the defined types.
For instance, if you set manage resources on agent it exports the
following.
@@zabbix_host { $hostname:
ipaddress => $ipaddress,
use_ip => $use_ip,
port =>
Brett, I haven't used it, but rather than using an exec, Puppet recommends
using https://forge.puppet.com/puppetlabs/puppet_agent. I was actually just
reading docs at
https://docs.puppet.com/pe/2015.3/install_upgrading_agents.html#upgrade-agents-to-pe-20153-from-38x
because we're going to be doing
Yes, all modules in an environment would be pluginsynced.
Rob Nelson
rnels...@gmail.com
On Thu, Apr 14, 2016 at 3:48 PM, Ugo Bellavance wrote:
> Hi,
>
> Is it normal that when a new client connects to a master, stdlib is
> sync'd? Is that part of pluginsync?
>
> Thanks,
>
> --
Hey Justin,
Interesting stuff. I just deployed a consul cluster for the purpose of DNS
- and we haven't yet used the key/value store or the hiera backend.
This is less of a question on your gem, but more on your use case that I'm
interested in. When you say you automatically push values to
I'm trying to wrap my head around how you would use puppet to upgrade
agents. Maybe my assumptions on how this 'should' work are wrong.
I just migrated a puppet agent from a 2015.2.3 master to a 2016.1.1 master.
I signed the cert on the new master and no dice on the upgrade.
The
On Thu, Apr 14, 2016 at 07:34:34AM -0700, o...@soluto.com wrote:
> Hi,
>We need to manage many keys in Hiera. Since many people should be able to
>edit the keys and in order to avoid a complete mess I was thinking to work
>with many different files. The problem is that I don't know
Hi,
Is it normal that when a new client connects to a master, stdlib is sync'd?
Is that part of pluginsync?
Thanks,
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
It's up on nightlies, we've been building against the RCs.
http://nightlies.puppetlabs.com/puppet-agent-latest/repos/apt/xenial/pool/PC1/p/puppet-agent/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
Am Donnerstag, 14. April 2016 18:32:24 UTC+2 schrieb o...@soluto.com:
>
> Hi,
> We need to manage many keys in Hiera. Since many people should be able to
> edit the keys and in order to avoid a complete mess I was thinking to work
> with many different files. The problem is that I don't know
Hi,
We need to manage many keys in Hiera. Since many people should be able to
edit the keys and in order to avoid a complete mess I was thinking to work
with many different files. The problem is that I don't know how to make
Hiera read from new files. I don't want to add each file to the
Hi John,
Thank you for your help.
I have installed modules on master.
root@3puppet:/etc/puppetlabs/code/environments/osx/manifests# puppet module
list --environment osx
/etc/puppetlabs/code/environments/osx/modules
├── glarizza-osx_management (v0.1.0)
├── mosen-cups (v1.4.1)
├──
>
>
>1. It's usually a good idea to restart the master after making changes
>to your modules.
>
> John, not sure I agree with the need to restart, except in some very
specific cases. Is there a particular reason you advise for that?
Rob Nelson
rnels...@gmail.com
--
You received this
On Wednesday, April 13, 2016 at 1:11:56 PM UTC-5, Ari wrote:
>
> I'm looking to use puppet for OS X management.
>
> I have puppet server 4.4.1 running and one OS X device connected to it.
> I'm trying to deploy simple manifest with module wfarr/osx_defaults.
>
> In site.pp I have following
>
>
On Wednesday, April 13, 2016 at 1:23:48 PM UTC-5, Vince Skahan wrote:
>
> Still confused about the great version renumbering I guess, as well as
> version compatibility.
>
> We have an (admittedly old) linux-hosted 3.7.x server setup ('not'
> enabling future parser), and want to try to manage
On 13/04/16 03:31, Garrett Honeycutt wrote:
On 4/12/16 2:53 PM, Mike Reed wrote:
Hello all,
I've recently experienced some inconsistencies around referencing
Boolean values within a puppet manifest. We've written some custom
Boolean facts and we look to the true/false values within our
Hello,
Try this in your template:
HWADDR is <%= scope.lookupvar('::networking')['interfaces']['eth0']['mac'] %>
or this:
HWADDR is <%=
scope.lookupvar('::facts')['networking']['interfaces']['eth0']['mac'] %>
Now, with Puppet 4, facts are structured. You can use the global $::facts hash.
Dear James,
that was the solution, thank you!
I was buried in different books plus Puppet online documentation and didn't
realize that at least for this topic Puppet PE has a different behavior.
Will teach me a lesson...
Best regards and have a nice day,
Manuela Atoui
--
You received this
23 matches
Mail list logo