[Puppet Users] Re: [voxpupuli] Do you have opinions on what module quality means?

[Trevor Vaughan]

uld be kept closer to what they are
>> describing via puppet-strings IMO.
>>
>> Speaking of the README.md, I think looking for select key sections would
>> be worthwhile. I think it should contain the following at a minimum:
>> - an H1 title at the top
>> - badges
>>   - that show the version released on the Forge and link to the module on
>> the Forge
>>   - build status
>>   - license (ideally via the shields.io badge that reads the license
>> file)
>> - an H2 Usage section
>> - an H2 Reference section that contains at least text referencing
>> REFERENCE.md
>> - an H2 Changelog section that at least contains text referring to
>> CHANGELOG.md
>>
>
> Sounds like a puppet-readme-lint tool to me! We can improve the spec
> <https://puppet.com/docs/puppet/latest/modules_documentation.html> and
> test for adherence to it. We could even consider integrating with
> https://errata-ai.github.io/vale-server/docs/style or some such.
>
>
> One other thing I wish there was a good way to flag on, maybe as part of
>> metadata-json-lint, is when author, summary, license, source, project_page,
>> and issues_url are not filled out in an expected format (or absent all
>> together).
>>
>
> We can absolutely improve metadata-lint to include whatever checks we
> think are useful. Probably a good first step would be a formal spec for
> that file 
>
> _._,_._,_
> --
> Groups.io Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#412) <https://groups.io/g/voxpupuli/message/412> | Reply
> To Group
> 
> | Reply To Sender
> 
> | Mute This Topic <https://groups.io/mt/86662086/1024671> | New Topic
> <https://groups.io/g/voxpupuli/post>
> Your Subscription <https://groups.io/g/voxpupuli/editsub/1024671> | Contact
> Group Owner  | Unsubscribe
> <https://groups.io/g/voxpupuli/leave/4249677/1024671/629153198/xyzzy> [
> tvaug...@onyxpoint.com]
> _._,_._,_
>
>

-- 
Trevor Vaughan
Vice President, Onyx Point
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXSk29BBbKiXJ%3DxBWK-4zXsmXw%3D5mGTQPDyghxOgHEEZA%40mail.gmail.com.

[Puppet Users] Re: [voxpupuli] Do you have opinions on what module quality means?

[Trevor Vaughan]

I've certainly got a few opinions.

I think that the following are mandatory:

   - rspec-puppet tests (that pass)
   - beaker, litmus, or test-kitchen tests (that pass)
   - Critical path test coverage that matches your supported operating
   systems (as much as is reasonable)
   - Documented parameters (generated docs with puppet-strings should pass)
   - A reasonable README.md
   - A generated REFERENCE.md
   - A useful Changelog (however you do it)
   - No embedded binaries
   - Use vendor provided packages as a default
   - A reasonable update period/response time to bugs
   - No telemetry/phone home capabilities
   - Fail closed/safe

I think that the following are nice to have:

   - Arrow alignment
   - Indentation
   - Muti-node tests (for externally-facing services)

I think that the following are largely pointless:

   - Line length checks
   - Trailing comma checks
   - Code coverage checks
  - Taking time to add tests for trivial non-critial-path items just
  makes it more difficult to refactor the module. Acceptance tests
should be
  used for functionality.

Trevor



On Thu, Oct 28, 2021 at 4:33 PM Ben Ford  wrote:

> Trick question, I know. Having strong opinions is part of why we do the
> work we do. So I'm hoping that many of you will help us out on this project.
>
> Some time ago, the Forge turned off the quality scores detail display
> because many of the warnings were confusing and frightening to less
> experienced Puppet users. And we didn't really have a good specification of
> what made quality code anyway. That's what I hope to improve on today, and
> we'd like to turn it back on with a better picture of each module's quality.
>
> Vox Pupuli has a meta-gem that defines a list of the puppet-lint checks
> <https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec>
> that they use for their definition of a quality Puppet module. I'd like the
> Forge and Vox Pupuli to be in alignment here, and this seems like the best
> place to start.
>
> Do you have a favorite list of puppet-lint checks you use? Do you think
> they'd be useful as an ecosystem standard? Can you support that opinion
> with a cogent argument for it? Suggest it as a pull request and let's have
> that conversation. Together as a community we can all come up with a solid
> starting point as a standard definition of module quality.
>
>
> https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins/blob/master/voxpupuli-puppet-lint-plugins.gemspec
>
> Thank you all for your help!
>
> --
> Ben Ford
> @binford2k
> Ecosystem Product Manager
> _._,_._,_
> --
> Groups.io Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#395) <https://groups.io/g/voxpupuli/message/395> | Reply
> To Group
> 
> | Reply To Sender
> 
> | Mute This Topic <https://groups.io/mt/86662086/1024671> | New Topic
> <https://groups.io/g/voxpupuli/post>
> Your Subscription <https://groups.io/g/voxpupuli/editsub/1024671> | Contact
> Group Owner  | Unsubscribe
> <https://groups.io/g/voxpupuli/leave/4249677/1024671/629153198/xyzzy> [
> tvaug...@onyxpoint.com]
> _._,_._,_
>
>

-- 
Trevor Vaughan
Vice President, Onyx Point
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV-6fcCAZAq5L5AQeqDs03-K_96d0Mx-HsHbAMjd3Qgjg%40mail.gmail.com.

Re: [Puppet Users] Where is source rpm for puppet6 open source rpm

[Trevor Vaughan]

Ah, you need the whole thing to be relocatable!

Yeah, that's much more difficult, even with a SRPM to be honest depending
on how the components are built.

I think that it's configurable in Vanagon so you can probably build the
container image, hop into it and dig around to see where you might have to
modify the /opt path.

Others on the mailing list might know more about specifics on that.

On Wed, Apr 22, 2020 at 3:54 PM hai wu  wrote:

> Thank you! Unfortunately that won't work for me. The issue I have is
> due to /opt is some NFS read-only mounts. I am wondering about how to
> get a new RPM created for puppet-agent6, so that it could be installed
> on some folder like /opt2 instead. Right now I could not install this
> rpm. The other workaround is to copy whole puppet folder to that NFS
> mount. Just thinking that modifying /opt if we have src rpm would be
> much easier..
>
> On Wed, Apr 22, 2020 at 12:43 PM Trevor Vaughan 
> wrote:
> >
> > This community hosted project contains dockerfiles that outline the
> steps required for building from source
> https://github.com/simp/releng-misc/tree/master/puppet_agent_build
> >
> > On Mon, Apr 20, 2020 at 2:22 PM Morgan Rhodes  wrote:
> >>
> >> Hi,
> >>
> >> We no longer provide source RPMs for puppet6 packages due to lack of
> support from the packaging tools we use.
> >>
> >> On Sat, Apr 18, 2020 at 1:28 PM hai wu  wrote:
> >>>
> >>> Where is source rpm for puppet6 open source rpms? I could not find
> them ..
> >>>
> >>> --
> >>> 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 email to puppet-users+unsubscr...@googlegroups.com.
> >>> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAJ1%3DnZdo%2BC_q4EcfwgKcg9SdkT3QeqpaSJNT5bA61tr9JCZyaQ%40mail.gmail.com
> .
> >>
> >>
> >>
> >> --
> >> Morgan Rhodes
> >> Release Engineering
> >> mor...@puppet.com
> >> she/her/hers
> >>
> >> --
> >> 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 email to puppet-users+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1o75DP2zZN%2BHdrSKfxoWsFAtiWX9Vh_RnWrG4TOw-YEA%40mail.gmail.com
> .
> >
> >
> >
> > --
> > Trevor Vaughan
> > Vice President, Onyx Point, Inc
> > (410) 541-6699 x788
> >
> > -- This account not approved for unencrypted proprietary information --
> >
> > --
> > 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 email to puppet-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUdmG2bxUKaOoNnG8EVTnyehWtChav5%2Bu5Yen8kdBjBhQ%40mail.gmail.com
> .
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAJ1%3DnZcOUOyUE0d_WaSyuncGw3_0Ft_rTqBo9o7DE%2BRtdH27vw%40mail.gmail.com
> .
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWJZmb3HipS84C4ZTO-viaWXY2m0SnYNeVAtcZwTkYPHw%40mail.gmail.com.

Re: [Puppet Users] Where is source rpm for puppet6 open source rpm

[Trevor Vaughan]

This community hosted project contains dockerfiles that outline the steps
required for building from source
https://github.com/simp/releng-misc/tree/master/puppet_agent_build

On Mon, Apr 20, 2020 at 2:22 PM Morgan Rhodes  wrote:

> Hi,
>
> We no longer provide source RPMs for puppet6 packages due to lack of
> support from the packaging tools we use.
>
> On Sat, Apr 18, 2020 at 1:28 PM hai wu  wrote:
>
>> Where is source rpm for puppet6 open source rpms? I could not find them ..
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CAJ1%3DnZdo%2BC_q4EcfwgKcg9SdkT3QeqpaSJNT5bA61tr9JCZyaQ%40mail.gmail.com
>> .
>>
>
>
> --
> Morgan Rhodes
> Release Engineering
> mor...@puppet.com
> she/her/hers
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1o75DP2zZN%2BHdrSKfxoWsFAtiWX9Vh_RnWrG4TOw-YEA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1o75DP2zZN%2BHdrSKfxoWsFAtiWX9Vh_RnWrG4TOw-YEA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUdmG2bxUKaOoNnG8EVTnyehWtChav5%2Bu5Yen8kdBjBhQ%40mail.gmail.com.

Re: [Puppet Users] Beaker - what’s your perspective?

[Trevor Vaughan]

Bram and Konrad,

I'm personally interested in your perspective on multi-node testing.

In my experience with our stack of around 100 modules, I've found that
single node testing is marginally better than spec testing in that it tells
you if a service actually starts. However, my project has found that
multi-node testing is the only way to know if most services (outside of
node-only services) actually function properly.

For instance, we found that perfectly valid rsyslog configurations would
cause the daemon to start and appear to be functioning properly but that
remote queueing, forwarding to multiple hosts, etc... was horribly broken.
This was only possible to troubleshoot with multi-node environments via
beaker (without writing something like beaker ourselves from scratch).

I understand that we're the minority but I think that it's a gap that has
significant real-world implications across the board.

Note, we do use InSpec for compliance testing and have actually integrated
it with Beaker in the simp-beaker-helpers gem.

Thanks,

Trevor

On Tue, Apr 21, 2020 at 2:51 PM Konrad Scherer 
wrote:

> On 4/21/20 3:33 AM, Bram Vogelaar wrote:
> > I too find it excruciating to use, I have described it in the past as
> having a rage inducing cli, and the lack of
> > documentation makes it hard to use. Which has driven me to use
> test-kitchen for doing puppet acceptance testing. (with
> > the added benefit of being able to use inspec profiles).
> > In my world view the uptake has been very small outside the vox
> pupuli and puppet supported modules because of this.
> > After Litmus was released i have never considered Beaker again for any
> real testing needs, since test-kitchen is very
> > very single node only by design.
>
> My experience was similar. I tried to figure out beaker but was unable to
> make progress due to the lack of documentation
> and examples (almost two years ago now). With test-kitchen and
> kitchen-puppet I was able to do my testing and it is my
> preferred runtime testing framework. I also found the integration with
> InSpec very useful.
>
> --
> Konrad Scherer, MTS, Linux Products Group, Wind River
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e3571a4a-036c-5cea-7ae7-c92e8c3d08eb%40windriver.com
> .
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWjv88hxUsxbudn0ZWVHRWmayuuGzy3OyMuBhd2PkBA1A%40mail.gmail.com.

Re: [Puppet Users] Beaker - what’s your perspective?

[Trevor Vaughan]

So, I chimed in over in Slack but wanted to go ahead and respond here with
a summary of what we've been talking about there so that it'll be preserved
for the future and searchable.

This is a summary of multiple views and anyone participating in that
discussion should feel free to correct my biased opinions in here (I like
Beaker). I have a presentation that I did on exactly what I use Beaker for
and why I like it from last year's conference at
https://www.youtube.com/watch?v=4iBEIMQkBCk. The associated repository can
be found at
https://github.com/trevor-vaughan/puppetize_2019_multi_node_beaker for
those that want a full working example.

Who Uses it (module count is just modules, not necessarily modules with
tests though the vast majority of the SIMP modules have tests):

   - Voxpupuli
  - 127 Forge Modules
  - The System Integrity Management Project
  - 106 Forge Modules
   - A handful of other community folks
  - I'd love to see a full analysis of all forge modules and what type
  of testing they use but I don't have time to dig into that right
now (Gene?)

The Pros:

   - Beaker generally works as it is for both single node and multi-node
   (my main use case) testing.
  - See the video as to why multi-node testing is important
  - It preserves the rspec syntax that makes the output of the tests
   easy to understand for non-technical folks as well as easy to trace for
   technical folks.
   - It has the ability to be extended relatively easily in Ruby
   - It works with most major cloud providers (and Vagrant)
   - It hasn't really taken a lot of care and feeding recently to keep it
   chugging along

The Cons:

   - It's not well documented (at all)
  - When the project was modularized a couple of years ago, the
  documentation was thrown to the four winds with each of the
modules and the
  care and feeding of the docs pretty much dried up.
   - The DSL is inconsistent. Some methods are 'on(host)' others are
   'host.thing()' which is pretty darn confusing
   - Since it hasn't had a ton of internal care and feeding, it hasn't kept
   up with all of the things that Bolt can do. On the other hand, it also
   seems to have solved some issues that are currently being faced by the next
   generation of proposed testing tech.


Thanks,

Trevor

On Fri, Apr 17, 2020 at 7:40 AM Gene Liverman 
wrote:

> Hi friends! I’m trying to better understand the community perspective on
> Beaker and its supplemental gems. I’m particularly interested in hearing
> your thoughts on the state of its maintenance and what, if anything, you’d
> like to see change in that regard. I’m looking for both positive and
> negative opinions and impressions.
> --
>
>
>
> Gene Liverman
> Sr. Site Reliability Engineer
> gene.liver...@puppet.com
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BmGaMcuF0OrPjjkSqJdb%2Bd_Nq9vSN0c3k8wP4L1v2SSZ-7Htw%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CA%2BmGaMcuF0OrPjjkSqJdb%2Bd_Nq9vSN0c3k8wP4L1v2SSZ-7Htw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCtGHEbo8ENO9Cd_RcAJBjKKHqg67OTpUDvUMoF69kaA%40mail.gmail.com.

[Puppet Users] Re: Building puppet-agent AIO from scratch on EL7 (partially working)

[Trevor Vaughan]

Finally got this working with the help of Morgan Rhodes at Puppet.

The final working version is currently at
https://github.com/trevor-vaughan/releng-misc/blob/puppet-agent-build/puppet_agent_build/Puppet_EL7_Build.dockerfile
Ref: abf6b72

On Tue, Sep 24, 2019 at 2:46 PM Trevor Vaughan 
wrote:

> As an update, the latest push to this works using a pre-built docker
> container.
>
> It looks like you need a stock ruby installation so I'm going to give that
> a go to see if I can go all the way from pure CentOS 7.
>
> On Mon, Sep 23, 2019 at 3:28 PM Trevor Vaughan 
> wrote:
>
>> Hi All,
>>
>> I thought that some of you might be interested in helping me figure out
>> what's wrong here.
>>
>> I've got a Dockerfile that I'm working on at
>> https://github.com/trevor-vaughan/releng-misc/blob/puppet-agent-build/puppet_agent_build/Puppet_EL7_Build.dockerfile
>> that can build the AIO, but not a functional AIO.
>>
>> You can, of course, see some of the madness in there that I had to do to
>> just make it work.
>>
>> Hopefully, if a few of us hit it with sticks, we'll be able to figure out
>> how to do it properly.
>>
>> Thanks,
>>
>> Trevor
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699 x788
>>
>> -- This account not approved for unencrypted proprietary information --
>>
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699 x788
>
> -- This account not approved for unencrypted proprietary information --
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWzWHbvQaMJyyusaO-DptXZchkThUy4VJ2AiokzvMzWxA%40mail.gmail.com.

[Puppet Users] Re: Building puppet-agent AIO from scratch on EL7 (partially working)

[Trevor Vaughan]

As an update, the latest push to this works using a pre-built docker
container.

It looks like you need a stock ruby installation so I'm going to give that
a go to see if I can go all the way from pure CentOS 7.

On Mon, Sep 23, 2019 at 3:28 PM Trevor Vaughan 
wrote:

> Hi All,
>
> I thought that some of you might be interested in helping me figure out
> what's wrong here.
>
> I've got a Dockerfile that I'm working on at
> https://github.com/trevor-vaughan/releng-misc/blob/puppet-agent-build/puppet_agent_build/Puppet_EL7_Build.dockerfile
> that can build the AIO, but not a functional AIO.
>
> You can, of course, see some of the madness in there that I had to do to
> just make it work.
>
> Hopefully, if a few of us hit it with sticks, we'll be able to figure out
> how to do it properly.
>
> Thanks,
>
> Trevor
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699 x788
>
> -- This account not approved for unencrypted proprietary information --
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUhSgSWp9uVZwy4eTZ-rFPQYP3LLOW79_ijdgkUkso1sw%40mail.gmail.com.

[Puppet Users] Building puppet-agent AIO from scratch on EL7 (partially working)

[Trevor Vaughan]

Hi All,

I thought that some of you might be interested in helping me figure out
what's wrong here.

I've got a Dockerfile that I'm working on at
https://github.com/trevor-vaughan/releng-misc/blob/puppet-agent-build/puppet_agent_build/Puppet_EL7_Build.dockerfile
that can build the AIO, but not a functional AIO.

You can, of course, see some of the madness in there that I had to do to
just make it work.

Hopefully, if a few of us hit it with sticks, we'll be able to figure out
how to do it properly.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUDYkUtYKSu%2B7ZwVxscz0Ewxz8oELu4VWOFo6w4-6Y%2Bww%40mail.gmail.com.

Re: [Puppet Users] How do you keep the forge modules you use up to date (and keep your sanity)

[Trevor Vaughan]

I agree with the approach proposed by Martin.

Forge for discovery, Git mirrors, pinning, and testing for daily use. This
also makes it really easy to mesh in with your own internal module
development and add privacy controls across the board without standing a
new service.

Trevor

On Wed, Jul 10, 2019 at 1:39 PM Martin Alfke  wrote:

> Hi,
>
> we never use the puppet module tool.
> Instead we mirror upstream modules on an internal git server (including
> tags) and reference module, git url and tag in a control-repository
> Puppetfile.
> When we want to upgrade modules we create a branch and veriffy that
> everything still works as expected.
> We sometimes even use the octocatalog-diff tool to verify catalogs build
> with old and new module versions.
>
> hth,
> Martin
>
>
> On Jul 9 2019, at 4:47 pm, Karsten Heymann 
> wrote:
>
> Am Di., 9. Juli 2019 um 10:12 Uhr schrieb Bart-Jan Vrielink
> :
>
> I share your pain.
>
>
> Thank you :)
>
> https://github.com/voxpupuli/ra10ke
> https://voxpupuli.org/plugins/#r10k
>
>
> Thank you for the links. I will check them out, maybe the make the
> upgrade task a bit easier.
>
> Best regards
> Karsten
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAL017hAj0-7R_VQUb9%2B4q%3D3eW27%2Bi185HsuNWTXXgLj%3DUen1dw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/29402CD0-6E43-4334-842E-791BF2FCA093%40getmailspring.com
> <https://groups.google.com/d/msgid/puppet-users/29402CD0-6E43-4334-842E-791BF2FCA093%40getmailspring.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW7F3XiFOz%3Demcpg%3Du7qsGeEaj2uoBzpVOqT1YhXLtAGw%40mail.gmail.com.

Re: [Puppet Users] Re: Pastebin like service for sharing Profiles?

[Trevor Vaughan]

The SIMP project came up with the idea of 'component profiles'. These are
profiles that are meant to be shared but that work best within a specific
ecosystem.

Though our naming is a little askew at the moment, we currently use
'simp_' as the component profile and '' as the component
module.

For example:

   - https://github.com/simp/pupmod-simp-rsyslog
   - https://github.com/simp/pupmod-simp-simp_rsyslog

The first is "just rsyslog" and the second is "rsyslog the SIMP way".

Profiles are generally part of frameworks and can be abstracted but, to do
so, have to be designed for abstraction.

Technically, our main 'simp' module at
https://github.com/simp/pupmod-simp-simp is *the* SIMP profile from which
all things spring and one of the main integration testing points.

Doing it this way means that we don't have to have alternate paths, just a
different module name similar to the '_p' suggestion above.

Trevor

On Mon, Jul 15, 2019 at 8:13 AM Rob Nelson  wrote:

