[Puppet Users] [INFO, maybe ACTION] r10k Feature Proposal

[Molly Waggett]

Hey folks!

We are planning an r10k feature to stop deploying module spec directories.
This will lower disk usage, particularly for folks with a lot of modules
and multiple compilers.

Our hope is to enable this behavior by default, but leave the option to opt
out (i.e. continue including spec directories when deploying modules). This
is based on the assumption that most folks have no need for module spec
directories in a production environment, since they typically just include
testing materials for module development.

If you think this assumption is inaccurate, or even if it’s just inaccurate
for you, please let us know! If we don’t hear any objections by Tuesday,
March 23, we will proceed with the above plan to adopt this behavior but
include a way to opt out.

If you have any questions, please reply to this email or ping @r10k in
the Puppet
Community Slack <https://slack.puppet.com/>.

Thanks!

-- 
*Molly Waggett*
she/her
Senior Software Engineer @ Puppet

-- 
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/CAFOE68C%2BWNLmtfgJgCUkRkjX-rYqoAUAQvUApa-xp1_k7sp7vA%40mail.gmail.com.

Re: [Puppet Users] "puppetserver ca migrate" error

[Molly Waggett]

On Thu, Mar 4, 2021 at 4:07 AM Erwin Bogaard 
wrote:

> Hi Molly,
>
> thanks for opening the ticket. No further info to add from my side.
> I just executed the manual migration. To me it seems that way is actually
> easier than the puppetserver migrate-way, where yhou have to look for the
> location of your config file  ;-)
>

For what it's worth, you shouldn't have to look for your config file. The
command will use your puppet.conf file by default, but you can use the
--config flag if you want to use a different config file.

>
> On Wednesday, 3 March 2021 at 22:39:08 UTC+1 Molly Waggett wrote:
>
>> Hi Erwin,
>>
>> I have opened SERVER-2979
>> <https://tickets.puppetlabs.com/browse/SERVER-2979> to investigate your
>> issue. Any additional info you can add to that ticket would be greatly
>> appreciated.
>>
>> In the meantime, you can manually migrate your CA directory:
>> 1. stop the puppetserver service:
>> systemctl stop puppetserver
>> 2. move your CA directory to the new location:
>> mv /etc/puppetlabs/puppet/ssl/ca /etc/puppetlabs/puppetserver/ca
>> 3. to maintain backwards compatibility, create a symlink from the new
>> location to the old location:
>> ln -sf /etc/puppetlabs/puppetserver/ca /etc/puppetlabs/puppet/ssl/ca
>> 4. restart the puppetserver service:
>> systemctl start puppetserver
>>
>> Let us know if you have any other issues.
>>
>> Thanks!
>>
>> On Fri, Feb 26, 2021 at 6:40 AM Erwin Bogaard 
>> wrote:
>>
>>> Hi Molly,
>>>
>>> We don't really run an unusual setup: just a regular machine with
>>> hostname in local DNS available, no IPv6.
>>> The installed Puppet component versions are as follows:
>>> puppet-agent-7.4.1-1.el7.x86_64
>>> puppet-client-tools-1.2.6-1.el7.x86_64
>>> puppetdb-7.2.0-1.el7.noarch
>>> puppetdb-termini-7.2.0-1.el7.noarch
>>> puppet-release-1.0.0-15.el7.noarch
>>> puppetserver-7.0.3-1.el7.noarch
>>>
>>> The requested configuration is as follows:
>>> networking => {
>>>   dhcp => "192.168.100.1",
>>>   domain => "kntr.xxx.loc",
>>>   fqdn => "puppet01.kntr.xxx.loc",
>>>   hostname => "puppet01",
>>> ...
>>> }
>>> os => {
>>>   architecture => "x86_64",
>>>   family => "RedHat",
>>>   hardware => "x86_64",
>>>   name => "CentOS",
>>>   release => {
>>> full => "7.9.2009",
>>> major => "7",
>>> minor => "9"
>>>   },
>>>   selinux => {
>>> enabled => false
>>>   }
>>> }
>>> ruby => {
>>>   platform => "x86_64-linux",
>>>   sitedir => "/opt/puppetlabs/puppet/lib/ruby/site_ruby/2.7.0",
>>>   version => "2.7.2"
>>> }
>>> On Thursday, 25 February 2021 at 19:52:23 UTC+1 Molly Waggett wrote:
>>>
>>>> Hi Erwin,
>>>>
>>>> The puppetserver ca migrate command must be run while the puppetserver
>>>> service is stopped, but it looks like we're not catching the particular
>>>> connection error you're getting when we check to see whether the service is
>>>> running.
>>>>
>>>> I'm wondering if you have an unusual networking setup, e.g. custom DNS
>>>> config, IPv6, etc.
>>>> I was not able to reproduce your issue on a first attempt, so it would
>>>> also be helpful to know which version of puppetserver you're running, what
>>>> OS platform you're running on, and which version of Ruby you're using.
>>>>
>>>> Thanks!
>>>>
>>>> On Thu, Feb 25, 2021 at 2:59 AM Erwin Bogaard 
>>>> wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm trying to solve the notofocation about "The cadir is currently
>>>>> configured to be inside the /etc/puppetlabs/puppet/ssl directory".
>>>>> When I follow the steps, and run:
>>>>>
>>>>> #  puppetserver ca migrate --config /etc/puppetlabs/puppet/puppet.conf
>>>>>
>>>>> I get the message: "Puppetserver service is running. Please stop it
>>>>> before attempting to run this command."
>>>>>
>>>>> If I then stop the puppetserver service and run the command again, I
>>>

Re: [Puppet Users] "puppetserver ca migrate" error

[Molly Waggett]

Hi Erwin,

I have opened SERVER-2979
<https://tickets.puppetlabs.com/browse/SERVER-2979> to investigate your
issue. Any additional info you can add to that ticket would be greatly
appreciated.

In the meantime, you can manually migrate your CA directory:
1. stop the puppetserver service:
systemctl stop puppetserver
2. move your CA directory to the new location:
mv /etc/puppetlabs/puppet/ssl/ca /etc/puppetlabs/puppetserver/ca
3. to maintain backwards compatibility, create a symlink from the new
location to the old location:
ln -sf /etc/puppetlabs/puppetserver/ca /etc/puppetlabs/puppet/ssl/ca
4. restart the puppetserver service:
systemctl start puppetserver

Let us know if you have any other issues.

Thanks!

On Fri, Feb 26, 2021 at 6:40 AM Erwin Bogaard 
wrote:

> Hi Molly,
>
> We don't really run an unusual setup: just a regular machine with hostname
> in local DNS available, no IPv6.
> The installed Puppet component versions are as follows:
> puppet-agent-7.4.1-1.el7.x86_64
> puppet-client-tools-1.2.6-1.el7.x86_64
> puppetdb-7.2.0-1.el7.noarch
> puppetdb-termini-7.2.0-1.el7.noarch
> puppet-release-1.0.0-15.el7.noarch
> puppetserver-7.0.3-1.el7.noarch
>
> The requested configuration is as follows:
> networking => {
>   dhcp => "192.168.100.1",
>   domain => "kntr.xxx.loc",
>   fqdn => "puppet01.kntr.xxx.loc",
>   hostname => "puppet01",
> ...
> }
> os => {
>   architecture => "x86_64",
>   family => "RedHat",
>   hardware => "x86_64",
>   name => "CentOS",
>   release => {
> full => "7.9.2009",
> major => "7",
> minor => "9"
>   },
>   selinux => {
> enabled => false
>   }
> }
> ruby => {
>   platform => "x86_64-linux",
>   sitedir => "/opt/puppetlabs/puppet/lib/ruby/site_ruby/2.7.0",
>   version => "2.7.2"
> }
> On Thursday, 25 February 2021 at 19:52:23 UTC+1 Molly Waggett wrote:
>
>> Hi Erwin,
>>
>> The puppetserver ca migrate command must be run while the puppetserver
>> service is stopped, but it looks like we're not catching the particular
>> connection error you're getting when we check to see whether the service is
>> running.
>>
>> I'm wondering if you have an unusual networking setup, e.g. custom DNS
>> config, IPv6, etc.
>> I was not able to reproduce your issue on a first attempt, so it would
>> also be helpful to know which version of puppetserver you're running, what
>> OS platform you're running on, and which version of Ruby you're using.
>>
>> Thanks!
>>
>> On Thu, Feb 25, 2021 at 2:59 AM Erwin Bogaard 
>> wrote:
>>
>>>
>>> Hi,
>>>
>>> I'm trying to solve the notofocation about "The cadir is currently
>>> configured to be inside the /etc/puppetlabs/puppet/ssl directory".
>>> When I follow the steps, and run:
>>>
>>> #  puppetserver ca migrate --config /etc/puppetlabs/puppet/puppet.conf
>>>
>>> I get the message: "Puppetserver service is running. Please stop it
>>> before attempting to run this command."
>>>
>>> If I then stop the puppetserver service and run the command again, I get
>>> the following Error: "Fatal error when running action 'migrate'
>>>   Error: Failed connecting to https://xxx.loc:8140/status/v1/simple/ca
>>>   Root cause: Failed to open TCP connection to xxx.loc:8140 (Invalid
>>> argument - connect(2) for "xxx.loc" port 8140)"
>>>
>>> That no connection is possible seems logical, as I stopped the service
>>> prevously.
>>>
>>> If "puppetsever ca migrate" won't run when the service is running, but
>>> it needs to connect to the service, how is that ever going to work? I'm
>>> baffeled.
>>>
>>> As a work around: is there maybe a manual way to execute this migration?
>>>
>>> --
>>> 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/c4627ffb-887d-490e-9dc6-7b730cdf3622n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/c4627ffb-887d-490e-9dc6-7b730cdf3622n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
&g

