Oh, so modules that claim to be non-puppet3-compatible from now on is
because they implemented things that are only supported in Puppet 4? It's
clearer in my head now. I'll try the modules I use under puppet 4 and see
which break. I'm pretty sure that my current puppet setup will not work as
On Wednesday, May 3, 2017 at 4:35:02 PM UTC-5, Lesley Kimmel wrote:
>
> I've [somewhat] recently started developing Puppet modules for use with
> Foreman[...]
>
I recently came across some modules on the Forge that got me considering
> using modules with defined types exposing their functional
Hey;
Thanks again; unfortunately, that's not it. volume_groups is set as a
parameter to the lvm class:
class lvm (
$package_ensure = 'installed',
$manage_pkg = undef,
* $volume_groups *
*= {},*) {
I tried it w/o the 's' anyways. While the error went away, I didn't get my
lv create
The mount resource has an "atboot" parameter. If set to true it will modify
/etc/fstab and ensure that it gets mounted every time at boot. I have
something similar for one of our manifests:
I create a logical volume, then a filesystem, then mount it. The mount
option ensures that it gets mounte
I'll give that try. I was retyping/copying/pasting from the link
directly, figuring the forge module handled that some how. I appreciate
the suggestion.
Thanks
Doug
On Thursday, May 4, 2017 at 9:53:18 AM UTC-5, Joshua Schaeffer wrote:
>
> You list volume_group*s* in Hiera (with an "s"):
>
>
Is there a question here? What specifically are you asking for?
On Monday, May 1, 2017 at 6:02:33 PM UTC-6, Samir Gahirwal wrote:
>
> Hi,
>
> I am new to puppet and writing very first puppet module. Please pardon me
> for asking basic question.
>
> I am trying to write a module to generate diff
You list volume_group*s* in Hiera (with an "s"):
---
lvm::volume_groups:
vg00:
createonly: true
physical_volumes:
/dev/sda2:
unless_vg: 'vg00'
logical_volumes:
audit:
size: 2G
You list volume_group (without an "s") in your manifest:
create_resources('lvm
Ho everyone,
I have a lot of difficulty on Puppet for writing my own module and I don't
succeed to understand how the module are made on Internet.
I need to develop a custom module for put ssh keys into the right file. My
ideas is to put an array with the SSH keys and write the key in the file
You should be able to roll Puppetboard back to an earlier version that
supports PuppetDB 2.x...
Glad I could help though...
Gav
On 4 May 2017 13:35, "Sans" wrote:
Thanks Gav! I see that now.
PuppetDB v3 is only compatible with Puppet v4, which I cannot upgrade to it
yet.
Some issue with newer
Thanks Gav! I see that now.
PuppetDB v3 is only compatible with Puppet v4, which I cannot upgrade to it
yet.
Some issue with newer version of puppetboard module, I suppose, which seems
require puppetDB v3
-San
On Thursday, May 4, 2017 at 11:11:38 AM UTC+1, Gavin Williams wrote:
>
> Sans
>
> I
Sans
I wouldn't be surprised if that version of the 'puppetdb' pkg has a
dependency on 'puppetagent', which will install Puppet 4.x.
See https://docs.puppet.com/puppetdb/#versions for more info on PuppetDB +
Puppet support...
So if you *really *want to use Puppet 3.x, you could try and install
Looks like Puppetforge puppetdb module is doing some thing under the hood.
With a vanilla installation, everything seems look right:
root@e115-s-pmaster-001:/# dpkg -l|egrep 'puppet((master|db){,1})[ -]'|awk
'{printf ("%-22s%s\n",$2,$3)}'
puppet3.8.7-1puppetlabs1
puppet-common
12 matches
Mail list logo