> Hrm, I wonder how much this has to do with definitions of what a profile
> module is. To me, a profile module includes a lot of component modules and
> conditional logic and an occasional primitive (include apache, include a
> logrotate config, conditionally manage all cron jobs or not). What you're
> describing sounds a lot like component modules I incorporate into profiles
> with an "include ssh" or "include wordpress" statement, possibly
> accompanied by some hiera data (Firefox keeps a good list of ssh ciphers
> depending on your OS, for example,
> https://wiki.mozilla.org/Security/Server_Side_TLS). Sometimes I have let
> a profile get too large, at which point I have split it into a component
> module, and it's often tricky to find that line. Ultimately, for me, a
> profile is implementation-specific; a component is technology- or
> concept-specific and not implementation-specific.
>
> Of course, the forge is a great place to share component modules when
> possible (some of us aren't allowed to share stuff that starts internal,
> unfortunately), but not profiles. While, as Martin noted, profiles tend to
> be pretty specific to implementations and cannot be shared, there are
> certainly good or common patterns that would be useful to share (like the
> conditional management of cron jobs mentioned earlier), but short of
> treating profiles like component modules, I haven't found a good place to
> host them. That's an interesting possibility, to make at least some "base"
> profiles into a component module. I do think it might be more helpful as a
> reference project than as a module people include in their Puppetfile
> (there are bound to be conflicts and disagreements with any opinionated
> codebase that limits their usefulness), BUT that is still a worthwhile
> endeavor for those interested.
>
> Rob Nelson
>
>
> On Mon, Jul 15, 2019 at 5:38 AM comport3  wrote:
>
>> Thanks Martin, the PSIC repos are excellent - thanks!
>>
>> And Tim, the logic of having the p_ modules avoiding namespace collisions
>> also makes perfect sense at scale.
>>
>> I was thinking more of a searchable, more goal oriented view of sharing
>> Profiles that implement 1 or more technologies to form a "stack".
>>
>> Eg, 'Securing SSH', 'Achieving an A-Grade with NGiNX TLS on Qualys SSL
>> test, with maximum compatibility', 'WordPress/Magento/Drupal battle tested
>> hosting stacks', etc.
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/71988a6c-d0f4-4f04-a768-b3f4caf49bce%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/71988a6c-d0f4-4f04-a768-b3f4caf49bce%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAC76iT_90u%2BuCMbsetswR5apA%3DKFCi0UFQDK-jkO0iAiJa4K2g%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAC76iT_90u%2BuCMbsetswR5apA%3DKFCi0UFQDK-jkO0iAiJa4K2g%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Trevor Vaughan

Re: [Puppet Users] Puppet Gurus, Question

[Trevor Vaughan]

Thanks for the recommendation Nick!

We're in the general DC area and anyone should feel free to reach out to
us, or me directly if that's easier, if they need help.

We definitely know Puppet and maintain https://simp-project.com. No worries
if you don't want to dive into the project, we consult on all things Puppet
and are active in the community.

Thanks,

Trevor

On Fri, Oct 19, 2018 at 6:22 AM Nick Hasser  wrote:

> Have you tried https://www.onyxpoint.com/?
>
> On Thu, Oct 18, 2018 at 2:41 PM 
> wrote:
>
>> Puppet Gurus, I am looking for a person or contracting company to assist
>> my company in the Washington DC area for a Contract Puppet SME. Where is a
>> good place to look or post? Any help would be appreciated. The agencies
>> around here DONT specialize in it and I am fed a lot of BS. Any help would
>> be appreciated.
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/a3ff5af1-1580-4f4d-b419-9a5ee75fb8f9%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/a3ff5af1-1580-4f4d-b419-9a5ee75fb8f9%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAAmyyqqq20WAyM0XmaUZdrJGkq6xs0BzrU%2Bt4R%2BfjgoGZCWFKA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAAmyyqqq20WAyM0XmaUZdrJGkq6xs0BzrU%2Bt4R%2BfjgoGZCWFKA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVWF4Go50Mja40GyWWZcxYt39Y5BSkoE7VWEpXY-cgRUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Problems installing PuppetDB from source - the instructions don't actually work

[Trevor Vaughan]

Hi Simon,

While this isn't directly related to your question, you might want to pile
onto this ticket to ensure that the community can build all of the package
artifacts.

https://tickets.puppetlabs.com/browse/LTH-156

Thanks,

Trevor

On Wed, Jun 13, 2018 at 8:01 PM Simon Tideswell 
wrote:

> See also
> https://tickets.puppetlabs.com/projects/PDB/issues/PDB-3938?filter=allissues
> .
>
>
> Hello
>
>
> The instructions here
> https://puppet.com/docs/puppetdb/5.2/install_from_source.html don't
> actually work! I'm doing this on Ubuntu 18 (Bionic). I've installed *lein*
> from the Ubuntu 18 packages rather than pulling it down from github (in
> case that is relevant).
>
>
> When performing this step ...
>
>
> *lein with-profile ezbake ezbake stage*
>
>
> I get the response (after some time) of ...
>
>
> *"Could not transfer metadata
> puppetlabs:puppetdb:5.3.0-SNAPSHOT/maven-metadata.xml from/to snapshots
> (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/
> <https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/>):
> Connect to artifactory.delivery.puppetlabs.net:443
> <http://artifactory.delivery.puppetlabs.net:443>
> [artifactory.delivery.puppetlabs.net/192.69.65.54
> <http://artifactory.delivery.puppetlabs.net/192.69.65.54>] failed:
> Connection timed out (Connection timed out)*
> *Failed to retrieve remote metadata
> puppetlabs:puppetdb:5.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer
> metadata puppetlabs:puppetdb:5.3.0-SNAPSHOT/maven-metadata.xml from/to
> snapshots
> (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/
> <https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/>):
> Connect to artifactory.delivery.puppetlabs.net:443
> <http://artifactory.delivery.puppetlabs.net:443>
> [artifactory.delivery.puppetlabs.net/192.69.65.54
> <http://artifactory.delivery.puppetlabs.net/192.69.65.54>] failed:
> Connection timed out (Connection timed out)*
> *Error encountered performing task 'ezbake' with profile(s): 'ezbake'*
> *Failed to retrieve remote metadata
> puppetlabs:puppetdb:5.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer
> metadata puppetlabs:puppetdb:5.3.0-SNAPSHOT/maven-metadata.xml from/to
> snapshots
> (https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/
> <https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/>):
> Connect to artifactory.delivery.puppetlabs.net:443
> <http://artifactory.delivery.puppetlabs.net:443>
> [artifactory.delivery.puppetlabs.net/192.69.65.54
> <http://artifactory.delivery.puppetlabs.net/192.69.65.54>] failed:
> Connection timed out (Connection timed out)"*
>
>
> Indeed the output is correct, *https://artifactory.delivery.puppetlabs.net
> <https://artifactory.delivery.puppetlabs.net>*, is inaccessible from any
> of the networks I've tried, and has been so for a number of days.
>
>
> Are there instructions that will work for Joe Average anywhere, i.e.
> someone who does not have access to that host and who isn't a Java *maven*
> (seems more appropriate than the word *guru* in this instance)? On Ubuntu
> 16 the OS distributor provides a pre-rolled package for puppetdb. Perhaps
> Canonical are unable to provide a package on Ubuntu 18 for PuppetDB for
> similar reasons to me (namely inaccessible sources)?
>
>
> Thanks, Simon.
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b20aa70d-9663-49d2-b5ad-dfe09966eb04%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/b20aa70d-9663-49d2-b5ad-dfe09966eb04%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXyCF%3D91wz3GT_KC6-E-tPtSoXvDNvxKLNmgzJMwvRVkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How can one communicate the $confdir to the catalog builder?

[Trevor Vaughan]

Hey John,

We've tested it all the way through a running Puppet 5 from upstream at
this point.

Feedback is most welcome!

Trevor

On Mon, Apr 16, 2018 at 9:31 AM, jcbollinger <john.bollin...@stjude.org>
wrote:

>
>
> On Sunday, April 15, 2018 at 9:11:48 PM UTC-5, Trevor Vaughan wrote:
>>
>> Hey John,
>>
>> We added this to 'simplib' a while ago. We named it
>> 'simp_puppet_settings' so we didn't get name smashed whenever Puppet Inc
>> decides to incorporate it.
>>
>> https://github.com/simp/pupmod-simp-simplib/blob/master/lib/
>> facter/simp_puppet_settings.rb
>>
>>
> That looks great, thanks!
>
> And it works with Facter 3?  I guess I'll find out.
>
>
> John
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/0b139940-edbc-4f37-8b8a-1dc5fbf88ed9%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/0b139940-edbc-4f37-8b8a-1dc5fbf88ed9%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVkiz1Z-G8Va%2B2Kig1mqXdtb8cbCgVfSK0evbGaJrZKCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How can one communicate the $confdir to the catalog builder?

[Trevor Vaughan]

Hey John,

We added this to 'simplib' a while ago. We named it 'simp_puppet_settings'
so we didn't get name smashed whenever Puppet Inc decides to incorporate it.

https://github.com/simp/pupmod-simp-simplib/blob/master/lib/facter/simp_puppet_settings.rb

Thanks,

Trevor

On Fri, Apr 13, 2018 at 5:04 AM, Henrik Lindberg <henrik.lindb...@puppet.com
> wrote:

> On 12/04/18 14:58, jcbollinger wrote:
>
>>
>>
>> On Wednesday, April 11, 2018 at 11:28:12 AM UTC-5, Henrik Lindberg wrote:
>>
>> On 11/04/18 18:21, jcbollinger wrote:
>>  > I'm writing a module for Puppet self-management, or at least I
>> think I
>>  > am.  I was surprised to not find very much along those lines on the
>>  > Forge, and maybe I should take that as a bad sign, but I want to
>> explore
>>  > it at least a little bit.  Maybe I just didn't find the right
>> search
>>  > terms -- searching there for "puppet" is not very useful.
>>  >
>>  > Anyway, I've run into a snag with a threshold issue: how to find
>> the
>>  > config file(s) to manage in the first place.  I know where Puppet
>> stores
>>  > its config files by default, for various versions of Puppet and for
>>  > various operational contexts, but with the existence of the
>> --confdir
>>  > option that can be specified on a per-run basis, it is not safe to
>>  > assume that the config files that informed the current Puppet run
>> is in
>>  > the default location (and those are the ones I want to manage).
>>  In any
>>  > case, I'm lazy, so I'd rather get Puppet to tell me what it already
>>  > knows than try to recompute it.
>>  >
>>  > But there does not seem to be a standard fact that communicates
>> this
>>  > information (at least, 'puppet facts' does not print one), and
>> I'm not
>>  > seeing any appealing ways to extract the necessary information
>> from a
>>  > custom fact's runtime context.  I do see at least one nasty,
>> tricksome,
>>  > system-dependent way, but I'm more likely to chuck the whole idea
>> than
>>  > go there.  Am I missing some clean way to write a custom fact for
>> this
>>  > purpose?  Or does someone have an alternative to suggest?
>>  >
>>
>> Have you read the documentation regarding $settings ?
>> https://puppet.com/docs/puppet/5.5/lang_facts_and_builtin_
>> vars.html#puppet-master-variables
>> <https://puppet.com/docs/puppet/5.5/lang_facts_and_builtin_
>> vars.html#puppet-master-variables>
>>
>>
>> - henrik
>>
>>
>>
>> Thanks, Henrik, I'm not sure I had read those in detail, since they come
>> under the heading of variables set by the master, and the whole problem is
>> that the master doesn't have the wanted information.  Still, having now
>> read them, I find that the documentation seems to agree with my
>> expectations.  In particular:
>>
>> Note that, other than $environment and $clientnoop, the agent node’s
>> settings are not available in manifests. If you wish to expose them
>> to the master in this version of Puppet, you will have to create a
>> custom fact.
>>
>>
>> Creating a custom fact to report on the agent's /dynamic/ $confdir
>> setting, as recommended by those docs, is precisely what I would like to
>> do.  What I'm struggling with is how the fact implementation can determine
>> the value for such a fact, inasmuch as the value I want is a property of
>> the puppet (agent) process on whose behalf Facter is computing facts.
>>
>>
> I recall now that we have a ticket with a request to make agent settings
> available on the master side. No progress on that for quite some time
> though. Not sure if ticket is still open or if it was closed in the last
> big triage. I assume it could be implemented as sending all of the settings
> as one fact. Or - indeed as you plan, just the actual setting you are
> interested in.
>
> - henrik
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/puppet-users/paprm7%24t6

[Puppet Users] Re: [Puppet-dev] Ticket Backlog triages

[Trevor Vaughan]

Jira is making me feel so loved.

On Mon, May 15, 2017 at 1:27 PM, Branan Riley <bra...@puppet.com> wrote:

> Hi All,
>
> We're starting this triage process today, and it will last through
> Wednesday.
>
> On Thu, Mar 23, 2017 at 3:55 PM Eric Sorenson <e...@puppet.com> wrote:
>
>> Hi All – we're trying to get on top of the backlogs of Jira tickets.
>> Those of you who have been around for a while might remember this was the
>> original purpose of the "Triage-A-Thon" events, when we parcelled out
>> batches of Redmine tickets for categorization, clean-up, and
>> prioritization. (Hi, @kartar!)
>>
>> I wanted to let everyone know that this activity is going on, so if you
>> see updates on long-dormant Jira tickets it doesn't come as a surprise.
>> Although the commentary as we're dispositioning the tickets is boilerplate
>> copy-pasta, these are not automatic mass-closures. Teams are going through
>> the tickets in batches and spending some time on each one. If you get mail
>> about a ticket that you feel is dispositioned incorrectly (such as "Cannot
>> reproduce", when you can provide a repro case), please re-open them.
>>
>> Additionally, if you're interested in helping out, the query we're
>> working through is publicly available here:
>> https://tickets.puppetlabs.com/issues/?filter=25600#
>>
>> The workflow and response text for triaging tickets is available here:
>> https://docs.puppet.com/community/puppet_projects_
>> workflow.html#workflow-for-bugs
>>
>> The benefit at the end of all of this will be that we will be able to
>> provide much better response time for new issues as they come in.
>>
>> Eric Sorenson - e...@puppet.com
>> director of product, ecosystem and platform
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-dev/B4C79B78-F85E-42E9-A0D9-5830D4640843%40puppet.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Regards,
>
> Branan Riley
> Senior Sofware Engineer, Puppet inc.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-dev/CADWDnr%3D%3DoCurj29EBFRVQzuYZDyxV20y4e-
> GfKiBEOubp%3DYLVg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CADWDnr%3D%3DoCurj29EBFRVQzuYZDyxV20y4e-GfKiBEOubp%3DYLVg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUHJoBMHs8rf%2BQFUq0U92NwVZr3G2AjH7kPhk2YprsChQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-firewall rspec

[Trevor Vaughan]

affic from
> 10.64.0.0/25") }
> end
>   end
> end
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/2d1c3d33-4586-4f2d-bb53-265d45305058%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/2d1c3d33-4586-4f2d-bb53-265d45305058%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUf23AuzaYMgdPQu-dK%2B7rU8bYrjtg%3Dm2XHFFGeYdvO7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Agent starting too soon

[Trevor Vaughan]

I just ditched it.

On Tue, Mar 28, 2017 at 9:23 AM, Rob Nelson <rnels...@gmail.com> wrote:

> Did you replace it with systemd-networkd, or just ditch it? Regardless,
> I've updated us to EL7.3 (CentOS though) and not observed this issue, so
> I'm not sure it's that generic of a problem, there must be *something*
> triggering it. Even a simple race condition should result in some successes
> if Laverne has rebooted it a few dozen times.
>
>
> Rob Nelson
> rnels...@gmail.com
>
> On Tue, Mar 28, 2017 at 9:08 AM, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
>> Disabling NetworkManager hasn't caused any issues for me so far. That
>> said, EL7.3 might break that, so Fedora may already be broken.
>>
>> Trevor
>>
>> On Tue, Mar 28, 2017 at 9:00 AM, Rob Nelson <rnels...@gmail.com> wrote:
>>
>>> That wiki page says that all you should need to do is have
>>> NetworkManager or systemd-networkd services enabled. Do you by any chance
>>> have them both disabled on the affected node? I know many of us don't like
>>> NetworkManager, but disabling it entirely can cause some problems. Just a
>>> guess, as I haven't seen this issue on any of my nodes, including the
>>> low-RAM ones.
>>>
>>>
>>> Rob Nelson
>>> rnels...@gmail.com
>>>
>>> On Mon, Mar 27, 2017 at 11:33 PM, Laverne Schrock <
>>> lvernschr...@gmail.com> wrote:
>>>
>>>> I have a box on which puppet-agent does not start correctly on reboot.
>>>> Well, to be more precise, the puppet-agent starts, but never contacts the
>>>> server.
>>>>
>>>>
>>>> $ sudo journalctl -b 0 -u puppet -f
>>>>> -- Logs begin at Wed 2017-02-01 18:27:11 CST. --
>>>>> Mar 06 12:42:03 localhost.localdomain systemd[1]: Started Puppet agent.
>>>>> Mar 06 12:42:16 localhost.localdomain puppet-agent[927]: Could not 
>>>>> request certificate: getaddrinfo: Temporary failure in name resolution
>>>>> Mar 06 12:44:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>>>> certificate: getaddrinfo: Temporary failure in name resolution
>>>>> Mar 06 12:46:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>>>> certificate: getaddrinfo: Temporary failure in name resolution
>>>>> Mar 06 12:48:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>>>> certificate: getaddrinfo: Temporary failure in name resolution
>>>>>
>>>>>
>>>> Note how when the puppet-agent starts, the box doesn't yet know its
>>>> hostname because the network stack is (apparently) not fully up. Running
>>>> `systemctl restart puppet` resolves the issue until the next reboot.
>>>>
>>>> I was able to find a work-around. In the systemd unit file for puppet,
>>>> I changed
>>>>
>>>> After=basic.target network.target
>>>>>
>>>> to
>>>>
>>>>>  After=basic.target network-online.target
>>>>>
>>>>
>>>> See: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>>>>
>>>> The box is a fresh install of Fedora 25 and is using the following
>>>> packages:
>>>>
>>>>> puppet-agent-1.9.3-1.fedoraf25.x86_64
>>>>> puppetlabs-release-pc1-1.1.0-5.fedoraf25.noarch
>>>>>
>>>>
>>>> I have another box with the same setup (but a little more RAM) and the
>>>> issue does not occur there.
>>>>
>>>> I have two thoughts on this.
>>>> 1) This is a subtle timing issue which is why I see it on one box, but
>>>> not the other.
>>>> 2) puppet-agent is misbehaving and ought to  properly detect when the
>>>> networking stack comes up.
>>>> 3) If I want to resolve this, I should just use my workaround.
>>>>
>>>> Does #3 seem like the best plan? I'd appreciate any insight into why
>>>> the issue is occurring.
>>>>
>>>> Cheers,
>>>> -Laverne Schrock
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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 email to puppet-users+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit http

Re: [Puppet Users] Puppet Agent starting too soon

[Trevor Vaughan]

Disabling NetworkManager hasn't caused any issues for me so far. That said,
EL7.3 might break that, so Fedora may already be broken.

Trevor

On Tue, Mar 28, 2017 at 9:00 AM, Rob Nelson <rnels...@gmail.com> wrote:

> That wiki page says that all you should need to do is have NetworkManager
> or systemd-networkd services enabled. Do you by any chance have them both
> disabled on the affected node? I know many of us don't like NetworkManager,
> but disabling it entirely can cause some problems. Just a guess, as I
> haven't seen this issue on any of my nodes, including the low-RAM ones.
>
>
> Rob Nelson
> rnels...@gmail.com
>
> On Mon, Mar 27, 2017 at 11:33 PM, Laverne Schrock <lvernschr...@gmail.com>
> wrote:
>
>> I have a box on which puppet-agent does not start correctly on reboot.
>> Well, to be more precise, the puppet-agent starts, but never contacts the
>> server.
>>
>>
>> $ sudo journalctl -b 0 -u puppet -f
>>> -- Logs begin at Wed 2017-02-01 18:27:11 CST. --
>>> Mar 06 12:42:03 localhost.localdomain systemd[1]: Started Puppet agent.
>>> Mar 06 12:42:16 localhost.localdomain puppet-agent[927]: Could not request 
>>> certificate: getaddrinfo: Temporary failure in name resolution
>>> Mar 06 12:44:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>> certificate: getaddrinfo: Temporary failure in name resolution
>>> Mar 06 12:46:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>> certificate: getaddrinfo: Temporary failure in name resolution
>>> Mar 06 12:48:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>>> certificate: getaddrinfo: Temporary failure in name resolution
>>>
>>>
>> Note how when the puppet-agent starts, the box doesn't yet know its
>> hostname because the network stack is (apparently) not fully up. Running
>> `systemctl restart puppet` resolves the issue until the next reboot.
>>
>> I was able to find a work-around. In the systemd unit file for puppet, I
>> changed
>>
>> After=basic.target network.target
>>>
>> to
>>
>>>  After=basic.target network-online.target
>>>
>>
>> See: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>>
>> The box is a fresh install of Fedora 25 and is using the following
>> packages:
>>
>>> puppet-agent-1.9.3-1.fedoraf25.x86_64
>>> puppetlabs-release-pc1-1.1.0-5.fedoraf25.noarch
>>>
>>
>> I have another box with the same setup (but a little more RAM) and the
>> issue does not occur there.
>>
>> I have two thoughts on this.
>> 1) This is a subtle timing issue which is why I see it on one box, but
>> not the other.
>> 2) puppet-agent is misbehaving and ought to  properly detect when the
>> networking stack comes up.
>> 3) If I want to resolve this, I should just use my workaround.
>>
>> Does #3 seem like the best plan? I'd appreciate any insight into why the
>> issue is occurring.
>>
>> Cheers,
>> -Laverne Schrock
>>
>>
>>
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/puppet-users/36ca1e68-fa09-4654-ba62-9c13c2561c76%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/36ca1e68-fa09-4654-ba62-9c13c2561c76%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAC76iT_vimf_MmN--mBLA2fnqSAxQUJ%
> 3DBAzNRMOQOgM1F0TevA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAC76iT_vimf_MmN--mBLA2fnqSAxQUJ%3DBAzNRMOQOgM1F0TevA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWZ9Vfa%3DLY_MYgavrsBZaN6imUyWfZKT1776EsN5yyEXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Agent starting too soon

[Trevor Vaughan]

This does seem to be the fix that is required both for Fedora and EL7.

Trevor

On Mon, Mar 27, 2017 at 11:33 PM, Laverne Schrock <lvernschr...@gmail.com>
wrote:

> I have a box on which puppet-agent does not start correctly on reboot.
> Well, to be more precise, the puppet-agent starts, but never contacts the
> server.
>
>
> $ sudo journalctl -b 0 -u puppet -f
>> -- Logs begin at Wed 2017-02-01 18:27:11 CST. --
>> Mar 06 12:42:03 localhost.localdomain systemd[1]: Started Puppet agent.
>> Mar 06 12:42:16 localhost.localdomain puppet-agent[927]: Could not request 
>> certificate: getaddrinfo: Temporary failure in name resolution
>> Mar 06 12:44:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>> certificate: getaddrinfo: Temporary failure in name resolution
>> Mar 06 12:46:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>> certificate: getaddrinfo: Temporary failure in name resolution
>> Mar 06 12:48:16 a.real.hostname.tld puppet-agent[927]: Could not request 
>> certificate: getaddrinfo: Temporary failure in name resolution
>>
>>
> Note how when the puppet-agent starts, the box doesn't yet know its
> hostname because the network stack is (apparently) not fully up. Running
> `systemctl restart puppet` resolves the issue until the next reboot.
>
> I was able to find a work-around. In the systemd unit file for puppet, I
> changed
>
> After=basic.target network.target
>>
> to
>
>>  After=basic.target network-online.target
>>
>
> See: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>
> The box is a fresh install of Fedora 25 and is using the following
> packages:
>
>> puppet-agent-1.9.3-1.fedoraf25.x86_64
>> puppetlabs-release-pc1-1.1.0-5.fedoraf25.noarch
>>
>
> I have another box with the same setup (but a little more RAM) and the
> issue does not occur there.
>
> I have two thoughts on this.
> 1) This is a subtle timing issue which is why I see it on one box, but not
> the other.
> 2) puppet-agent is misbehaving and ought to  properly detect when the
> networking stack comes up.
> 3) If I want to resolve this, I should just use my workaround.
>
> Does #3 seem like the best plan? I'd appreciate any insight into why the
> issue is occurring.
>
> Cheers,
> -Laverne Schrock
>
>
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/36ca1e68-fa09-4654-ba62-9c13c2561c76%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/36ca1e68-fa09-4654-ba62-9c13c2561c76%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVA-wswK8Dvn5NF_Z7JgkzmjcFi4EYOaUHLvgMDBzQo-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] RHEL 7 STIG compliance using Puppet

[Trevor Vaughan]

Hi Chris,

So glad you asked.

Try https://github.com/NationalSecurityAgency/SIMP for the 'official'
overview and https://simp-project.com for the more visually appealing
version.

Thanks,

Trevor

On Fri, Mar 3, 2017 at 1:09 PM, Chris S. <chris4...@gmail.com> wrote:

> Hello all,
>
> Does anyone have a good method to Adhere to the RHEL STIG or even CIS
> benchmark usign Puppet.  I'm inclined to write some of my own modules
> and/or use some from the forge to piecemeal a solution.  I was wondering is
> anyone has an Approved or Supported all encompassing solution to this
> problem.
>
> Thanks in advance
> -cs
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/742b3c46-6232-4e5f-b718-6df08797c062%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/742b3c46-6232-4e5f-b718-6df08797c062%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVeSEg2SLov8%3D35%2BFmnU08ZG4Vwi-czBt%2Btc7Y0eao1eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] Re: Draft for new type and provider API

[Trevor Vaughan]