Re: [Puppet Users] "puppetserver ca migrate" error

[Molly Waggett]

Hi Erwin,

The puppetserver ca migrate command must be run while the puppetserver
service is stopped, but it looks like we're not catching the particular
connection error you're getting when we check to see whether the service is
running.

I'm wondering if you have an unusual networking setup, e.g. custom DNS
config, IPv6, etc.
I was not able to reproduce your issue on a first attempt, so it would also
be helpful to know which version of puppetserver you're running, what OS
platform you're running on, and which version of Ruby you're using.

Thanks!

On Thu, Feb 25, 2021 at 2:59 AM Erwin Bogaard 
wrote:

>
> Hi,
>
> I'm trying to solve the notofocation about "The cadir is currently
> configured to be inside the /etc/puppetlabs/puppet/ssl directory".
> When I follow the steps, and run:
>
> #  puppetserver ca migrate --config /etc/puppetlabs/puppet/puppet.conf
>
> I get the message: "Puppetserver service is running. Please stop it before
> attempting to run this command."
>
> If I then stop the puppetserver service and run the command again, I get
> the following Error: "Fatal error when running action 'migrate'
>   Error: Failed connecting to https://xxx.loc:8140/status/v1/simple/ca
>   Root cause: Failed to open TCP connection to xxx.loc:8140 (Invalid
> argument - connect(2) for "xxx.loc" port 8140)"
>
> That no connection is possible seems logical, as I stopped the service
> prevously.
>
> If "puppetsever ca migrate" won't run when the service is running, but it
> needs to connect to the service, how is that ever going to work? I'm
> baffeled.
>
> As a work around: is there maybe a manual way to execute this migration?
>
> --
> 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/c4627ffb-887d-490e-9dc6-7b730cdf3622n%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/c4627ffb-887d-490e-9dc6-7b730cdf3622n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Molly Waggett*
she/her
Senior Software Engineer @ Puppet

-- 
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/CAFOE68BoFH--d632-qBiB%2BsfL80BX%3Do7JXExOiN04HU1p9d2NQ%40mail.gmail.com.

Re: [Puppet Users] Puppet 6.10.0?

[Molly Waggett]

Hi John,

We are currently in the process of shipping Puppet Platform 6.10.0. There
were some issues with our automation that has delayed getting the release
out, but packages should be available before the end of the day. You should
see a release announcement with more details once bits are live.

Thanks for your understanding,

On Tue, Oct 1, 2019 at 11:41 AM jcbollinger 
wrote:

> Is it intentional that the docs site is currently claiming
> <https://puppet.com/docs/puppet/latest/puppet_index.html> that Puppet
> 6.10.0 was released today?
>
> I mean, it seems much too soon after v6.9.0, and I haven't seen any
> announcements around here, and no v6.10 packages seem yet to be available
> from the Puppet EL7 repository.  Plus, the published release notes document
> only bugfixes, not any new features, and none of those even seem especially
> urgent.
>
> What gives?
>
>
> 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/34da8380-36ac-449a-890d-c77f7fa1270b%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/34da8380-36ac-449a-890d-c77f7fa1270b%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.
Join us for Puppetize PDX <http://www.puppet.com/puppetize> 9-10 October.

-- 
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/CAFOE68A%3DRxikY%2BZomSk-Ty--7Jv6tZniUkJpAVXRjvhrrejk_g%40mail.gmail.com.

Re: [Puppet Users] Building puppet agent for ARM - looking for info on config settings

[Molly Waggett]

Hi!

How are you building puppet-runtime? If you're using a recent version of
vanagon, I would expect you to have an
agent-runtime-6.4.x-201906190.debian-9-arm.settings.yaml file in addition
to the files you listed.

Otherwise, many of the settings used to build puppet-agent (like sysconfdir)
are inherited from puppet-runtime here:
https://github.com/puppetlabs/puppet-runtime/blob/master/configs/projects/_shared-agent-settings.rb.
So you can determine the appropriate values for your other setting from
that.

Hope that helps!

On Mon, Aug 12, 2019 at 5:15 PM JonY  wrote:

> I have some belief that I've successfully assembled the various bits for
> 'puppet-runtime' (v6.4). Now Im trying to build the puppet-agent (also
> v6.4).
>
> At the end of the runtime build I have these 4 files:
>
> -rw-r--r--  1 pocl root   514 Aug 11 12:53
> agent-runtime-6.4.x-201906190.debian-9-arm-bill-of-materials
>
> -rw-r--r--  1 pocl root  2538 Aug 11 12:52
> agent-runtime-6.4.x-201906190.debian-9-arm.json
>
> -rw-r--r--  1 pocl root  4752 Aug 11 12:53
> *agent-runtime-6.4.x-201906190.debian-9-arm.tar.gz*
>
> -rw-r--r--  1 pocl root99 Aug 11 12:53
> agent-runtime-6.4.x-201906190.debian-9-arm.tar.gz.sha1
>
> In the agent build files "puppet-agent.rb" appears to be looking for a
> file called "#{proj.settings[:puppet_runtime_basename]}.settings.yaml'
> but I don't see any reference to this in the runtime Makefile.
> Im trying to work around this omission but am wondering what to use for
> these settings:
>
>
>   proj.setting(:puppet_configdir, File.join(proj.sysconfdir, 'puppet'))
>
>   proj.setting(:puppet_codedir, File.join(proj.sysconfdir, 'code'))
>
>
>   # Target directory for vendor modules
>
>   proj.setting(:module_vendordir, File.join(proj.prefix,
> 'vendor_modules'))
>
> --
> 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/7359e31b-6fbc-462c-a942-0daf63f56084%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/7359e31b-6fbc-462c-a942-0daf63f56084%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.
Join us for Puppetize PDX <http://www.puppet.com/puppetize> 9-10 October.

-- 
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/CAFOE68BPHh6BrAdypN9DW-vSsqYNsTZq3BX0V4kd3L-NijmaTQ%40mail.gmail.com.

[Puppet Users] [INFO] Removal of nightly release packages from main yum/apt sites

[Molly Waggett]

Hey folks!

In an effort to reduce clutter and confusion on some of our public download
sites, we are removing all *-nightly-release packages from yum.puppet.com
<https://yum.puppetlabs.com/> and apt.puppet.com
<https://apt.puppetlabs.com/>. Links like yum.puppet.com/puppet-nightly
<http://yum.puppetlabs.com/puppet-nightly/> and
apt.puppet.com/puppet-nightly <http://apt.puppetlabs.com/puppet-nightly/>
WILL BE REMOVED TODAY.

Nightly repositories and packages can still be found at nightlies.puppet.com
.

If you have any questions or concerns about these changes, please reply-all
to this email.

Thanks!

-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68CJS9WvTbH7ZK5zUyFGkw3m51gqr%2BRXmesKLiHyvCNF%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

The puppetlabs-release-pc1 packages on yum.puppetlabs.com are the ones we
plan to re-archive. You will need to install new release packages from
http://release-archives.puppet.com/yum/ if you want to continue using the
PC1 repository. Neither of these repos will receive future updates.

If you have additional questions, please let me know!

On Wed, Jun 5, 2019 at 10:36 AM Michael Watters  wrote:

> Hello,
>
> I see the puppetlabs-release-pc1 package is available on
> yum.puppetlabs.com however it doesn't actually show as an available
> update when running "yum update".
>
> For example, here's the output on one of our servers.
>
> ```
> [root@server1 yum.repos.d]# yum update puppetlabs-release-pc1
> Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks,
> versionlock
> Loading mirror speeds from cached hostfile
>  * elrepo: reflector.westga.edu
>  * epel-debuginfo: mirror.uic.edu
> No packages marked for update
> ```
>
> I *was* able to update the package using the rpm command directly however
> I'd like to avoid doing this on hundreds of nodes.
>
>
> On Tuesday, June 4, 2019 at 12:37:21 PM UTC-4, Molly Waggett wrote:
>>
>> Hi all,
>>
>> We have enabled repositories on release-archives.puppet.com.
>>
>> If you're using Puppet 3, install the puppet-archives-release-* packages.
>> If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.
>>
>> We do not yet have a timeline for when these packages will be re-archived
>> from the main {yum,apt}.puppet.com sites, but we'll let you know when we
>> do.
>> Nonetheless, we recommend switching to these archive repositories as soon
>> as possible.
>>
>> Thanks for bearing with us!
>>
> --
> 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/71411a67-f71e-47df-8e6e-915cebcc6e2b%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/71411a67-f71e-47df-8e6e-915cebcc6e2b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68CGTA%2B0Rt%3DMN2Hzicq4-m%2BOc4SROUmHE8Pne7LFQRuTiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi all,

