[Puppet Users] Setting puppet up to use a dns alias as a servername
Can I configure puppet to use a DNS name that would work on two different hosts? For example, I have host1 and host2.example.com. I'd like agents to connect to "puppet.example.com" which will point to one of these. I wamt to be sure agents can connect to either without certificate errors. How do I configure the puppet.conf certname/servername, and generate the master certificate such that agents will happily connect to host1 and host2 without complaining? I've experimented and googled but can't seem to figure out what's the right approach. -- 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/8f1380d0-b58e-4bac-a48a-d91eccc60633%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Setting puppet up to use a dns alias as a servername
'dns_alt_names' is the config you're looking for... https://puppet.com/docs/puppetserver/5.1/scaling_puppet_server.html#creating-and-configuring-compile-masters provides more info on running multiple Puppet servers. HTH Gav On Wednesday, 2 May 2018 11:02:16 UTC+1, buoyant_puppy wrote: > > Can I configure puppet to use a DNS name that would work on two different > hosts? For example, I have host1 and host2.example.com. > I'd like agents to connect to "puppet.example.com" which will point to > one of these. I wamt to be sure agents can connect to either without > certificate errors. > > How do I configure the puppet.conf certname/servername, and generate the > master certificate such that agents will happily connect to host1 and host2 > without complaining? > > I've experimented and googled but can't seem to figure out what's the > right approach. > -- 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/3e6f0b50-0e6d-4b34-97ef-131ab6f78efa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] hiera command line - search with structured facts (key.subkey)
It works fine for me, thanks !
Sorry, I missed the switch to the new command and the doc here :
https://puppet.com/docs/puppet/5.5/hiera_automatic.html#ariaid-title4
I was looking for 'hiera cli'
Regards,
Louis Coilliot
2018-04-27 19:13 GMT+02:00 Henrik Lindberg :
> On 27/04/18 18:12, Louis Coilliot wrote:
>
>> Hello,
>>
>> this work :
>>
>> hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
>> ::environment=production ::osfamily=RedHat
>>
>> this does not (at least on my platform) :
>>
>> hiera -d -c /etc/puppetlabs/puppet/hiera.yaml core::packages
>> ::environment=production ::os.family=RedHat
>>
>> (note the dot between os and family).
>>
>> In the hiera-rchy I have levels like :
>>
>> %{::environment}/hieradata/os/%{::os.family}/%{::os.release.major}"
>>
>> I works fine with lookups in puppet 5 but not from the hiera command line.
>>
>> I use the hiera command line tool for debugging.
>>
>> With the last version of hiera.
>>
>> # hiera -v
>> 3.4.3
>>
>> My syntax in hiera.yaml is still in version 3.
>>
>> How do you query with the command line and some structured facts in the
>> variable interpolation of the levels in hiera ?
>>
>> I can't find any doc. or information about that.
>>
>>
> Switch to using the lookup CLI instead of hiera CLI.
> The hiera CLI is deprecated and has quite a few known problems.
>
> The lookup CLI may not be perfect, but it has a lot of documentation (and
> features).
>
> Best,
> - 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/pbvlkg%24scl%242%40blaine.gmane.org.
> 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/CAE9jN30OjxB-JuSoohODOELk6FGkEytPXNT2B6_pAGqi5G9zpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Setting puppet up to use a dns alias as a servername
On Wednesday, May 2, 2018 at 6:25:37 AM UTC-5, Gavin Williams wrote: > > 'dns_alt_names' is the config you're looking for... > > > https://puppet.com/docs/puppetserver/5.1/scaling_puppet_server.html#creating-and-configuring-compile-masters > > provides more info on running multiple Puppet servers. > It is covered in the referenced doc (scroll both up and down), but it's worth highlighting that using a single CA for the whole site is a key detail, too. 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/58cccf17-d26f-4233-9ab7-5d34de9cb69e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Puppet Platform 6 pre-release builds available
Hei Eric, good news, especially the extra modularization and the agent side functions, from my point of view. Are expected in Puppet 6 any remarkable backwards incompatibilities or deprecations? Best Al On Monday, April 23, 2018 at 11:44:32 PM UTC+2, Eric Sorenson wrote: > > Hi all, we've started landing changes for what will become Puppet Platform > 6. Here's the News You Can Use relating to the release. > > Scope and Timeline > We expect to release it in the fall, and the major features of the release > are currently scoped to be: > - improved secret and ephemeral data handling through the use of a new API > for evaluating functions an the agent at catalog application time (more on > this to come, it's still pretty early in design) > - modularized types and providers; things like the nagios types will live > in their own module and be included at packaging time. This will make it > easier to get changes into this code and opens the door to including more > modules in packages so, for example, you don't need to download stdlib > separate from puppet. Josh posted a PR to the specifications repo > describing this approach here: > https://github.com/puppetlabs/puppet-specifications/pull/106 > - consolidate the CA code onto the clojure CA and provide 1st class > support for intermediate CA signing - this means the Ruby CA and tooling > around it will change in favor of a CLI that supports your actual workflow. > (PUP-7877 is the epic to follow for this work) > > > Branches, Builds, and Repos > The upshot is that the 'master' branch of the main platform projects > (puppetdb, puppetserver, facter, puppet) will become the 6.0 versions of > those projects, and PRs that target master can contain larger changes - so > things like improving facter output, changing default settings for things > that had previously been opt-in, etc have a place to land. > In addition to automatic builds that go into the nightly repos, we're > working in iterations towards monthly milestones that contain completed > features and are ready for testing and feedback. As these come out, we'll > post updates to the mailing list describing the contents in more detail and > would love for you to try them out and let us know how it goes. > The release packages are up here for apt/yum systems: > yum: https://yum.puppet.com/puppet6-nightly/ > apt: https://apt.puppet.com/puppet6-nightly/ > > and the direct download repos for mac, windows, and eos are here: > http://nightlies.puppet.com/downloads/ > > (Note that although the content of the agent packages in particular is > being built off what will become puppet 6, the version numbers won't > reflect that until it's tagged as such.) > Once the release is out, the 'puppet' repo and associated release package > for apt and yum will shift to 'puppet6'; the 'puppet5' repo/release package > will remain as-is so you can stay pinned to that until you're ready to > move. > > > EOL / Lifecycle of Older versions > The 5.x versions are incorporated into the upcoming PE2018.1 LTS, so the > branches that feed into those versions will be open for changes. But they > need to be targeted bug fixes that won't introduce instability into the > components, so please be judicious when targeting non-master branches with > your PRs. > The 4.x series (puppet-agent 1.10, puppet-server 2.8, etc) will be going > EOL towards the end of 2018. They're already on "deep LTS" mode and only > critical security fixes and hyper-targeted backports are landing on these > branches. > > Please let me know if you have any questions. I'm pretty excited about > this release; the slightly longer development timeline and milestone build > process should enable more interesting features and a smoother upgrade > path. > > --eric0 > > > -- 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/0a22285c-a719-44c0-bf64-6ce4c767f822%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Tutorial on example42's Puppet Tip of the Week Blog
Dear all, I hope someone here can find useful the 4 posts long *Puppet Tutorial* we just finished to publish on example42's blog, where we regularly publish a Puppet Tip of The Week. Find the tutorial, and a lot more Puppet related content, at: https://www.example42.com/blog/ Sorry for the "unsolicited post" but I hope and think we have valuable and useful Puppet information to share. Needless to say that any feedback, link, tweet, comment here or anywhere (as long as we can see it :-) is welcomed (feedback, possibly positive, is always the main drive for motivation). Alessandro Franceschi CTO @ example42 -- 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/69b70a2f-9629-4632-832d-0d9fd44d1116%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Puppetfile with 'puppet apply'?
You can definitively use a Puppetfile with puppet apply. As you already found is a matter of running r10k puppetfile install -v from your control-repo directory (where Puppetfile is placed). You need to resolve all the dependencies by yourself in Puppetfile (r10k does not do that for you), so list explicitly in Puppetfile all the modules you need, with their dependencies. With the proper options, you can run puppet apply for a whole control repo, basically reproducing on the local node what is done on a Puppet server (when an ENC is not used), in this way you can use the modules from the control repo's modules dir (populated via r10k puppetfile install) and hieradata from the defined hieradata directory. Look here https://github.com/example42/psick/blob/production/bin/papply.sh for the needed command line parameters. On Wednesday, May 2, 2018 at 5:55:12 AM UTC+2, Joaquin Menchaca wrote: > > Is it possible to use Puppetfile with 'puppet apply'? I have been having > difficulty finding this. I wanted to use the Puppetfile to download and > vendor modules in the modules directory. > > From my research so far, it looks like r10k with open source puppet > server, and code manager with PE, but for 'puppet apply', I couldn't find > anything. > > > -- 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/585ae5de-df82-4aa3-9408-abf4beaf1c4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet Basics Blog Post
Hi Joaquin, many thanks for also thinking on newbies. Some notes from my side: - Don't use puppet module generate, use PDK to create new modules, classes and defines. - Stop using ERB templates, switch to EPP Best, Martin > On 1. May 2018, at 23:47, Joaquin Menchaca wrote: > > I wrote this blog to teach newbies* about Puppet: > > https://medium.com/@Joachim8675309/learn-puppet-puppet-basics-b58787ad > > * I was a newbie once > > -- > 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/15ee346e-8b77-4d21-be92-090a427c5a49%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/F3701944-8F59-476B-8F57-595ACD2B72BA%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Puppet Platform 6 pre-release builds available
Hi Al - The main thing is that the certificate authority and network stack are going to consolidate onto the puppetserver implementations, rather than having a split between ruby/webrick and clojure/puppetserver. So if anyone is still using 'puppet master' standalone or apache-based servers, now's the time to cut the cord. On Wednesday, May 2, 2018 at 7:56:41 AM UTC-7, a...@example42.com wrote: > > Hei Eric, > good news, especially the extra modularization and the agent side > functions, from my point of view. > Are expected in Puppet 6 any remarkable backwards incompatibilities or > deprecations? > > Best > Al > > On Monday, April 23, 2018 at 11:44:32 PM UTC+2, Eric Sorenson wrote: >> >> Hi all, we've started landing changes for what will become Puppet >> Platform 6. Here's the News You Can Use relating to the release. >> >> Scope and Timeline >> We expect to release it in the fall, and the major features of the >> release are currently scoped to be: >> - improved secret and ephemeral data handling through the use of a new >> API for evaluating functions an the agent at catalog application time (more >> on this to come, it's still pretty early in design) >> - modularized types and providers; things like the nagios types will >> live in their own module and be included at packaging time. This will make >> it easier to get changes into this code and opens the door to including >> more modules in packages so, for example, you don't need to download stdlib >> separate from puppet. Josh posted a PR to the specifications repo >> describing this approach here: >> https://github.com/puppetlabs/puppet-specifications/pull/106 >> - consolidate the CA code onto the clojure CA and provide 1st class >> support for intermediate CA signing - this means the Ruby CA and tooling >> around it will change in favor of a CLI that supports your actual workflow. >> (PUP-7877 is the epic to follow for this work) >> >> >> Branches, Builds, and Repos >> The upshot is that the 'master' branch of the main platform projects >> (puppetdb, puppetserver, facter, puppet) will become the 6.0 versions of >> those projects, and PRs that target master can contain larger changes - so >> things like improving facter output, changing default settings for things >> that had previously been opt-in, etc have a place to land. >> In addition to automatic builds that go into the nightly repos, we're >> working in iterations towards monthly milestones that contain completed >> features and are ready for testing and feedback. As these come out, we'll >> post updates to the mailing list describing the contents in more detail and >> would love for you to try them out and let us know how it goes. >> The release packages are up here for apt/yum systems: >> yum: https://yum.puppet.com/puppet6-nightly/ >> apt: https://apt.puppet.com/puppet6-nightly/ >> >> and the direct download repos for mac, windows, and eos are here: >> http://nightlies.puppet.com/downloads/ >> >> (Note that although the content of the agent packages in particular is >> being built off what will become puppet 6, the version numbers won't >> reflect that until it's tagged as such.) >> Once the release is out, the 'puppet' repo and associated release package >> for apt and yum will shift to 'puppet6'; the 'puppet5' repo/release package >> will remain as-is so you can stay pinned to that until you're ready to >> move. >> >> >> EOL / Lifecycle of Older versions >> The 5.x versions are incorporated into the upcoming PE2018.1 LTS, so the >> branches that feed into those versions will be open for changes. But they >> need to be targeted bug fixes that won't introduce instability into the >> components, so please be judicious when targeting non-master branches with >> your PRs. >> The 4.x series (puppet-agent 1.10, puppet-server 2.8, etc) will be going >> EOL towards the end of 2018. They're already on "deep LTS" mode and only >> critical security fixes and hyper-targeted backports are landing on these >> branches. >> >> Please let me know if you have any questions. I'm pretty excited about >> this release; the slightly longer development timeline and milestone build >> process should enable more interesting features and a smoother upgrade >> path. >> >> --eric0 >> >> >> -- 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/594dbe09-5421-4749-b1d2-9b94ea305992%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