iled: #{exception message}
>> # TODO: update messages to match current log message formats for resource 
>> messages
>>
>> Logging contexts process all exceptions. StandardErrors
>> <https://ruby-doc.org/core/StandardError.html> are assumed to be regular
>> failures in handling a resources, and they are swallowed after logging.
>> Everything else is assumed to be a fatal application-level issue, and is
>> passed up the stack, ending execution. See the ruby documentation
>> <https://ruby-doc.org/core/Exception.html> for details on which
>> exceptions are not StandardErrors.
>>
>> The equivalent long-hand form with manual error handling:
>>
>> logger.updating(title: title)begin
>>   if key_not_found
>> logger.warning(title: title, message: 'Original key not found')
>>   end
>>
>>   # Update the key by calling CLI tool
>>   try_apt_key(...)
>>
>>   if $?.exitstatus != 0
>> logger.error(title: title, "Failed executing apt-key #{...}")
>>   else
>> logger.attribute_changed(
>>   title: title,
>>   attribute: 'content',
>>   old_value: nil,
>>   new_value: content_hash,
>>   message:   "Created with content hash #{content_hash}")
>>   end
>>   logger.changed(title: title)rescue StandardError => e
>>   logger.error(title: title, exception: e, message: 'Updating failed')
>>   raise unless e.is_a? StandardErrorend
>>
>> This example is only for demonstration purposes. In the normal course of
>> operations, implementations should always use the utility functions.
>>
>> <https://github.com/puppetlabs/pick-playground/tree/master/tnp-design#logging-reference>Logging
>> reference
>>
>> The following action/context methods are available:
>>
>>- creating(title:, message: 'Creating', )
>>- updating(title:, message: 'Updating', )
>>- deleting(title:, message: 'Deleting', )
>>-
>>
>>attribute_changed(title:, attribute:, old_value:, new_value:,
>>message: nil)
>>-
>>
>>created(title:, message: 'Created')
>>- updated(title:, message: 'Updated')
>>-
>>
>>deleted(title:, message: 'Deleted')
>>-
>>
>>fail(title:, message:) - abort the current context with an error
>>
>>
>> 
>>
>>
>>
>> Regards, David
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-dev/CALF7fHZ-PYgrqboexxDJzzLPgbxidu%2BZs%
>> 3DRYHyc85LBOnr4EfA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-dev/CALF7fHZ-PYgrqboexxDJzzLPgbxidu%2BZs%3DRYHyc85LBOnr4EfA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-dev/CAAAzDLcHRk0crAwcXHsP-2QS6Bv1OVHGxQV8_-QoOUnf%
> 2BDvoQg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CAAAzDLcHRk0crAwcXHsP-2QS6Bv1OVHGxQV8_-QoOUnf%2BDvoQg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoU5CXGM0UWduYGKXtp2b7JAi%2BqcT7j%3DLpN_cebHAjvzYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] Draft for new type and provider API

[Trevor Vaughan]

I'm still thinking about a lot of this but one thing that I will ask is
that you don't drop the actual compiled catalog (in whatever form).

One of the reasons that Puppet is good for compliance focused architectures
is based on the fact that I can easily hook it to validate input on the fly

https://github.com/simp/pupmod-simp-compliance_markup

Thanks,

Trevor

On Fri, Feb 3, 2017 at 12:23 PM, David Schmitt <david.schm...@puppet.com>
wrote:

>
>
> On 3 February 2017 at 11:12, Martin Alfke <tux...@gmail.com> wrote:
>
>> Hi David,
>>
>> many thanks for sharing your ideas.
>>
>> As you already know: personally I don’t say that types and providers are
>> way to difficult.
>> It is more a matter on how to explain them.
>> I will dig through your document during weekend. We can have a chat on
>> Monday in Ghent.
>>
>> But besides this:
>> is your idea somehow related to the libral project?
>> https://github.com/puppetlabs/libral
>>
>>
>>
>
>>
>>   * It maps 1:1 to the capabilities of PCore, and is similar to the
>> libral interface description (see [libral#1](https://github.com/
>> puppetlabs/libral/pull/2)). This ensures future interoperability between
>> the different parts of the ecosystem.
>>
>>
> libral is a neighbouring project, with its own set of distinct design
> goals. Staying bidirectionally compatible is a necessary requisite for this
> proposal here. (Which can be handled on both sides, depending on a wide
> variety of things).
>
> Cheers, David
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-dev/CALF7fHb9b7HknTGrhMbu5213kpMX3
> rHg-nwiOKr2jvcqnzTh-Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CALF7fHb9b7HknTGrhMbu5213kpMX3rHg-nwiOKr2jvcqnzTh-Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX46Snm5vLTkWMbq7hL3bdCs4thaOLeay16uQYRCjG1TQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] Draft for new type and provider API

[Trevor Vaughan]

I think I'm slowly talking myself into this.

The issue that I've had is that the current Data Types are composable.
There's a ticket open about it and hopefully that will fix a lot of my
issues.

Unfortunately, it looks like my heap/stack discussion was with Henrik on
Slack, so that's not super helpful.

Basically, the idea is that, instead of using a pure object model, objects
would be created *as necessary* and the linear execution model would be
kept in a simple array (stack). The data space (heap) would contain the
attributes that are required for each object to execute.

This means that the data structure would be extremely efficient and there
would be almost no cost to building and manipulating an object graph.

The benefit of the object graph is to keep the object model. However, the
object model is simply not necessary and has proven not to scale to 10k+
resources. The Heap/Stack model should scale based on the amount of data
that you have and would be *extremely* portable to other languages.

The biggest down side (for me) is that I manipulate the catalog graph at
run time for various reasons. There would probably be an easy way to work
this into the API though since it would just be an array insertion.

In terms of the validate/munge question, munging can *absolutely* be done
client side. But do you even want to pass a catalog to the client if you
have invalid data that might be used by other resources. Also, I do quite a
bit of checking based on the values of other parameters/properties. If this
could be maintained reasonably, that would be fine.

I do think that having a global data space would be extremely important to
making this feasible. There are a couple of tickets on for this as well but
I don't know the numbers off hand. And, of course, if we use the heap/stack
model, the data is all in place (but may change based on resource
processing).

Hopefully this all makes sense.

Thanks,

Trevor

On Thu, Feb 2, 2017 at 8:42 AM, David Schmitt <david.schm...@puppet.com>
wrote:

>
>
> On 2 February 2017 at 02:50, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
>> Hi David,
>>
>> Most of this looks fine (I still need to digest some of it) but I don't
>> know that I'm a huge fan of no munge or validate functionality. This seems
>> to fly in the face of a 'fail fast' mentality.
>>
>
> With puppet 4 data types much of the trivial stuff munge and validate do
> can be handled much easier and consistently than before. Many other checks
> will never be possible on the server, because they depend on values only
> available on the agent (credential validity, max tablename length dependent
> on mysql flavour), or would be error prone duplication of things the target
> API does check for us (validity of file mode bit combinations, validity of
> AMI references when talking to EC2 instances, etc). There is a bit of stuff
> in-between those two (e.g. content specified on a file), which we'd
> trade-off for a much simpler server side. Failing on the agent, also means
> that independent parts of the catalog can move forward, instead of failing
> the whole compilation.
>
>
>> Also, if everything happens on the client, some of the catalog munging
>> that I do on the fly isn't going to work any longer.
>>
>
> Those resources will not look anything different than existing types
> (which will stay as they are for a considerable while). Since I don't know
> what catalog munging you're doing I'm having a hard time following here.
>
> I *do* like the idea of types being pure data but will this bloat the
>> catalog even further?
>>
>
> The resources in the catalog won't look any different than today. In fact,
> the first version will most likely just call Puppet::Type.newtype() under
> the hood somewhere.
>
>
>> I still think that moving toward a heap/stack model would serve the
>> Puppet clients best and get past the resource count limitations.
>>
>
> Do you have those ideas written up somewhere?
>
>
>> Fundamentally, I want my clients to do as little work as possible since
>> they're meant to be running business processes.
>>
>
> Same.
>
>
>>
>> I'll definitely be keeping an eye on this conversation though.
>>
>> Thanks,
>>
>
> Thanks for your time and work you're putting in here.
>
>
> David
>
>
>>
>> Trevor
>>
>> On Tue, Jan 31, 2017 at 11:04 AM, David Schmitt <david.schm...@puppet.com
>> > wrote:
>>
>>> Hi *,
>>>
>>> The type and provider API has been the bane of my existence since I
>>> [started writing native resources](https://github.com/
>>> DavidS/puppet-mysql-old/commit/d33c7aa10e3a4bd9e97e947c471ee3ed36e9d1e2).
>>> Now, finally, we'l

[Puppet Users] Re: [Puppet-dev] Draft for new type and provider API

[Trevor Vaughan]

efinition are mostly aesthetic at the current point in time, but will make
> for better documentation, and allow more intelligence built on top of this
> later.
>
> * The implementation are two simple functions `current_state = get()`, and
> `set(current_state, target_state, noop)`.
>   * `get` on its own is already useful for many things, like puppet
> resource.
>   * `set` receives the current state from `get`. While this is necessary
> for proper operation, there is a certain race condition there, if the
> system state changes between the calls. This is no different than what
> current implementations face, and they are well-equipped to deal with this.
>   * `set` is called with a list of resources, and can do batching if it is
> beneficial. This is not yet supported by the agent.
>   * the `current_state` and `target_state` values are lists of simple data
> structures built up of primitives like strings, numbers, hashes and arrays.
> They match the schema defined in the type.
>   * Calling `r.set(r.get, r.get)` would ensure the current state. This
> should run without any changes, proving the idempotency of the
> implementation.
>   * The ruby instance hosting the `get` and `set` functions is only alive
> for the duration of an agent transaction. An implementation can provide a
> `initialize` method to read credentials from the system, and setup other
> things as required. The single instance is used for all instances of the
> resource.
>   * There is no direct dependency on puppet core libraries in the
> implementation.
> * While implementations can use utility functions, they are completely
> optional.
> * The dependencies on the `logger`, `commands`, and similar utilities
> can be supplied by a small utility library (TBD).
>
> * Having a well-defined small API makes remoting, stacking, proxying,
> batching, interactive use, and other shenanigans possible, which will make
> for a interesting time ahead.
>
> * The logging of updates to the transaction is only a sketch. See the
> usage of `logger` throughout the example. I've tried different styles for
> fit.
>   * the `logger` is the primary way of reporting back information to the
> log, and the report.
>   * results can be streamed for immediate feedback
>   * block-based constructs allow detailed logging with little code
> ("Started X", "X: Doing Something", "X: Success|Failure", with one or two
> calls, and only one reference to X)
>
> * Obviously this is not sufficient to cover everything existing types and
> providers are able to do. For the first iteration we are choosing
> simplicity over functionality.
>   * Generating more resource instances for the catalog during compilation
> (e.g. file#recurse or concat) becomes impossible with a pure data-driven
> Type. There is still space in the API to add server-side code.
>   * Some resources (e.g. file, ssh_authorized_keys, concat) cannot or
> should not be prefetched. While it might not be convenient, a provider
> could always return nothing on the `get()` and do a more customized enforce
> motion in the `set()`.
>   * With current puppet versions, only "native" data types will be
> supported, as type aliases do not get pluginsynced. Yet.
>   * With current puppet versions, `puppet resource` can't load the data
> types, and therefore will not be able to take full advantage of this. Yet.
>
> * There is some "convenient" infrastructure (e.g. parsedfile) that needs
> porting over to this model.
>
> * Testing becomes possible on a completely new level. The test library can
> know how data is transformed outside the API, and - using the shape of the
> type - start generating test cases, and checking the actions of the
> implementation. This will require developer help to isolate the
> implementation from real systems, but it should go a long way towards
> reducing the tedium in writing tests.
>
>
> What do you think about this?
>
>
> Cheers, David
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-dev/CALF7fHaJdvPrkqRQEMqEgLSUvOy-
> O4DuL-iNsLrPt74HY7djvw%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CALF7fHaJdvPrkqRQEMqEgLSUvOy-O4DuL-iNsLrPt74HY7djvw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWyRAW0uuAQwiEOj1ja3F-WgU6auKsgMKGWVTCmwdeKYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet managing thousands of resources

[Trevor Vaughan]

By my calculations...really.

I'm around 3k normally right now with no issue but, as you move toward 10k,
your agents start to have a bad time.

CC'ing Henrik and Eric since this is an "in the wild" case outside of my
theoretical ranting.

It's pretty easy to test using 'puppet apply' and files with resource
generators and 'notify' statements.

Thanks,

Trevor

On Wed, Jan 11, 2017 at 2:59 PM, Zachary Vida <vida.z...@gmail.com> wrote:

> Exponential? Really or just an expression, but rough estimate is probably
> about 5k
>
> On Wed, Jan 11, 2017, 2:50 PM Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
>> How many resources are in your catalog?
>>
>> Puppet starts to hit exponential catalog sizes and run times as you
>> approach 10k resources.
>>
>> Thanks,
>>
>> Trevor
>>
>> On Wed, Jan 11, 2017 at 12:58 PM, Zachary Vida <vida.z...@gmail.com>
>> wrote:
>>
>> Hello, I was wonder if there are any significant impovements in later
>> version of puppet >= 2.6 to catolog compilation and/or application
>> runtimes.
>>
>> In an environment I manage we populate many local files
>> (/etc/passwd,/etc/group,/etc/hosts) via ENC. This results in a steady
>> state catalog compilation/apply run times of several minutes and during an
>> inital puppet apply clocking in at 90 minutes.
>>
>>
>>
>> --
>>
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>>
>>
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/d7cc6062-722b-4f8a-9284-27ded5048c34%
>> 40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/d7cc6062-722b-4f8a-9284-27ded5048c34%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699 x788 <(410)%20541-6699>
>>
>> -- This account not approved for unencrypted proprietary information --
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/puppet-users/fS1cHkjuWco/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/CANs%2BFoWo0EGkWKeLepqP%2BkOmbPN-
>> hEa_cQV9Zq4C_H3caVuKSA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWo0EGkWKeLepqP%2BkOmbPN-hEa_cQV9Zq4C_H3caVuKSA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAC0dne-h3Fu%2BxDARb6yzW0OiN6mPwSqa4UR7qjh2
> 8oe_gjAP4A%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAC0dne-h3Fu%2BxDARb6yzW0OiN6mPwSqa4UR7qjh28oe_gjAP4A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWB%2BtO9ZmWay6JEcQp-aMLR%3DSwymFp1gfYMq%2Bceye%3DdVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet managing thousands of resources

[Trevor Vaughan]

How many resources are in your catalog?

Puppet starts to hit exponential catalog sizes and run times as you
approach 10k resources.

Thanks,

Trevor

On Wed, Jan 11, 2017 at 12:58 PM, Zachary Vida <vida.z...@gmail.com> wrote:

> Hello, I was wonder if there are any significant impovements in later
> version of puppet >= 2.6 to catolog compilation and/or application
> runtimes.
>
> In an environment I manage we populate many local files
> (/etc/passwd,/etc/group,/etc/hosts) via ENC. This results in a steady
> state catalog compilation/apply run times of several minutes and during an
> inital puppet apply clocking in at 90 minutes.
>
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/d7cc6062-722b-4f8a-9284-27ded5048c34%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d7cc6062-722b-4f8a-9284-27ded5048c34%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWo0EGkWKeLepqP%2BkOmbPN-hEa_cQV9Zq4C_H3caVuKSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Over-engineering rant

[Trevor Vaughan]

"puppet can just do it for us"

This * 1000

On Tue, Jan 10, 2017 at 9:42 AM, R.I.Pienaar <r...@devco.net> wrote:

>
>
> - Original Message -
> > From: "Rob Nelson" <rnels...@gmail.com>
> > To: "puppet-users" <puppet-users@googlegroups.com>
> > Sent: Tuesday, 10 January, 2017 15:28:07
> > Subject: Re: [Puppet Users] Over-engineering rant
>
> > I would argue that it's when you break steps 1-3 down into implementation
> > details that it becomes confusing for many. If you've done it before,
> it's
> > trivial; if it's your first time, it can be hairy.
>
> this really is the same flow as I highlighted and as shown puppet could
> just
> do it for us
>
> >
> >
> > Rob Nelson
> > rnels...@gmail.com
> >
> > On Tue, Jan 10, 2017 at 9:16 AM, Trevor Vaughan <tvaug...@onyxpoint.com>
> > wrote:
> >
> >> Actually, from an automation point of view, this is pretty trivial.
> >>
> >> Step 1) Create new CA (preserving old CA trust) X number of days prior
> to
> >> expiration
> >> Step 2) Pass out both CA trust roots to all systems
> >> Step 3) Start a re-signing party using the fact that you already have a
> >> bi-directional trust in place
> >> Step 4) Let the old CA certificate gracefully expire and remove it
> >> whenever you like (nothing will trust it anyway)
> >>
> >> That's pretty much it.
> >>
> >> For traditional *NIX applications using a CAPath approach, this is
> trivial.
> >>
> >> As long as you have a valid CA in your CAPath, you can roll over
> >> certificates with ease.
> >>
> >> Trevor
> >>
> >> On Mon, Jan 9, 2017 at 9:04 PM, Rob Nelson <rnels...@gmail.com> wrote:
> >>
> >>> I think certificate handling is a valid critique of puppet's security
> >>> implementation. Running a public key infrastructure of any sort is
> >>> difficult. Things like expired CAs and a lack of intermediate signing
> CAs
> >>> does expose puppet administrators who are lacking those fairly rare
> skill
> >>> sets to some difficult potential issues. I don't want to run a CA,
> mostly
> >>> because I've had to run one before. Many people would also like to
> extend
> >>> the expiration to more than 5 years, but don't find out about this
> issue
> >>> until 4.5 years in. Whoops :)
> >>>
> >>> It's just that the fix isn't agents automatically accepting new CAs. In
> >>> the example given of bringing a new CA online, the issue isn't that the
> >>> client would be missing a copy of the original CA signatures, but that
> >>> there's no way to verify the new CA is related to the old CA. This
> >>> constitutes a pretty high security risk with a decent probability for
> >>> exploitation - and not just by external parties, it would be easy to
> DoS
> >>> your agents during a failed migration or by testing with vagrant or
> >>> additional VMs by forgetting to change DNS/IPs or a dozen other simple
> >>> things to miss. Any improvement here probably ends up being relatively
> >>> complex to ensure risks remain low.
> >>>
> >>> It would be much more reasonable to have an extremely long lived CA and
> >>> some intermediate CAs. This is supported by puppet, but only I believe
> with
> >>> an external CA setup (https://docs.puppet.com/puppe
> >>> t/latest/config_ssl_external_ca.html) - again, not something most of
> us
> >>> should probably be doing. I don't know that there's a great way to
> handle
> >>> this for the masses, unless Puppet wants to become a CA and sign
> >>> intermediates for us ;)
> >>>
> >>> On Mon, Jan 9, 2017 at 7:18 PM John Gelnaw <jgel...@gmail.com> wrote:
> >>>
> >>>> since the agent has, in theory, a valid copy of the original CA which
> it
> >>>> can use to validate the connection.
> >>>>
> >>> --
> >>> Rob Nelson
> >>>
> >>> --
> >>> 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
> >>> email to puppet-users+unsubscr...@googlegroups.com.
> >>> To view this discussion on the web visit
> https://groups.google.com/d/ms
> >>> gid/p

Re: [Puppet Users] Over-engineering rant

[Trevor Vaughan]

Actually, from an automation point of view, this is pretty trivial.

Step 1) Create new CA (preserving old CA trust) X number of days prior to
expiration
Step 2) Pass out both CA trust roots to all systems
Step 3) Start a re-signing party using the fact that you already have a
bi-directional trust in place
Step 4) Let the old CA certificate gracefully expire and remove it whenever
you like (nothing will trust it anyway)

That's pretty much it.

For traditional *NIX applications using a CAPath approach, this is trivial.

As long as you have a valid CA in your CAPath, you can roll over
certificates with ease.

Trevor

On Mon, Jan 9, 2017 at 9:04 PM, Rob Nelson <rnels...@gmail.com> wrote:

> I think certificate handling is a valid critique of puppet's security
> implementation. Running a public key infrastructure of any sort is
> difficult. Things like expired CAs and a lack of intermediate signing CAs
> does expose puppet administrators who are lacking those fairly rare skill
> sets to some difficult potential issues. I don't want to run a CA, mostly
> because I've had to run one before. Many people would also like to extend
> the expiration to more than 5 years, but don't find out about this issue
> until 4.5 years in. Whoops :)
>
> It's just that the fix isn't agents automatically accepting new CAs. In
> the example given of bringing a new CA online, the issue isn't that the
> client would be missing a copy of the original CA signatures, but that
> there's no way to verify the new CA is related to the old CA. This
> constitutes a pretty high security risk with a decent probability for
> exploitation - and not just by external parties, it would be easy to DoS
> your agents during a failed migration or by testing with vagrant or
> additional VMs by forgetting to change DNS/IPs or a dozen other simple
> things to miss. Any improvement here probably ends up being relatively
> complex to ensure risks remain low.
>
> It would be much more reasonable to have an extremely long lived CA and
> some intermediate CAs. This is supported by puppet, but only I believe with
> an external CA setup (https://docs.puppet.com/puppet/latest/config_ssl_
> external_ca.html) - again, not something most of us should probably be
> doing. I don't know that there's a great way to handle this for the masses,
> unless Puppet wants to become a CA and sign intermediates for us ;)
>
> On Mon, Jan 9, 2017 at 7:18 PM John Gelnaw <jgel...@gmail.com> wrote:
>
>> since the agent has, in theory, a valid copy of the original CA which it
>> can use to validate the connection.
>>
> --
> Rob Nelson
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAC76iT_2XN3vaZKrpzsrXOzkT%2B4_
> 3P82ZZWkipigm8%3D%3DXew9ZA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAC76iT_2XN3vaZKrpzsrXOzkT%2B4_3P82ZZWkipigm8%3D%3DXew9ZA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVhHTsauG_gA_fODFXWYAoj9McHuvLk5ikOC%3DoReFd35Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Issue using NFS directories as environments in Puppet 4

[Trevor Vaughan]

The Puppet *server* should be running as 'puppet' or 'pe-puppet', not
'root'.

Can you double check that this isn't the root of your issue?

Trevor

On Tue, Jan 3, 2017 at 2:10 PM, PK <p.karni...@gmail.com> wrote:

> Rob,
>
> No. Symlink to a local file system works fine.
>
> Tried it with:
> dev -> /tmp/dev
> dev2 -> /etc/puppetlabs/code/environments/devorig
>
> Trevor,
>
> SELinux is disabled and the puppet master server has full superuser access
> to the NetApp volume/directory. The client cannot see those NFS directories
> because I haven't exported them to the client, but that shouldn't matter as
> the Puppet server has complete root access to the files/directories.
>
> Thanks!
>
>
> On Tuesday, January 3, 2017 at 3:34:37 AM UTC-8, Rob Nelson wrote:
>>
>> Does this happen if you use a symlink to a local file system location?
>> dev -> /tmp/dev for example?
>>
>> On Tue, Jan 3, 2017 at 4:32 AM PK <p.kar...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I seem to be running into an issue when I try to use
>>>
>>> environments in my test Puppet 4 setup. I am in the process of migrating
>>>
>>> from Puppet 3 to Puppet 4.
>>>
>>> puppetserver version: 2.7.2
>>> puppet agent: 4.8.1
>>> Server is running CentOS Linux release 7.3.1611
>>>
>>> If
>>>
>>> I create local directories
>>>
>>> /etc/puppetlabs/code/environments/{dev,production} and populate it with
>>>
>>> all my Puppet related files, everything works fine. However, if I copy
>>>
>>> the same files over to a NFS share mounted at a different location and
>>>
>>> then create a symlink from /etc/puppetlabs/code/environments/dev to that
>>>
>>> new location, puppet agent doesn't like it and errors out.
>>>
>>> [root] pwd
>>> /etc/puppetlabs/code/environments
>>> [root]# ll
>>> lrwxrwxrwx 1 root root 23 Jan  2 14:21 dev -> /ln/systems/puppet4/dev
>>>
>>> Errors on the client while running puppet agent -t:
>>> Error:
>>>
>>> Could not retrieve catalog from remote server: Find
>>>
>>> /puppet/v3/catalog/hostname.com?environment=dev_format
>>> =pson=%257B%2522name%...
>>>
>>> resulted in 404 with the message: {"message":"Not Found: Could not find
>>>
>>> environment 'dev'","issue_kind":"RUNTIME_ERROR"}
>>>
>>> Puppetserver errors:
>>> 2017-01-02 14:26:12,505 INFO  [qtp1908253991-68] [puppetserver] Puppet
>>> Not Found: Could not find environment 'dev'
>>>
>>> This same setup (symlink to a NFS share) works perfectly fine with our
>>> current Puppet 3.7.5
>>>
>>> I also tried mounting the NFS share directly at
>>> /etc/puppetlabs/code/environments, but that doesn't work either.
>>>
>>> Has someone seen this before? Am I missing something?
>>>
>>> Thanks!
>>> PK
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> 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 email to puppet-users...@googlegroups.com.
>>>
>>>
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/puppet-users/01451c04-cbb4-418a-a138-8a0b4ffa581b%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/01451c04-cbb4-418a-a138-8a0b4ffa581b%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>> Rob Nelson
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/17558bfa-0ead-4f28-b836-c846f289fdd8%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/17558bfa-0ead-4f28-b836-c846f289fdd8%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoU6cjv2FiPYj%3D9Y3HdEeu%3DoMRw%2B9iLYhg6Q-CpD8_n9ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Issue using NFS directories as environments in Puppet 4

[Trevor Vaughan]

Do you have SELinux enabled?

Also, do you have 'all_squash' enabled on your NFS directories?

Trevor

On Mon, Jan 2, 2017 at 5:51 PM, PK <p.karni...@gmail.com> wrote:

> Hi All,
>
> I seem to be running into an issue when I try to use environments in my
> test Puppet 4 setup. I am in the process of migrating from Puppet 3 to
> Puppet 4.
>
> puppetserver version: 2.7.2
> puppet agent: 4.8.1
> Server is running CentOS Linux release 7.3.1611
>
> If I create local directories 
> /etc/puppetlabs/code/environments/{dev,production}
> and populate it with all my Puppet related files, everything works fine.
> However, if I copy the same files over to a NFS share mounted at a
> different location and then create a symlink from 
> /etc/puppetlabs/code/environments/dev
> to that new location, puppet agent doesn't like it and errors out.
>
> [root] pwd
> /etc/puppetlabs/code/environments
> [root]# ll
> lrwxrwxrwx 1 root root 23 Jan  2 14:21 dev -> /ln/systems/puppet4/dev
>
> Errors on the client while running puppet agent -t:
> Error: Could not retrieve catalog from remote server: Find
> /puppet/v3/catalog/hostname.com?environment=dev_
> format=pson=%257B%2522name%... resulted in 404 with the message:
> {"message":"Not Found: Could not find environment
> 'dev'","issue_kind":"RUNTIME_ERROR"}
>
> Puppetserver errors:
> 2017-01-02 14:26:12,505 INFO  [qtp1908253991-68] [puppetserver] Puppet Not
> Found: Could not find environment 'dev'
>
> This same setup (symlink to a NFS share) works perfectly fine with our
> current Puppet 3.7.5
>
> I also tried mounting the NFS share directly at 
> /etc/puppetlabs/code/environments,
> but that doesn't work either.
>
> Has someone seen this before? Am I missing something?
>
> Thanks!
> PK
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/01451c04-cbb4-418a-a138-8a0b4ffa581b%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/01451c04-cbb4-418a-a138-8a0b4ffa581b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVWm59kHGexvAw-TvR-8xD9zrkgTc23btAqhhSUkm3p5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Exported resources in Puppet 4 without using PuppetDB?

[Trevor Vaughan]

Fair enough. It's good to know just in case something can be done.

In this case, I don't think there's much of a choice.

However, if it is a competing product, I don't think that the PuppetDB
project would reject a PR for support for your internal project. It might
be faster than getting approval from on high!

Thanks,

Trevor

On Sun, Dec 18, 2016 at 1:14 PM, Johnson Earls <darkfoxpr...@gmail.com>
wrote:

> Trevor: PostgreSQL is considered a competing product.  We're not allowed
> to use competing products without getting approval from the corporate
> information security group, legal, marketing, and a high level corporate
> officer (I don't remember how high off the top of my head, but at least 4
> levels above my manager), and it's a process that takes months to go
> through.
>
> On Sunday, December 18, 2016 at 9:50:18 AM UTC-8, Trevor Vaughan wrote:
>>
>> Hi Johnson,
>>
>> Do you have any information on why PostgreSQL is taboo? It might help to
>> justify supporting additional back-end databases.
>>
>> To solve your exported resources problem, you can use this as an example
>> https://github.com/simp/pupmod-simp-ssh/blob/master/
>> lib/puppet/parser/functions/ssh_global_known_hosts.rb.
>>
>> Now, be aware that this will *not* synchronize between multiple servers
>> but, if you have a single master, it will work just fine. Alternatively, if
>> you have a shared filesystem it will also work.
>>
>> We're working toward revamping these types of items to use a shared
>> synchronization system but it's not high priority at this time since most
>> places can use PuppetDB.
>>
>> A better bet might be to take this snippet and turn it into something
>> that writes to a DB that you control and then have a Hiera backend that
>> feeds your your data as collected from that backend on a regular basis.
>>
>> In Puppet functions, you have the entire catalog at your disposal and can
>> do with the data what you will.
>>
>> Good Luck,
>>
>> Trevor
>>
>> On Fri, Dec 16, 2016 at 5:52 PM, Johnson Earls <darkfo...@gmail.com>
>> wrote:
>>
>>> Hello all,
>>>
>>> I was just wondering - has anyone come across a plugin or something that
>>> would allow the use of exported resources in Puppet 4.x *without* using
>>> PuppetDB?  The company I work for has declared PostgreSQL taboo within the
>>> corporate network and so I cannot run PuppetDB, and the lack of exported
>>> resources is really starting to grate.  I'm hoping someone has seen
>>> something out there that can help solve this for me :)
>>>
>>> Thanks in advance,
>>> - Johnson
>>>
>>> --
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/puppet-users/95a0f132-7b41-4158-af41-8a9785646aa8%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/95a0f132-7b41-4158-af41-8a9785646aa8%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699 x788 <(410)%20541-6699>
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/7966276a-e6d6-4447-b2d3-6654667fd1e3%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/7966276a-e6d6-4447-b2d3-6654667fd1e3%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXJZ8ryw47xdo6KR%3D04%3Dvz5SBHQy5B40VRaBg8z0uHcbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Exported resources in Puppet 4 without using PuppetDB?

[Trevor Vaughan]

Hi Johnson,

Do you have any information on why PostgreSQL is taboo? It might help to
justify supporting additional back-end databases.

To solve your exported resources problem, you can use this as an example
https://github.com/simp/pupmod-simp-ssh/blob/master/lib/puppet/parser/functions/ssh_global_known_hosts.rb
.

Now, be aware that this will *not* synchronize between multiple servers
but, if you have a single master, it will work just fine. Alternatively, if
you have a shared filesystem it will also work.

We're working toward revamping these types of items to use a shared
synchronization system but it's not high priority at this time since most
places can use PuppetDB.

A better bet might be to take this snippet and turn it into something that
writes to a DB that you control and then have a Hiera backend that feeds
your your data as collected from that backend on a regular basis.

In Puppet functions, you have the entire catalog at your disposal and can
do with the data what you will.

Good Luck,

Trevor

On Fri, Dec 16, 2016 at 5:52 PM, Johnson Earls <darkfoxpr...@gmail.com>
wrote:

> Hello all,
>
> I was just wondering - has anyone come across a plugin or something that
> would allow the use of exported resources in Puppet 4.x *without* using
> PuppetDB?  The company I work for has declared PostgreSQL taboo within the
> corporate network and so I cannot run PuppetDB, and the lack of exported
> resources is really starting to grate.  I'm hoping someone has seen
> something out there that can help solve this for me :)
>
> Thanks in advance,
> - Johnson
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/95a0f132-7b41-4158-af41-8a9785646aa8%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/95a0f132-7b41-4158-af41-8a9785646aa8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWP%2B211_QL3Md4ukAg%2Bfx05339-DXig49Xt9gCV2suzcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] any way to debug a Puppet custom function?

[Trevor Vaughan]

Hi Thomas,

This might help as a reference if you want to use rspec to test your
functions.
https://github.com/simp/pupmod-simp-simplib/tree/master/spec/functions

Thanks,

Trevor

On Mon, Sep 19, 2016 at 9:30 PM, Thomas Cheng 
wrote:

> Hi howdies,
>
>  Recently I'm picking up some legacy puppet codes in my new company. the
> puppet code base has custom functions written in ruby before.
>
> One major issue is: how to debug the custom functions to figure out the
> logic inside? Can I copy/paste into an external general ruby script and
> debug it with 'ruby -rdebug 

Re: [Puppet Users] A Scalable HA Setup with on 2 configs, check this out !

[Trevor Vaughan]

 why I don't see
>>> >> anyone doing it like this yet.
>>> >>
>>> >> Million dollar question:
>>> >> Why must i use a centralized the ca server?
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> 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
>>> >> email to puppet-users+unsubscr...@googlegroups.com.
>>> >> To view this discussion on the web visit
>>> >> https://groups.google.com/d/msgid/puppet-users/6dcd4a20-909c
>>> -4373-892f-0f7a3e69d19d%40googlegroups.com.
>>> >> For more options, visit https://groups.google.com/d/optout.
>>> >>
>>> >>
>>> >> --
>>> >> 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
>>> >> email to puppet-users+unsubscr...@googlegroups.com.
>>> >> To view this discussion on the web visit
>>> >> https://groups.google.com/d/msgid/puppet-users/c5dbbb59-4de7
>>> -720f-3424-3135db424522%40alter3d.ca.
>>> >> For more options, visit https://groups.google.com/d/optout.
>>> >
>>> > --
>>> > 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
>>> > email to puppet-users+unsubscr...@googlegroups.com.
>>> > To view this discussion on the web visit
>>> > https://groups.google.com/d/msgid/puppet-users/CAAohVBfGJx14
>>> uUqocAXPw7oJvBdVsenQhE4rjDSNCXCwjM94Vg%40mail.gmail.com.
>>> >
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> Gareth Rushgrove
>>> @garethr
>>>
>>> devopsweekly.com
>>> morethanseven.net
>>> garethrushgrove.com
>>>
>>> --
>>> 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 email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/puppet-users/CAFi_6yLdmbE9QZ2%2BZ-OpuFGyt-mNRF5n2NuQ21SF
>>> iNTyTEbA0g%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAAohVBfC-E%2BXp5_td2j0n9EW4rcKPcx47kxYJ4tT8sjpN
> %3DSBkw%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAAohVBfC-E%2BXp5_td2j0n9EW4rcKPcx47kxYJ4tT8sjpN%3DSBkw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX3jnRD6O%2BNUKNyrmiN9vMeQNt986oeV6DqRCxGoS9uNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] I'd like to see you at PuppetConf 2016

[Trevor Vaughan]

Mike,

You couldn't keep me away man

Even if you wanted to

Which you probably do

I'm bad at haiku

T

On Fri, Sep 16, 2016 at 11:31 AM, Michael Stahnke <stah...@puppet.com>
wrote:

> PuppetConf is coming up in just about a month, in San Diego, CA. It would
> be wonderful to see you there. If you haven't been to one before, it's a
> great time to learn about all things automations and DevOps. The talk
> line-up this year looks stellar, and the hallways will be packed with
> people sharing tips, stories, disasters, and their vision of the future
> when it comes to automation.
>
> PuppetConf is great not only because you connect with other folks doing
> Puppet stuff, but because the attendees are among the best systems people
> in the world. You get a chance to learn from them, as well as the
> sessions.  Join us a day early for the contributor summit for open forums
> if that works for you.
>
> I want to invite you to come, but time is running out for the cheaper
> tickets. Today is the last day for the 20% off price.
>
> Michael Stahnke
> Director of Engineering
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAMto7L%2BRv6Qwkqpn1rcDSQn6DSStZj_
> 4EtVrCVgD6zfbnpwNxw%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAMto7L%2BRv6Qwkqpn1rcDSQn6DSStZj_4EtVrCVgD6zfbnpwNxw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVxdgbJBYmjYrakqbjO7jPq7ZCGUT1s3TNwdxqH0pRkFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Stubbing functions in Puppet rspec

[Trevor Vaughan]

Hi Peter,

See if this helps
https://github.com/onyxpoint/puppet-gpasswd/blob/master/spec/unit/provider/group/gpasswd_spec.rb

Thanks,

Trevor

On Fri, Aug 5, 2016 at 8:04 AM, Peter Berghold <salty.cowd...@gmail.com>
wrote:

> I have this wonderful module that calls various custom functions that I've
> written that I'm trying to adopt RSpec testing for.  After seeing it crash
> and burn with "function unknown" errors I took a rather meandering path and
> arrived here: https://github.com/TomPoulton/rspec-puppet-unit-testing
>
> So I attempted to follow the instructions given and I ended up with a
> result like this:
>
> - 8< snip!   file: spec/classes/init_spec.rb
> 
>
> require 'spec_helper'
> describe 'ourbind' do
>
>   let!(:ipdot2dash) { MockFunction.new('ipdot2dash') { |f|
>   f.stubbed.with('10.1.2.3').returns('10-1-2-3')
> }
>   }
>   context 'with defaults for all parameters' do
> it do
>   ipdot2dash.stubs(:call).with('10.1.2.3').returns('10-1-2-3')
>   should compile
>   should contain_class('ourbind')
>
> end
>   end
> end
>
> -- 8< snip! 8< --
> --
>
> I run "rake spec" and I get this (at least to me) undecipherable message:
>
> --8< error spew 8<
> ---
>
> Failure/Error: should compile
>
>  Mocha::ExpectationError:
>unexpected invocation: # MockFunction:0x2b67950>.call(['', '21'])
>satisfied expectations:
>- allowed any number of times, not yet invoked:
> #.root?(any_parameters)
>- allowed any number of times, not yet invoked: # MockFunction:0x2b67950>.call('10.1.2.3')
>- allowed any number of times, not yet invoked: # MockFunction:0x2b67950>.execute('10.1.2.3')
>
> -8< snip! 8< --
> 
>
>
> Apparently I'm missing something here, what's it trying to tell me and how
> do I fix it?
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAArvnv2mhr7qyOhgRJWQ%2Bfr9hm88gdhmCB1AYB2aeqq1TFCA%
> 2BA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAArvnv2mhr7qyOhgRJWQ%2Bfr9hm88gdhmCB1AYB2aeqq1TFCA%2BA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVkgH7uz-VkZqiE9ie3pA3oz53dvjj7MPq5xmO2-d9Ysg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] new CIS Benchmark compliance module for RHEL 7

[Trevor Vaughan]

Hi Mike,

I would HIGHLY suggest renaming your module unless you've paid CIS the
requisite $9-20k to use their name.

Red Hat has a C2S profile that should work.

Trevor

On Sun, Jul 31, 2016 at 12:58 PM, mike r <mike.rei...@gmail.com> wrote:

> testing welcome. thanks.
>
> https://forge.puppet.com/perfecto25/cis_rhel7
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1e5045af-c1e9-41b0-be75-794c00512944%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/1e5045af-c1e9-41b0-be75-794c00512944%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVhh7us-yMgTtRF95iSzuyH%2BS3wAAvvBsobEuJ9-ETTLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Newbie question re Hiera

[Trevor Vaughan]

Hi Alex,

You can use this Gist to do what you want:
https://gist.github.com/trevor-vaughan/2c404efd0f1f881bbf56eef7bc949eb0

Thanks,

Trevor

On Tue, Jun 21, 2016 at 7:14 PM, Alex Samad <a...@samad.com.au> wrote:

> Hi
>
> I have a greenfield install. Centos 6.x puppet opensource latest.
>  installed r10k.
>
> I have setup my git repo, used the control repo as a starting spot.
>
> now I am getting my head around hiera
>
> Looking at this https://docs.puppet.com/hiera/3.1/complete_example.html
>  I understand the way that works for each environment.
>
> But how do I use hiera to allocate nodes to environments ?
>
> for example can I classify by name regex, so all hosts with name
> ".*prod.*" is in production and ".*inf.*" into inf environment
> can I also classify by ip address ?
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/8236b18c-2b1c-4733-a744-7dbeb281784c%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/8236b18c-2b1c-4733-a744-7dbeb281784c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXpwda9pZ0PCyMaSskxY2aHsweG6rRY1mqj868Nxn2FHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Broken puppetdb

[Trevor Vaughan]

Get rid of this:   storeconfigs = true

Trevor

On Sat, Jun 11, 2016 at 10:35 PM, Zeke Dehnert <zdehn...@enphaseenergy.com>
wrote:

> Here is my puppet.conf.
>
> # This file can be used to override the default puppet settings.
> # See the following links for more details on what settings are available:
> # -
> https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html
> # -
> https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html
> # -
> https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html
> # - https://docs.puppetlabs.com/references/latest/configuration.html
> [main]
>   certname = puppetmaster.enphaseenergy.com
>   dns_alt_names = puppet,puppet.enphaseenergy.com,puppetmaster,
> puppetmaster.enphaseenergy.com
>   server = puppetmaster
>   environment = production
>   runinterval = 1h
>   strict_variables = true
>   ordering = manifest
>   reports = http,store
>   module_repository = https://forgeapi.puppetlabs.com
>
> [master]
>   vardir = /opt/puppetlabs/server/data/puppetserver
>   logdir = /var/log/puppetlabs/puppetserver
>   rundir = /var/run/puppetlabs/puppetserver
>   pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
>   codedir = /etc/puppetlabs/code
>   reports = store
>   storeconfigs = true
>   environment_timeout = unlimited
>
> [agent]
>   pluginsync = true
>   graph = true
>   graphdir = /opt/puppetlabs/puppet/cache/state/graphs
>
> I can’t find any more puppetdb, or fact_terminus references at all.
> Unless its a but obscure.  I don’t know all of them so some things could be
> sneaking by me.
>
> There was a puppetdb.conf file in the /etc/puppetlabs/puppet directory,
> but I moved it out, restarted puppet server and I’m still getting errors:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Failed to execute
> '/pdb/cmd/v1?checksum=2e834ba5e4cdeae4ab27b04da26fa8c52cfbcfca=4=
> it-lnx-01.enphaseenergy.com=replace_facts' on at least 1 of the
> following 'server_urls': https://puppetdb:8081
>
> Aaarrggg!!!
>
> From: Matthaus Owens <matth...@puppet.com> <matth...@puppet.com>
> Reply: puppet-users@googlegroups.com <puppet-users@googlegroups.com>
> <puppet-users@googlegroups.com>
> Date: June 11, 2016 at 5:37:04 PM
> To: puppet-users@googlegroups.com <puppet-users@googlegroups.com>
> <puppet-users@googlegroups.com>
> Subject:  Re: [Puppet Users] Broken puppetdb
>
> It seems like you still have some puppetdb settings in puppet.conf, like
> fact_terminus for example. I'd look there before uninstalling the packages.
>
> HTH
>
> --
> Thanks,
>James “Zeke” Dehnert
>
> *Enphase Energy*  |  Senior Linux Administrator
>
>
>
> (707)763.4787 x7636  // Office
>
> GPG Fingerprint: E899 A10A 960D 4B6C 22D2 8FC2 EA5E4E81
> The information contained in this message may be privileged and
> confidential. It is intended to be read only by the individual or entity to
> whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and delete or
> destroy any copy of this message!
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/etPan.575cca55.752f2e1b.1b4d%40enphaseenergy.com
> <https://groups.google.com/d/msgid/puppet-users/etPan.575cca55.752f2e1b.1b4d%40enphaseenergy.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXz5zkAKBkVE65WgD%2Bsx8KKPheLg5%3D0ZfB5wCp0nCjw1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Broken puppetdb

[Trevor Vaughan]

That still looks like your server is trying to send things to PuppetDB.

Check the puppet.conf and grep for puppetdb in your puppet and puppet
server configuration settings and make sure it's been removed.

Also, fully restart your puppetserver process. An API hit won't do the job.

Trevor

On Sat, Jun 11, 2016 at 4:48 PM, jdehnert <jdehn...@gmail.com> wrote:

> Thanks for the tips Trevor.
>
> I did make the change on the puppet server, but my clients are still
> complaining:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Failed to execute
> '/pdb/cmd/v1?checksum=5c49765a6d1ef8e77fa85c53f70e9f572615463e=4=
> it-lnx-01.myhost.com=replace_facts' on at least 1 of the
> following 'server_urls': https://puppetmaster.myhost.com:8081
>
> any idea how I can clean that up, or why its happening?
>
> On Saturday, June 11, 2016 at 12:54:19 PM UTC-7, Trevor Vaughan wrote:
>>
>> Hi James,
>>
>> The puppetdb module should take care of your DB certs. However, if it
>> doesn't, or something goes wrong, you will need to fix the DB certs
>> manually.
>>
>> Also, if you update your Puppet certificates, the PuppetDB module will
>> *not* notice and you'll need to erase the existing certs and run the
>> manifests again.
>>
>> Of course, the puppet server is probably tied to your DB and you'll need
>> to disconnect the two before Puppet will run cleanly again.
>>
>> Remove any mention of 'puppetdb' from puppet.conf as well as deleting
>> your routes.yaml file (if PuppetDB is the only thing in there). Restart the
>> puppet server and things should work again.
>>
>> Trevor
>>
>> On Fri, Jun 10, 2016 at 11:36 PM, jdehnert <jdeh...@gmail.com> wrote:
>>
>>> Greetings All,
>>>
>>> I decided to try and implement the puppetlabs-puppetdb and
>>> puppetlabs-postgres modules after I had both puppetdb and postgres
>>> installed and working on my puppet server.  This was ill advised as it
>>> broke my working setup and no amount of re-configuring seems to be able to
>>> get things working again.
>>>
>>> I finally pulled the manifest that "describes" my configuration, but now
>>> I cannot seem to get puppetdb working at all.  My clients are giving me
>>> these kind of errors:
>>>
>>> Error: Could not retrieve catalog from remote server: Error 400 on
>>> SERVER: Failed to execute
>>> '/pdb/cmd/v1?checksum=2b3883d84fd2c7f9899bd6280247edbccc31cf15=4=
>>> it-lnx-01.myhost.com=replace_facts' on at least 1 of the
>>> following 'server_urls': https://puppetmaster.myhost.com:8081
>>> Warning: Not using cache on failed catalog
>>> Error: Could not retrieve catalog; skipping run
>>>
>>> I have crawled through  the puppet docs to try and fix my
>>> configurations, but I can't seem to get things operating properly.
>>>
>>> It seemed pretty clear that I did not need to configure the SSL portion
>>> of puppetdb, but these errors seem to be flying the the face of what I read.
>>>
>>> Do I need to configure SSL for puppetdb to get it to work?  and  What's
>>> my best chance of getting things working again.  Start from scratch, or am
>>> I just overlooking something from my configs.?
>>>
>>> Thanks,
>>>   jdeh...@gmail.com
>>>
>>>
>>> --
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699 x788
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/ac8e8d1

Re: [Puppet Users] Broken puppetdb

[Trevor Vaughan]

Hi James,

The puppetdb module should take care of your DB certs. However, if it
doesn't, or something goes wrong, you will need to fix the DB certs
manually.

Also, if you update your Puppet certificates, the PuppetDB module will
*not* notice and you'll need to erase the existing certs and run the
manifests again.