We have enabled repositories on release-archives.puppet.com.

If you're using Puppet 3, install the puppet-archives-release-* packages.
If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.

We do not yet have a timeline for when these packages will be re-archived
from the main {yum,apt}.puppet.com sites, but we'll let you know when we
do.
Nonetheless, we recommend switching to these archive repositories as soon
as possible.

Thanks for bearing with us!

On Thu, May 30, 2019 at 1:36 PM Molly Waggett 
wrote:

> Hi Michael,
>
> We don't plan to remove anything from our rsync servers at this time, so
> you should be able to continue using that as you currently are.
>
> On Thu, May 30, 2019 at 6:33 AM Michael Watters 
> wrote:
>
>> How does this change affect private mirrors?  Will rsync services be
>> available on the archive repos?
>>
>>
>> On Monday, April 22, 2019 at 5:31:09 PM UTC-4, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>>> yum.puppet.com; 2. links to nightly release packages will be removed
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be
>>> moved to release-archives.puppet.com.
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths
>>> will be updated by the time these changes are made. Please ensure that
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>>> and nightlies.puppet.com), we are planning to make some changes.
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the
>>> old ones on May 14. Please plan to make all updates during this period.
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly
>>> <http://yum.puppetlabs.com/puppet-nightly/> and
>>> apt.puppet.com/puppet-nightly
>>> <http://apt.puppetlabs.com/puppet-nightly/> WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>>> downloads}.puppet.com.
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>>> end-of-life, so all packages will be moved to
>>> release-archives.puppet.com on May 14 and no further updates will be
>>> made to these streams.
>>>
>>> ---*---*---
>>>
>>> We have set up a temporary s3 bucket that reflects the new layout if
>>> you’d like to test changes before the cutover:
>>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>>
>>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>>> you visit the above url in your browser, the info you'll see is NOT
>>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>>> should only affect human eyes.
>>>
>>> If you have any questions or concerns about these changes, please
>>> reply-all to this email.
>>>
>>> Thanks!
>>>
>

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

We don't plan to remove anything from our rsync servers at this time, so
you should be able to continue using that as you currently are.

On Thu, May 30, 2019 at 6:33 AM Michael Watters  wrote:

> How does this change affect private mirrors?  Will rsync services be
> available on the archive repos?
>
>
> On Monday, April 22, 2019 at 5:31:09 PM UTC-4, Molly Waggett wrote:
>>
>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>> yum.puppet.com; 2. links to nightly release packages will be removed
>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved
>> to release-archives.puppet.com.
>>
>> All Puppet-maintained tooling and documentation referencing these paths
>> will be updated by the time these changes are made. Please ensure that
>> you are using current versions.
>>
>> Read on for details, especially if you've written custom tooling with
>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>
>> ---*---*---
>>
>> Hey folks,
>>
>> In an effort to reduce clutter and confusion on some of our public
>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>> and nightlies.puppet.com), we are planning to make some changes.
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>> Old: nightlies.puppet.com/yum/puppet-nightly/
>> puppet-nightly-release-sles-12.noarch.rpm
>>
>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>
>> These new paths are currently available for use. We plan to remove the
>> old ones on May 14. Please plan to make all updates during this period.
>>
>> 2. There will be no links to nightlies from main download sites.
>>
>> Links like yum.puppet.com/puppet-nightly
>> <http://yum.puppetlabs.com/puppet-nightly/> and
>> apt.puppet.com/puppet-nightly <http://apt.puppetlabs.com/puppet-nightly/>
>> WILL BE REMOVED on May 14.
>>
>> If you're looking for nightlies, visit nightlies.puppet.com. The
>> directory structure will match that of our main download sites.
>>
>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>> downloads}.puppet.com.
>>
>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>> end-of-life, so all packages will be moved to release-archives.puppet.com
>> on May 14 and no further updates will be made to these streams.
>>
>> ---*---*---
>>
>> We have set up a temporary s3 bucket that reflects the new layout if
>> you’d like to test changes before the cutover:
>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>
>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>> you visit the above url in your browser, the info you'll see is NOT
>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>> should only affect human eyes.
>>
>> If you have any questions or concerns about these changes, please
>> reply-all to this email.
>>
>> Thanks!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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/67d776c9-7490-4113-8220-580a838098f4%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/67d776c9-7490-4113-8220-580a838098f4%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Yosuke,

We will likely remove the release packages from the subdirectories *before* the
archives are ready. I'll send an update next week when we have a better
sense of the timeline.

Let us know if you have any concerns.

Thanks!

On Thu, May 23, 2019 at 1:13 PM Yosuke Adachi  wrote:

> Hi Molly,
>
> When are you planning to remove release packages from
> yum.puppet.com/puppet6/ or puppet5/ sub directory (e.g. yum.puppet.com/
> puppet6/puppet6-release-el-7.noarch.rpm) ?
> Is it same timing as when the release-archive repository is ready?
>
>
> Kind regards
> Yosuke
>
> On Monday, May 6, 2019 at 11:16:25 PM UTC+1, Molly Waggett wrote:
>>
>> Hey folks,
>>
>> REMINDER that the repository path changes* will take effect next week,
>> on Tuesday, May 14.
>>
>> Please make sure any custom tooling using these paths has been updated.
>>
>> If you have any questions or concerns, please reply-all to this email.
>>
>> Thanks!
>>
>> * in case you forgot, changes include:
>>
>> 1. yum release packages will be removed from nested directories on
>> yum.puppet.com (e.g. yum.puppet.com/puppet6/
>> puppet6-release-el-7.noarch.rpm
>>
>> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>>
>> PLEASE NOTE that these are actually symlinks to release packages that
>> live inside their respective repositories, so package updates can be
>> applied via your package manager, like any other package.
>>
>> 2. links to nightly release packages will be removed from {yum,apt}.
>> puppet.com.
>> 3. PC1 (and older) packages will be moved to release-archives.puppet.com.
>> This includes puppet-agent 1.10.x and puppet 4.x.
>>
>> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett 
>> wrote:
>>
>>> Hi John,
>>>
>>> The top-level release packages are actually symlinks to release packages
>>> that *are* inside their respective repositories. When we publish new
>>> release packages, we update those links so that users don't have to bump
>>> version numbers in any tooling that installs these repositories.
>>>
>>> Thanks!
>>>
>>> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>>>>
>>>>> 1. Release packages (for all active streams) will live at the top
>>>>> level only.
>>>>>
>>>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>>>> giving us consistency with the layout on apt.puppet.com. Currently,
>>>>> yum release packages live inside their corresponding repo directory, e.g.
>>>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>>>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>>>>> THESE WILL BE REMOVED.
>>>>>
>>>>> Here are some examples of where you will be able to find release
>>>>> packages:
>>>>>
>>>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>>>
>>>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>>>
>>>>>
>>>> It is conventional for repository release packages to be inside their
>>>> repositories so that repository configuration updates can be published and
>>>> applied via the same mechanism that is used for ordinary packages.  Even if
>>>> this is a capability that Puppet rarely uses, it seems ill-considered to
>>>> give it up.  The desire for consistency could be as well served by moving
>>>> the other release packages into their repos, or by making the release
>>>> packages consistently  available in both places.
>>>>
>>>>
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optou

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi all,

As you may have seen, the packages we removed from {yum,apt}.puppetlabs.com
this week have been put back. This was due to an outage and the need to
restore from backups.

While we originally did not intend to enable repositories on
release-archives.puppet.com, the overwhelming demand has made this a
priority for us. We will keep the EOL packages on {yum,apt}.puppetlabs.com
until that work is done, but then they will be re-archived. You can follow
along here: https://tickets.puppetlabs.com/browse/CPR-685

To provide some clarity:

   - The puppetlabs-release-* repos contain puppet 3 packages. THESE WILL
   BE ARCHIVED. You will soon be able to find them at
   http://release-archives.puppet.com/yum/puppet-archives-release-*.
   - The puppetlabs-release-pc1-* repos contain puppet 4 packages. THESE
   WILL BE ARCHIVED. You will soon be able to find them at
   http://release-archives.puppet.com/yum/puppetlabs-release-pc1-*.
   - puppet-release-* is our rolling repository, which always points to our
   latest software stream. This is currently puppet 6.

If you have any questions, please feel free to reach out.

Thanks!



On Wed, May 15, 2019 at 4:04 PM Chris Taylor  wrote:

> Try
> http://release-archives.puppet.com/yum/el/7/PC1/x86_64/puppetlabs-release-pc1-1.1.0-5.el7.noarch.rpm
>
> Just be aware it will probably install a repo with yum.puppetlabs.com
> into /etc/yum.repos.d/, so you will need to update the path to the
> appropriate place.
>
>
> On Wednesday, May 15, 2019 at 11:25:19 PM UTC+1, michael mack wrote:
>>
>> How do you get the following old repo to work?
>>
>> rpm -Uvh
>> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>>
>>
>> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>>> yum.puppet.com; 2. links to nightly release packages will be removed
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be
>>> moved to release-archives.puppet.com.
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths
>>> will be updated by the time these changes are made. Please ensure that
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>>> and nightlies.puppet.com), we are planning to make some changes.
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the
>>> old ones on May 14. Please plan to make all updates during this period.
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly
>>> <http://yum.puppetlabs.com/puppet-nightly/> and
>>> apt.puppet.com/puppet-nightly
>>> <http://apt.puppetlabs.com/puppet-nightly/> WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>>> downloads}.puppet.com.
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>>> end-of-life, so all packages will be moved to
>>> release-archives

Re: [Puppet Users] Puppet apt repository broken?

[Molly Waggett]

Hi Chris,

We originally did not plan to support repositories on release-archives, but
due to the high demand, yes we are working to enable them as soon as
possible.

On Wed, May 15, 2019 at 3:23 PM Chris Taylor  wrote:

> Guessing this is related to the archiving of the puppet 4 & older packages?
>
> I note that the yum archive still functions as a repo, but the apt one
> doesn't have any release files (or a dists folder), in spite of otherwise
> being structured appropriately.. Is this going to be fixed? (
> release-archives.puppet.com/apt/)
>
> On Wednesday, May 15, 2019 at 10:06:23 PM UTC+1, Morgan Rhodes wrote:
>>
>> The bionic repo should be working again. Let us know if you have any more
>> issues.
>>
>> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:
>>
>>> Hi Peter,
>>>
>>> Apologies, we've been having some repo issues today. I'm getting the
>>> bionic repository updated now and it should be done within the hour. I will
>>> send another update here when it completes.
>>>
>>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
>>> wrote:
>>>
>>>> Just this afternoon around 4PM I started noticing this happen in my
>>>> Docker builds that incorporate loading the Puppet agent:
>>>> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
>>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
>>>> the component 'puppet' (component misspelt in sources.list?)
>>>> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages'
>>>> as repository 'http://apt.puppetlabs.com bionic InRelease' doesn't
>>>> have the component 'puppet' (component misspelt in sources.list?)
>>>> Reading package lists...
>>>> Building dependency tree...
>>>> Reading state information...
>>>> Package puppet-agent is not available, but is referred to by another
>>>> package.
>>>> This may mean that the package is missing, has been obsoleted, or
>>>> is only available from another source
>>>>
>>>> E: Package 'puppet-agent' has no installation candidate
>>>>
>>>> same Docker build worked swimmingly earlier today and seems broken now
>>>> with NOTHING changing in the build (except to add NTP).  Any idea why this
>>>> is happening and more importantly any idea when the issue will go away?
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Peter L. Berghold   salty@gmail.com
>>>>
>>>> http://devops.berghold.net
>>>>
>>>>
>>>> --
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> Morgan Rhodes
>>> Release Engineering
>>> mor...@puppet.com
>>>
>>
>>
>> --
>> Morgan Rhodes
>> Release Engineering
>> mor...@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/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/5eaf34fc-a524-45b2-9c94-8ba176bb8c94%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

That path has been removed, as PC1 has gone EOL. All associated packages
have been moved to release-archives.puppet.com. We currently don't have
repositories enabled, since these streams will not receive any future
updates. Due to high demand, however, we are working to enable repositories
on release-archives. We will let you know when those are available.

On Wed, May 15, 2019 at 3:25 PM michael mack  wrote:

> How do you get the following old repo to work?
>
> rpm -Uvh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>
>
> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>
>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>> yum.puppet.com; 2. links to nightly release packages will be removed
>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved
>> to release-archives.puppet.com.
>>
>> All Puppet-maintained tooling and documentation referencing these paths
>> will be updated by the time these changes are made. Please ensure that
>> you are using current versions.
>>
>> Read on for details, especially if you've written custom tooling with
>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>
>> ---*---*---
>>
>> Hey folks,
>>
>> In an effort to reduce clutter and confusion on some of our public
>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>> and nightlies.puppet.com), we are planning to make some changes.
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>> Old: nightlies.puppet.com/yum/puppet-nightly/
>> puppet-nightly-release-sles-12.noarch.rpm
>>
>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>
>> These new paths are currently available for use. We plan to remove the
>> old ones on May 14. Please plan to make all updates during this period.
>>
>> 2. There will be no links to nightlies from main download sites.
>>
>> Links like yum.puppet.com/puppet-nightly
>> <http://yum.puppetlabs.com/puppet-nightly/> and
>> apt.puppet.com/puppet-nightly <http://apt.puppetlabs.com/puppet-nightly/>
>> WILL BE REMOVED on May 14.
>>
>> If you're looking for nightlies, visit nightlies.puppet.com. The
>> directory structure will match that of our main download sites.
>>
>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>> downloads}.puppet.com.
>>
>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>> end-of-life, so all packages will be moved to release-archives.puppet.com
>> on May 14 and no further updates will be made to these streams.
>>
>> ---*---*---
>>
>> We have set up a temporary s3 bucket that reflects the new layout if
>> you’d like to test changes before the cutover:
>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>
>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>> you visit the above url in your browser, the info you'll see is NOT
>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>> should only affect human eyes.
>>
>> If you have any questions or concerns about these changes, please
>> reply-all to this email.
>>
>> Thanks!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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/37de6ec5-f1a5-4d83-ba2f-5cb0f89f3e53%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/37de6ec5-f1a5-4d83-ba2f-5cb0f89f3e53%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hey folks,

REMINDER that the repository path changes* will take effect next week,
on Tuesday,
May 14.

Please make sure any custom tooling using these paths has been updated.

If you have any questions or concerns, please reply-all to this email.

Thanks!

* in case you forgot, changes include:

1. yum release packages will be removed from nested directories on
yum.puppet.com (e.g. yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm

--> yum.puppet.com/puppet6-release-el-7.noarch.rpm).

PLEASE NOTE that these are actually symlinks to release packages that live
inside their respective repositories, so package updates can be applied via
your package manager, like any other package.

2. links to nightly release packages will be removed from {yum,apt}.
puppet.com.
3. PC1 (and older) packages will be moved to release-archives.puppet.com.
This includes puppet-agent 1.10.x and puppet 4.x.

On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett 
wrote:

> Hi John,
>
> The top-level release packages are actually symlinks to release packages
> that *are* inside their respective repositories. When we publish new
> release packages, we update those links so that users don't have to bump
> version numbers in any tooling that installs these repositories.
>
> Thanks!
>
> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
> wrote:
>
>>
>>
>> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>>
>> It is conventional for repository release packages to be inside their
>> repositories so that repository configuration updates can be published and
>> applied via the same mechanism that is used for ordinary packages.  Even if
>> this is a capability that Puppet rarely uses, it seems ill-considered to
>> give it up.  The desire for consistency could be as well served by moving
>> the other release packages into their repos, or by making the release
>> packages consistently  available in both places.
>>
>>
>> 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/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68DrRGy%2BiO5yCykhCd0MwpLJSjY8FifFAB4HscNvuoQS%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] libxslt problem - how does it manifest?

[Molly Waggett]

Hi Tim,

Puppet itself is not affected by the libxslt security issue. We package
libxslt as a convenience for those who wish to install additional packages
that depend on it, like nokogiri, in a puppet-agent environment.

On Tue, Apr 30, 2019 at 1:41 PM Tim Skirvin  wrote:

> The primary purpose of this last puppet release (6.4.2, etc) seems
> to be to address a libxslt critical security bug.  Can somebody comment
> on how this bug affects puppet itself?  I want to know how to explain the
> need to patch to my management.
>
> https://tickets.puppetlabs.com/browse/PA-2667
> https://puppet.com/docs/puppet/6.4/release_notes_puppet.html
>
> - Tim Skirvin (tskir...@fnal.gov)
> --
> HPC Systems Administrator / Developer
> http://www.linkedin.com/in/tskirvin
>USCMS-T1 Collaboration Fermilab ECF
>
> --
> 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/20190430204147.GA5630%40fnal.gov
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi John,

The top-level release packages are actually symlinks to release packages
that *are* inside their respective repositories. When we publish new
release packages, we update those links so that users don't have to bump
version numbers in any tooling that installs these repositories.

Thanks!

On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
wrote:

>
>
> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> <http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>>
> It is conventional for repository release packages to be inside their
> repositories so that repository configuration updates can be published and
> applied via the same mechanism that is used for ordinary packages.  Even if
> this is a capability that Puppet rarely uses, it seems ill-considered to
> give it up.  The desire for consistency could be as well served by moving
> the other release packages into their repos, or by making the release
> packages consistently  available in both places.
>
>
> 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/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

[Puppet Users] [ACTION] Changes to release package links

[Molly Waggett]

TLDR: On May 14, 1. yum release packages will move to the top-level of
yum.puppet.com; 2. links to nightly release packages will be removed from
{yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved to
release-archives.puppet.com.

All Puppet-maintained tooling and documentation referencing these paths
will be updated by the time these changes are made. Please ensure that you
are using current versions.

Read on for details, especially if you've written custom tooling with
hard-coded download paths (e.g. CI testing or provisioning workflows).

---*---*---

Hey folks,

In an effort to reduce clutter and confusion on some of our public download
sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, and
nightlies.puppet.com), we are planning to make some changes.

1. Release packages (for all active streams) will live at the top level
only.

