Re: [Puppet Users] how were your puppet 3-4 upgrades?
Same here. El miércoles, 26 de agosto de 2015, 15:45:07 (UTC+2), Pete Harvey escribió: On 26 August 2015 at 09:16, Fabrice Bacchella fabrice@orange.fr javascript: wrote: My biggest problem: there isn't any working dashboard working with Puppet 4. This. Our upgrade to 4 is essentially blocked until Foreman supports it. Pete -- 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/0ceb69f1-4a5d-49d4-a970-38f31146d395%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
Agreed. Between the AIO packaging, change in configuration file locations, lack of dashboards, and the many other minor annoyances I do not feel the benefits of 4 outweigh the hassle of upgrading. 2-3 was much, much less painful. Jeffrey. On Thu, Aug 27, 2015 at 1:46 PM, Felix Barbeira fbarbe...@gmail.com wrote: Same here. El miércoles, 26 de agosto de 2015, 15:45:07 (UTC+2), Pete Harvey escribió: On 26 August 2015 at 09:16, Fabrice Bacchella fabrice@orange.fr wrote: My biggest problem: there isn't any working dashboard working with Puppet 4. This. Our upgrade to 4 is essentially blocked until Foreman supports it. Pete -- 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/CAMvPdm1dFEOT4T8yP1TojV4jcoc1o2ERjJKZnyurA1Rp_QEAiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
Le 24 août 2015 à 21:59, Christopher Wood christopher_w...@pobox.com a écrit : I am not seeing a large amount of blog entries complaining about this upgrade, how has that gone for you? Is there anything you found particularly painful? Would you have done anything different in retrospect? I'm staring down a 3.7.2 - 4.2.1 upgrade and after reading a number of docs the back-of-the-envelope optimal upgrade path is as follows. If any of you have commentary I am quite interested, otherwise I will try it and see what happens. I feel like this might be more time-consuming work but less brainpower effort than just yanking everything to 4.2. 1) rpms up to puppet 3.8 PostgreSQL 8.4 to 9.4 PuppetDB 2.2.2 to 2.3.7 (puppetdb-terminus from 2.2.2 to 2.3.7) Puppet 3.7.2 to 3.8.2 2) enable the future parser 3) replace puppet 3.8.2, passenger 5 with puppetserver 1.1.1 4) replace puppetserver 1.1.1 with puppetserver 2.1.1 5) upgrade PuppetDB from 2.3.7 to 3.0.2 6) use the puppetlabs-puppet_agent forge module to upgrade agents to 4.2.1 My biggest problem: there isn't any working dashboard working with Puppet 4. The puppetdb APIv4 in puppet db 3.1 is not the same as the APIv4 in puppetdb 2, so all of them are now broken, even the one that thought they uses the v4 API. I had a lot of trouble with facter, it's rewritten but not tested on older release, a few things were broken on Redhat 5 : https://tickets.puppetlabs.com/browse/FACT-1152 https://tickets.puppetlabs.com/browse/FACT-1137 If you use mcollective there is a bug that prevent installation of both mcollective and puppet on the same server on Redhat 6 : https://tickets.puppetlabs.com/browse/PUP-4970 and no one take care for this bug at puppetlabs. All the path change /etc/puppet, /usr/bin to /etc/puppetlab, /opt/puppetlabs. Minor problems might arise from that, if you don't prepare that on puppet modules, other management scripts. I hade no problem with embedded PKI, rsync -av /var/lib/puppet/ssl /etc/puppetlabs/puppet/ is enough to keep it. Check your: [master] certname =... in puppet.conf. Rules changes slightly and I had problem with that. If you wrote you own modules, expect a lot of warning and broken modules becase of new variable typing. Once the new server was up and running, I used this simple script on all the nodes: [ -x /opt/puppetlabs/bin/puppet ] || (\ [ -x $(type -p facter) ] \ rpm -e puppetlabs-release \ rpm -Uvh http://.../puppetlabs/$(facter operatingsystemmajrelease)/PC1/x86_64/puppetlabs-release-pc1-0.9.2-1.el$(facter operatingsystemmajrelease).noarch.rpm \ yum install -y puppet-agent \ rsync -av /var/lib/puppet/ssl /etc/puppetlabs/puppet/ \ /opt/puppetlabs/bin/puppet agent -v --onetime --no-daemonize --no-show_diff --pluginsource puppet:///plugins --use_srv_records \ service mcollective restart -- 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/88164374-6100-425D-B7D1-C4C944B35642%40orange.fr. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
Le 26 août 2015 à 11:30, Stefan Heijmans heijm...@gmail.com a écrit : On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote: Le 24 août 2015 à 21:59, Christopher Wood christop...@pobox.com javascript: a écrit : My biggest problem: there isn't any working dashboard working with Puppet 4. The puppetdb APIv4 in puppet db 3.1 is not the same as the APIv4 in puppetdb 2, so all of them are now broken, even the one that thought they uses the v4 API. Hopefully PuppetDB 3.x.x will support Puppet 3 clients again, like PuppetServer. In the PuppetDB release notes is says that version 2.3.0 supports Puppet 4 [1], so will this not work together with PuppetExplorer 1.5.0 [2]? They don't give a lot of details, that's puppetbd 2.3 release notes any way. The API v4 changed between puppetdb 2 and puppetdb 3. So this release note don't apply any more. For puppet explorer, good news: https://github.com/spotify/puppetexplorer/issues/34 https://github.com/spotify/puppetexplorer/issues/34 Good news with puppet explorer any way : https://github.com/spotify/puppetexplorer/releases/tag/2.0.0 https://github.com/spotify/puppetexplorer/releases/tag/2.0.0 1. https://docs.puppetlabs.com/puppetdb/latest/release_notes.html#section-11 https://docs.puppetlabs.com/puppetdb/latest/release_notes.html#section-11 2. https://github.com/spotify/puppetexplorer/releases/tag/1.5.0 https://github.com/spotify/puppetexplorer/releases/tag/1.5.0 Stefan -- 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 mailto:puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f359ca60-1b0d-4fac-96c3-dfba460995fc%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/f359ca60-1b0d-4fac-96c3-dfba460995fc%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout 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/C569E049-6183-4B97-A174-7CD1E609B7DE%40orange.fr. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
On Wed, Aug 26, 2015 at 10:16:28AM +0200, Fabrice Bacchella wrote: Le 24 août 2015 à 21:59, Christopher Wood christopher_w...@pobox.com a écrit : I am not seeing a large amount of blog entries complaining about this upgrade, how has that gone for you? Is there anything you found particularly painful? Would you have done anything different in retrospect? I'm staring down a 3.7.2 - 4.2.1 upgrade and after reading a number of docs the back-of-the-envelope optimal upgrade path is as follows. If any of you have commentary I am quite interested, otherwise I will try it and see what happens. I feel like this might be more time-consuming work but less brainpower effort than just yanking everything to 4.2. 1) rpms up to puppet 3.8 PostgreSQL 8.4 to 9.4 PuppetDB 2.2.2 to 2.3.7 (puppetdb-terminus from 2.2.2 to 2.3.7) Puppet 3.7.2 to 3.8.2 2) enable the future parser 3) replace puppet 3.8.2, passenger 5 with puppetserver 1.1.1 4) replace puppetserver 1.1.1 with puppetserver 2.1.1 5) upgrade PuppetDB from 2.3.7 to 3.0.2 6) use the puppetlabs-puppet_agent forge module to upgrade agents to 4.2.1 My biggest problem: there isn't any working dashboard working with Puppet 4. The puppetdb APIv4 in puppet db 3.1 is not the same as the APIv4 in puppetdb 2, so all of them are now broken, even the one that thought they uses the v4 API. I had a lot of trouble with facter, it's rewritten but not tested on older release, a few things were broken on Redhat 5 : https://tickets.puppetlabs.com/browse/FACT-1152 https://tickets.puppetlabs.com/browse/FACT-1137 If you use mcollective there is a bug that prevent installation of both mcollective and puppet on the same server on Redhat 6 : https://tickets.puppetlabs.com/browse/PUP-4970 and no one take care for this bug at puppetlabs. That would have been a bit of a gotcha, but I don't manage repos with release rpms. It interferes with purging /etc/yum.repos.d. All the path change /etc/puppet, /usr/bin to /etc/puppetlab, /opt/puppetlabs. Minor problems might arise from that, if you don't prepare that on puppet modules, other management scripts. I figure just adding some sync'ing before the upgrade would do it. Have to check if the puppet-agent rpm does anything to these files after the sync. Thank you! I hade no problem with embedded PKI, rsync -av /var/lib/puppet/ssl /etc/puppetlabs/puppet/ is enough to keep it. Check your: [master] certname =... in puppet.conf. Rules changes slightly and I had problem with that. If you wrote you own modules, expect a lot of warning and broken modules becase of new variable typing. Once the new server was up and running, I used this simple script on all the nodes: [ -x /opt/puppetlabs/bin/puppet ] || (\ [ -x $(type -p facter) ] \ rpm -e puppetlabs-release \ rpm -Uvh http://.../puppetlabs/$(facter operatingsystemmajrelease)/PC1/x86_64/puppetlabs-release-pc1-0.9.2-1.el$(facter operatingsystemmajrelease).noarch.rpm \ yum install -y puppet-agent \ rsync -av /var/lib/puppet/ssl /etc/puppetlabs/puppet/ \ /opt/puppetlabs/bin/puppet agent -v --onetime --no-daemonize --no-show_diff --pluginsource puppet:///plugins --use_srv_records \ service mcollective restart -- 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/88164374-6100-425D-B7D1-C4C944B35642%40orange.fr. 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/20150826111034.GA14773%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
(Following up to myself.) My current set of puppetdb classes do not have an easy upgrade path, especially given how I macgyvered in the capacity to manage certificate whitelisting. However I'm still not sure I care about past data in (appliance'y) puppetdb enough to upgrade anything. I may just build a new puppetdb server and point the puppetmasters at it. -- 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/20150826111940.GA15065%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote: Le 24 août 2015 à 21:59, Christopher Wood christop...@pobox.com javascript: a écrit : My biggest problem: there isn't any working dashboard working with Puppet 4. The puppetdb APIv4 in puppet db 3.1 is not the same as the APIv4 in puppetdb 2, so all of them are now broken, even the one that thought they uses the v4 API. Hopefully PuppetDB 3.x.x will support Puppet 3 clients again, like PuppetServer. In the PuppetDB release notes is says that version 2.3.0 supports Puppet 4 [1], so will this not work together with PuppetExplorer 1.5.0 [2]? 1. https://docs.puppetlabs.com/puppetdb/latest/release_notes.html#section-11 2. https://github.com/spotify/puppetexplorer/releases/tag/1.5.0 Stefan -- 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/f359ca60-1b0d-4fac-96c3-dfba460995fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
On 26 August 2015 at 09:16, Fabrice Bacchella fabrice.bacche...@orange.fr wrote: My biggest problem: there isn't any working dashboard working with Puppet 4. This. Our upgrade to 4 is essentially blocked until Foreman supports it. Pete -- 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/CADZuy8jTTM9OrgCKY%2B85oLbb5E%2BOrXPKyE8iKtyu6%3D7tqvPRfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
On 8/24/15 12:59 PM, Christopher Wood wrote: (Although I may dump/restore the data via puppetdb since that's the actual api to the data, we do not log in via PostgreSQL.) Others can speak to the rest of the plan, but just to clarify in case I'm understanding you right: the PuppetDB import/export tools are not intended to work across different versions of PDB, so an export of 2.x data will not be importable on 3.x. I can see that this is a hole in our documentation, which I'll fix up in a minute. Instead, the necessary data migrations will be handled by the upgrade itself on the first startup of PuppetDB 3.0. Taking a pg_dump or PuppetDB export for a backup prior to the upgrade is still a prudent thing to do in case a downgrade is required, but that will only allow you to restore from the version you came from (possibly earlier ones too in the export case, but only by happenstance). For your use case I'd recommend pg_dump over PuppetDB export since it'll run a lot faster, but either one will get the job done. Wyatt -- 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/55DB8009.6080300%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] how were your puppet 3-4 upgrades?
I am not seeing a large amount of blog entries complaining about this upgrade, how has that gone for you? Is there anything you found particularly painful? Would you have done anything different in retrospect? I'm staring down a 3.7.2 - 4.2.1 upgrade and after reading a number of docs the back-of-the-envelope optimal upgrade path is as follows. If any of you have commentary I am quite interested, otherwise I will try it and see what happens. I feel like this might be more time-consuming work but less brainpower effort than just yanking everything to 4.2. 1) rpms up to puppet 3.8 PostgreSQL 8.4 to 9.4 PuppetDB 2.2.2 to 2.3.7 (puppetdb-terminus from 2.2.2 to 2.3.7) Puppet 3.7.2 to 3.8.2 2) enable the future parser 3) replace puppet 3.8.2, passenger 5 with puppetserver 1.1.1 4) replace puppetserver 1.1.1 with puppetserver 2.1.1 5) upgrade PuppetDB from 2.3.7 to 3.0.2 6) use the puppetlabs-puppet_agent forge module to upgrade agents to 4.2.1 My reading: https://docs.puppetlabs.com/puppet/latest/reference/ https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_pre.html https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_server.html https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_agent.html https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_post.html https://forge.puppetlabs.com/puppetlabs/puppet_agent https://docs.puppetlabs.com/puppetdb/2.3/upgrade.html http://docs.puppetlabs.com/puppetdb/3.0/upgrade.html http://www.postgresql.org/docs/9.4/static/upgrading.html (Although I may dump/restore the data via puppetdb since that's the actual api to the data, we do not log in via PostgreSQL.) -- 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/20150824195938.GA28076%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
I will be snapshotting the VM to lower the rollback effort there, but good point at that. Otherwise that saves me a bunch of preprod fiddling, thank you. On Mon, Aug 24, 2015 at 01:35:21PM -0700, Wyatt Alt wrote: On 8/24/15 12:59 PM, Christopher Wood wrote: (Although I may dump/restore the data via puppetdb since that's the actual api to the data, we do not log in via PostgreSQL.) Others can speak to the rest of the plan, but just to clarify in case I'm understanding you right: the PuppetDB import/export tools are not intended to work across different versions of PDB, so an export of 2.x data will not be importable on 3.x. I can see that this is a hole in our documentation, which I'll fix up in a minute. Instead, the necessary data migrations will be handled by the upgrade itself on the first startup of PuppetDB 3.0. Taking a pg_dump or PuppetDB export for a backup prior to the upgrade is still a prudent thing to do in case a downgrade is required, but that will only allow you to restore from the version you came from (possibly earlier ones too in the export case, but only by happenstance). For your use case I'd recommend pg_dump over PuppetDB export since it'll run a lot faster, but either one will get the job done. Wyatt -- 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/55DB8009.6080300%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150824222044.GA28904%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