Of course, the puppet server is probably tied to your DB and you'll need to
disconnect the two before Puppet will run cleanly again.

Remove any mention of 'puppetdb' from puppet.conf as well as deleting your
routes.yaml file (if PuppetDB is the only thing in there). Restart the
puppet server and things should work again.

Trevor

On Fri, Jun 10, 2016 at 11:36 PM, jdehnert <jdehn...@gmail.com> wrote:

> Greetings All,
>
> I decided to try and implement the puppetlabs-puppetdb and
> puppetlabs-postgres modules after I had both puppetdb and postgres
> installed and working on my puppet server.  This was ill advised as it
> broke my working setup and no amount of re-configuring seems to be able to
> get things working again.
>
> I finally pulled the manifest that "describes" my configuration, but now I
> cannot seem to get puppetdb working at all.  My clients are giving me these
> kind of errors:
>
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Failed to execute
> '/pdb/cmd/v1?checksum=2b3883d84fd2c7f9899bd6280247edbccc31cf15=4=
> it-lnx-01.myhost.com=replace_facts' on at least 1 of the
> following 'server_urls': https://puppetmaster.myhost.com:8081
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> I have crawled through  the puppet docs to try and fix my configurations,
> but I can't seem to get things operating properly.
>
> It seemed pretty clear that I did not need to configure the SSL portion of
> puppetdb, but these errors seem to be flying the the face of what I read.
>
> Do I need to configure SSL for puppetdb to get it to work?  and  What's my
> best chance of getting things working again.  Start from scratch, or am I
> just overlooking something from my configs.?
>
> Thanks,
>   jdehn...@gmail.com
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWbeARKOSgTNGprUb3G98tzTuTJc7vz%2BvGCB69fcre6Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Outofmemory error for puppetserver process

[Trevor Vaughan]

ps/puppetserver/puppet-se...
>>>
>>> May 24 12:52:22 jim-Ubuntu1504 systemd[1]: Starting LSB: puppetserver...
>>> May 24 12:53:06 jim-Ubuntu1504 systemd[1]: Started LSB: puppetserver.
>>> root@jim-Ubuntu1504
>>> :/etc/puppetlabs/code/environments/production/manifests#
>>>
>>> Any advice would be much appreciated.
>>>
>>> Cheers
>>> Jim
>>>
>>> --
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/60c8e923-10ca-4d01-a09c-7e87a5036fdb%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/60c8e923-10ca-4d01-a09c-7e87a5036fdb%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/375e3af0-4592-4ac8-b87d-473b85107b70%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/375e3af0-4592-4ac8-b87d-473b85107b70%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW%2BoRG-8abU8etCqydf30Rm7pTM88tAr6A46skzcpHHBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera 2.0 with Puppet 3.x

[Trevor Vaughan]

Hi Scott,

We're using Hiera 3.0.5 with Puppet 3.8 on the SIMP project right now with
absolutely no issues.

We used Hiera 2 briefly, but moved on to Hiera 3 when it got to be stable.

Thanks,

Trevor

On Thu, May 19, 2016 at 4:19 PM, Scott Briggs <scott...@gmail.com> wrote:

> Does anyone have any experience with Hiera 2.0 with Puppet 3.x?  Is that
> even possible given the newer "all in one" architecture?
>
> Cheers,
> Scott
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/63e2178c-b784-41a9-ab03-da012f5d664f%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/63e2178c-b784-41a9-ab03-da012f5d664f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWoh%3Div%2BVdOj%3D%2BdaBKSJOor7h0SW1QeKfO4dptX6SDmFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] My custom puppet function changes values

[Trevor Vaughan]

This should work in all versions of Ruby (YMMV)

'foo.bar.baz'.each_byte.map{|x| x}.join.to_i % 64511 + 1024

Trevor

On Wed, May 18, 2016 at 7:37 PM, p <pe...@poproj.com> wrote:

> I'm doing this instead:
> module Puppet::Parser::Functions
>   newfunction(:ip_port, :type => :rvalue) do |args|
> require 'zlib'
> Zlib.crc32(args[0]) % 64511 + 1024
>   end
> end
>
>
>
>
> On Wednesday, May 18, 2016 at 10:16:19 AM UTC-7, p wrote:
>>
>> Any suggestions on how I can get the hash of the string content itself so
>> I can get this function to work? I really just don't want to manage ports
>> anymore.
>>
>> On Wednesday, May 18, 2016 at 7:35:55 AM UTC-7, Trevor Vaughan wrote:
>>>
>>> Hi Peter,
>>>
>>> Object.hash in Ruby provides the hash of the Object ID, not a consistent
>>> cryptographic hash of the string provided.
>>>
>>> Try it in two different IRB sessions and you'll see what I mean. It will
>>> change between garbage collection runs and/or at every invocation of Puppet
>>> if done in cron.
>>>
>>> Trevor
>>>
>>>
>>>
>>> On Tue, May 17, 2016 at 7:42 PM, p <pe...@poproj.com> wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>> My custom puppet code changes values randomly. Why?
>>>>
>>>> This code creates a random port for me based on the argument's hash.
>>>> The idea is that this will create a TCP port for me based on the name of
>>>> the argument I give it (for instance the FQDN) so that it is unique, above
>>>> 1024 but below 65535. I don't want to have to worry about port numbers, it
>>>> should just calculate the same every time.
>>>>
>>>> module Puppet::Parser::Functions
>>>>   newfunction(:ip_port, :type => :rvalue) do |args|
>>>> args[0].hash % 64511 + 1024
>>>>   end
>>>> end
>>>>
>>>>
>>>> I use it in a manifest this way:
>>>> $ip_port = ip_port('www.example.com')
>>>>
>>>> The puppet agent runs every 30 minutes by default. It's a master/slave
>>>> v3.8 setup. When I run it manually, the value always comes back the same.
>>>> But when I leave it alone, at some point the value changes. I use this to
>>>> create ports for haproxy. Thanks for your help.
>>>>
>>>>
>>>> Peter
>>>>
>>>> --
>>>> 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 email to puppet-users...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/puppet-users/d2551534-236d-4598-b288-1faa7d3c6bb0%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/puppet-users/d2551534-236d-4598-b288-1faa7d3c6bb0%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Trevor Vaughan
>>> Vice President, Onyx Point, Inc
>>> (410) 541-6699 x788
>>>
>>> -- This account not approved for unencrypted proprietary information --
>>>
>> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/92bf5ec3-5ad9-4289-9ee5-496dd8fe3239%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/92bf5ec3-5ad9-4289-9ee5-496dd8fe3239%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXHAWwLr9poru7gLE2VxHXK817M1dU2tPDBKZDQJSincA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] My custom puppet function changes values

[Trevor Vaughan]

Hi Peter,

Object.hash in Ruby provides the hash of the Object ID, not a consistent
cryptographic hash of the string provided.

Try it in two different IRB sessions and you'll see what I mean. It will
change between garbage collection runs and/or at every invocation of Puppet
if done in cron.

Trevor



On Tue, May 17, 2016 at 7:42 PM, p <pe...@poproj.com> wrote:

> Hi Everyone,
>
> My custom puppet code changes values randomly. Why?
>
> This code creates a random port for me based on the argument's hash. The
> idea is that this will create a TCP port for me based on the name of the
> argument I give it (for instance the FQDN) so that it is unique, above 1024
> but below 65535. I don't want to have to worry about port numbers, it
> should just calculate the same every time.
>
> module Puppet::Parser::Functions
>   newfunction(:ip_port, :type => :rvalue) do |args|
> args[0].hash % 64511 + 1024
>   end
> end
>
>
> I use it in a manifest this way:
> $ip_port = ip_port('www.example.com')
>
> The puppet agent runs every 30 minutes by default. It's a master/slave
> v3.8 setup. When I run it manually, the value always comes back the same.
> But when I leave it alone, at some point the value changes. I use this to
> create ports for haproxy. Thanks for your help.
>
>
> Peter
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d2551534-236d-4598-b288-1faa7d3c6bb0%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d2551534-236d-4598-b288-1faa7d3c6bb0%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXt2%2BFfrK_WW5wNjagXvZj4vuABa65LNZa1Ja6TB%3DwUqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4 syntax highlighting in Wordpress

[Trevor Vaughan]

Nigel, that is pure sorcery and how did I not know this existed?!

On Mon, Apr 11, 2016 at 3:48 PM, Nigel Kersten <ni...@puppet.com> wrote:

> I do Puppet syntax highlighting like this:
>
> Open up puppet code in Vim with syntax highlighting on.
>
> Use ":TOhtml" to save it as a formatted HTML file.
>
> Either use the HTML snippet directly on a web page, or for some GUI HTML
> editors, they'll understand styled text in your clipboard buffer (that's
> how I preserve editable text, but syntax highlighted for PowerPoint/Keynote
> slide decks)
>
> This way I can toggle stuff like Vim line numbering that sometimes I want
> on, and sometimes I want off, and I'm using the same syntax highlighter
> that I use for normal editing of Puppet code.
>
>
>
> On Sat, Apr 9, 2016 at 1:35 AM, Alex Harvey <alexharv...@gmail.com> wrote:
>
>> I still haven't found any Puppet syntax highlighting plugins for Puppet
>> (3 or 4).  I'll be most grateful to anyone willing to share their secrets
>> with me. :)
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/247df98c-0a7c-4883-ae27-7580d5c2a808%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/247df98c-0a7c-4883-ae27-7580d5c2a808%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAGUqgV8abAnVfSzk5mH_nzMETxjo2APa-%2B7-V_HUTUL9o499bg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAGUqgV8abAnVfSzk5mH_nzMETxjo2APa-%2B7-V_HUTUL9o499bg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW1S-Y1Ac4_VVTty-58bsfFniQ%2Bc5-zxqb6YETbmwP4rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Types auto generator

[Trevor Vaughan]

Hi,

It's not a generator, but this should get you started with an
understandable example framework
https://forge.puppet.com/onyxpoint/learning_custom_types.

It doesn't cover 100% of the functionality but it will allow you to create
an understandable and maintainable Type and Provider.

Thanks,

Trevor

On Thu, Apr 7, 2016 at 4:15 AM, Christoph Andreas Torlinsky <
christ...@nuagenetworks.net> wrote:

> Hello there, i'm looking for a puppet types generator tool / toolkit as we
> have an API (Restful interface) and spec files that we would like
> to convert to puppet types for some use. If anyone has any tips, that is
> most welcomed.
>
> many thanks,
>
> c
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d714b52a-c7f7-4104-ba1a-cb697a893d0a%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d714b52a-c7f7-4104-ba1a-cb697a893d0a%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUSFyu71e8rkftrrvqbfpMMwiMAsCpfiMtoH4HyQgc04A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] how to check existences of a file in a ERB template?

[Trevor Vaughan]

Hi San,

Templates are executed on the master and so it will be checking the
existence on the master as written.

You'll need to write a custom fact (they're easy)
https://docs.puppetlabs.com/facter/3.1/custom_facts.html. Something like a
boolean 'has_wp_extra_config' would be ideal.

Then, in your template, change your line to <%- if @has_wp_extra_config -%>
and you should be good to go.

Trevor

On Mon, Mar 28, 2016 at 3:44 PM, Sans <r.santanu@gmail.com> wrote:

> Hi there,
>
> I'm setting up a multi-tenancy WordPress environment, where multiple sites
> are structured as: /var/www/. Long story short: I want to put
> a line in the wp-config.php based on existences of a file in wp-content
> (under each site_location, provided by my users) directory, which I don't
> actively managed. So, I have this in the template that generates the
> wp-config.php file:
>
> <%- if File.exist?('/var/www/'+@title+'/wp-content/wp-extra-config.php') -
> %>
> require_once(ABSPATH . 'wp-content/wp-extra-config.php');
> <%- end -%>
>
> where @title is the site_name that comes from a hiera hash. But it's not
> working and I think the reason being Puppet checking the existences of
> wp-extra-config.php file on the master during the compilation, hence
> setting it as false, for obvious reason. I cannot have it as a fact,
> because of the multi-tenancy and existences of that file varies from
> project to project. How do I go around this issue?
>
> -San
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/15dd9afc-a55c-45d3-ab22-ed3ffc68fc3c%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/15dd9afc-a55c-45d3-ab22-ed3ffc68fc3c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWSAHHzbV%2BpMU2aUX8R33shmBdL58j-wt6mk3bii157kA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4 syntax highlighting in Wordpress

[Trevor Vaughan]

Hi Alex,

I don't think that any specific highlighting has been released for Puppet 4
but I find that the Ruby syntax highlighting does a reasonable job in most
cases.

Trevor

On Sun, Mar 27, 2016 at 4:53 AM, Alex Harvey <alexharv...@gmail.com> wrote:

> Hi all,
>
> Does anyone out there have any tips for getting nice-looking Puppet 4
> syntax highlighting to work in a Wordpress blog?  I am currently using Alex
> Mills's SyntaxHighlighter Evolved
> <http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/> and I
> found one apparently unmaintained plugin for Puppet 3 era plugin
> en-jbrinkley/syntaxhighlighter-puppet
> <https://github.com/en-jbrinkley/syntaxhighlighter-puppet>.  Googling
> isn't bringing up anything written after Puppet 4 was released.
>
> All the best,
> Alex
>
> --
> Partner
> RAZOR Consulting
> t: +61 409 665 227
> w: http://razorconsulting.com.au
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/3d915b0d-402a-4944-9ef2-fc1f64908519%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/3d915b0d-402a-4944-9ef2-fc1f64908519%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXvvms9gtThpqLb%2Bbc2%2BvmdtdovaD%3D0QqntWvV19sD2Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Enterprise + SELinux

[Trevor Vaughan]

Hi Thomas,

This looks like a bug in the installation RPM. I would file a bug against
PE with your proposed fix as it looks correct and should be part of the RPM
post installation.

Trevor

On Thu, Mar 24, 2016 at 5:16 AM, Thomas Müller <tho...@chaschperli.ch>
wrote:

> Hi
>
> Does Puppet Enterprise support running puppet agent selinux confined?
>
> Seems at least EL6 and EL7 provide types but it seems pe-agent is not
> using them as they are started in initrc_t (EL6) or unconfined_service_t
> (EL7).
>
> I can't find documentation about this topic on docs.puppetlabs.com .
>
> The problem with selinux policy enforced is (at least on EL6), that it has
> some AVC logged when puppet tries to manage confined services (like sshd)
> as puppet causes tmp-files created with wrong context (initrc_tmp_t
> instead of puppet_tmp_t).
>
> - Thomas
>
>
> types on EL7
>
> # seinfo -t | grep pupp
>puppet_var_lib_t
>puppet_var_run_t
>puppetca_exec_t
>puppetmaster_tmp_t
>puppet_client_packet_t
>puppetagent_exec_t
>puppet_port_t
>puppetagent_t
>puppet_etc_t
>puppet_log_t
>puppetmaster_initrc_exec_t
>puppetmaster_exec_t
>puppetmaster_t
>puppetagent_initrc_exec_t
>puppet_server_packet_t
>puppet_tmp_t
>puppetca_t
>
>
> AVC on EL6
> type=AVC msg=audit(11.111:123): avc: denied { write } for pid=123
> comm="sshd" path="/tmp/puppet20160301-123-123q1xb" dev=dm-1 ino=3 scontext
> =system_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:
> initrc_tmp_t:s0 tclass=file
>
>
> Quick fix:
>
> # will be reset with restorecon -rv or "touch /.autorelabel" and reboot
> # only a temp solution
> # EL6
> chcon -t puppet_initrc_exec_t /etc/init.d/pe-puppet
> chcon -t puppet_exec_t /opt/puppet/bin/puppet
> # EL7
> chcon -t puppetagent_exec_t /opt/puppet/bin/puppet
>
> # both
> service pe-puppet restart
>
>
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d9b65399-bc63-4509-bb2e-2d345350a91e%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d9b65399-bc63-4509-bb2e-2d345350a91e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWqE8F7Ko8RhiSNRR%3DZ9cQ%3D5KgHstLKgdYO5M_czDKY5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Thanks Eric.

I know I'm being super irritating on this thread, but a link from one to
the other might make this management proof.

For now, I'll just send along both to those that ask.

Thanks,

Trevor

On Tue, Mar 22, 2016 at 4:54 PM, Eric Sorenson <eric.soren...@puppetlabs.com
> wrote:

> Oh boy. It could, I guess, it's HTML so anything is possible.  But the
> canonical location for the component versions is on the docs site which is
> its own CMS and it's a lot of data:
>
> https://docs.puppetlabs.com/pe/latest/overview_version_table.html
>
>
>
> On Mar 22, 2016, at 1:50 PM, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
> Security releases are really all that's important to most
> compliance-focused orgs.
>
> Could that page link to the versions of each sub-component that is
> included?
>
> Thanks!
>
> Trevor
>
> On Tue, Mar 22, 2016 at 11:37 AM, Eric Sorenson <
> eric.soren...@puppetlabs.com> wrote:
>
>> Sorry for the slow reply, we had some internal ducks to get in a row.
>> The enterprise support page now shows the current support dates for all the
>> recent series:
>>
>> https://puppetlabs.com/misc/puppet-enterprise-lifecycle
>>
>> As a practical matter we're going to provide open-source releases of
>> components of a particular PE series for as long as that PE series is
>> supported; outside of security fixes though, the content of releases behind
>> the current one will be driven largely by customer requests.
>>
>> --eric0
>>
>> On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
>>>
>>> Certainly possible, but deductions aren't stated facts on URLs that you
>>> can put in front of management.
>>>
>>> Trevor
>>>
>>> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
>>> mig...@instruct.com.br> wrote:
>>>
>>>> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan <
>>>> tvaug...@onyxpoint.com> wrote:
>>>> > Thanks Carthik. Unfortunately, we need to know this for all of the
>>>> > components, FOSS or otherwise.
>>>> >
>>>>
>>>> I think one can deduce that, if PE 3 series has an EOL set to July 28,
>>>> 2016, all FOSS components present there will most definitely not be
>>>> supported anymore also.
>>>>
>>>> --
>>>> 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 email to puppet-users+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/puppet-users/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Trevor Vaughan
>>> Vice President, Onyx Point, Inc
>>> (410) 541-6699
>>>
>>> -- This account not approved for unencrypted proprietary information --
>>>
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
>
> -- This account not approved for unencrypted proprietary information --
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/15QSPcvkGDI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3DV1E7O9Rqn-8Xt7tw9NTPHVg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3D

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Security releases are really all that's important to most
compliance-focused orgs.

Could that page link to the versions of each sub-component that is included?

Thanks!

Trevor

On Tue, Mar 22, 2016 at 11:37 AM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:

> Sorry for the slow reply, we had some internal ducks to get in a row.  The
> enterprise support page now shows the current support dates for all the
> recent series:
>
> https://puppetlabs.com/misc/puppet-enterprise-lifecycle
>
> As a practical matter we're going to provide open-source releases of
> components of a particular PE series for as long as that PE series is
> supported; outside of security fixes though, the content of releases behind
> the current one will be driven largely by customer requests.
>
> --eric0
>
> On Wednesday, March 16, 2016 at 9:57:05 AM UTC-7, Trevor Vaughan wrote:
>>
>> Certainly possible, but deductions aren't stated facts on URLs that you
>> can put in front of management.
>>
>> Trevor
>>
>> On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
>> mig...@instruct.com.br> wrote:
>>
>>> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan <tvaug...@onyxpoint.com>
>>> wrote:
>>> > Thanks Carthik. Unfortunately, we need to know this for all of the
>>> > components, FOSS or otherwise.
>>> >
>>>
>>> I think one can deduce that, if PE 3 series has an EOL set to July 28,
>>> 2016, all FOSS components present there will most definitely not be
>>> supported anymore also.
>>>
>>> --
>>> 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 email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/e0bddb7b-f9a7-47cf-a34a-8dad8876edf3%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW04-0UUP4%2BkJCdkFvWky%3DV1E7O9Rqn-8Xt7tw9NTPHVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Thanks Carthik. Unfortunately, we need to know this for all of the
components, FOSS or otherwise.

Thanks for the links.

Trevor

On Tue, Mar 15, 2016 at 7:51 PM, Carthik Sharma <cart...@puppetlabs.com>
wrote:

> HI Trevor,
>
> For PE, this page might help:
> https://puppetlabs.com/misc/puppet-enterprise-lifecycle
> For the agent, the EOL depends on the end of official support for the
> platform itself, see:
> https://docs.puppetlabs.com/guides/platforms.html#puppet-agent-and-operating-system-support-life-cycles
>
> I am sure someone will correct me if that is wrong.
>
> Thanks,
> Carthik.
>
> On Wed, Mar 9, 2016 at 12:15 PM, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
>> I've had a few questions and I realized that I didn't actually know.
>>
>> Thanks,
>>
>> Trevor
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWbfYDC5hjWwqRtkKQFsWi5A5Qrn%3DheHgkuRwMPN7ZQsA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWbfYDC5hjWwqRtkKQFsWi5A5Qrn%3DheHgkuRwMPN7ZQsA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAOzFSfFMRdpvGewkwagB%3DWTSF2YOOqpn%3DA4q6BworVn0_2j3LA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAOzFSfFMRdpvGewkwagB%3DWTSF2YOOqpn%3DA4q6BworVn0_2j3LA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVwqtV-uBCaQdzjUf8UCxrxu7hnk-vQS3FUHDH6zud8xQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

Certainly possible, but deductions aren't stated facts on URLs that you can
put in front of management.

Trevor

On Wed, Mar 16, 2016 at 10:41 AM, Miguel Di Ciurcio Filho <
mig...@instruct.com.br> wrote:

> On Wed, Mar 16, 2016 at 10:12 AM, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
> > Thanks Carthik. Unfortunately, we need to know this for all of the
> > components, FOSS or otherwise.
> >
>
> I think one can deduce that, if PE 3 series has an EOL set to July 28,
> 2016, all FOSS components present there will most definitely not be
> supported anymore also.
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAK6Yst%3DNT5%2B2aXG3PNEy9M2X0o6w791dWT9_za1gWefj7cwy%3DQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXnmBUTX-CtNrG7o_31Atd4vTMn%3D5C6W614S6C7Z2LbvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Pasword retrievel from external source on node

[Trevor Vaughan]

One of the main issues is ensuring that the sensitive contents of the
catalog do not make their way back into PuppetDB, Foreman, etc

I've been toying with the idea of adding a special, non-translated function
to Puppet core that will provide direction for the agent itself to reach
out to a 'trusted' data source regardless of placement in the catalog.

Essentially, this would be a special string, combined with some sort of
metaparameter that alters the catalog content on the fly.

It should absolutely be doable and the Conjur FOSS codebase is close to
there but doesn't quite hit the mark across the board for what I would like.

If anyone would like to start this, I'd be more than happy to help
contribute when I have time. Otherwise, I'll just hack at it when I get the
chance.

Thanks,

Trevor

On Thu, Mar 10, 2016 at 11:01 AM, Craig Dunn <cr...@craigdunn.org> wrote:

