Is server still present in puppet 6?

Hmm digged a little and found puppet master commands removed[1] and running as as service is removed [2] in puppet 6 which was deprecated since long, now for server functionality puppetserver(https://github.com/puppetlabs/puppetserver) needs to be used. Also looks like they missed removing some puppetmaster things from puppet repo[3].
I doubt seeing the deprecation from long puppet-server package in Fedora was working? Now how to move forward with 6.4.1, just remove the server package completely?

[1] https://puppet.com/docs/puppet/6.0/release_notes_puppet.html#puppet-master-command
[2] https://tickets.puppetlabs.com/browse/PUP-8591
[3] https://github.com/puppetlabs/puppet/blob/master/ext/redhat/server.init

I am not sure, that's why I have not upgraded to puppet 6 :-)

Getting a puppetserver package based on https://github.com/puppetlabs/puppetserver
would be the best option, unsure how much work that will be.

Any reason you need to upgrade to puppet 6 now?

OpenStack is switching to puppet-6 and we use fedora builds to test it, that's the immediate need for it.

IIUC, puppet-6 was released in sept '18, so I'd say it'd be good to update it in next Fedora release.

@terjeros can you please check the plan regarding packaging puppetserver to clear path for puppet-6.4.1.

According to puppet lifecycle, puppet-5.5 will be maintained until may-2020 while fedora31 will be " until 1 month after the release of Fedora 33" which is long after may-2020 so i'd say updating to puppet-6 would be good in FC31.

@terjeros what do you think?

Note that Puppet 6 vendors a few modules. These used to be built in, but were extracted. Copying my comment from https://bugs.gentoo.org/671886

• augeas_core https://github.com/puppetlabs/puppetlabs-augeas_core
• cron_core https://github.com/puppetlabs/puppetlabs-cron_core
• host_core https://github.com/puppetlabs/puppetlabs-host_core
• mount_core https://github.com/puppetlabs/puppetlabs-mount_core
• scheduled_task https://github.com/puppetlabs/puppetlabs-scheduled_task
• selinux_core https://github.com/puppetlabs/puppetlabs-selinux_core
• sshkeys_core https://github.com/puppetlabs/puppetlabs-sshkeys_core
• yumrepo_core https://github.com/puppetlabs/puppetlabs-yumrepo_core
• zfs_core https://github.com/puppetlabs/puppetlabs-zfs_core
• zone_core https://github.com/puppetlabs/puppetlabs-zone_core

Note that Puppet 6 vendors a few modules. These used to be built in, but were extracted. Copying my comment from https://bugs.gentoo.org/671886

Each separated module has it's own release and lifecycle so i guess we should create separated packages and make puppet-agent depends on them for backwards compatibility?

I think that's best. You probably want to set a minimum version that matches to what puppet-agent ships. Not sure if Puppetlabs has a policy on what to allow (probably not because they just bundle a single version), but I'd also apply a maximum version. I think we can assume they follow semantic versioning. This will allow users to treat Puppet x.y.z in Fedora the same Puppet AIO from Puppetlabs.

While testing it, i've also found i need to add semver_puppet ruby library which has been unbundled also

For reference, puppet-agent describes what it bundles. It's good for module authors to consider these the lower version bounds so Fedora isn't odd. Note that this is from puppet-agent 6.6.0.

Name        : puppet-agent
Arch        : x86_64
Version     : 6.6.0
Release     : 1.el7
Size        : 22 M
Repo        : puppet/x86_64
Summary     : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, and hiera.
URL         : https://www.puppetlabs.com
License     : See components
Description : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, and hiera.
            : 
            : Contains the following components:
            : cleanup
            : cpp-hocon 0.2.0
            : cpp-pcp-client 1.6.0
            : dmidecode 2.12
            : facter 3.14.1
            : hiera 3.5.0
            : leatherman 1.7.0
            : libwhereami 0.2.2
            : module-puppetlabs-augeas_core 1.0.4
            : module-puppetlabs-cron_core 1.0.0
            : module-puppetlabs-host_core 1.0.2
            : module-puppetlabs-mount_core 1.0.2
            : module-puppetlabs-scheduled_task 1.0.0
            : module-puppetlabs-selinux_core 1.0.1
            : module-puppetlabs-sshkeys_core 1.0.2
            : module-puppetlabs-yumrepo_core 1.0.3
            : module-puppetlabs-zfs_core 1.0.1
            : module-puppetlabs-zone_core 1.0.1
            : puppet 6.6.0
            : puppet-resource_api 1.8.5
            : puppet-runtime 201906190
            : pxp-agent 1.12.1
            : runtime
            : shellpath 2015-09-18
            : virt-what 1.18
            : wrapper-script

I've prepared some distgits with required new packages and updated puppet in:

https://github.com/amoralej/puppet6_distgit

Also I've built them in a copr for rawhide https://copr.fedorainfracloud.org/coprs/amoralej/puppet6/. Preliminary tests shows it working.

it's weird it doesn't bundle semantic_puppet, in my case i needed it and codewise it shows it was unbundled in 6.0.0.

In addition to this bz, i've created https://bugzilla.redhat.com/show_bug.cgi?id=1728768 about puppet update.

By now Puppet 6.13.0 is out. I know that @skottler no longer works for Red Hat so perhaps it's time to hand over maintenance?

Hi,

This is the first time I am seeing this PR.
I was added as co-maintainer for puppet a few weeeks ago.
I am working on both puppet and puppetserver for el8 [1].

I am in the process of having the code review of all the spec files.
In special the new packages: rubygem-cane [2], rubygem-puppetserver-ca, rubygem-semantic_puppet, puppetserver.

If you want to help, please take a look on those spec files/srpms and let me know if you have suggestions. My email address is brandfbb@gmail.com.

You or anyone else that wants to help, feel free to email me.

• B

1 - https://copr.fedorainfracloud.org/coprs/brandfbb/puppet-6-on-EPEL-8-with-deps/
2 - https://bugzilla.redhat.com/show_bug.cgi?id=1803276

Oh, I mean puppet and puppetserver 6.

The issue that Puppet in EPEL6 and EPEL7 had was always that it got outdated at some point. EL8 is in a better position with modules but it's still a pain that an ancient Puppet version is in EPEL7. How do you intend to do major version bumps?

Yes, I intend to. Taking into consideration the EPEL's guidelines and policies[1].

If I had more help it would be easier too.
Right now there's a lot on my plate.

1 https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies