Re: [Puppet Users] facter 3.2 global custom facts directory?

[dkoleary]

Thanks for the response. I'm pretty sure I tried /etc/faster/facts.d; but, I'll 
confirm that.  

Thanks again.

-- 
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/2dacc5a3-1b67-4ec3-b2f0-0b338ceaa2b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] facter 3.2 global custom facts directory?

[Christopher Wood]

All the custom facts here in /etc/facter/facts.d have worked just fine across 
the facter 2.4.4 -> facter 3.1.6 upgrade.

https://docs.puppet.com/facter/3.1/custom_facts.html

On Fri, May 27, 2016 at 12:28:50PM -0700, dkoleary wrote:
>Hey;
>I'm drafing some custom facts that I would like to have available to
>everyone even outside of puppet.  The facts themselves work just fine for
>root and will work for normal users if I specify the --external-dir
>option:
> 
>$ sudo facter env                                     
>tst
>$ facter --external-dir=/opt/puppetlabs/facter/facts.d env
>tst
>Without that, facter run as a normal user doesn't find the script. Is
>there a config file somewhere that I can specify, globally, that custom
>facts are in /opt/puppetlabs/facter/facts.d or a default global directory
>(facter --debug doesn't seem to show one...)? Alternatively, I could set
>an alias in /etc/profile so everyone gets it but that seems like a bit of
>a kludge.
>Any info is appreciated.
>Thanks
>Doug O'Leary
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/a9867381-4b0d-457e-aea3-173730ac86cf%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/a9867381-4b0d-457e-aea3-173730ac86cf%40googlegroups.com?utm_medium=email&utm_source=footer
>3. 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/20160527203839.GA22243%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] facter 3.2 global custom facts directory?

[dkoleary]

Hey;

I'm drafing some custom facts that I would like to have available to 
everyone even outside of puppet.  The facts themselves work just fine for 
root and will work for normal users if I specify the --external-dir option:

$ sudo facter env 
tst
$ facter --external-dir=/opt/puppetlabs/facter/facts.d env
tst

Without that, facter run as a normal user doesn't find the script. Is there 
a config file somewhere that I can specify, globally, that custom facts are 
in /opt/puppetlabs/facter/facts.d or a default global directory (facter 
--debug doesn't seem to show one...)? Alternatively, I could set an alias 
in /etc/profile so everyone gets it but that seems like a bit of a kludge.

Any info is appreciated.

Thanks

Doug O'Leary

-- 
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/a9867381-4b0d-457e-aea3-173730ac86cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet "autoconfigured" clients on AWS - classes from EC2 tags/userdata

[Martin Langhoff]

On Fri, May 27, 2016 at 6:51 AM, Gareth Rushgrove 
wrote:

>
> There are lots of hints and tips in this white paper.
>
>
> https://puppet.com/blog/making-life-puppet-and-aws-or-other-cloud-services-easier
>
> In particular it covers using the policy based autosigning and trusted
> facts to secure doing what I think you're doing.
>

Thank you. It mostly covers other topics around these practices, but not
the specific point I am trying to figure out. At least not that I can see
(maybe it's hiding somewhere?).

To recap what I am looking for: I want to build VMs (on AWS or something
else) that Puppet has no name for, using EC2 tags and userdata (and similar
facilities on RHEV-M, VMWare etc) _to list a number of puppet modules and
puppet variables_.

What I have seen proposed/used is to read in data from EC2 tags and
userdata via facter, and use conditionals in puppet code. While workable,
this means writing a lot of pointless conditionals in puppet code.

What I would prefer is a bit of magic "include all classes listed by name
in this variable", like it's done with hiera classes.

cheers,



m
-- 
 martin.langh...@gmail.com
 - ask interesting questions  ~  http://linkedin.com/in/martinlanghoff
 - don't be distracted~  http://github.com/martin-langhoff
   by shiny stuff

-- 
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/CACPiFCLDCYN5znaOaM74ren-ZzNhrk3ytf3PgzPoxUNYv4YpkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 3.8.5 Master with 3.7.2 Agents

[Rob Nelson]

IME you definitely won't have issues with 3.7.2 agents talking to a 3.8.5
master.

When you are ready to move to puppet 4, however, the upgrade docs say that
the agents should all hit 3.8 before you upgrade the master to 4.latest.
However, I skipped that step in my upgrade and 3.7.x agents talked fine
with 4.3.x (latest when I did this). I can't say if the docs are over
protective, or if I just missed all the cases where that breaks something.

On Friday, May 27, 2016, christg76  wrote:

> Hi, background here is that I want to use both Master and agents from the
> Debian repo. The Master runs on Jessie (3.8.5 from the backports), and some
> agents still on wheezy (3.7.2 from the backports).
> This is not a new install, but rather an intermediate upgrade to the last
> Puppet 3 version, before moving on to 4 and Puppet Server.
> Is anybody aware of issues with 3.8.5 Master and 3.7.2 Agents? Is there
> any reason why I should not be running this setup for a while? Cant see
> anything pressing from the release notes..
>
> Many Thanks,
> Chris
>
> --
> 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/a19fc9f0-8636-489e-bf8a-aaeec46040ab%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Rob Nelson
rnels...@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/CAC76iT_wOQ%2Bbt-T%3DZNEJbLQBA0DRcP21By9JLr9Kp6UDCc8ZUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet "autoconfigured" clients on AWS - classes from EC2 tags/userdata

[Gareth Rushgrove]

On 26 May 2016 at 22:11, Martin Langhoff  wrote:
> Hi Puppeteers,
>
> folks are mapping "role" from EC2 tags or userdata into a `case`
> statement in site.pp to choose a pre-built configuration.
>
> I wonder whether there is a way to bring in a listing of classes, as
> can be done with hiera (`hiera_include("classes")`).
>

There are lots of hints and tips in this white paper.

https://puppet.com/blog/making-life-puppet-and-aws-or-other-cloud-services-easier

In particular it covers using the policy based autosigning and trusted
facts to secure doing what I think you're doing.

Obviously I'm biased as I now work at Puppet, but it's definitely worth a read.

Gareth

> thoughts?
>
>
>
> m
> --
>  martin.langh...@gmail.com
>  -  ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  ~ http://docs.moodle.org/en/User:Martin_Langhoff
>
> --
> 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/CACPiFCJK%2BAAVgpdo7LBi_H1AGfKyuF9HJbPaD21FMn_dcQzFDg%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/msgid/puppet-users/CAFi_6yKOhovji58TXZGOwKj7p3Gw_wLtVx0i4KpJTrm%3Du_mKcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] 3.8.5 Master with 3.7.2 Agents

[christg76]

Hi, background here is that I want to use both Master and agents from the 
Debian repo. The Master runs on Jessie (3.8.5 from the backports), and some 
agents still on wheezy (3.7.2 from the backports).
This is not a new install, but rather an intermediate upgrade to the last 
Puppet 3 version, before moving on to 4 and Puppet Server.
Is anybody aware of issues with 3.8.5 Master and 3.7.2 Agents? Is there any 
reason why I should not be running this setup for a while? Cant see 
anything pressing from the release notes..

Many Thanks,
Chris

-- 
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/a19fc9f0-8636-489e-bf8a-aaeec46040ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.