Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On 2/14/23 21:07, Sebastian Reitenbach wrote: On Sunday, February 12, 2023 10:36 CET, Giovanni Bechis wrote: On Sat, Feb 11, 2023 at 10:12:25PM +0100, Sebastian Reitenbach wrote: On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" wrote: On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" wrote: On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis wrote: On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis wrote: On 1/30/23 21:42, Sebastian Reitenbach wrote: Hi, with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master on OpenBSD was gone. These two new packages replace the old PuppetDB 5, with PuppetDB 7 and introduces the new Puppetserver. Similarly to systuls/ruby-puppet, they go into branches based on the major version, to have future room for Puppet 8. Their paths where software gets installed is aligned to Puppet, under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. Puppetserver usually comes bundled with a Ruby interpreter and Puppet agent. That doesn't work out on OpenBSD. Therefore some bootstrapping has to be done manually that is OpenBSD specific, and noted in the Puppetserver pkg/README. A couple of tweaks I had to do to my hiera files, as well as to some of the modules, mostly updating them. Overall, the changes weren't that big. As everyone might have different (custom) modules or hiera plugins in use, ymmv. Therefore I can't really provide a step by step upgrade path. Install on a test environment before attempting to upgrade/replace your former Puppet 5 Master. That said, Puppet 7 works for me standalone with puppet apply ... but also against this Puppetserver with PuppetDB backend, autosigning setup... comments to the ports, test reports, or maybe even OKs welcome ;) cheers, Sebastian thanks for testing. Few issues: - puppetdb is missing pkg/README file in the tarball This is missing on purpose, forgot to remove that, as I did last-minute clean-ups before sending out the tarball. Puppetdb is quite standard, so the upstream doc should more or less just work. Also the old puppetdb 5 README contained quite some outdated/misleading info If there turns to be out some OpenBSD specific issues, I'm happy to re-add. - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory oops - puppetserver doesn't start on my server log file attached, it seems there is a dependency missing (no such file to load...). puppetserver is quite non-standard, compared to puppetdb, just to make sure, did you do the initial bootstrap as described in the README? actually I did not bootstrapped it. After bootstrap it fails with a slightly different error (no such file to load -- facter). this diff fixes the issue. I don't think puppetserver picks up facter from "outside" but it seems I forgot to add facter as a gem to install in the README: # puppetserver gem install --no-document puppet hiera-eyaml \ hiera-file ipaddress msgpack facter This is not in the packages I just sent, but have it updated in my mystuff/ or wait, it actually should have pulled pulled facter in via the bootstrap step. Do you can check sudo puppetserver gem list Facter should actually be there? forgot that facter is BAD, due to the extra copy step, until the OpenBSD patch is merged upstream and released. So yes, for the time being, the facter version installed via puppetserver gem install and in the system should be the same version. does this mean we have to keep facter port updated to latest version on -stable as well until code will be committed upstream ? Otherwise I think bootstrap might break. I tried to address the issue with an updated README. Hope that should be OK? now? yes, ok giovanni@ Cheers Giovanni Sebastian Giovanni maybe commenting and bugging on the PR might help: https://github.com/puppetlabs/facter/pull/2531 Therefore, as it seems to work for you, OK for the ruby-facter update. Sebastian Sebastian Sebastian Thanks Giovanni Index: Makefile === RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v retrieving revision 1.92 diff -u -p -r1.92 Makefile --- Makefile22 Jan 2023 19:21:56 - 1.92 +++ Makefile11 Feb 2023 10:34:05 - @@ -1,7 +1,6 @@ COMMENT = Puppet module management -DISTNAME = facter-4.2.14 -REVISION = 0 +DISTNAME = facter-4.3.0 CATEGORIES = sysutils HOMEPAGE =https://github.com/puppetlabs/facter MAINTAINER = Sebastian Reitenbach Index: distinfo === RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v retrieving revision 1.30 diff -u -p -r1.30 distinfo --- distinfo22 Jan 2023 15:42:43 - 1.30 +++ distinfo
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sunday, February 12, 2023 10:36 CET, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 10:12:25PM +0100, Sebastian Reitenbach wrote: > > On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" > > wrote: > > > > > On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > > > wrote: > > > > > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > > > wrote: > > > > > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach > > > > > > wrote: > > > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > > > wrote: > > > > > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > > > These two new packages replace the old PuppetDB 5, with > > > > > > > > > PuppetDB 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based > > > > > > > > > on the major version, to have future room for Puppet 8. > > > > > > > > > Their paths where software gets installed is aligned to > > > > > > > > > Puppet, under /var/puppetlabs/... > > > > > > > > > /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter > > > > > > > > > and Puppet agent. That doesn't work out > > > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done > > > > > > > > > manually that is OpenBSD specific, and noted > > > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well > > > > > > > > > as to some of the modules, mostly updating > > > > > > > > > them. Overall, the changes weren't that big. As everyone > > > > > > > > > might have different (custom) modules or > > > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide > > > > > > > > > a step by step upgrade path. Install on a test > > > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > > > Puppet 5 Master. > > > > > > > > > That said, Puppet 7 works for me standalone with puppet apply > > > > > > > > > ... but also against this Puppetserver with PuppetDB backend, > > > > > > > > > autosigning setup... > > > > > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs > > > > > > > > > welcome ;) > > > > > > > > > > > > > > > > > > cheers, > > > > > > > > > Sebastian > > > > > > > > > > > > > > > > > > > > > > thanks for testing. > > > > > > > > Few issues: > > > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > > > last-minute clean-ups before sending out the tarball. > > > > > > > Puppetdb is quite standard, so the upstream doc should more or > > > > > > > less just work. Also the old puppetdb 5 README > > > > > > > contained quite some outdated/misleading info > > > > > > > If there turns to be out some OpenBSD specific issues, I'm happy > > > > > > > to re-add. > > > > > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > > > directory > > > > > > > oops > > > > > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > > > seems there is a dependency missing (no such file to load...). > > > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > > > make sure, did you do the initial bootstrap as described in the > > > > > > > README? > > > > > > > > > > > > > actually I did not bootstrapped it. > > > > > > After bootstrap it fails with a slightly different error (no such > > > > > > file > > > > > > to load -- facter). > > > > > > > > > > > this diff fixes the issue. > > > > > > > > I don't think puppetserver picks up facter from "outside" > > > > > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > > > hiera-file ipaddress msgpack facter > > > > > > > > This is not in the packages I just sent, but have it updated in my > > > > mystuff/ > > > > > > or wait, it actually should have pulled pulled facter in via the > > > bootstrap step. > > > > > > Do you can check > > > sudo puppetserver gem list > > > Facter should actually be there? > > > > forgot that facter is BAD, due to the extra copy step, until the OpenBSD > > patch > > is merged upstream and released. > > So yes, for the time being, the facter version installed via puppetserver > > gem install > > and in the system should be the same version. > does this mean we have to keep facter port updated to latest
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sunday, February 12, 2023 10:36 CET, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 10:12:25PM +0100, Sebastian Reitenbach wrote: > > On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" > > wrote: > > > > > On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > > > wrote: > > > > > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > > > wrote: > > > > > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach > > > > > > wrote: > > > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > > > wrote: > > > > > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > > > These two new packages replace the old PuppetDB 5, with > > > > > > > > > PuppetDB 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based > > > > > > > > > on the major version, to have future room for Puppet 8. > > > > > > > > > Their paths where software gets installed is aligned to > > > > > > > > > Puppet, under /var/puppetlabs/... > > > > > > > > > /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter > > > > > > > > > and Puppet agent. That doesn't work out > > > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done > > > > > > > > > manually that is OpenBSD specific, and noted > > > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well > > > > > > > > > as to some of the modules, mostly updating > > > > > > > > > them. Overall, the changes weren't that big. As everyone > > > > > > > > > might have different (custom) modules or > > > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide > > > > > > > > > a step by step upgrade path. Install on a test > > > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > > > Puppet 5 Master. > > > > > > > > > That said, Puppet 7 works for me standalone with puppet apply > > > > > > > > > ... but also against this Puppetserver with PuppetDB backend, > > > > > > > > > autosigning setup... > > > > > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs > > > > > > > > > welcome ;) > > > > > > > > > > > > > > > > > > cheers, > > > > > > > > > Sebastian > > > > > > > > > > > > > > > > > > > > > > thanks for testing. > > > > > > > > Few issues: > > > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > > > last-minute clean-ups before sending out the tarball. > > > > > > > Puppetdb is quite standard, so the upstream doc should more or > > > > > > > less just work. Also the old puppetdb 5 README > > > > > > > contained quite some outdated/misleading info > > > > > > > If there turns to be out some OpenBSD specific issues, I'm happy > > > > > > > to re-add. > > > > > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > > > directory > > > > > > > oops > > > > > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > > > seems there is a dependency missing (no such file to load...). > > > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > > > make sure, did you do the initial bootstrap as described in the > > > > > > > README? > > > > > > > > > > > > > actually I did not bootstrapped it. > > > > > > After bootstrap it fails with a slightly different error (no such > > > > > > file > > > > > > to load -- facter). > > > > > > > > > > > this diff fixes the issue. > > > > > > > > I don't think puppetserver picks up facter from "outside" > > > > > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > > > hiera-file ipaddress msgpack facter > > > > > > > > This is not in the packages I just sent, but have it updated in my > > > > mystuff/ > > > > > > or wait, it actually should have pulled pulled facter in via the > > > bootstrap step. > > > > > > Do you can check > > > sudo puppetserver gem list > > > Facter should actually be there? > > > > forgot that facter is BAD, due to the extra copy step, until the OpenBSD > > patch > > is merged upstream and released. > > So yes, for the time being, the facter version installed via puppetserver > > gem install > > and in the system should be the same version. > does this mean we have to keep facter port updated to latest
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sat, Feb 11, 2023 at 10:12:25PM +0100, Sebastian Reitenbach wrote: > On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" > wrote: > > > On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > > wrote: > > > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > > wrote: > > > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > > wrote: > > > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > > These two new packages replace the old PuppetDB 5, with > > > > > > > > PuppetDB 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based > > > > > > > > on the major version, to have future room for Puppet 8. > > > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > > > Puppet agent. That doesn't work out > > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done > > > > > > > > manually that is OpenBSD specific, and noted > > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as > > > > > > > > to some of the modules, mostly updating > > > > > > > > them. Overall, the changes weren't that big. As everyone might > > > > > > > > have different (custom) modules or > > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a > > > > > > > > step by step upgrade path. Install on a test > > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > > Puppet 5 Master. > > > > > > > > That said, Puppet 7 works for me standalone with puppet apply > > > > > > > > ... but also against this Puppetserver with PuppetDB backend, > > > > > > > > autosigning setup... > > > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome > > > > > > > > ;) > > > > > > > > > > > > > > > > cheers, > > > > > > > > Sebastian > > > > > > > > > > > > > > > > > > > thanks for testing. > > > > > > > Few issues: > > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > > last-minute clean-ups before sending out the tarball. > > > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > > > just work. Also the old puppetdb 5 README > > > > > > contained quite some outdated/misleading info > > > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > > > re-add. > > > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > > directory > > > > > > oops > > > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > > seems there is a dependency missing (no such file to load...). > > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > > make sure, did you do the initial bootstrap as described in the > > > > > > README? > > > > > > > > > > > actually I did not bootstrapped it. > > > > > After bootstrap it fails with a slightly different error (no such file > > > > > to load -- facter). > > > > > > > > > this diff fixes the issue. > > > > > > I don't think puppetserver picks up facter from "outside" > > > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > > hiera-file ipaddress msgpack facter > > > > > > This is not in the packages I just sent, but have it updated in my > > > mystuff/ > > > > or wait, it actually should have pulled pulled facter in via the bootstrap > > step. > > > > Do you can check > > sudo puppetserver gem list > > Facter should actually be there? > > forgot that facter is BAD, due to the extra copy step, until the OpenBSD patch > is merged upstream and released. > So yes, for the time being, the facter version installed via puppetserver gem > install > and in the system should be the same version. does this mean we have to keep facter port updated to latest version on -stable as well until code will be committed upstream ? Otherwise I think bootstrap might break. Giovanni > maybe commenting and bugging on the PR might help: > https://github.com/puppetlabs/facter/pull/2531 > > > Therefore, as it seems to work for you, OK for the ruby-facter update. > > Sebastian > > >
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" wrote: > On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > wrote: > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > wrote: > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > wrote: > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > Hi, > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB > > > > > > > 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on > > > > > > > the major version, to have future room for Puppet 8. > > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > > Puppet agent. That doesn't work out > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually > > > > > > > that is OpenBSD specific, and noted > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > > > some of the modules, mostly updating > > > > > > > them. Overall, the changes weren't that big. As everyone might > > > > > > > have different (custom) modules or > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a > > > > > > > step by step upgrade path. Install on a test > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > Puppet 5 Master. > > > > > > > That said, Puppet 7 works for me standalone with puppet apply ... > > > > > > > but also against this Puppetserver with PuppetDB backend, > > > > > > > autosigning setup... > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > > > > > cheers, > > > > > > > Sebastian > > > > > > > > > > > > > > > > thanks for testing. > > > > > > Few issues: > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > last-minute clean-ups before sending out the tarball. > > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > > just work. Also the old puppetdb 5 README > > > > > contained quite some outdated/misleading info > > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > > re-add. > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > directory > > > > > oops > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > seems there is a dependency missing (no such file to load...). > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > make sure, did you do the initial bootstrap as described in the > > > > > README? > > > > > > > > > actually I did not bootstrapped it. > > > > After bootstrap it fails with a slightly different error (no such file > > > > to load -- facter). > > > > > > > this diff fixes the issue. > > > > I don't think puppetserver picks up facter from "outside" > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > hiera-file ipaddress msgpack facter > > > > This is not in the packages I just sent, but have it updated in my mystuff/ > > or wait, it actually should have pulled pulled facter in via the bootstrap > step. > > Do you can check > sudo puppetserver gem list > Facter should actually be there? forgot that facter is BAD, due to the extra copy step, until the OpenBSD patch is merged upstream and released. So yes, for the time being, the facter version installed via puppetserver gem install and in the system should be the same version. maybe commenting and bugging on the PR might help: https://github.com/puppetlabs/facter/pull/2531 Therefore, as it seems to work for you, OK for the ruby-facter update. Sebastian > > Sebastian > > > > > Sebastian > > > > > Thanks > > > Giovanni > > > > > > Index: Makefile > > > === > > > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > > > retrieving revision 1.92 > > > diff -u -p -r1.92 Makefile > > > --- Makefile 22 Jan 2023 19:21:56 - 1.92 > > > +++ Makefile 11 Feb 2023 10:34:05 - > > > @@ -1,7 +1,6 @@ > > > COMMENT =Puppet module management > > > > >
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" wrote: > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > wrote: > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > wrote: > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > Hi, > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > > > master on OpenBSD was gone. > > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 > > > > > > and introduces the new Puppetserver. > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on > > > > > > the major version, to have future room for Puppet 8. > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > Puppet agent. That doesn't work out > > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually > > > > > > that is OpenBSD specific, and noted > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > > some of the modules, mostly updating > > > > > > them. Overall, the changes weren't that big. As everyone might have > > > > > > different (custom) modules or > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step > > > > > > by step upgrade path. Install on a test > > > > > > environment before attempting to upgrade/replace your former Puppet > > > > > > 5 Master. > > > > > > That said, Puppet 7 works for me standalone with puppet apply ... > > > > > > but also against this Puppetserver with PuppetDB backend, > > > > > > autosigning setup... > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > > > cheers, > > > > > > Sebastian > > > > > > > > > > > > > thanks for testing. > > > > > Few issues: > > > > > - puppetdb is missing pkg/README file in the tarball > > > > This is missing on purpose, forgot to remove that, as I did last-minute > > > > clean-ups before sending out the tarball. > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > just work. Also the old puppetdb 5 README > > > > contained quite some outdated/misleading info > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > re-add. > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > directory > > > > oops > > > > > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > > > there is a dependency missing (no such file to load...). > > > > puppetserver is quite non-standard, compared to puppetdb, just to make > > > > sure, did you do the initial bootstrap as described in the README? > > > > > > > actually I did not bootstrapped it. > > > After bootstrap it fails with a slightly different error (no such file > > > to load -- facter). > > > > > this diff fixes the issue. > > I don't think puppetserver picks up facter from "outside" > > but it seems I forgot to add facter as a gem to install in the README: > > # puppetserver gem install --no-document puppet hiera-eyaml \ > hiera-file ipaddress msgpack facter > > This is not in the packages I just sent, but have it updated in my mystuff/ or wait, it actually should have pulled pulled facter in via the bootstrap step. Do you can check sudo puppetserver gem list Facter should actually be there? Sebastian > > Sebastian > > > Thanks > > Giovanni > > > > Index: Makefile > > === > > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > > retrieving revision 1.92 > > diff -u -p -r1.92 Makefile > > --- Makefile22 Jan 2023 19:21:56 - 1.92 > > +++ Makefile11 Feb 2023 10:34:05 - > > @@ -1,7 +1,6 @@ > > COMMENT = Puppet module management > > > > -DISTNAME = facter-4.2.14 > > -REVISION = 0 > > +DISTNAME = facter-4.3.0 > > CATEGORIES = sysutils > > HOMEPAGE = https://github.com/puppetlabs/facter > > MAINTAINER = Sebastian Reitenbach > > Index: distinfo > > === > > RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v > > retrieving revision 1.30 > > diff -u -p -r1.30 distinfo > > --- distinfo22 Jan 2023 15:42:43 - 1.30 > > +++ distinfo11 Feb 2023 10:34:05 - > > @@ -1,2 +1,2 @@ > > -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= > > -SIZE (facter-4.2.14.gem) = 159232 > > +SHA256 (facter-4.3.0.gem) =
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > wrote: > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > Hi, > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > > master on OpenBSD was gone. > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 > > > > > and introduces the new Puppetserver. > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > > > major version, to have future room for Puppet 8. > > > > > Their paths where software gets installed is aligned to Puppet, under > > > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > > > agent. That doesn't work out > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually that > > > > > is OpenBSD specific, and noted > > > > > in the Puppetserver pkg/README. > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > some of the modules, mostly updating > > > > > them. Overall, the changes weren't that big. As everyone might have > > > > > different (custom) modules or > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step > > > > > by step upgrade path. Install on a test > > > > > environment before attempting to upgrade/replace your former Puppet 5 > > > > > Master. > > > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > > > also against this Puppetserver with PuppetDB backend, autosigning > > > > > setup... > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > cheers, > > > > > Sebastian > > > > > > > > > > thanks for testing. > > > > Few issues: > > > > - puppetdb is missing pkg/README file in the tarball > > > This is missing on purpose, forgot to remove that, as I did last-minute > > > clean-ups before sending out the tarball. > > > Puppetdb is quite standard, so the upstream doc should more or less just > > > work. Also the old puppetdb 5 README > > > contained quite some outdated/misleading info > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > re-add. > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > > > oops > > > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > > there is a dependency missing (no such file to load...). > > > puppetserver is quite non-standard, compared to puppetdb, just to make > > > sure, did you do the initial bootstrap as described in the README? > > > > > actually I did not bootstrapped it. > > After bootstrap it fails with a slightly different error (no such file > > to load -- facter). > > > this diff fixes the issue. I don't think puppetserver picks up facter from "outside" but it seems I forgot to add facter as a gem to install in the README: # puppetserver gem install --no-document puppet hiera-eyaml \ hiera-file ipaddress msgpack facter This is not in the packages I just sent, but have it updated in my mystuff/ Sebastian > Thanks > Giovanni > > Index: Makefile > === > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > retrieving revision 1.92 > diff -u -p -r1.92 Makefile > --- Makefile 22 Jan 2023 19:21:56 - 1.92 > +++ Makefile 11 Feb 2023 10:34:05 - > @@ -1,7 +1,6 @@ > COMMENT =Puppet module management > > -DISTNAME = facter-4.2.14 > -REVISION = 0 > +DISTNAME = facter-4.3.0 > CATEGORIES = sysutils > HOMEPAGE = https://github.com/puppetlabs/facter > MAINTAINER = Sebastian Reitenbach > Index: distinfo > === > RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v > retrieving revision 1.30 > diff -u -p -r1.30 distinfo > --- distinfo 22 Jan 2023 15:42:43 - 1.30 > +++ distinfo 11 Feb 2023 10:34:05 - > @@ -1,2 +1,2 @@ > -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= > -SIZE (facter-4.2.14.gem) = 159232 > +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJdbBsrSw= > +SIZE (facter-4.3.0.gem) = 159232
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis wrote: > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > Hi, > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master > > on OpenBSD was gone. > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > introduces the new Puppetserver. > > > > Similarly to systuls/ruby-puppet, they go into branches based on the major > > version, to have future room for Puppet 8. > > Their paths where software gets installed is aligned to Puppet, under > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > agent. That doesn't work out > > on OpenBSD. Therefore some bootstrapping has to be done manually that is > > OpenBSD specific, and noted > > in the Puppetserver pkg/README. > > > > A couple of tweaks I had to do to my hiera files, as well as to some of > > the modules, mostly updating > > them. Overall, the changes weren't that big. As everyone might have > > different (custom) modules or > > hiera plugins in use, ymmv. Therefore I can't really provide a step by step > > upgrade path. Install on a test > > environment before attempting to upgrade/replace your former Puppet 5 > > Master. > > That said, Puppet 7 works for me standalone with puppet apply ... but also > > against this Puppetserver with PuppetDB backend, autosigning setup... > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > cheers, > > Sebastian > > Few issues: > - puppetdb is missing pkg/README file in the tarball > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory revisited puppetdb and puppetserver packages. They now create /var/log/puppetlabs/XXX directories, as well as I saw, also properly puppetdb vardir to the right position. While there exchanged a number of hardcoded /etc /var /usr/local with respective variables. Updated dependencies a bit for puppetdb-termini. The main puppetdb is not really depending on it, but puppetserver is, so made that one depending on the termini. > - puppetserver doesn't start on my server log file attached, it seems there > is a dependency missing (no such file to load...). To let the puppetserver startup properly, you have to take the initial bootstrapping steps as described in the README. On other OS, puppetserver comes bundled with puppet, and a bundled Ruby etc. That's not possible for us, so have to install puppet "within" puppetserver, so it's jruby interpreter can find and use it. > New package doesn't upgrade from puppet5, a pkg_path is missing I think. I'm lousy whith pkg_path thingies, and don't have a box where to properly test it out. those that still have Puppet5 are old, and these that switched already, don't have puppet5 anymore. Esp. with the clean-up to the first two points, and taking puppetserver README into account, I believe things should now work smoothly. They installed fine for me, as well as starting up. More feedback welcome, other than that, OKs as well. If ther's oddities left, they can be fixed in-tree afterward. cheers, Sebastian puppetserver.tar.gz Description: application/gzip puppetdb.tar.gz Description: application/gzip ruby-puppetserver-ca.tar.gz Description: application/gzip
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > wrote: > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > Hi, > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > master on OpenBSD was gone. > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > > > introduces the new Puppetserver. > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > > major version, to have future room for Puppet 8. > > > > Their paths where software gets installed is aligned to Puppet, under > > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > > agent. That doesn't work out > > > > on OpenBSD. Therefore some bootstrapping has to be done manually that > > > > is OpenBSD specific, and noted > > > > in the Puppetserver pkg/README. > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to some > > > > of the modules, mostly updating > > > > them. Overall, the changes weren't that big. As everyone might have > > > > different (custom) modules or > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step by > > > > step upgrade path. Install on a test > > > > environment before attempting to upgrade/replace your former Puppet 5 > > > > Master. > > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > > also against this Puppetserver with PuppetDB backend, autosigning > > > > setup... > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > cheers, > > > > Sebastian > > > > > > > thanks for testing. > > > Few issues: > > > - puppetdb is missing pkg/README file in the tarball > > This is missing on purpose, forgot to remove that, as I did last-minute > > clean-ups before sending out the tarball. > > Puppetdb is quite standard, so the upstream doc should more or less just > > work. Also the old puppetdb 5 README > > contained quite some outdated/misleading info > > If there turns to be out some OpenBSD specific issues, I'm happy to re-add. > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > > oops > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > there is a dependency missing (no such file to load...). > > puppetserver is quite non-standard, compared to puppetdb, just to make > > sure, did you do the initial bootstrap as described in the README? > > > actually I did not bootstrapped it. > After bootstrap it fails with a slightly different error (no such file > to load -- facter). > this diff fixes the issue. Thanks Giovanni Index: Makefile === RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v retrieving revision 1.92 diff -u -p -r1.92 Makefile --- Makefile22 Jan 2023 19:21:56 - 1.92 +++ Makefile11 Feb 2023 10:34:05 - @@ -1,7 +1,6 @@ COMMENT = Puppet module management -DISTNAME = facter-4.2.14 -REVISION = 0 +DISTNAME = facter-4.3.0 CATEGORIES = sysutils HOMEPAGE = https://github.com/puppetlabs/facter MAINTAINER = Sebastian Reitenbach Index: distinfo === RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v retrieving revision 1.30 diff -u -p -r1.30 distinfo --- distinfo22 Jan 2023 15:42:43 - 1.30 +++ distinfo11 Feb 2023 10:34:05 - @@ -1,2 +1,2 @@ -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= -SIZE (facter-4.2.14.gem) = 159232 +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJdbBsrSw= +SIZE (facter-4.3.0.gem) = 159232
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > wrote: > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > Hi, > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > master on OpenBSD was gone. > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > > introduces the new Puppetserver. > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > major version, to have future room for Puppet 8. > > > Their paths where software gets installed is aligned to Puppet, under > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > agent. That doesn't work out > > > on OpenBSD. Therefore some bootstrapping has to be done manually that is > > > OpenBSD specific, and noted > > > in the Puppetserver pkg/README. > > > > > > A couple of tweaks I had to do to my hiera files, as well as to some of > > > the modules, mostly updating > > > them. Overall, the changes weren't that big. As everyone might have > > > different (custom) modules or > > > hiera plugins in use, ymmv. Therefore I can't really provide a step by > > > step upgrade path. Install on a test > > > environment before attempting to upgrade/replace your former Puppet 5 > > > Master. > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > also against this Puppetserver with PuppetDB backend, autosigning setup... > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > cheers, > > > Sebastian > > > > thanks for testing. > > Few issues: > > - puppetdb is missing pkg/README file in the tarball > This is missing on purpose, forgot to remove that, as I did last-minute > clean-ups before sending out the tarball. > Puppetdb is quite standard, so the upstream doc should more or less just > work. Also the old puppetdb 5 README > contained quite some outdated/misleading info > If there turns to be out some OpenBSD specific issues, I'm happy to re-add. > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > oops > > > - puppetserver doesn't start on my server log file attached, it seems there > > is a dependency missing (no such file to load...). > puppetserver is quite non-standard, compared to puppetdb, just to make sure, > did you do the initial bootstrap as described in the README? > actually I did not bootstrapped it. After bootstrap it fails with a slightly different error (no such file to load -- facter). > > > New package doesn't upgrade from puppet5, a pkg_path is missing I think. > not sure if that should. as puppetserver is now "extra", and before, it was > just a single package conaining client and master. > makes sense, we should add some info to upgrade.html then. Thanks Giovanni > Sebastian > > > > > Cheers > > > > Giovanni > 2023-02-11T11:00:43.864+01:00 INFO [main] [o.e.j.u.log] Logging initialized @7581ms to org.eclipse.jetty.util.log.Slf4jLog 2023-02-11T11:00:46.148+01:00 INFO [async-dispatch-2] [p.t.s.s.scheduler-service] Initializing Scheduler Service 2023-02-11T11:00:46.191+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Using default implementation for ThreadExecutor 2023-02-11T11:00:46.208+01:00 INFO [async-dispatch-2] [o.q.c.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2023-02-11T11:00:46.208+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Quartz Scheduler v.2.3.2 created. 2023-02-11T11:00:46.210+01:00 INFO [async-dispatch-2] [o.q.s.RAMJobStore] RAMJobStore initialized. 2023-02-11T11:00:46.210+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.3.2) 'a5bac081-c72e-4658-90a6-b4afbc9df9a7' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler 'a5bac081-c72e-4658-90a6-b4afbc9df9a7' initialized from an externally provided properties instance. 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler version: 2.3.2 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler a5bac081-c72e-4658-90a6-b4afbc9df9a7_$_NON_CLUSTERED started. 2023-02-11T11:00:46.214+01:00 INFO [async-dispatch-2] [p.t.s.w.jetty9-service] Initializing web server(s). 2023-02-11T11:00:46.244+01:00 INFO [async-dispatch-2] [p.t.s.s.status-service] Registering status callback
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis wrote: > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > Hi, > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master > > on OpenBSD was gone. > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > introduces the new Puppetserver. > > > > Similarly to systuls/ruby-puppet, they go into branches based on the major > > version, to have future room for Puppet 8. > > Their paths where software gets installed is aligned to Puppet, under > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > agent. That doesn't work out > > on OpenBSD. Therefore some bootstrapping has to be done manually that is > > OpenBSD specific, and noted > > in the Puppetserver pkg/README. > > > > A couple of tweaks I had to do to my hiera files, as well as to some of > > the modules, mostly updating > > them. Overall, the changes weren't that big. As everyone might have > > different (custom) modules or > > hiera plugins in use, ymmv. Therefore I can't really provide a step by step > > upgrade path. Install on a test > > environment before attempting to upgrade/replace your former Puppet 5 > > Master. > > That said, Puppet 7 works for me standalone with puppet apply ... but also > > against this Puppetserver with PuppetDB backend, autosigning setup... > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > cheers, > > Sebastian > thanks for testing. > Few issues: > - puppetdb is missing pkg/README file in the tarball This is missing on purpose, forgot to remove that, as I did last-minute clean-ups before sending out the tarball. Puppetdb is quite standard, so the upstream doc should more or less just work. Also the old puppetdb 5 README contained quite some outdated/misleading info If there turns to be out some OpenBSD specific issues, I'm happy to re-add. > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory oops > - puppetserver doesn't start on my server log file attached, it seems there > is a dependency missing (no such file to load...). puppetserver is quite non-standard, compared to puppetdb, just to make sure, did you do the initial bootstrap as described in the README? > New package doesn't upgrade from puppet5, a pkg_path is missing I think. not sure if that should. as puppetserver is now "extra", and before, it was just a single package conaining client and master. Sebastian > > Cheers > > Giovanni
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On 1/30/23 21:42, Sebastian Reitenbach wrote: Hi, with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master on OpenBSD was gone. These two new packages replace the old PuppetDB 5, with PuppetDB 7 and introduces the new Puppetserver. Similarly to systuls/ruby-puppet, they go into branches based on the major version, to have future room for Puppet 8. Their paths where software gets installed is aligned to Puppet, under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. Puppetserver usually comes bundled with a Ruby interpreter and Puppet agent. That doesn't work out on OpenBSD. Therefore some bootstrapping has to be done manually that is OpenBSD specific, and noted in the Puppetserver pkg/README. A couple of tweaks I had to do to my hiera files, as well as to some of the modules, mostly updating them. Overall, the changes weren't that big. As everyone might have different (custom) modules or hiera plugins in use, ymmv. Therefore I can't really provide a step by step upgrade path. Install on a test environment before attempting to upgrade/replace your former Puppet 5 Master. That said, Puppet 7 works for me standalone with puppet apply ... but also against this Puppetserver with PuppetDB backend, autosigning setup... comments to the ports, test reports, or maybe even OKs welcome ;) cheers, Sebastian Few issues: - puppetdb is missing pkg/README file in the tarball - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory - puppetserver doesn't start on my server log file attached, it seems there is a dependency missing (no such file to load...). New package doesn't upgrade from puppet5, a pkg_path is missing I think. Cheers Giovanni OpenBSD 7.2-current (GENERIC.MP) #1026: Wed Feb 8 22:50:35 MST 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2129526784 (2030MB) avail mem = 2045648896 (1950MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (242 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 11/12/2020 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) PE50(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz, 2394.72 MHz, 06-3a-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 35MB 64b/line 20-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 66MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz, 2394.61 MHz, 06-3a-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 35MB 64b/line 20-way L3 cache cpu1: smt 0, core 0, package 2 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0A05" at acpi0 not configured acpiac0 at acpi0: AC unit online acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) cpu0: using VERW MDS workaround pvbus0 at mainbus0: VMware vmt0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01 ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01 pci1 at ppb0 bus 1 pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08 pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus disabled "VMware VMCI" rev 0x10 at pci0 dev 7
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
Hi, as I was pointed out by rsadowski@, I was missing a dependency for puppetserver: sysutils/ruby-puppetserver-ca: in my inital submission. This gem provides the functionality behind the Puppet Server CA interactions. The actual CLI executable lives within the Puppet Server project. tarball attached. other comments or even OK regarding quality of this port, as well as puppetdb/puppetserver etc. welcome. cheers, Sebastian On Monday, January 30, 2023 21:42 CET, "Sebastian Reitenbach" wrote: > Hi, > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master on > OpenBSD was gone. > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > introduces the new Puppetserver. > > Similarly to systuls/ruby-puppet, they go into branches based on the major > version, to have future room for Puppet 8. > Their paths where software gets installed is aligned to Puppet, under > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet agent. > That doesn't work out > on OpenBSD. Therefore some bootstrapping has to be done manually that is > OpenBSD specific, and noted > in the Puppetserver pkg/README. > > A couple of tweaks I had to do to my hiera files, as well as to some of the > modules, mostly updating > them. Overall, the changes weren't that big. As everyone might have different > (custom) modules or > hiera plugins in use, ymmv. Therefore I can't really provide a step by step > upgrade path. Install on a test > environment before attempting to upgrade/replace your former Puppet 5 Master. > That said, Puppet 7 works for me standalone with puppet apply ... but also > against this Puppetserver with PuppetDB backend, autosigning setup... > > comments to the ports, test reports, or maybe even OKs welcome ;) > > cheers, > Sebastian ruby-puppetserver-ca.tar.gz Description: GNU Zip compressed data
NEW: databases/puppetdb and sysutils/puppetserver 7.X
Hi, with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master on OpenBSD was gone. These two new packages replace the old PuppetDB 5, with PuppetDB 7 and introduces the new Puppetserver. Similarly to systuls/ruby-puppet, they go into branches based on the major version, to have future room for Puppet 8. Their paths where software gets installed is aligned to Puppet, under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. Puppetserver usually comes bundled with a Ruby interpreter and Puppet agent. That doesn't work out on OpenBSD. Therefore some bootstrapping has to be done manually that is OpenBSD specific, and noted in the Puppetserver pkg/README. A couple of tweaks I had to do to my hiera files, as well as to some of the modules, mostly updating them. Overall, the changes weren't that big. As everyone might have different (custom) modules or hiera plugins in use, ymmv. Therefore I can't really provide a step by step upgrade path. Install on a test environment before attempting to upgrade/replace your former Puppet 5 Master. That said, Puppet 7 works for me standalone with puppet apply ... but also against this Puppetserver with PuppetDB backend, autosigning setup... comments to the ports, test reports, or maybe even OKs welcome ;) cheers, Sebastian puppetdb.tar.gz Description: GNU Zip compressed data puppetserver.tar.gz Description: GNU Zip compressed data