This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
giving us consistency with the layout on apt.puppet.com. Currently, yum
release packages live inside their corresponding repo directory, e.g.
yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
<http://yum.puppetlabs.com/puppet6/puppet6-release-fedora-28.noarch.rpm>.
THESE WILL BE REMOVED.

Here are some examples of where you will be able to find release packages:

Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm

New: yum.puppet.com/puppet6-release-el-7.noarch.rpm

Old: nightlies.puppet.com/yum/puppet-nightly/
puppet-nightly-release-sles-12.noarch.rpm

New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm

These new paths are currently available for use. We plan to remove the old
ones on May 14. Please plan to make all updates during this period.

2. There will be no links to nightlies from main download sites.

Links like yum.puppet.com/puppet-nightly
<http://yum.puppetlabs.com/puppet-nightly/> and
apt.puppet.com/puppet-nightly <http://apt.puppetlabs.com/puppet-nightly/>
WILL BE REMOVED on May 14.

If you're looking for nightlies, visit nightlies.puppet.com. The directory
structure will match that of our main download sites.

3. All PC1 (and older) packages will be removed from {yum, apt, downloads}.
puppet.com.

PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
end-of-life, so all packages will be moved to release-archives.puppet.com
on May 14 and no further updates will be made to these streams.

---*---*---

We have set up a temporary s3 bucket that reflects the new layout if you’d
like to test changes before the cutover:
yum-test.puppet.com.s3-website-us-west-2.amazonaws.com

PLEASE NOTE that s3 buckets are not naturally browsable on the web. If you
visit the above url in your browser, the info you'll see is NOT ACCURATE.
You CAN, however, download packages via wget/curl/etc. so this should only
affect human eyes.

If you have any questions or concerns about these changes, please reply-all
to this email.

Thanks!

-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

[Puppet Users] Removing puppet-client-tools from puppet6

[Molly Waggett]

Hey folks!

Unfortunately we've had to pull the puppet-client-tools packages from the
puppet6 package repositories. These packages were built against puppet5 and
are therefore incompatible with the version of OpenSSL used in puppet6.

We will republish puppet6-compatible packages soon.

Thanks for your understanding!

-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68A%2BbN-hKiH0H8oCfzDj5GEwc_c%2BSSSVqdpPOrLzxSyKtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Platform 6.3.0 is now available!

[Molly Waggett]

Hi Simon,

Puppetserver and PuppetDB versions do not necessarily match the overall
Puppet Platform version.
Puppet Platform 6.3.0 includes puppetserver 6.2.1. It did not include a new
release of puppetdb.

Hope that helps!

On Thu, Feb 28, 2019 at 4:25 PM Simon Tideswell 
wrote:

> Hello
>
> Was puppet DB 6.3.0 and Puppet server 6.3.0 withdrawn? I've had
> puppet-agent 6.3.0 deploy in my environment from apt.puppetlabs.com but
> not DB or server. And looking at apt.puppetlabs.com today in my browser I
> can see that 6.3.0 is not available? I'm using Ubuntu 18 (bionic).
>
> Is this a CDN issue? For me apt.puppetlabs.com resolves to ...
> d3e8phsy3q3gj7.cloudfront.net. 0 IN A 13.35.146.21
> d3e8phsy3q3gj7.cloudfront.net. 0 IN A 13.35.146.9
> d3e8phsy3q3gj7.cloudfront.net. 0 IN A 13.35.146.89
> d3e8phsy3q3gj7.cloudfront.net. 0 IN A 13.35.146.34
>
> I'm in Sydney, Australia. I get the same from home (Telstra) or at work
> (something else).
>
> Simon
>
> On Thu, Feb 21, 2019 at 5:58 AM Puppet Product Updates <
> puppet-product-upda...@puppet.com> wrote:
>
>> The next monthly release in the Puppet 6 series is now available. Puppet
>> Platform 6.3.0 includes security improvements, bug fixes, and
>> backwards-compatible feature updates to Puppet Server, Puppet Agent, and
>> Facter. Highlights of this release include:
>>
>>- Updates to Puppet Server's SSL (bouncycastle) library from upstream
>>to address security issues (SERVER-2431
>><https://tickets.puppetlabs.com/browse/SERVER-2431>)
>>- Support for macOS Mojave (10.14) agents (PA-2217
>><https://tickets.puppetlabs.com/browse/PA-2217>)
>>- An improvement to the Puppet agent's log output to distinguish
>>between intentional change (additional or updated resources in the 
>> catalog)
>>and corrective change (drift detected on the node) (PUP-9324
>><https://tickets.puppetlabs.com/browse/PUP-9324>)
>>
>> View the full release notes and installation information:
>> https://puppet.com/docs/puppet/6.3/puppet_index.html
>>
>>
>> --
>> 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/CAFOE68AVvdnc%2BjGn6%2BHb%3DGbfEyY6AHz0viM%3D_0%2BOio8L5y%3DD3w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CAFOE68AVvdnc%2BjGn6%2BHb%3DGbfEyY6AHz0viM%3D_0%2BOio8L5y%3DD3w%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/CAEei81nSeHfWzFrEW0dyoMx9xr1aHPaE%2BmyQ95pfPNgykgKL9A%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAEei81nSeHfWzFrEW0dyoMx9xr1aHPaE%2BmyQ95pfPNgykgKL9A%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68CywrXXGffnmy_wE4NRMjFCwK%2BmZiNmPE%2BRU%3DNh%3Dh7jGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] pupet collections eol

[Molly Waggett]

Hi João,

The EOL for Puppet Collections (now called Puppet Platform) corresponds
with Puppet Enterprise EOL (see our lifecycle page
<https://puppet.com/misc/puppet-enterprise-lifecycle>).

PC1 is included in PE 2016.4, so its EOL is December 31, 2018 (though we
are in the extended support period, so only critical bug fixes and security
updates will trigger a release).
puppet5 is included in PE 2018.1, so it will EOL in May 2020.

Thanks!


On Tue, Oct 2, 2018 at 3:21 AM João Matos  wrote:

> Hi
>
> spent several hours online searching and couldnt find an answer.
> where is the information about the end of life (specific date) for the
> puppet collections?
>
>
> Tks
>
> --
> 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/92a6bb39-2e84-4263-ac11-d712f25feb41%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/92a6bb39-2e84-4263-ac11-d712f25feb41%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Puppet 4 open source EOL

[Molly Waggett]

After PC1, we changed how we name our collections to align with the version
of puppet included in them.
puppet5 is the collection that would've been PC2, which we shipped a year
ago.
puppet6 is the latest collection, which we shipped last week.

On Tue, Oct 2, 2018 at 3:49 AM João Matos  wrote:

> If PC1 is EOL  where is PC2?
>
>
>
>
> On Wednesday, 15 August 2018 17:54:02 UTC+1, Branan Purvine-Riley wrote:
>>
>> That's correct. At this point we have no more scheduled PC1 releases, and
>> would only do one for a security issue. In October we will stop releasing
>> it entirely.
>>
>> The new PE LTS release is based on puppet-agent 5.5.z, so that release
>> will be receiving fixes until May of 2020. We are also planning to have
>> Puppet 6 available in the fall.
>>
>> On Wed, Aug 15, 2018 at 9:49 AM Nick Bertrand 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've found a few mentions that Puppet 4, specifically Puppet Collection
>>> 1, reaches end-of-life October 2018. Does this mean that
>>> http://yum.puppetlabs.com/el/7/PC1/, for example, will no longer get
>>> security or other fixes backported after October 2018?
>>>
>>> Thanks,
>>>
>>> Nick Bertrand
>>>
>>> --
>>> 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/db6a6b11-9d60-4186-9b1c-a1d9e8933fad%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/db6a6b11-9d60-4186-9b1c-a1d9e8933fad%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Regards,
>>
>> Branan Riley
>> Senior Software Engineer, Puppet inc.
>>
> --
> 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/bc74dcf3-874b-4ce5-a7b3-d3bd0ad757fe%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/bc74dcf3-874b-4ce5-a7b3-d3bd0ad757fe%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68AmsttCMJ%2Bry%3DptUOUiBv5orprp4zVZB%2BwwSLcouOsdgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Platform 5.5.6 is now available!

[Molly Waggett]

Puppet Platform 5.5.6 is a bug-fix, feature, and deprecations release that
includes updates for Puppet 5.5.6, Facter 3.11.4, and Puppet agent 5.5.6.
For details, see the Puppet
<https://puppet.com/docs/puppet/5.5/release_notes.html>, Facter
<https://puppet.com/docs/facter/3.11/release_notes.html>, and puppet-agent
<https://puppet.com/docs/puppet/5.5/release_notes_agent.html>release notes.

Puppet Server 5.3.5, also going out with this release, includes a new
command line tool for interacting with the Puppet CA. For details, see Puppet
Server <https://puppet.com/docs/puppetserver/5.3/release_notes.html> release
notes.


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Puppet repository accessable on IPv6

[Molly Waggett]

Hi Bart-Jan,

We have a ticket to track this effort: CPR-518
<https://tickets.puppetlabs.com/browse/CPR-518>. If you could add your
comments regarding your setup there, we will work on getting that
prioritized.

Thanks!

On Fri, Jun 15, 2018 at 6:57 AM, Bart-Jan Vrielink 
wrote:

> Hello,
>
>
> I'm trying to install a puppet agent on a server that only has IPv6
> access. Is there any mirror of yum.puppet.com that has IPv6 or are we
> waiting for the next greatest thing to come after IPv6?
>
> --
> 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/zarafa.5b23c5dd.3052.6f668b597e71d333%40anjie.
> dontpanic.nl
> <https://groups.google.com/d/msgid/puppet-users/zarafa.5b23c5dd.3052.6f668b597e71d333%40anjie.dontpanic.nl?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68C%2Bob%3Dkoyw3uLC137HuXmhLP2kag7mHfQLQLYmH6Gc11w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Molly Waggett]

Dirk,

There are Bionic packages in the puppet-agent 5.5.x stream:
http://apt.puppetlabs.com/pool/bionic/puppet5/p/puppet-agent/


On Wed, Jun 13, 2018 at 10:58 PM, Dirk Heinrichs 
wrote:

> From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com]
> On Behalf Of Garrett Guillotte
>
> > • Puppet agent 1.10.13 and 1.10.14
>
> What about Ubuntu Bionic (18.04)?
>
> Bye...
>
> Dirk
>
> --
> 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/DM3PR15MB08772366FF7077E797B4AB7FAA7D0%40DM3PR15MB0877.
> namprd15.prod.outlook.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] Re: Announce: Puppet Platform 5.5.0 is now available

[Molly Waggett]

Hi Ryan,

We expect to include Puppet Platform 5.5.x in the next PE release (2018.1),
coming in the next couple months.

On Wed, Mar 21, 2018 at 6:28 AM, Ryan Murphy <ryan.mur...@rychannel.com>
wrote:

> What version of PE will contain this?
>
>
> On Tuesday, March 20, 2018 at 3:20:15 PM UTC-5, Molly Waggett wrote:
>>
>> Puppet Platform 5.5.0 is a bug-fix and feature release that adds agent
>> support for Fedora 27, adds several stdlib functions to Puppet's core
>> functions, improves the puppet config command and yumrepo provider,
>> restores the ability to upload facts to Puppet Server and other Puppet
>> masters, and adds additional performance metrics to the run report.
>>
>> Puppet Server 5.3.0 can now use some gems shipped by puppet-agent and
>> compresses catalog response bodies. PuppetDB 5.2.1 improves the performance
>> of fact queries. Facter 3.11 fixes an issue with uptime tracking in Windows
>> and reports SSH key types in the `ssh` fact.
>>
>> For details, see the release notes for Puppet agent 5.5.0
>> <https://puppet.com/docs/puppet/5.5/release_notes_agent.html>, Facter
>> 3.11.0 <https://puppet.com/docs/facter/3.11/release_notes.html>, Puppet
>> Server 5.3.0
>> <https://puppet.com/docs/puppetserver/5.3/release_notes.html>, and PuppetDB
>> 5.2.1 <https://puppet.com/docs/puppetdb/5.2/release_notes.html>.
>>
>> Thanks!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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/3f54d375-250a-49d8-b839-5424ec9208ac%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/3f54d375-250a-49d8-b839-5424ec9208ac%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

[Puppet Users] Announce: Puppet Platform 5.5.0 is now available

[Molly Waggett]

Puppet Platform 5.5.0 is a bug-fix and feature release that adds agent
support for Fedora 27, adds several stdlib functions to Puppet's core
functions, improves the puppet config command and yumrepo provider,
restores the ability to upload facts to Puppet Server and other Puppet
masters, and adds additional performance metrics to the run report.

Puppet Server 5.3.0 can now use some gems shipped by puppet-agent and
compresses catalog response bodies. PuppetDB 5.2.1 improves the performance
of fact queries. Facter 3.11 fixes an issue with uptime tracking in Windows
and reports SSH key types in the `ssh` fact.

For details, see the release notes for Puppet agent 5.5.0
<https://puppet.com/docs/puppet/5.5/release_notes_agent.html>, Facter 3.11.0
<https://puppet.com/docs/facter/3.11/release_notes.html>, Puppet Server
5.3.0 <https://puppet.com/docs/puppetserver/5.3/release_notes.html>,
and PuppetDB
5.2.1 <https://puppet.com/docs/puppetdb/5.2/release_notes.html>.

Thanks!

-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

Re: [Puppet Users] What changed on yum.puppetlabs.com and apt.puppetlabs.com?

[Molly Waggett]

Hi Sean,

We have opened CPR-519 <https://tickets.puppetlabs.com/browse/CPR-519> and
are looking into your issue.

Thanks!

On Thu, Mar 1, 2018 at 8:34 AM, Sean <smalde...@gmail.com> wrote:

> Hi,
>
> Has something significant changed on repo sites?  For years, I have been
> using lftp to selectively mirror parts of these repos to use on Internet
> isolated networks.  lftp is a great tool and a little easier and more
> efficient than wget.  Note, we are not able to use rsync, it is not
> permitted as an outbound protocol.
>
> So, what's happening when I use lftp today?  Every directory on the repo
> looks like a file, not a directory, see below:
> $ lftp http://apt.puppetlabs.com
> cd ok, cwd=/
> lftp apt.puppetlabs.com:/> ls
> -rw-r--r--  --  index_by_name_reverse.html
> -rw-r--r--  --  index_by_lastModified.html
> -rw-r--r--  --  index_by_size.html
> -rw-r--r--  --  index_by_name.html
> -rw-r--r--  --  DEB-GPG-KEY-puppet
> -rw-r--r--  --  DEB-GPG-KEY-puppetlabs
> -rw-r--r--  --  DEB-GPG-KEY-reductive
> -rw-r--r--  --  README.txt
> -rw-r--r--  --  dists
> -rw-r--r--  --  keyring.gpg
> -rw-r--r--  --  pool
> -rw-r--r--  --  pubkey.gpg
> ..
>
> What should happen?
> $ lftp http://mirror.centos.org
> cd ok, cwd=/
> lftp mirror.centos.org:/> ls
> drwxr-xr-x  --  /
> -rw-r--r--  --  HEADER.images/modern-CentOS-logo.png
> -rw-r--r--  --  icons/blank.gif
> -rw-r--r--  --  icons/unknown.gif
> -rw-r--r--   11  2018-03-01 16:12  TIME
> -rw-r--r--  --  icons/folder.gif
> drwxr-xr-x-  2017-09-06 06:57  altarch
> drwxr-xr-x-  2009-09-09 05:18  centos-2
> drwxr-xr-x-  2007-10-22 17:16  centos-3
> drwxr-xr-x-  2011-03-02 14:00  centos-4
> drwxr-xr-x-  2014-09-29 08:59  centos-5
> drwxr-xr-x-  2017-04-05 11:36  centos-6
> drwxr-xr-x-  2017-09-13 20:25  centos-7
> drwxr-xr-x-  2017-09-13 13:56  centos
> -rw-r--r--  132  2018-03-01 16:10  dir_sizes_altarch
> -rw-r--r--  924  2018-03-01 16:10  dir_sizes_centos
> drwxr-xr-x-  2014-07-07 12:49  mirrorscripts
> -rw-r--r--  --  icons/text.gif
> ..
>
> As a result, my entire mirror of both apt/yum.puppetlabs.com turned into
> a bunch of static files, deleting a heap of data I'm going to have figure
> out how to download again using some other means.  I attempted to
> reconfigure my mirror script to use wget instead of lftp, but it only
> downloaded html versions of the directory indexes, no RPMs, no repodata.
>
> Any ideas or anything as to what's up?
>
> Thanks for the assistance!
>
> --
> 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/7355d1ea-9a01-4338-ad53-7fa9fc8cc80d%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/7355d1ea-9a01-4338-ad53-7fa9fc8cc80d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

[Puppet Users] Re: puppet5-nightly repos coming soon to nightlies.puppet.com!

[Molly Waggett]

Hey Puppet Users!

puppet5 nightlies are finally live at nightlies.puppet.com!

We've done our best to make this transition smooth, but if you run into
issues or have any questions, please let us know!

Thanks!


On Tue, Jan 2, 2018 at 11:25 AM, Molly Waggett <molly.wagg...@puppet.com>
wrote:

> Hello Puppet Users!
>
> We are excited to announce new and improved puppet5-nightly and
> puppet-nightly package repositories, which will be rolling out mid-January!
>
> The puppet5-nightly repo will always contain the latest dev builds from
> components of Puppet Platform 5 (puppet-agent, puppetserver, and puppetdb),
> while puppet-nightly will contain the latest dev builds for the latest
> Puppet Platform major version. In other words, puppet-nightly will contain
> Platform 6, 7, etc. builds when they are released, but puppet5-nightly will
> not go beyond Platform 5.
>
> Previously, nightlies were spread across apt.puppetlabs.com,
> yum.puppetlabs.com, and downloads.puppetlabs.com. With this change, we
> will consolidate all of the nightly builds in one place:
> nightlies.puppet.com. Builds that currently exist on nightlies.puppet.com
> will be replaced with these new nightly builds. If you have already
> downloaded nightly release packages, you will need to replace them with one
> pointing at the new location.
>
> In general, nightly builds will be purged after 30 days.
>
> If you have any questions, please let me know!
>
> Thanks!
>
> --
> *Molly Waggett*
> Assoc. Release Engineer
>



-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68DPsOHv0Y%2BOFhofSLm2CWBT-HgsWwf2Y8rQZ%3Dg9%2BRkXrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Platform 5.3.5 is now available

[Molly Waggett]

This is a bug-fix release of Puppet Platform. Only Puppet Agent has been
updated.

Puppet Agent 5.3.5 is a bug-fix release that includes a fix for Puppet
5.3.4 regressions. It also includes Facter 3.9.5, which fixes a bug on c5
instances for AWS EC2. For details, see the Puppet 5.3.5
<https://puppet.com/docs/puppet/5.3/release_notes.html> and Facter 3.9.5
<https://puppet.com/docs/facter/3.9/release_notes.html> release notes.

Thanks!

-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

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

[Puppet Users] Announce: Puppet Agent 1.10.10 is now available

[Molly Waggett]

This is a bug-fix release of Puppet Agent, which updates Puppet to 4.10.10
and Facter to 3.6.9. Puppet 4.10.10 adds two new settings, `sourceaddress`
and `runtimeout`, and fixes several bugs. This release also adds support
for macOS 10.13 (High Sierra) and EL 7 on arm64. For details, see the Puppet
Agent <https://puppet.com/docs/puppet/4.10/release_notes_agent.html> release
notes.

Thanks!


-- 
*Molly Waggett*
Release Engineer @ Puppet, Inc.

-- 
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/CAFOE68DH8s1VWT_sFAsqgH_HdHtRopTwbj3-HDYmKR%3Dq%3DsohzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Platform 5.3.4 is now available

[Molly Waggett]

This is a bug-fix release of Puppet Platform. All three components -
puppet-agent, PuppetDB, and Puppet Server - have been updated.

This release of Puppet Agent updates Puppet to 5.3.4 and Facter to 3.9.4.
Puppet 5.3.4 adds two new settings, `sourceaddress` and `runtimeout`. It
also adds module translation distribution to pluginsync, improves Japanese
localization, and fixes several bugs. This release also adds support for
macOS 10.13 (High Sierra), EL 7 on arm64, and Amazon Linux 2. For details,
see the Puppet Agent
<https://puppet.com/docs/puppet/5.3/release_notes_agent.html> release notes.

PuppetDB 5.1.4 and Puppet Server 5.1.5 add Debian 9 (Stretch) packages, as
well as additional bug fixes. For details, see the Puppet Server
<https://puppet.com/docs/puppetserver/5.1/release_notes.html> and PuppetDB
<https://puppet.com/docs/puppetdb/5.1/release_notes.html> release notes.

Thanks!

-- 
*Molly Waggett*
Release Engineer @ Puppet, Inc.

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

[Puppet Users] puppet5-nightly repos coming soon to nightlies.puppet.com!

[Molly Waggett]

Hello Puppet Users!

We are excited to announce new and improved puppet5-nightly and
puppet-nightly package repositories, which will be rolling out mid-January!

The puppet5-nightly repo will always contain the latest dev builds from
components of Puppet Platform 5 (puppet-agent, puppetserver, and puppetdb),
while puppet-nightly will contain the latest dev builds for the latest
Puppet Platform major version. In other words, puppet-nightly will contain
Platform 6, 7, etc. builds when they are released, but puppet5-nightly will
not go beyond Platform 5.

Previously, nightlies were spread across apt.puppetlabs.com,
yum.puppetlabs.com, and downloads.puppetlabs.com. With this change, we will
consolidate all of the nightly builds in one place: nightlies.puppet.com.
Builds that currently exist on nightlies.puppet.com will be replaced with
these new nightly builds. If you have already downloaded nightly release
packages, you will need to replace them with one pointing at the new
location.

In general, nightly builds will be purged after 30 days.

If you have any questions, please let me know!

Thanks!

-- 
*Molly Waggett*
Assoc. Release Engineer

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

[Puppet Users] Puppet Enterprise 2016.4.9, 2017.2.5, and 2017.3.2 are now available!

[Molly Waggett]

Dear Puppet Enterprise Users,

Puppet Enterprise 2016.4.9, 2017.2.5, and 2017.3.2 are now available.

These are security and bugfix releases of Puppet Enterprise. All users of
Puppet Enterprise are encouraged to upgrade when possible to the newest
versions.

These releases include fixes to address security vulnerabilities in Java,
Curl, Ruby, Rubygems, as well as a number of other bugfixes and
improvements.

For more information on the releases, see
https://puppet.com/docs/pe/2016.4/release_notes.html,
https://puppet.com/docs/pe/2017.2/release_notes.html, and
https://puppet.com/docs/pe/2017.3/release_notes/release_notes.html

As a current Puppet Enterprise user, you can upgrade to these new versions
as part of your annual subscription. If upgrading, it is required to
upgrade your master, puppetdb, and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Support.

And if you’re wondering what’s new in Puppet Enterprise 2017.3, you can
learn more about new task automation and package inspection capabilities by
visiting our blog:
https://puppet.com/blog/taking-you-journey-automation-puppet-enterprise-20173


-- 
*Molly Waggett*
Assoc. Release Engineer

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

[Puppet Users] Announce: Puppet Platform 5.3.3 is now available

[Molly Waggett]

This is a bug-fix release of Puppet Platform. All three components -
puppet-agent, PuppetDB, and Puppet Server - have been updated.

This release of Puppet Agent contains several Puppet and Facter bug fixes,
and updates Puppet to 5.3.3, Facter to 3.9.3, and MCollective to version
2.11.4. For details, see the Puppet agent release notes
<https://puppet.com/docs/puppet/5.3/release_notes_agent.html>.

PuppetDB 5.1.3 includes bug fixes and performance improvements, including
an optional facts backlist and a fix for crashes after fact data
migrations. For details, see the PuppetDB release notes
<https://puppet.com/docs/puppetdb/5.1/release_notes.html>.

Puppet Server 5.1.4 adds a new feature: serving versioned tasks files from
the static file content endpoint. For details, see the Puppet Server
release notes <https://puppet.com/docs/puppetserver/5.1/release_notes.html>.

-- 
*Molly Waggett*
Assoc. Release Engineer

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

[Puppet Users] Today’s a big day for Puppet customers and users

[Molly Waggett]

Today we’re thrilled to announce our largest and most important set of
product innovations. If you want to scale automation across your entire
organization or deliver better software faster, keep reading or join us for
the PuppetConf live stream (https://puppet.com/puppetconf/livestream/signup)
between 9 a.m. and 10:20 a.m. PT.

*Puppet Discovery™*
See everything you have in real time across your on-premises, cloud and
container infrastructure with the new Puppet Discovery. With full
visibility into your infrastructure, plus meaningful insights, you can
easily see what you have and what you need to automate next. Learn more:
https://puppet.com/blog/announcing-puppet-discovery

*Puppet Tasks™*
Puppet Tasks is a family of offerings that include a new open source
product and Puppet Enterprise capabilities that make it easy to
troubleshoot systems, deploy one-off changes, and execute sequenced
actions. Learn more about Puppet Bolt™ and Puppet Enterprise Task
Management:
https://puppet.com/blog/easily-automate-ad-hoc-work-new-puppet-tasks

*Puppet Enterprise 2017.3*
In our latest release, Package Inspector updates make it easier to browse
and search for packages, Task Management helps you execute ad hoc tasks
across tens of thousands of nodes, the Puppet 5 Platform is baked in, and
there’s expanded Japanese language support. Learn more:
https://puppet.com/blog/taking-you-journey-automation-puppet-enterprise-20173

*Puppet Pipelines™ and Puppet® Container Registry*
We recently acquired Distelli, an innovative continuous delivery platform
for developers and enterprises. We’re happy to introduce their products as
part of our portfolio: Puppet Pipelines for Applications, Puppet Pipelines
for Containers, and Puppet Container Registry. Learn more:
https://puppet.com/blog/introducing-puppet-pipelines-and-puppet-container-registry

*New Splunk integrations*
We’re pleased to announce our new partnership and integrations with Splunk.
The new integrations will help you fully leverage the data, insights,
action, and ongoing policy enforcement across the platforms so you can gain
deeper insights and drive change. Learn more:
https://puppet.com/blog/automating-modern-it-splunk-puppet

*New and updated Google Cloud Platform modules*
Our friends at Google Cloud updated their recently released IaaS modules
with new functionality, including the ability to use Puppet Tasks. They
also published a new set of modules to automate even more of their
services. Learn more: https://puppet.com/products/managed-technology/google

*New Kubernetes, Helm and Docker modules*
We’re thrilled to announce new modules to install and manage Kubernetes and
Helm, and the applications running on your Kubernetes clusters. We also
released an enhanced Docker module with support for Puppet Code Manager,
Docker Swarm mode, and Docker Secrets. Learn more:
https://puppet.com/blog/announcing-kream-and-new-kubernetes-helm-and-docker-modules

Thanks!

-- 
*Molly Waggett*
Assoc. Release Engineer

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

[Puppet Users] Announce: Puppet Platform 5.3.2 is now available

[Molly Waggett]

This is a bug-fix release of Puppet Platform. The only updated component is
Puppet, to version 5.3.2.

Puppet 5.3.2 adds an optional `disable_i18n` setting to `puppet.conf`. If
set to `true`, this setting disables localized strings in Puppet log
messages, reports, and parts of the CLI. For details, see the Puppet 5.3.2
release notes at
https://docs.puppet.com/puppet/5.3/release_notes.html#puppet-532.


-- 
*Molly Waggett*
Assoc. Release Engineer
--


*PuppetConf 2017, 10-12 OctoberSan Francisco, CaliforniaRegister now to
save <https://puppet.com/puppetconf/registration-pricing>.*

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

[Puppet Users] Announce: Puppet Enterprise 2016.4.8 and 2017.2.4 are now available!

[Molly Waggett]

Dear Puppet Enterprise Users,

Puppet Enterprise 2016.4.8 and 2017.2.4 are now available.

These are security and bugfix releases of Puppet Enterprise. All users of
Puppet Enterprise 2016.4.x and 2017.2.x are encouraged to upgrade when
possible to Puppet Enterprise 2016.4.8 and 2017.2.4, respectively.

These releases include fixes to address security vulnerabilities in
PostgreSQL and augeas, as well as a number of other bugfixes and
improvements.

For information on the bug fixes in these releases, see
https://docs.puppet.com/pe/2016.4/release_notes.html and
https://docs.puppet.com/pe/2017.2/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is required to upgrade
your master, puppetdb, and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Support.

-- 
*Molly Waggett*
Assoc. Release Engineer
--


*PuppetConf 2017, 10-12 OctoberSan Francisco, CaliforniaRegister now to
save <https://puppet.com/puppetconf/registration-pricing>.*

-- 
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/CAFOE68A8g6j_raYbA2_TH-OnvyP7qtnhO9X%2BWY4f33p%3D%2BUy4Aw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Enterprise 2016.4.7 and 2017.2.3 are now available!

[Molly Waggett]

Dear Puppet Enterprise Users,

Puppet Enterprise 2016.4.7 and 2017.2.3 are now available.

These are security and bugfix releases of Puppet Enterprise. All users of
Puppet Enterprise 2016.4.x and 2017.2.x are encouraged to upgrade when
possible to Puppet Enterprise 2016.4.7 and 2017.2.3, respectively.

These releases include fixes to address security vulnerabilities in Java
and nginx, as well as a number of other bugfixes and improvements.

For information on the bug fixes in these releases, see
https://docs.puppet.com/pe/2016.4/release_notes.html and
https://docs.puppet.com/pe/2017.2/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is required to upgrade
your master, puppetdb, and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Support.

-- 
*Molly Waggett*
Assoc. Release Engineer
--
Register now:
PuppetConf 2017 <https://puppet.com/puppetconf>, 10-12 October
San Francisco, California
Save $328, register by 30 June w/ early adopter discount
<https://www.eventbrite.com/e/puppetconf-2017-10-12-october-tickets-28617829699?discount=earlyadopter>

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

[Puppet Users] Announce: Puppet Enterprise 2016.4.6 and 2017.2.2 are now available!

[Molly Waggett]

Dear Puppet Enterprise Users,

Puppet Enterprise 2016.4.6 and 2017.2.2 are now available.

These are security and bugfix releases of Puppet Enterprise. All users of
Puppet Enterprise 2016.4.x and 2017.2.x are encouraged to upgrade when
possible to Puppet Enterprise 2016.4.6 and 2017.2.2, respectively.

These releases include fixes to address security vulnerabilities in the
Classifier, PostgreSQL, and libxslt, as well as a number of other bugfixes
and improvements.

For information on the bug fixes in these releases, see
https://docs.puppet.com/pe/2016.4/release_notes.html and
https://docs.puppet.com/pe/2017.2/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is required to upgrade
your master, puppetdb, and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Support.

-- 
*Molly Waggett*
Assoc. Release Engineer
--
Register now:
PuppetConf 2017 <https://puppet.com/puppetconf>, 10-12 October
San Francisco, California
Save $328, register by 30 June w/ early adopter discount
<https://www.eventbrite.com/e/puppetconf-2017-10-12-october-tickets-28617829699?discount=earlyadopter>

-- 
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/CAFOE68Au%2B86g0JZYOBgFdTuoY-orDmbOw7-M%2BP0-RPFLTQQHLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Problem with load balanced puppetdb

[Molly Waggett]

Angel,

Glad your issue seems to have been resolved. Let us know if you have any
more questions.

On Wed, Jul 6, 2016 at 12:31 AM, Angel L. Mateo <ama...@um.es> wrote:

> Looking deeper... I have been using puppetdb 2.3.x until a few
> days. The problem I found after upgrading to puppetdb 4.1.2 and I didn't
> realize that tables for catalog entries have changed. In puppetdb 2.3.x
> catalog_resources and catalogs tables where directly related with the id of
> the catalog entry, but now they are related with the latest_catalog table.
> Now all make sense.
>
> El 06/07/16 a las 08:18, Angel L. Mateo escribió:
>
>> El 05/07/16 a las 20:00, Molly Waggett escribió:
>>
>>> Hi Angel,
>>>
>>> Could you provide more information about your setup? Specifically, how
>>> are you replicating data between your PuppetDBs?
>>>
>>>  They both use the same database, so I don't replicate data. I don't
>> have HA postgresql server, it is server by just one.
>>
>>  Besides this, puppetdb configuration is done with
>> puppetlabs/puppetdb module (v5.1.2) which its default options.
>>
>>
> --
> Angel L. Mateo Martínez
> Sección de Telemática
> Área de Tecnologías de la Información
> y las Comunicaciones Aplicadas (ATICA)
> http://www.um.es/atica
> Tfo: 868887590
> Fax: 86337
>
> --
> 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/577CB3C9.40907%40um.es.
>
> 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/CAFOE68CMZ%3DRCAOh5JGbNyVEVQDoY5mykGNqnMR0MmP7cEjU_FA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] near-identical puppetdb queries, dissimilar outputs

[Molly Waggett]

Hi Christopher,

Could you clarify exactly how you're making these queries, either by
including the exact curl invocation or the code you're using?

Thanks!

On Sun, Jul 3, 2016 at 7:24 PM, Christopher Wood  wrote:

> This is with puppetdb 3.2.4 running on java 1.8 on CentOS 6. Does this
> behaviour sound familiar to anybody?
>
> This query (query1) produces fact paths limited to the named facts from
> the "stype" of "pmail" in the "environment" of "mail".
>
> https://gist.github.com/christopherwood/aec60bc751828ccfcaa01cbaa18b43a4
>
> This query (query7), different from the first only in that the string
> "pmail" is replaced by the string "relay", produces a list of every fact
> path from every host in every environment.
>
> https://gist.github.com/christopherwood/6ad03d58452175ba3a81d4f5d2693e3f
>
> This behaviour is consistent through puppetdb restarts.
>
> [root@puppetdb2 ~]# rpm -q puppetdb
> puppetdb-3.2.4-1.el6.noarch
>
> [root@puppetdb2 ~]# rpm -qa | grep openjdk
> java-1.8.0-openjdk-headless-1.8.0.71-1.b15.el6_7.x86_64
>
>
> $ mco facts stype -T mail -S 'stype=relay or stype=pmail'
> Report for fact: stype
>
> pmailfound 149 times
> relayfound 113 times
>
> Finished processing 262 / 262 hosts in 1088.18 ms
>
>
> My next step would be pointing the production puppetmasters at another
> puppetdb instance and elevating to debug logging here, but I'd rather not
> make a production change if this is something obvious. Or obvious to
> somebody else, I can't find anything about this on tickets.puppetlabs.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/20160704022432.GA17400%40iniquitous.heresiarch.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/CAFOE68BgAaTw%2BtCJoTf6tONcBXRoWUPiZkwC92kginqhnuQL%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: PuppetDB 4.1.2 is now available

[Molly Waggett]

PuppetDB 4.1.2 - June 22, 2016
===

PuppetDB 4.1.2 is a backward-compatible bugfix release that speeds up node
queries, fixes a bug that slowed garbage collection, and improves error
logging.

PuppetDB 4.1.2 Downloads


Available in native package format as part of Puppet Collection 1
(PC1). More information on the PC1 repositories is available here:
https://bit.ly/1MpEieG

Binary tarball: https://downloads.puppetlabs.com/puppetdb/

Source: https://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an
affected PuppetDB version of 4.1.2:
https://tickets.puppetlabs.com/browse/PDB

Documentation: https://docs.puppetlabs.com/puppetdb/4.1/

Puppet module: https://forge.puppetlabs.com/puppetlabs/puppetdb

PuppetDB 4.1.2 Release Notes


Please consult the release notes here:
https://docs.puppetlabs.com/puppetdb/4.1/release_notes.html
<https://docs.puppet.com/puppetdb/4.1/release_notes.html#section>

Contributors

Andrew Roetker, Chris Cowell, Garrett Guillotte, Molly Waggett, Rob
Browning,
Ryan Senior, and Wyatt Alt

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