>
>
> On Thu, Mar 10, 2016 at 3:09 PM, Thomas Müller <tho...@chaschperli.ch>
> wrote:
>
>> I'm too interested in how people manage credentials without having it in
>> the catalog.
>>
>
> The problem as I see it is that there isn't a blanket approach.  If you
> need a secret value in a template, that template is already compiled into
> the catalog before the agent receives it, and there are numerous ways to
> get a file on a system.  One idea would be a kind of "eyaml in reverse"
> approach, where files could be deployed with inline encrypted data, and
> then a type and provider to do a pattern substitution on the file on the
> agent using local keys.
>
> But the problem isn't just files - what about, for example, exec commands
> that need to use a secret in the command line?  file_line resources?
> augeas? - theres a whole host of places the data might end up.
>
> I think the bigger issue to address would be why are your catalogs not
> considered a safe place to have this data? Access to the catalog should be
> at the same level of trust as root access to the agent.
>
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CACxdKhGrdrciDbSnPNAnGSjfspNP7azB%2BvMofR057dODZ9VL2A%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CACxdKhGrdrciDbSnPNAnGSjfspNP7azB%2BvMofR057dODZ9VL2A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUwF3AOLt8nxaMsBKSG-dbn_f_8vD9iHyct0dtqn8304Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Trevor Vaughan]

I've had a few questions and I realized that I didn't actually know.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWbfYDC5hjWwqRtkKQFsWi5A5Qrn%3DheHgkuRwMPN7ZQsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Force Fact within manifest

[Trevor Vaughan]

st want to see Facter expand on the whole gathering of
>> inventory.  No need to pull in another inventory management system, when
>> Facter can do it.   Facter and Puppet allow you to get new facts at the
>> end, but don't provide any native way of doing so.  I think that is the
>> main point people that request this are trying to say.
>>
>> You are in luck, however: Puppet's source is open
>>
>> Yep, and thats what makes it such an amazing tool and great community.
>> As well as allows users like myself, OP, and others, that want this kind of
>> reporting feature, to be able to actually do so.
>>
>> All in all, I truly understand what you're saying, and even agree when it
>> comes to Puppet.  Although, I also believe all things can be made better.
>> Giving users the ability to query changed or custom facts, after a puppet
>> run (or heck even without Puppet at all, just via Facter), seems like
>> something that could be made better.
>>
>> Right now, (especially since postrun_command is broke in windows) I run a
>> quick powershell script in its own new session that calls puppet upload
>> facts, or a nohup in the background (if nix), after every puppet run.  This
>> keeps it in its own environment and outside of puppets ruby process and env
>> vars.  I then use a ENC script to pull in the latest facts and push them to
>> reporting.  If I need to see the facts prior to Puppets run, I can also
>> view those, as I store them on the master as well.  Best of both worlds;
>> latest correct and latest prior to puppet.  Or if need be, we can even go
>> back 2 weeks and see every fact for each time puppet was ran.
>>
>> Thanks for your input and its always good to hear others reasonings and
>> opinions.
>>
>
> FYI this same suggestion came up recently in
> https://tickets.puppetlabs.com/browse/PUP-5934 (and I've linked this
> thread there).
>
> This strikes me as an ecosystem concern: i.e. I'm not convinced offhand
> we'd want to address the base use cases here by submitting facts with the
> report, because I wouldn't want to lose the current fact-set-to-catalog
> linkage in puppetdb. So I think we'd want to consider how this would be
> supported in puppetdb if/as we consider something like this.
>
> Also, in the spirit of linking related conversations: this idea may also
> dovetail with a current thread on puppet-dev:
> https://groups.google.com/d/msg/puppet-dev/bebmBUyRETg/v0VFTogWCgAJ.
> Specifically, one idea there is to specify fact ttl's, which might in turn
> impact fact submission times and fact storage schema, etc.
>
> Kylo
>
>
>>
>>
>>
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/d36b749c-7717-49e2-a057-8faccafb2dc5%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/d36b749c-7717-49e2-a057-8faccafb2dc5%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CALsUZFGiOoH2gjqaCzE-5pzO97%2BqJ3%2BYvz1SFpakySn8icsbKQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CALsUZFGiOoH2gjqaCzE-5pzO97%2BqJ3%2BYvz1SFpakySn8icsbKQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXOuU-%2Bavgu84G58FPpW7QF-a0KUmeyEdzmnTfFhJx9FQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] validate_bool() throwing in error syaing the value not a boolean

[Trevor Vaughan]

You can try using the hiera command line tool on your hiera.yaml file.

hiera -c '/path/to/hiera.yaml' your::variable.

You may also need to check your server logs to see if there is an error.

If you're using the Java Pupperserver, you may want to restart it due to
the change in environment caching.

Finally, you can add a notify to the code in question and see what comes
out the other side.

Trevor

On Thu, Mar 3, 2016 at 9:02 AM, Sans <r.santanu@gmail.com> wrote:

>
> Looks like to me it's not getting value from the Hiera at all. How can I
> make sure of that?
>
> -S
>
> On Thursday, March 3, 2016 at 1:28:51 PM UTC, Trevor Vaughan wrote:
>>
>> Hi Sam,
>>
>> Are you 100% sure that $wp_multisite is getting the value from Hiera?
>>
>> In this case, it looks like the value is empty.
>>
>> Thanks,
>>
>> Trevor
>>
>>
>> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/8cc362dc-cc0e-4e5a-bde2-aeec9045ef29%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/8cc362dc-cc0e-4e5a-bde2-aeec9045ef29%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVz03ChxSvtJaPxHiECFAbH1M4UvMXgA14TOupzWtuiOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] validate_bool() throwing in error syaing the value not a boolean

[Trevor Vaughan]

Hi Sam,

Are you 100% sure that $wp_multisite is getting the value from Hiera?

In this case, it looks like the value is empty.

Thanks,

Trevor

On Thu, Mar 3, 2016 at 5:23 AM, Sans <r.santanu@gmail.com> wrote:

>
> Hi guys,
>
> Suddenly started getting this error, which I cannot understand why I'm
> getting this:
>
>
> Error: Evaluation Error: Error while evaluating a Function Call, "" is not
> a boolean.  It looks to be a String at /usr/local/K101/puppet/modules/apps
> /manifests/app.pp:32:5 on node..
>
> the line 32 is: validate_bool($wp_multisite), which is coming from hiera
> and set to true
> Running PM in foreground or running the agent with --trace doesn't
> provide any additional information. I'm running out of ideas. Can anyone
> please help? Thanks in advance!!
>
> -S
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b6cc0809-a742-4f29-828b-27da5eda904e%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/b6cc0809-a742-4f29-828b-27da5eda904e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUoeQW6ScDhMEZE4x7UOjBJeaGdw9Kmw9TnQphmPE%3DPwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Strings 'Stack Level Too Deep'

[Trevor Vaughan]

PDOC-71 Created: https://tickets.puppetlabs.com/browse/PDOC-71

Thanks,

Trevor

On Tue, Feb 23, 2016 at 8:54 PM, Henrik Lindberg <
henrik.lindb...@puppetlabs.com> wrote:

> On 23/02/16 23:54, Trevor Vaughan wrote:
>
>> Thanks for the response Henrik,
>>
>> I was worried that it would be something this fun...
>>
>> The following script can be used to easily repeat the phenomenon that
>> I'm seeing if someone with some more in depth knowledge on the workings
>> of the Parser and Strings has a chance to take a look.
>>
>> Any errors that are thrown appear to be object corruption since I can
>> run 'puppet strings' directly on them without issue.
>>
>> #!/bin/sh
>> git clone https://github.com/simp/simp-core puppetdoc_test
>> cd puppetdoc_test
>> git checkout 5.1.X
>> bundle
>> rake deps:checkout
>> cd src/doc
>> git remote add doctest https://github.com/trevor-vaughan/simp-doc
>> git fetch --all
>> git checkout autodoc
>> bundle
>> rake docs:auto
>>
>> Thanks,
>>
>> Trevor
>>
>>
> Please file a PDOC Jira ticket if you have not already (with the
> information how to reproduce).
>
> - henrik
>
> On Tue, Feb 23, 2016 at 3:41 PM, Henrik Lindberg
>> <henrik.lindb...@puppetlabs.com <mailto:henrik.lindb...@puppetlabs.com>>
>>
>> wrote:
>>
>> On 23/02/16 19:24, Trevor Vaughan wrote:
>>
>> Hi All,
>>
>> I'm attempting (once again) to document all of my materials with
>> Puppet
>> Strings as a collected reference for *all* of my utilized modules.
>>
>> Right now, this is somewhere around 1058 Puppet and Ruby
>> artifacts.
>>
>> Unfortunately, at some point, the Strings Gem gives up the ghost
>> and
>> prints "SystemStackError: stack level too deep'.
>>
>> It also starts printing errors on files that clearly do not have
>> errors
>> (lint passes and 'puppet strings' on just the failing file
>> passes).
>>
>> Not quite sure what's going on here or even how to debug it
>> properly.
>>
>> Thanks,
>>
>> Trevor
>>
>> Out of stack is nasty to solve. It helps running on JRuby as you get
>> more intelligent backtraces than the "ooops, out of stack" that MRI
>> has to offer. (The place it says it is out of stack is just unlucky,
>> it can be one step in a very long cycle).
>>
>> The first problem is if it needs more stack or not. Bumping it up to
>> twice the amount or so may make it work. It could also be an
>> infinite recursion bug in Strings or in Puppet.
>>
>> Getting a stack trace is thus of value. Armed with the first stack
>> trace it may be possible to figure out where to instrument the code.
>> Even it the trace does not show where a cycle starts, it is possible
>> to figure out what is involved in the cycle. Then artifically
>> inserting a raise and exception or invoke the debugger at that point
>> i.e. when stack level is over a certain treshold. Then look at that
>> stack trace to see the entry into the cycle. Then debug that...
>>
>> (painful and slow)
>>
>> - henrik
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699 <tel:%28410%29%20541-6699>
>>
>> -- This account not approved for unencrypted proprietary
>> information --
>>
>> --
>> 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 email to puppet-users+unsubscr...@googlegroups.com
>> <mailto:puppet-users%2bunsubscr...@googlegroups.com>
>> <mailto:puppet-users+unsubscr...@googlegroups.com
>> <mailto:puppet-users%2bunsubscr...@googlegroups.com>>.
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV_G4uFqFPJ7pj5qEg6k-5jAowm50r-esFUsD8U5osUEw%40mail.gmail.com
>> <
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV_G4uFqFPJ7pj5qEg6k-5jAowm50r-esFUsD8U5osUEw%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>>     For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>

Re: [Puppet Users] Puppet Strings 'Stack Level Too Deep'

[Trevor Vaughan]

Thanks for the response Henrik,

I was worried that it would be something this fun...

The following script can be used to easily repeat the phenomenon that I'm
seeing if someone with some more in depth knowledge on the workings of the
Parser and Strings has a chance to take a look.

Any errors that are thrown appear to be object corruption since I can run
'puppet strings' directly on them without issue.

#!/bin/sh
git clone https://github.com/simp/simp-core puppetdoc_test
cd puppetdoc_test
git checkout 5.1.X
bundle
rake deps:checkout
cd src/doc
git remote add doctest https://github.com/trevor-vaughan/simp-doc
git fetch --all
git checkout autodoc
bundle
rake docs:auto

Thanks,

Trevor

On Tue, Feb 23, 2016 at 3:41 PM, Henrik Lindberg <
henrik.lindb...@puppetlabs.com> wrote:

> On 23/02/16 19:24, Trevor Vaughan wrote:
>
>> Hi All,
>>
>> I'm attempting (once again) to document all of my materials with Puppet
>> Strings as a collected reference for *all* of my utilized modules.
>>
>> Right now, this is somewhere around 1058 Puppet and Ruby artifacts.
>>
>> Unfortunately, at some point, the Strings Gem gives up the ghost and
>> prints "SystemStackError: stack level too deep'.
>>
>> It also starts printing errors on files that clearly do not have errors
>> (lint passes and 'puppet strings' on just the failing file passes).
>>
>> Not quite sure what's going on here or even how to debug it properly.
>>
>> Thanks,
>>
>> Trevor
>>
>> Out of stack is nasty to solve. It helps running on JRuby as you get more
> intelligent backtraces than the "ooops, out of stack" that MRI has to
> offer. (The place it says it is out of stack is just unlucky, it can be one
> step in a very long cycle).
>
> The first problem is if it needs more stack or not. Bumping it up to twice
> the amount or so may make it work. It could also be an infinite recursion
> bug in Strings or in Puppet.
>
> Getting a stack trace is thus of value. Armed with the first stack trace
> it may be possible to figure out where to instrument the code.
> Even it the trace does not show where a cycle starts, it is possible to
> figure out what is involved in the cycle. Then artifically inserting a
> raise and exception or invoke the debugger at that point i.e. when stack
> level is over a certain treshold. Then look at that stack trace to see the
> entry into the cycle. Then debug that...
>
> (painful and slow)
>
> - henrik
>
>
> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
>> --
>> 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 email to puppet-users+unsubscr...@googlegroups.com
>> <mailto:puppet-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV_G4uFqFPJ7pj5qEg6k-5jAowm50r-esFUsD8U5osUEw%40mail.gmail.com
>> <
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV_G4uFqFPJ7pj5qEg6k-5jAowm50r-esFUsD8U5osUEw%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/56CCC403.9070504%40puppetlabs.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX1R_JRL%3D%2BfqS3JwSoANxtQmk_L2O22%3D8UxwgFB0E3MsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Strings 'Stack Level Too Deep'

[Trevor Vaughan]

Hi All,

I'm attempting (once again) to document all of my materials with Puppet
Strings as a collected reference for *all* of my utilized modules.

Right now, this is somewhere around 1058 Puppet and Ruby artifacts.

Unfortunately, at some point, the Strings Gem gives up the ghost and prints
"SystemStackError: stack level too deep'.

It also starts printing errors on files that clearly do not have errors
(lint passes and 'puppet strings' on just the failing file passes).

Not quite sure what's going on here or even how to debug it properly.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV_G4uFqFPJ7pj5qEg6k-5jAowm50r-esFUsD8U5osUEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Updating facts for a client in PuppetDB independently from the master

[Trevor Vaughan]

Yeah, it would.

What I'm looking at doing would be injected as part of the reporting phase
so it would be updated after each client run.

Not an ideal solution, I would much rather be able to add some extra
metadata to my clients in PuppetDB instead of needing to drag around yet
another database interface.

Thanks,

Trevor

On Wed, Feb 17, 2016 at 4:28 PM, Thomas Müller <tho...@chaschperli.ch>
wrote:

> wouldnt next puppet run replace your out of band added fact?
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/6c69c0c7-c433-434f-a9f2-faa6999bf4c7%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWGGtOcMQVKHcJXOMsee44-_fC3hd0Ho2N8PCf%2BufKoRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Updating facts for a client in PuppetDB independently from the master

[Trevor Vaughan]

Hi All,

Is is possible to add facts to a client in PuppetDB independently of a run
of Puppet on a client?

Basically, I need to add some data to the client runs but the data is
irrelevant to the client itself so there's no need to shove it across the
network multiple times.

I took a look at the API and it seems like I might have to use
'replace_facts' but I'd need to fetch the last fact set, update it, and
then resubmit it with the updated information which isn't ideal but would
be doable.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW1Jyx2Hy6A13BjdZhopGk0Gc_cRZTKJF4b%2BXUP1qniSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Problems testing branching using rspec-puppet with hiera

[Trevor Vaughan]

othing else),
>> and that didn't work.  The example above was the last thing I tried, since
>> rspec-puppet is supposed to provide the fqdn fact, so I thought setting the
>> node might help it switch. Failure on all sides!
>>
>> I'm trying to do this because we've tried to write our profiles following
>> the practice of doing hiera lookups instead of class parameters, as
>> recommended here:
>> http://garylarizza.com/blog/2014/10/24/puppet-workflows-4-using-hiera-in-anger/
>>
>> At this point, I'm almost ready to throw in the towel.  There has to be
>> some way to change what values hiera supplies so I can test all branches of
>> my code, but I'm not sure how to do it.  Any suggestions or alternatives
>> would be welcome.
>>
>> Thanks!
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/puppet-users/QRK6MJsN6fY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/56C3A253.70303%40Alumni.TU-Berlin.de
>> <https://groups.google.com/d/msgid/puppet-users/56C3A253.70303%40Alumni.TU-Berlin.de?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAFwCtQRmBuX8vzdYcz1hixx4AgOAqQNpG4mT6-_%3DqoGN71mn7Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAFwCtQRmBuX8vzdYcz1hixx4AgOAqQNpG4mT6-_%3DqoGN71mn7Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoV86PRYVhN2qjwFitRfgYmdrCwgeTa3opjwV92EymKjUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet 3 to 4 deprication error

[Trevor Vaughan]

>From the error, I would say that not all of those values are defined at
that point and that's why you're seeing issues.

You'll need to rewrite the statement to check if the variables are defined.

Trevor

On Fri, Jan 22, 2016 at 12:38 PM, <rhpuppetu...@gmail.com> wrote:

> I typed the code here. It's a typo here in the post. Still getting the
> error.
>
> On Friday, January 22, 2016 at 11:24:33 AM UTC-6, Trevor Vaughan wrote:
>>
>> If that's a copy/paste, then your second occurrence of enable_nfsd is
>> misspelled.
>>
>> Trevor
>>
>> On Fri, Jan 22, 2016 at 11:51 AM, <rhpupp...@gmail.com> wrote:
>>
>>> I'm planning to migrate puppet3.8 to 4.x, so testing the compatibility
>>> of code by using parser=future in puppet.conf file and was stuck at the
>>> following error when i run puppet agent. The error is pointing at the
>>> regular expression. Any help is appreciated.
>>>
>>> Code:
>>> ---
>>> if ($::enable_nfsd !~ /^false$/) and (($:: enable_nfsd =~ /^true$/) or
>>> ($::local_nfsd == "true"))
>>>
>>> ---
>>>
>>>
>>> Error 400 on server: Evaluation Error: left match operand must result in
>>> a string value. Got an undef value at *.pp .
>>>
>>> --
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/abda8229-0c5a-417e-bebd-eefc2b545b50%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/abda8229-0c5a-417e-bebd-eefc2b545b50%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/36c5a2a3-42ec-4bad-922d-ab04401475f0%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/36c5a2a3-42ec-4bad-922d-ab04401475f0%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWCiCih6Y9B6KX54rsgzHY1M0UbzCz3MjcpX9JDubOAFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet 3 to 4 deprication error

[Trevor Vaughan]

If that's a copy/paste, then your second occurrence of enable_nfsd is
misspelled.

Trevor

On Fri, Jan 22, 2016 at 11:51 AM, <rhpuppetu...@gmail.com> wrote:

> I'm planning to migrate puppet3.8 to 4.x, so testing the compatibility of
> code by using parser=future in puppet.conf file and was stuck at the
> following error when i run puppet agent. The error is pointing at the
> regular expression. Any help is appreciated.
>
> Code:
> ---
> if ($::enable_nfsd !~ /^false$/) and (($:: enalbe_nfsd =~ /^true$/) or
> ($::local_nfsd == "true"))
>
> ---
>
>
> Error 400 on server: Evaluation Error: left match operand must result in a
> string value. Got an undef value at *.pp .
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/abda8229-0c5a-417e-bebd-eefc2b545b50%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/abda8229-0c5a-417e-bebd-eefc2b545b50%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWTEXio1bbT7ZH865XyhaEFNDnhN7twD43Fzkpd441MPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to manage half file.

[Trevor Vaughan]

Albert's suggestion is probably your best bet at the least amount of work.

First, create a custom fact that pulls that line out of your file.
https://docs.puppetlabs.com/facter/3.1/custom_facts.html.

Next, your template would have a placeholder for that item.

my_template.erb

...usual_template...
<%= @my_custom_fact %>
---remaining_template...

This isn't a great solution but it's probably the easiest way to solve your
problem quickly. I would not do this if that line is huge (some encoded
binary blob or something).

Trevor

On Thu, Jan 14, 2016 at 11:47 AM, Albert Shih <albert.s...@obspm.fr> wrote:

>  Le 13/01/2016 à 13:21:51-0800, Hunter Haugen a écrit
> > Does the application have an "include" syntax that would allow you do
> have one
> > file that is one line that the application manages, and the file that
> puppet
> > manages includes it where appropriate?
>
> WellI would like itbut no...
>
> >
> > Or a stupid workaround would be to have a fact that is that one line,
> and a
> > puppet template that adds the line. So puppet would manage the whole
> file but
> > the line would not be affected by a puppet run.
>
> Hummsorry I don't understand your workaround
>
> Thanks.
>
> JAS
> --
> Albert SHIH
> DIO bâtiment 15
> Observatoire de Paris
> 5 Place Jules Janssen
> 92195 Meudon Cedex
> France
> Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
> xmpp: j...@obspm.fr
> Heure local/Local time:
> jeu 14 jan 2016 17:46:08 CET
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/20160114164728.GA18250%40pcjas.obspm.fr
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUnqdW%3DOr1gDMWkDudJzC75jDC%3DDH8p6Am65MSbVVFAyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to manage half file.

[Trevor Vaughan]

Sorry...Hunter's!

Too early in the morning.

On Fri, Jan 15, 2016 at 6:07 AM, Trevor Vaughan <tvaug...@onyxpoint.com>
wrote:

> Albert's suggestion is probably your best bet at the least amount of work.
>
> First, create a custom fact that pulls that line out of your file.
> https://docs.puppetlabs.com/facter/3.1/custom_facts.html.
>
> Next, your template would have a placeholder for that item.
>
> my_template.erb
>
> ...usual_template...
> <%= @my_custom_fact %>
> ---remaining_template...
>
> This isn't a great solution but it's probably the easiest way to solve
> your problem quickly. I would not do this if that line is huge (some
> encoded binary blob or something).
>
> Trevor
>
> On Thu, Jan 14, 2016 at 11:47 AM, Albert Shih <albert.s...@obspm.fr>
> wrote:
>
>>  Le 13/01/2016 à 13:21:51-0800, Hunter Haugen a écrit
>> > Does the application have an "include" syntax that would allow you do
>> have one
>> > file that is one line that the application manages, and the file that
>> puppet
>> > manages includes it where appropriate?
>>
>> WellI would like itbut no...
>>
>> >
>> > Or a stupid workaround would be to have a fact that is that one line,
>> and a
>> > puppet template that adds the line. So puppet would manage the whole
>> file but
>> > the line would not be affected by a puppet run.
>>
>> Hummsorry I don't understand your workaround
>>
>> Thanks.
>>
>> JAS
>> --
>> Albert SHIH
>> DIO bâtiment 15
>> Observatoire de Paris
>> 5 Place Jules Janssen
>> 92195 Meudon Cedex
>> France
>> Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
>> xmpp: j...@obspm.fr
>> Heure local/Local time:
>> jeu 14 jan 2016 17:46:08 CET
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/20160114164728.GA18250%40pcjas.obspm.fr
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
>
> -- This account not approved for unencrypted proprietary information --
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXrXAsO8ZwAK3Yucwbh7LZmJ95cEofidBUK_aqoLuNA3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Possible to subscribe to all resources of a specific type?

[Trevor Vaughan]

Hi Ben,

A resource collector should do what you want
https://docs.puppetlabs.com/puppet/latest/reference/lang_collectors.html.

User<| |> ~> Resource['my_resource']

*should* work (not tested).

Thanks,

Trevor

On Tue, Jan 12, 2016 at 3:34 PM, Schofield <dbschofi...@gmail.com> wrote:

> Is it possible to subscribe to a specific type?  For example, refresh a
> resource if any resources of the type 'user' change?  If so what's the
> syntax?
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/89ed3145-96ad-4431-a5a1-f8b09f1e02f3%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/89ed3145-96ad-4431-a5a1-f8b09f1e02f3%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWExMFuykEariWVPHTfckAnCsQAuLqcyn8GRzmm%2BTLR4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Scaling with open source puppet 4?

[Trevor Vaughan]

Hi Ryan,

You should be able to follow the 3.X documentation to scale Puppet 4. Some
of the paths will be different, but the fundamental method should be the
same.

Trevor

On Mon, Dec 28, 2015 at 10:50 AM, Ryan Anderson <ryan.c.ander...@gmail.com>
wrote:

> I am using open source puppet 3.7 with a single server hosting the master
> and puppetdb (with puppetboard for reporting). I am at a point where I need
> to scale out to multiple masters at different data centers and split off
> puppetdb. However, I prefer to devote resources to scaling out with puppet
> 4. There are resources on how to do this with puppet 3.x, but the official
> documentation to scale open source puppet 4 is completely absent (
> https://docs.puppetlabs.com/guides/scaling_multiple_masters.html) and I
> have found few posts on the subject on this list or elsewhere. I know PE
> would be a good solution for me, but that is not a possibility. Can anyone
> please provide guidance on doing a split installation with open source
> puppet 4?
>
> I hope the lack of information is not a sign of Puppet Labs' commitment to
> open source waning and/or decreased use of puppet generally. I've taken a
> couple Puppet Labs classes and attended Puppetconf, but am not in a
> position to purchase PE to get around this, and I assume there must be
> others like me.
>
> Thanks,
> RCA
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/900eafe4-0d50-4b2a-ab89-fbbc34b61e1f%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/900eafe4-0d50-4b2a-ab89-fbbc34b61e1f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXSmHgfkJp_4MacL4y%2B1jxqDqdVOO5gHV1yufi69%2BuEaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Baltimore PUG Catalog Diff Tool with Beaker

[Trevor Vaughan]

Hi All,

Just wanted to let you know that the Baltimore PUG threw together a proof
of concept catalog diff tool for helping users upgrade their FOSS Puppet
code from Puppet 3 to Puppet 4.

The code can be found at
https://github.com/baltimore-puppet-users-group/2015_11_Beaker_Catalog_Diff
and we'd love to get some feature enhancements in there.

It was a good time getting it all to work and hopefully we'll be doing more
work like this in the future.

http://www.meetup.com/Baltimore-Puppet-User-Group/events/226530296/

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVEwXh1p0Um2vAve%3DtjtRWr5_6Fvp4TY2ysC3oCiLO9Ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] RHEL 7 - Satellite 6.1 - Puppet Locally

[Trevor Vaughan]

Hi Tom,

What's the content of test.pp?

Thanks,

Trevor

On Mon, Oct 26, 2015 at 9:47 AM, Tom Zurita <tzur...@gmail.com> wrote:

> We deploy our servers and use Puppet using Satellite 6.1.  I deployed a
> server and am trying to test modules locally and it NEVER works.
>
> cat /etc/puppet/puppet.conf
>
>
> [main]
>
> vardir = /var/lib/puppet
>
> logdir = /var/log/puppet
>
> rundir = /var/run/puppet
>
> ssldir = $vardir/ssl
>
>
> [agent]
>
> pluginsync  = true
>
> report  = true
>
> ignoreschedules = true
>
> daemon  = false
>
> ca_server   = blah
>
> certname= rhel7-test2.blah.edu
>
> environment = KT_SI_Org_Default_RHEL7_Prod_RHEL7_comp_CV_14
>
> # server  = blah
>
>
> [root@rhel7-test2 manifests]#  puppet config print modulepath
>
> /etc/puppet/modules:/usr/share/puppet/modules
>
>
> [root@rhel7-test2 manifests]# puppet module list
>
> /etc/puppet/modules
>
> ├── cis-puppet (???)
>
> ├── duritong-sysctl (v0.0.11)
>
> └── puppetlabs-stdlib (v4.9.0)
>
> /usr/share/puppet/modules (no modules installed)
>
>
> puppet apply --modulepath=/etc/puppet/modules
> /etc/puppet/modules/cis-puppet/manifests/test.pp
>
>
> I don't get errors just doesn't change a thing, nor does it show it
> running that script.
>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/f7a79794-97d8-49d2-8a03-f64f847fef38%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/f7a79794-97d8-49d2-8a03-f64f847fef38%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXE4QTgmVJ%3Ddj9YvURPQGdsAjGE%2BKKPO_9pxA1wzZrT%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] What is the preferred method for getting back a single custom fact now that facter -p is deprecated?

[Trevor Vaughan]

Got it, thanks for the update!

Trevor

On Fri, Oct 23, 2015 at 6:00 PM, Peter Huene <peter.hu...@puppetlabs.com>
wrote:

> Hi Trevor,
>
> On Fri, Oct 23, 2015 at 2:46 PM, Trevor Vaughan <tvaug...@onyxpoint.com>
> wrote:
>
>> While I'm a master of parsing clumped JSON by eye, not everyone might
>> be...
>>
>
> TL;DR: you may continue to use the `--puppet` option in Facter 3.0.2+.
>
> We reversed course on removing the `--puppet` option from Facter in 3.0.2
> as there was no suitable replacement in place ("puppet facts" just doesn't
> cut it).  While it's still considered to be "deprecated" in the sense that
> we don't like having a "reverse" dependency on Puppet from Facter, I don't
> think we have plans to implement a replacement any time soon.
>
> If you have a single location where your custom facts are stored, you may
> also pass the "--custom-dir" option to Facter to let it search the given
> directory for custom facts; it's an easy alternative if you're just hacking
> a custom fact together without a Puppet module in place.
>
>
>>
>> Thanks,
>>
>> Trevor
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
>> --
>> 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
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVkcY6h9uJYAmACogR0EAggNbfhnPGYQf4yoMJcpH6ebA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVkcY6h9uJYAmACogR0EAggNbfhnPGYQf4yoMJcpH6ebA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CACZQQfN2gfVw8ihdM-Acc-bnto4YHf6Pe_1gxFo_FQP-oxKFdg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CACZQQfN2gfVw8ihdM-Acc-bnto4YHf6Pe_1gxFo_FQP-oxKFdg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVsiis3Whr5vNARwo87eO2bxvXZhfZ3oFUUMwtg5rEfrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] What is the preferred method for getting back a single custom fact now that facter -p is deprecated?

[Trevor Vaughan]

While I'm a master of parsing clumped JSON by eye, not everyone might be...

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVkcY6h9uJYAmACogR0EAggNbfhnPGYQf4yoMJcpH6ebA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Security: Potential exposure of CA key under puppetserver

[Trevor Vaughan]

Hi Eric,

Will a CVE be issued for this?

Thanks,

Trevor

On Wed, Sep 30, 2015 at 12:47 AM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:

> We've identified and are fixing a condition in puppet where the
> auto-generated
> CA private key is created with too-leinent permissions. We feel the
> exposure is
> pretty limited (it would require a local user account on the CA system, to
> discover and copy/modify the CA key before additional puppet commands run)
> but
> will be releasing patched versions which do not have the problem. I wanted
> to
> post this publicly so users could evaluate their own site and remediate if
> necessary, in advance of an upstream software release.
>
> You could be affected if:
> - you used puppet server or puppet master to automatically generate a CA
>   keypair and certificate and have NEVER restarted the process
> - you never subsequently ran a puppet agent, cert, or other subcommands
>   which use the certificate subsystem, on the host with the CA keypair.
>
> You will not be affected if:
> - you run Puppet Enterprise to initialize your CA
> - you have ever run 'puppet agent' or other 'puppet cert' commands as root
> on the host with the keypair.
> - you have ever restarted your puppet master/puppet server process. Ever.
> Really.
>
> The immediate fix is to either:
> - run `puppet agent` as root on the server which has the CA key
> - as root, `chmod 660 $(puppet master --configprint cadir)/ca_key.pem`
>
> A huge thank you/merci to Francois Lafont for reporting this issue.
>
> For more details, see https://tickets.puppetlabs.com/browse/PUP-5274
>
> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
> puppet platform // coffee // techno // bicycles
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXoQcfPx_K1dtX55zjTSmNJci97aQCWmkiqZXWVBr%2BL8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Submit a talk for an upcoming Puppet Camp

[Trevor Vaughan]

Hi Kara!

Well, I suck at filling out forms on time I guess but I'm still willing to
present on Nov 10 if you'll have me.

Same topic as PuppetConf
https://puppetconf2015.sched.org/event/98c3ad1627995c252bad95018d93ac17?iframe=no==yes=no#.VgNlymwVhBc
.

I can also hit Atlanta and North Carolina if you would like.

Thanks,

Trevor

On Tue, Sep 15, 2015 at 2:40 PM, Kara Sowles <k...@puppetlabs.com> wrote:

> I wanted to remind everyone that we have several open CFPs for
> upcoming events, and I would love to see more people submitting talk
> proposals for them!
>
> Puppet Camp London: November 3
> http://goo.gl/forms/s99NPdqKdl
>
> Puppet Camp Washington, D.C.: November 10
> http://goo.gl/forms/iDXPgds20X
>
> Puppet Camp Stockholm: November 11
> http://goo.gl/forms/6a0VCvQ6yc
>
> Puppet Camp Melbourne: November 16
> http://goo.gl/forms/Y8RToIrqST
>
> Puppet Camp Singapore: November 19
> http://goo.gl/forms/6mIFPolzDb
>
> Puppet Camp Tampa, Florida: December 1
> http://goo.gl/forms/SvN5mckWFz
>
> Puppet Camp Atlanta, Georgia: December 3
> http://goo.gl/forms/IpkmyC8q5j
>
> Puppet Camp Charlotte, North Carolina: December 7
> http://goo.gl/forms/Ga0qFLcSDD
>
> Let me know if you have any questions.
>
> Kara Sowles
> Community, Puppet Labs
> http://puppetlabs.com/community
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAB9WyvktpHKRqyHRZNypWLCgzPHYjygV%2BV2JQ1SosfafApf%2BVg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoW0x42WZ0d8JzKQPu22C5Nv%3DtRpzt-jHRe%2B0Dj8OTPDTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] fact truth, string interpolation, and str2bool

[Trevor Vaughan]

If I'm remembering correctly, str2bool used to fail when passed a Boolean.

Therefore, to be safe in *all* cases, you would want to use the prescribed
method.

Trevor

On Tue, Sep 15, 2015 at 5:53 PM, Clay Caviness <c...@boobah.com> wrote:

> I'm going through our puppet configuration trying to get ready for an
> eventual upgrade to puppet 4.
>
> One thing I'm curious about, though, is the use of str2bool.
>
> In the introduction to the future parser in the 3.8 documentation (
> http://docs.puppetlabs.com/puppet/3.8/reference/experiments_future.html#facts-can-have-additional-data-types),
> the suggestion for having code that works in both puppet 3 and 4 is to:
> * Interpolate the fact into a string ("$is_virtual")…
> * …then pass the string to the stdlib str2bool function
> (str2bool("$is_virtual")).
>
> However, I'm not sure why interpolating into a string is necessary? If you
> pass a bool into str2bool, you get that bool right back out, and my tests
> (with puppet 3.8 and with and without --parser=future) show that
> interpolating into a string first isn't necessary.
>
> Is there a subtlety I'm missing?
>
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1de2bcbe-a2ee-4f3a-ae6d-79720f62dc96%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/1de2bcbe-a2ee-4f3a-ae6d-79720f62dc96%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXgj7iNQxKKECzPgdimj8T-AKFYxji5btGwrkvAeY-HRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Digest for puppet-users@googlegroups.com - 2 updates in 1 topic

[Trevor Vaughan]

The audit -> exec trigger was one that I hadn't thought about really and is
a valid use case. However, that does scream that a custom type is needed.

Trevor

On Mon, Sep 14, 2015 at 12:17 PM, Corey Osman <co...@logicminds.biz> wrote:

> I have actually used audit quite extensively at a previous client.
> Although most of that requirement can be replaced with a custom type and
> provider.  It was definitely good to use for triggering exec calls.
> On Sep 14, 2015 4:15 AM, <puppet-users@googlegroups.com> wrote:
>
>> puppet-users@googlegroups.com
>> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/puppet-users/topics>
>>  Google
>> Groups
>> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
>> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
>> Topic digest
>> View all topics
>> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/puppet-users/topics>
>>
>>- Do you use Audit attribute or "puppet inspect" ?
>><#14fcca5cc604662a_14fcb918cedbe472_group_thread_0> - 2 Updates
>>
>> Do you use Audit attribute or "puppet inspect" ?
>> <http://groups.google.com/group/puppet-users/t/a37ecfc7e0b7bf2b?utm_source=digest_medium=email>
>> Jo Rhett <jrh...@netconsonance.com>: Sep 14 02:01AM -0700
>>
>> I have numerous clients using the audit attribute to track changes to
>> files not managed by Puppet. This provides tripwire-like functionality for
>> observing changes to files not directly managed by Puppet. It also allows
>> for backing up each version of the file to the file bucket.
>>
>> Therefore I was a bit shocked to find that they planned to drop support
>> for this entirely, as per https://tickets.puppetlabs.com/browse/PUP-893 <
>> https://tickets.puppetlabs.com/browse/PUP-893>
>>
>> If you make use of audit or “puppet inspect”, or would like to use the
>> functionality provided for tripwire-like tracking of resource changes,
>> please add your comments to this issue.
>>
>> If you have been unable to get “puppet inspect” working with recent
>> Puppet 3 or Puppet 4 versions, you may want to track
>> https://tickets.puppetlabs.com/browse/PUP-5233 <
>> https://tickets.puppetlabs.com/browse/PUP-5233>
>>
>> --
>> Jo Rhett
>> Net Consonance : net philanthropy to improve open source and internet
>> projects.
>> Trevor Vaughan <tvaug...@onyxpoint.com>: Sep 14 05:45AM -0400
>>
>> Honestly, I don't know of anyone using the audit functionality. However, I
>> have only really dealt with Operating Systems that have excellent
>> real-time
>> Audit subsystems built in.
>>
>> Also, using Puppet to audit large recursive directories is quite slow and
>> will bloat your catalog to no end.
>>
>> Thanks,
>>
>> Trevor
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>> Back to top <#14fcca5cc604662a_14fcb918cedbe472_digest_top>
>> You received this digest because you're subscribed to updates for this
>> group. You can change your settings on the group membership page
>> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/puppet-users/join>
>> .
>> To unsubscribe from this group and stop receiving emails from it send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAO19zWgvidm1pzfb89R2qZnXZFSb37p_5r5mKi7eFZUNMvETmg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAO19zWgvidm1pzfb89R2qZnXZFSb37p_5r5mKi7eFZUNMvETmg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXXGvsNdWz21i9pfWh7nW1EQFCV4YYBW1WWK9M2kjhORw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet module - check if port is opened before running resource

[Trevor Vaughan]

In this case, you can have a fact that uses the code that you posted above.
Facts are just Ruby so you can pretty much do whatever you need and return
the boolean as the fact content.

However, you may need to get a bit fancy and use a confine to ensure that
only that one node is triggering the fact run and not every node in your
infrastructure.

The most precise way to do this would be to drop a file on the system whose
presence indicates that the fact should run and bind the confine to the
presence of that file.

More information on creating custom facts can be found at
https://docs.puppetlabs.com/facter/2.2/custom_facts.html.

Thanks,

Trevor

On Tue, Sep 15, 2015 at 10:28 AM, aldantas <an...@mosin.com.br> wrote:

> No, it is remote. I am deploying a application cluster that has some nodes
> dependencies, so basically in order to execute a script in one node I need
> to make sure first that the remote node is already listening on a specific
> port, if that node is not listening on that port I do not want to execute
> the script.
>
> I used to work with Chef before and it was easy to accomplish that with
> ruby blocks.
>
> require 'socket'require 'timeout'
> def port_open?(ip, port, seconds=1)
>   Timeout::timeout(seconds) do
> begin
>   TCPSocket.new(ip, port).close
>   true
> rescue Errno::ECONNREFUSED, Errno::EHOSTUNREACH
>   false
> end
>   endrescue Timeout::Error
>   falseend
>
>
> I'm not sure how I can use something like that in puppet, I don't seem to
> be able to pass puppet module variables to factors?  With custom functions,
> I can pass variables as arguments but I was having trouble to get a boolean
> value returned. I might have to play with that some more, I just thought I
> would ask to see if anybody had any working example of that.
>
> Thanks!!
>
>
> On Monday, September 14, 2015 at 7:01:00 PM UTC-7, Trevor Vaughan wrote:
>>
>> Is this the *local* host listening on that port, or some remote system?
>>
>> If it's the local host, then you would want to use a fact that calls
>> something like netstat or ss and returns a Boolean based on the result of
>> that port selection. You could also return all listening ports as a Hash
>> and go from there.
>>
>> Generally, Puppet would be managing the service that actually listens on
>> the port and you would simply include your manifest after starting that
>> service. However, without knowing your setup, it's difficult to tell if you
>> are in this situation.
>>
>> Thanks,
>>
>> Trevor
>>
>> On Mon, Sep 14, 2015 at 8:01 PM, aldantas <an...@mosin.com.br> wrote:
>>
>>> Hello,
>>>
>>> I am writing a puppet module and I am looking into a way to have a
>>> validation before trying to execute something in puppet.
>>>
>>> For example:
>>>
>>> If host is listing on port 3306 {
>>>
>>> file { 'name':
>>> ensure => file,
>>> }
>>>
>>> }
>>>
>>> or
>>>
>>> If host is listing on port 3306 {
>>>
>>> include '::module::manifest'
>>>
>>> }
>>>
>>>
>>> I am a little lost on how to accomplish this. I have tried creating a
>>> custom function and custom factor but I wasn't successful.
>>>
>>>
>>> Does anyone have any good solution for this?
>>>
>>>
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/7776a753-d752-4a90-81a6-5cd71de6a3aa%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/7776a753-d752-4a90-81a6-5cd71de6a3aa%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> h

Re: [Puppet Users] puppet module - check if port is opened before running resource

[Trevor Vaughan]

Is this the *local* host listening on that port, or some remote system?

If it's the local host, then you would want to use a fact that calls
something like netstat or ss and returns a Boolean based on the result of
that port selection. You could also return all listening ports as a Hash
and go from there.

Generally, Puppet would be managing the service that actually listens on
the port and you would simply include your manifest after starting that
service. However, without knowing your setup, it's difficult to tell if you
are in this situation.

Thanks,

Trevor

On Mon, Sep 14, 2015 at 8:01 PM, aldantas <an...@mosin.com.br> wrote:

> Hello,
>
> I am writing a puppet module and I am looking into a way to have a
> validation before trying to execute something in puppet.
>
> For example:
>
> If host is listing on port 3306 {
>
> file { 'name':
> ensure => file,
> }
>
> }
>
> or
>
> If host is listing on port 3306 {
>
> include '::module::manifest'
>
> }
>
>
> I am a little lost on how to accomplish this. I have tried creating a
> custom function and custom factor but I wasn't successful.
>
>
> Does anyone have any good solution for this?
>
>
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/7776a753-d752-4a90-81a6-5cd71de6a3aa%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/7776a753-d752-4a90-81a6-5cd71de6a3aa%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoU6%3DMsEYJqP9EE8D3TL-CWK1Ht6jjEJw8aqz%3Dj-h%3D8fYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Do you use Audit attribute or "puppet inspect" ?

[Trevor Vaughan]

Honestly, I don't know of anyone using the audit functionality. However, I
have only really dealt with Operating Systems that have excellent real-time
Audit subsystems built in.

Also, using Puppet to audit large recursive directories is quite slow and
will bloat your catalog to no end.

Thanks,

Trevor

On Mon, Sep 14, 2015 at 5:01 AM, Jo Rhett <jrh...@netconsonance.com> wrote:

> I have numerous clients using the audit attribute to track changes to
> files not managed by Puppet. This provides tripwire-like functionality for
> observing changes to files not directly managed by Puppet. It also allows
> for backing up each version of the file to the file bucket.
>
> Therefore I was a bit shocked to find that they planned to drop support
> for this entirely, as per https://tickets.puppetlabs.com/browse/PUP-893
>
> If you make use of audit or “puppet inspect”, or would like to use the
> functionality provided for tripwire-like tracking of resource changes,
> please add your comments to this issue.
>
> If you have been unable to get “puppet inspect” working with recent Puppet
> 3 or Puppet 4 versions, you may want to track
> https://tickets.puppetlabs.com/browse/PUP-5233
>
> --
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and
> internet projects.
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/C58F4BBB-CA33-431E-9191-05305FAF5312%40netconsonance.com
> <https://groups.google.com/d/msgid/puppet-users/C58F4BBB-CA33-431E-9191-05305FAF5312%40netconsonance.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoViJz%2Bv8iz_W8EghWyB5rCv1BiKq4iy4sbT1uznBq41DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a method for puppet to find all suid files?

[Trevor Vaughan]

Just out of curiosity, what's the benefit of making this a fact?

I'm thinking that this would be better relegated to a monitoring system,
not a configuration management system.

(Yes, you can use Puppet as a monitoring system but that's not really what
it is designed for and you'll end up slowing everything down over time.)

Thanks,

Trevor

On Tue, Sep 8, 2015 at 12:15 AM, Corey Osman <co...@logicminds.biz> wrote:

> As Trevor mentioned above this is something you want to control externally
> via cron and not puppet. I took a slightly different approach and used an
> external fact which allowed be to write a fact in bash.  There is no reason
> why you couldn't do this in a Ruby based fact but since all the original
> code was written in bash I used external facts simply to save time.
>
> https://gist.github.com/logicminds/2389d980f00333dcb48d
>
> The key item is that this fact alone takes 37 seconds to run so I decided
> to cache the result for 12 hours which obviously speeds up fact values
> retrieval.
>
> I wasn't crazy about having a bunch of random cron jobs to cache the value
> of 10+ facts so I built the control mechanism into the fact code itself so
> that it doesn't rely on cron or some other service.
>
> Hit me up privately as I might have more code to share that could be
> useful to you.
>
> Corey
> On Sunday, September 6, 2015 at 7:22:28 AM UTC-7, Trevor Vaughan wrote:
>>
>> This rule will let you know when an SUID binary is *executed*
>> https://github.com/simp/pupmod-simp-auditd/blob/master/templates/base.erb#L50:L55
>> .
>>
>> I would not run any filesystem searches from Puppet, I would relegate
>> those to cron+syslog so that you can better control the amount of I/O churn
>> on your system over time.
>>
>> Thanks,
>>
>> Trevor
>>
>> On Fri, Sep 4, 2015 at 2:54 PM, Sean <smal...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm using a module from the Forge to manage auditd rules, the module
>>> works quite well and managing rules is very easy.  The hard part is that
>>> there's a requirement to audit use SUID files on each system.  With out
>>> knowing exactly what files are SUID on every server in the field, since
>>> there are several linux flavors and versions, I'm finding myself thinking
>>> the only way to accomplish this is to write a custom fact to hold all the
>>> SUID files as an array, then pass the array to the resource creator.  I
>>> just don't relish the idea of running a find command from / every 30
>>> minutes.
>>>
>>> Might anyone have any better ideas?
>>>
>>> Thank you kindly!
>>>
>>> --
>>> 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 email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/e848e8ab-0a96-4934-9382-42f3b828d529%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/e848e8ab-0a96-4934-9382-42f3b828d529%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b3f67609-2abb-431d-bd77-29860fc909ea%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/b3f67609-2abb-431d-bd77-29860fc909ea%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVKSM3UzYQYNv92UbfxtAW3rJVUP4V10yW_Yg795GoAPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is there a method for puppet to find all suid files?

[Trevor Vaughan]

This rule will let you know when an SUID binary is *executed*
https://github.com/simp/pupmod-simp-auditd/blob/master/templates/base.erb#L50:L55
.

I would not run any filesystem searches from Puppet, I would relegate those
to cron+syslog so that you can better control the amount of I/O churn on
your system over time.

Thanks,

Trevor

On Fri, Sep 4, 2015 at 2:54 PM, Sean <smalde...@gmail.com> wrote:

> Hi,
>
> I'm using a module from the Forge to manage auditd rules, the module works
> quite well and managing rules is very easy.  The hard part is that there's
> a requirement to audit use SUID files on each system.  With out knowing
> exactly what files are SUID on every server in the field, since there are
> several linux flavors and versions, I'm finding myself thinking the only
> way to accomplish this is to write a custom fact to hold all the SUID files
> as an array, then pass the array to the resource creator.  I just don't
> relish the idea of running a find command from / every 30 minutes.
>
> Might anyone have any better ideas?
>
> Thank you kindly!
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e848e8ab-0a96-4934-9382-42f3b828d529%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/e848e8ab-0a96-4934-9382-42f3b828d529%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX4cRCG39aSaSaLbu16Xpz27nMwNqd%3D_emN3kqA_TDt_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] vhosts with multiple ip addresses with apache Forge Module

[Trevor Vaughan]

Looks like that is, indeed, a bug.

I would file a bug report over at
https://tickets.puppetlabs.com/browse/MODULES/

Trevor

On Wed, Sep 2, 2015 at 10:17 AM, <benediktb1...@gmail.com> wrote:

> Hello,
>
> within the last project, I recognized that there is no way to generate one
> vhost with more than one ip address with the apache module of puppetlabs
> Forge Modules.
>
> Am I wrong? Or is there a good reason that it doesn't work?
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/3a2dd027-e5e0-495e-b010-898c08bba609%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/3a2dd027-e5e0-495e-b010-898c08bba609%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVVBXM%3D791LEf87EhATOv%3DkPhJ959GjnpajmL5S6mGShg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Can I store my hiera data file inside puppet agent side

[Trevor Vaughan]

Hi Malintha,

Well, the answer is that you can place it on the client but I'm not sure
what you're trying to accomplish as it won't be used by client side
activities.

This is because the values can change during compile time based on
variables that you set in your code (and facts).

If you could provide some additional details, it would be easier to provide
you with an answer that might meet your goals.

Thanks,

Trevor

On Mon, Aug 31, 2015 at 12:44 AM, Malintha Adikari <malin...@wso2.com>
wrote:

> Hi,
>
> Can I store and use my hiera data file in my puppet agent machine rather
> than storing in in puppet master  ? Then how can I do it ?
>
> Regards,
> Malintha
>
> --
> 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
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d1f8e027-ea7d-4a56-bce9-93e7f4b12a78%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d1f8e027-ea7d-4a56-bce9-93e7f4b12a78%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUgNwBxxzPSGU9Ur1Z1E5f9HNVKBjb0T-Lar48edxh8Tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How do you track large lists of modules?

[Trevor Vaughan]

Here are a few other items passed along to me:

* There's no way to make strings stop trying to add it's own default class
parameters. $::foo::params::bar isn't a very useful default besides to say
g look at the code.

* There wasn't a current way to document inline code and some of the YARD
parameters don't map well to Puppet code.

* Rendering legacy RDoc works, but renders dumb html instead of the current
puppet doc output which hurts when documenting class parameters.

I think that there are bugs reported out there for most of this but I ran
strings this morning and ran into most of them still.

Thanks,

Trevor

On Sat, Aug 29, 2015 at 1:05 AM, Trevor Vaughan tvaug...@onyxpoint.com
wrote:

 Hi Lindsey,

 These may be fixed (hoping!)

 1) The ability to run it as a Gem

 2) The ability to generate docs for all of your modules without 'strings'
 being part of the bunch (see #1)

 3) The ability to point at a directory and have strings just parse
 everything without needing to have it in your modulepath (see #1)

 4) If you're using RVM (or something like it), you'll run into issues with
 Gems and Gempaths unless you do some fancy shenanigans with your modulepath
 (which I've never gotten to work properly)

 5) I haven't been able to successfully get it to output a consolidated
 document set containing all of my modules which are formatted in the legacy
 style.

 Also, it sticks cruft all over my modules when I'd much rather be able to
 stick the docs all together in a single location.

 100% willing to admit that I might be doing something wrong here but the
 way that I *expect* it to work is:

 $ puppet-strings /path/to/my/development/stack/modules

 Output: puppet_doc/index.html and other stuff

 Faces are fun until you start trying to use them across 3 different
 versions of Ruby and not have them inject into your working module set.

 Thanks,

 Trevor

 On Fri, Aug 28, 2015 at 9:56 PM, Lindsey Smith l.sm...@puppetlabs.com
 wrote:



 On Fri, Aug 28, 2015 at 5:53 PM, Trevor Vaughan tvaug...@onyxpoint.com
 wrote:

 Hi Leam,

 We use Git Submodules to collect our various modules together and add
 comments to the headers of the files.

 Unfortunately, 'puppet doc' was deprecated and 'strings' isn't quite
 ready for prime time.


 What do you think is missing from puppet strings?



 The new skeleton suggests moving all of the information to a README.md
 in each module and we're slowly getting there but it's quite time consuming.

 Trevor

 On Fri, Aug 28, 2015 at 5:00 PM, leam hall leamh...@gmail.com wrote:

 I'm wondering how people track large lists of modules, to ensure new
 team members know which does what, when the last time a module was reviewed
 for usefulness, etc. How do you handle growth and complexity?

 Leam


 --
 Mind on a Mission http://leamhall.blogspot.com/

 --
 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 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699

 -- This account not approved for unencrypted proprietary information --

 --
 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 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCi-gVKVp6wgL2VTo%2BWQ13y3FHLsGuUoPKzGOD98ywEA%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCi-gVKVp6wgL2VTo%2BWQ13y3FHLsGuUoPKzGOD98ywEA%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAPyei8XedeyxUHTVoPCO8frpZ7qz0bZsA_uu7aFfVjZ_8qmZRQ%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CAPyei8XedeyxUHTVoPCO8frpZ7qz0bZsA_uu7aFfVjZ_8qmZRQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699

 -- This account not approved for unencrypted proprietary information --




-- 
Trevor Vaughan
Vice President, Onyx Point

Re: [Puppet Users] How do you track large lists of modules?

[Trevor Vaughan]

Hi Lindsey,

These may be fixed (hoping!)

1) The ability to run it as a Gem

2) The ability to generate docs for all of your modules without 'strings'
being part of the bunch (see #1)

3) The ability to point at a directory and have strings just parse
everything without needing to have it in your modulepath (see #1)

4) If you're using RVM (or something like it), you'll run into issues with
Gems and Gempaths unless you do some fancy shenanigans with your modulepath
(which I've never gotten to work properly)

5) I haven't been able to successfully get it to output a consolidated
document set containing all of my modules which are formatted in the legacy
style.

Also, it sticks cruft all over my modules when I'd much rather be able to
stick the docs all together in a single location.

100% willing to admit that I might be doing something wrong here but the
way that I *expect* it to work is:

$ puppet-strings /path/to/my/development/stack/modules

Output: puppet_doc/index.html and other stuff

Faces are fun until you start trying to use them across 3 different
versions of Ruby and not have them inject into your working module set.

Thanks,

Trevor

On Fri, Aug 28, 2015 at 9:56 PM, Lindsey Smith l.sm...@puppetlabs.com
wrote:



 On Fri, Aug 28, 2015 at 5:53 PM, Trevor Vaughan tvaug...@onyxpoint.com
 wrote:

 Hi Leam,

 We use Git Submodules to collect our various modules together and add
 comments to the headers of the files.

 Unfortunately, 'puppet doc' was deprecated and 'strings' isn't quite
 ready for prime time.


 What do you think is missing from puppet strings?



 The new skeleton suggests moving all of the information to a README.md in
 each module and we're slowly getting there but it's quite time consuming.

 Trevor

 On Fri, Aug 28, 2015 at 5:00 PM, leam hall leamh...@gmail.com wrote:

 I'm wondering how people track large lists of modules, to ensure new
 team members know which does what, when the last time a module was reviewed
 for usefulness, etc. How do you handle growth and complexity?

 Leam


 --
 Mind on a Mission http://leamhall.blogspot.com/

 --
 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 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699

 -- This account not approved for unencrypted proprietary information --

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCi-gVKVp6wgL2VTo%2BWQ13y3FHLsGuUoPKzGOD98ywEA%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCi-gVKVp6wgL2VTo%2BWQ13y3FHLsGuUoPKzGOD98ywEA%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAPyei8XedeyxUHTVoPCO8frpZ7qz0bZsA_uu7aFfVjZ_8qmZRQ%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CAPyei8XedeyxUHTVoPCO8frpZ7qz0bZsA_uu7aFfVjZ_8qmZRQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWK_ey_VOZ%3DLKFc3ut2y3oufr%2BYqQNzyO8G0Nu%2BLgUg3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How do you track large lists of modules?

[Trevor Vaughan]

Hi Leam,

We use Git Submodules to collect our various modules together and add
comments to the headers of the files.

Unfortunately, 'puppet doc' was deprecated and 'strings' isn't quite ready
for prime time.

The new skeleton suggests moving all of the information to a README.md in
each module and we're slowly getting there but it's quite time consuming.

Trevor

On Fri, Aug 28, 2015 at 5:00 PM, leam hall leamh...@gmail.com wrote:

 I'm wondering how people track large lists of modules, to ensure new team
 members know which does what, when the last time a module was reviewed for
 usefulness, etc. How do you handle growth and complexity?

 Leam


 --
 Mind on a Mission http://leamhall.blogspot.com/

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CACv9p5oKQNhGSxe9JFbrofTes3Z_bievoea6gs7U%2BZ0sK0FYag%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXCi-gVKVp6wgL2VTo%2BWQ13y3FHLsGuUoPKzGOD98ywEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] comments on the Type system and some questions

[Trevor Vaughan]

This seems a bit better:

define foo(
 Enum[present, absent] $ensure = present,
 Optional[String]$ssh_authorized_file   = undef,
 Optional[String]$email   = undef,
 Optional[Integer]   $uid  = undef,
 Optional[Integer]   $gid  = undef,
 Variant[Boolean, String]$sudoer = false,
 Boolean   $setup_shell  = false,
 Boolean   $setup_rbenv  = false
   ) {

It's relatively easy to achieve with Tabular but I do agree on the advanced
structs, that's some crazy.

This is the best that I could do:

Struct[
  {
mode= Enum[read, write, update],
path  = Optional[String[1]],
NotUndef[owner] = Optional[String[1]]
 }
]

I honestly have no idea if that will process correctly though, it's
massively tedious, and it would probably need a lot of commenting.

Trevor

On Thu, Jul 30, 2015 at 10:36 AM, R.I.Pienaar r...@devco.net wrote:

 hello,

 I've done a few little things with the type system and really like what it
 achieves,
 was able to find a few bad data items in my hiera data and it saves on a
 lot of the
 super annoying validation function calls.

 The syntax though is pretty difficult to use, consider:

define foo(
  Enum[present, absent] $ensure   = present,
  Optional[String] $ssh_authorized_file   = undef,
  Optional[String] $email = undef,
  Optional[Integer] $uid  = undef,
  Optional[Integer] $gid  = undef,
  Variant[Boolean, String] $sudoer= false,
  Boolean $setup_shell= false,
  Boolean $setup_rbenv= false
) {

 So this has a few issues for me:

 Reading it, I just don't see the property names now, its become a real
 effort
 to read this.

$ssh_authorized_file Optional[String] = undef,

 seems better for this use case to me and this is probably going to be the
 most
 often used use case.

 This gets much worse when we involve more complex type definitions, I
 can't imagine
 ever using a full on Struct definition here for example it would render it
 entirely
 unreadable and be impossible to maintain

 How would you ever fit this into a param declaration and maintain
 readability:

Struct[{mode= Enum[read, write, update],
path= Optional[String[1]],
NotUndef[owner] = Optional[String[1]]}]

 This leads to my 2nd question, I couldn't find a way to make my own
 abstract
 types.

 Consider this hypothetical with made up syntax and all:

site.pp:
typedef MyData Struct[{mode = Enum[read, write, update],
   path= Optional[String[1]],
   NotUndef[owner] = Optional[String[1]]}]

foo.pp:
define foo(Mydata $data) {

 this would improve matters a whole lot.  Does a typedef like feature
 exist? I couldn't
 find anything and tried a few things but failed


 ---
 R.I.Pienaar

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/143546306.116227.1438266987939.JavaMail.zimbra%40devco.net
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXyp8fCPdna4v_%2B1oMwWfjgRu9X4fT6ZHONnfz5ZfdM_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetserver does not sign its certificate

[Trevor Vaughan]

Hmm...I think you'll need to run 'puppet cert' by hand to set up the CA
prior to firing off the Puppet Server.

I don't know that it's a bug, but it's certainly a documentation issue if
you have to do this.

Thanks,

Trevor

On Sun, Jul 19, 2015 at 5:22 PM, Felix Frank 
felix.fr...@alumni.tu-berlin.de wrote:

 Hi,

 something I noticed when trying a simple puppetserver setup.

 I installed puppetserver from PC1 on a Debian 7 box (will try Debian 8
 once PC1 has puppetserver for it) and just started the service. It fails
 like this:

 Exception in thread main java.lang.IllegalStateException: Cannot
 initialize master with partial state; need all files or none.
 Found:
 /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.net.pem
 Missing:
 /etc/puppetlabs/puppet/ssl/certs/puppet.example.net.pem

 I helped myself by launching the WEBrick master briefly, which will sign
 the master certificate. After that, puppetserver starts up fine.

 Am I Doing It Wrong? Feels like a bug.

 Cheers,
 Felix

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/55AC1505.3050307%40Alumni.TU-Berlin.de
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVydDDWTNz%2B0zb0CBOsERWuG4oZmit%3DU0j2viYK__TzFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Case of the missing Ruby file

[Trevor Vaughan]

Hi Peter,

I would *highly* recommend using something like RVM to manage your ruby
installations for testing. This way you can ensure a clean environment and
also be sure that you don't have any conflicting modules or environment
pollution.

I'm guessing that there's something wrong with your GEM_PATH, but it could
be any number of things including conflicts with the system Ruby.

Thanks,

Trevor

On Mon, Jul 20, 2015 at 9:39 AM, Peter Berghold salty.cowd...@gmail.com
wrote:

 Hi folks,

 I've bravely stepped out into the world of writing tests for my Puppet
 modules to ensure code quality.  Have run into an issue.  My
 spec/spec_helper.rb has one line.

 require 'puppetlabs_spec_helper/module_spec_helper'

 I run rake spec and this happens:

 spec/spec_helper.rb:1:in `require': no such file to load --
 puppetlabs_spec_helper/module_spec_helper (LoadError)
 from /home/pb869e/src/pb869e-attbind/spec/spec_helper.rb:1
 -- and more---

 I did a  find /usr -name  module_spec_helper.rb  and it shows up here:

 /usr/lib/ruby/gems/1.8/gems/puppetlabs_spec_helper-0.10.3/lib/puppetlabs_spec_helper/module_spec_helper.rb

 so why isn't it loading?

 thoughts?

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAArvnv2-4L5qM4iLvNmnjXEAKs2Xi79SJDxqwmWOfKZj-%2BCPeQ%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CAArvnv2-4L5qM4iLvNmnjXEAKs2Xi79SJDxqwmWOfKZj-%2BCPeQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoXX63%2BUH-QVt2M-1TchotA_C6suT7iWArxzwm2hSgSvig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] [announce] puppetlabs-concat 2.0.x release deletion

[Trevor Vaughan]

Hi Bryan,

I'm sorry to hear about this as I have a lot of interest in this particular
topic.

So, I have a Native Concat (with the latest version here:
https://github.com/simp/pupmod-simp-concat) and Richard Clamp wrote Datacat
(https://github.com/richardc/puppet-datacat) which took a similar, but
different approach.

I apologize if I missed it, but is there a document that I can hit
regarding the development of this new capability?

It would be great if we could argue the three approaches so that the needs
that we had when we developed our versions are met in the Puppet Labs
supported version.

I'm 100% behind tossing my code if someone else is going to do the heavy
lifting but it needs to meet my requirements to be able to integrate it
successfully.

Thanks,

Trevor

On Thu, Jun 11, 2015 at 5:42 PM, Bryan Jen bryan@puppetlabs.com wrote:

 If you aren’t using puppetlabs-concat or are still using the
 puppetlabs-concat module with version 1.x you don’t need to continue
 reading. But, if you’re using puppetlabs-concat 2.0.x...

 tl;dr - we have uncovered an issue in the Puppet core that impacts the
 puppetlabs-concat 2.0.x series and are deleting those releases from the
 forge. Please downgrade your environments to use puppetlabs-concat 1.2.x.

 We recently reworked the puppetlabs-concat module to transition from an
 exec running a ruby script to concatenate files together to a native type
 (hooray!). This gave us vast performance improvements, but with the way the
 type was implemented we ended up running into a Puppet bug (
 https://tickets.puppetlabs.com/browse/PUP-1963)
 that we can’t effectively work around with the existing code. Due to this,
 we’re pulling the 2.0.x release series. The Puppet bug was causing us to
 not properly propagate notify and subscribe metaparameters triggered by
 changes in puppetlabs-concat resources. This means that, for example,
 services subscribing to concat resources will not get restarted when the
 configuration file is updated.

 To mitigate these issues, the puppetlabs-concat 2.0.x releases will be
 deleted from the forge. They will still be available for download but will
 not be installable using the PMT. We are still hoping to rework
 puppetlabs-concat to use a native type, however we don’t have a firm
 timeline for when that work will happen.

 --
 Bryan Jen
 *bryan@puppetlabs.com bryan@puppetlabs.com*
 Modules Software Engineer

 *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
 Oregon! Join us October 5-9.*
 *Register now to take advantage of the Early Adopter discount
 https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter
  *
 *—**save $349!*

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-dev/CAHak91XrJrq%3DWTa03t1RTn%3DNowwHrPxL_qRDE%2B4Qr3j7o4%3DPDQ%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-dev/CAHak91XrJrq%3DWTa03t1RTn%3DNowwHrPxL_qRDE%2B4Qr3j7o4%3DPDQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVaS4fPe_3Z7N7dviOkQ1f6zBux0cT4d_8PcYtG2TDqUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 8K node infrastructure and CA setup

[Trevor Vaughan]

Hi Corey,

That setup should work just fine and be even easier now that everything has
a solid set of certs that don't cross over at all.

If you're using PE, be sure to properly generate your role certificates
that are used by the Console, ActiveMQ, etc...

Trevor

On Mon, Jun 8, 2015 at 10:25 PM, Corey Osman co...@logicminds.biz wrote:

 Has anybody used this setup before?  Any caveats?


 https://docs.puppetlabs.com/puppet/3.8/reference/config_ssl_external_ca.html#option-3-two-intermediate-cas-issued-by-one-root-ca

 Does this still apply when using puppet server 2.1?


 Corey

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/7E32D1B6-A700-4643-B210-BD0F28738B9C%40logicminds.biz
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVa%3D3n9WPk1B7riQtpC9WZ%2B3LPPCN7ZJdo66ozS7ubb6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] New MCollective Plugin for OpenSCAP Scanning

[Trevor Vaughan]

I apologize for this Walid, the post got removed by mistake.

I have corrected this and the content is back online.

Thanks for your interest!

Trevor

On Sat, May 16, 2015 at 1:05 PM, Walid walid.sha...@gmail.com wrote:

 Hi Trevor

 the link is not working for me, it points to three blogs none of them are
 related to mco

 thanks,

 Walid

 On 14 May 2015 at 05:10, Trevor Vaughan tvaug...@onyxpoint.com wrote:

 Hi All,

 I presented a piece on a proof of concept that I put together to perform
 OpenSCAP scans against systems using MCollective.

 I thought that some of you might be interested. The relevant information
 is all linked from my post at
 http://www.onyxpoint.com/distributed-openscap-scanning-with-mcollective/.

 Thanks,

 Trevor

 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699
 tvaug...@onyxpoint.com

 -- This account not approved for unencrypted proprietary information --

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWJC749jmsXfwERsC8YDeodhN2DbDL6NG4dvczNa%3DS8cg%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWJC749jmsXfwERsC8YDeodhN2DbDL6NG4dvczNa%3DS8cg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAN4dctq04a42eon9_CXeeVxQWV0k0WYK3ZMA7WVUpeKhCfpe2A%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-users/CAN4dctq04a42eon9_CXeeVxQWV0k0WYK3ZMA7WVUpeKhCfpe2A%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoUk0%3Dm2-nMtO5cjJ4SQ_2kgU3QX1uGow1gyox%2B1zNWzKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Fast track to learning Puppet?

[Trevor Vaughan]

I think you may have just created a new shirt for the next conf!

On Fri, May 15, 2015 at 9:12 AM, jcbollinger john.bollin...@stjude.org
wrote:



 On Thursday, May 14, 2015 at 1:03:54 PM UTC-5, LinuxDan wrote:

 IMHO, there is no One Tool, but rather a combination of Tools That Do A
 Few Things Very Well.



 Haven't you ever thrown Puppet into your fireplace?

 One Tool to rule them all, one tool to find them.
 One tool to bring them all, and in Oregon to bind them.


 :-)

 John

 --
 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
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/03ec5674-f7f2-4f2e-8d55-ff93236c2e27%40googlegroups.com
 https://groups.google.com/d/msgid/puppet-users/03ec5674-f7f2-4f2e-8d55-ff93236c2e27%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX3O%3DOaxsC%2B2fqkYMsLgBUdXKW_gEdfdTrsKUfA9Ny9Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Learning Custom Types Module

[Trevor Vaughan]

Terribly sorry to those of you having trouble with the initial release.

I neglected to include the 'tests' directory which is required by the
Rakefile.

This has been fixed and uploaded to the Forge.

Thanks!

Trevor

On Wed, May 13, 2015 at 10:16 PM, Trevor Vaughan tvaug...@onyxpoint.com
wrote:

 Hi All,

 Yesterday, while at Puppet Camp DC, I pushed a module to the forge that's
 meant for learning the execution flow of custom types and providers.

 You can download it from the forge using 'puppet module install
 onyxpoint-learning_custom_types' or you can fork it on GitHub at
 https://github.com/onyxpoint/onyxpoint-learning_custom_types.

 This is an extension of my presentation on Types and Providers as
 presented last year at Puppet Camp DC 2014.

 Happy Hacking!

 Trevor

 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699
 tvaug...@onyxpoint.com

 -- This account not approved for unencrypted proprietary information --




-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoVoj%3DOXs58jQirBs%2B0hKSuuLOw3aUrUy4_twFqrQ5k3fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] New MCollective Plugin for OpenSCAP Scanning

[Trevor Vaughan]

Hi All,

I presented a piece on a proof of concept that I put together to perform
OpenSCAP scans against systems using MCollective.

I thought that some of you might be interested. The relevant information is
all linked from my post at
http://www.onyxpoint.com/distributed-openscap-scanning-with-mcollective/.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWJC749jmsXfwERsC8YDeodhN2DbDL6NG4dvczNa%3DS8cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Learning Custom Types Module

[Trevor Vaughan]

Hi All,

Yesterday, while at Puppet Camp DC, I pushed a module to the forge that's
meant for learning the execution flow of custom types and providers.

You can download it from the forge using 'puppet module install
onyxpoint-learning_custom_types' or you can fork it on GitHub at
https://github.com/onyxpoint/onyxpoint-learning_custom_types.

This is an extension of my presentation on Types and Providers as presented
last year at Puppet Camp DC 2014.

Happy Hacking!

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX5Ue4dzofi%3DO1MRJtNviMr%2BYMfg2cT1uz2OSfA2x6N1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.